Findings and Open Questions: Accounting → Transactions
This register identifies discrepancies, implementation debt and unresolved product choices. Each row links to its supporting evidence in the frontmatter.
Findings
| id | severity | statement | affects | evidence | kind |
|---|---|---|---|---|---|
FND-ACC-TRX-001 | low | The source registry initially omits cited milestone, API, snapshot and debt records. Its console scope also includes list pages that redirect to the shared transaction list. The examination records these distinctions. | MOD-ACC-TRX | Structured evidence | inconsistency |
FND-ACC-TRX-002 | medium | The payments milestone describes implementation based on recommendations while the plan and milestone index still show approval outstanding. Those records do not establish Andrew’s approval of the implemented choices. | FEAT-ACC-TRX-03, FEAT-ACC-TRX-04, OQ-ACC-TRX-004 | Structured evidence | inconsistency |
FND-ACC-TRX-003 | low | The posting milestone concerns batch management. Its guidance on partially recognized invoice lines belongs to posting rather than a separate transaction outcome. | MOD-ACC-TRX | Structured evidence | inconsistency |
FND-ACC-TRX-004 | high | The realignment assigns tax determination to Commerce, but Accounting still calculates tax when staff issue invoices and exposes a tax calculation service. The determination path for staff billing without an order remains unresolved. | BR-CAP-ACC-TRX-001-13, BR-CAP-ACC-TRX-020-10, CAP-ACC-TRX-001, CAP-ACC-TRX-020, OQ-ACC-TRX-001 | Structured evidence | inconsistency |
FND-ACC-TRX-005 | medium | The realignment calls for collection holds on payment-plan receivables. The pinned implementation contains no corresponding operation or customer-summary treatment. | BR-CAP-ACC-TRX-017-08, ATS-ACC-TRX-017-07, CAP-ACC-TRX-017 | Structured evidence | debt |
FND-ACC-TRX-006 | high | A lost dispute reverses the entire payment even when the disputed amount is smaller. The proposed partial-chargeback behavior cannot be represented by the existing whole-payment reversal model. | BR-CAP-ACC-TRX-013-11, ATS-ACC-TRX-013-09, CAP-ACC-TRX-013 | Structured evidence | defect |
FND-ACC-TRX-007 | low | The payments plan recommends refund approval by business unit, but the service reads a workspace setting and the console offers no control for it. The approval scope and configuration screen need a product decision. | BR-CAP-ACC-TRX-012-13, BR-CAP-ACC-TRX-012-05 | Structured evidence | debt |
FND-ACC-TRX-008 | medium | The recorded write-off approval policy is deferred. The implementation permits a caller with creation permission to write off a balance without a second approver. | BR-CAP-ACC-TRX-004-07, ATS-ACC-TRX-004-05 | Structured evidence | debt |
FND-ACC-TRX-009 | medium | The remittance records describe competing directions: an interim receipt split into member payments and a future receipt spanning customers. The current service supports the former without a staff console workflow. | CAP-ACC-TRX-010, BR-CAP-ACC-TRX-010-09 | Structured evidence | inconsistency |
FND-ACC-TRX-010 | low | The old acceptance inventory omits the customer guard on direct credit applications. The pinned command checks customer ownership, so the inventory no longer describes that behavior. | BR-CAP-ACC-TRX-011-05 | Structured evidence | inconsistency |
FND-ACC-TRX-011 | low | The transaction suites do not independently prove the refusal to void an invoice in a posted batch. The decision cites evidence owned by batch posting. | BR-CAP-ACC-TRX-002-04, ATS-ACC-TRX-002-04 | Structured evidence | debt |
FND-ACC-TRX-012 | low | The tax record leaves the memo rounding choice awaiting Andrew’s decision, although the implementation already apportions credit tax and adds debit tax. | BR-CAP-ACC-TRX-003-08 | Structured evidence | undocumented |
FND-ACC-TRX-013 | low | The old inventory describes a paid-money choice that the memo editor no longer presents. The recorded invoice milestone removes that choice. | BR-CAP-ACC-TRX-003-05 | Structured evidence | inconsistency |
FND-ACC-TRX-014 | low | The memo edit pages require draft records although the implemented memo lifecycle creates issued records directly. Those pages do not match the supported lifecycle. | CAP-ACC-TRX-003 | Structured evidence | debt |
FND-ACC-TRX-015 | low | Invoice rendering and email delivery exist in the service, but the registered staff console pages expose no corresponding controls. | CAP-ACC-TRX-005 | Structured evidence | debt |
FND-ACC-TRX-016 | low | The gateway replaces native processor collection, but legacy Stripe settings and the public webhook remain exposed. The development webhook reports that Stripe is unconfigured. | BR-CAP-ACC-TRX-007-14, CAP-ACC-TRX-007 | Structured evidence | debt |
FND-ACC-TRX-017 | low | The development processor retains charge information within one process. Browser evidence cannot establish recovery across processes; the service integration suites provide the available recovery proof. | BR-CAP-ACC-TRX-007-06, JNY-ACC-TRX-003 | Structured evidence | debt |
FND-ACC-TRX-018 | low | The implementation stores card-fee configuration on the business unit. Earlier records also allow a merchant-account location, and the payments record’s as-built wording does not resolve Product authority. | BR-CAP-ACC-TRX-009-07 | Structured evidence | inconsistency |
FND-ACC-TRX-019 | low | The settlement command checks customer ownership for invoices and credits. The module’s tests do not explicitly prove both cross-customer refusals. | BR-CAP-ACC-TRX-009-02, ATS-ACC-TRX-009-03 | Structured evidence | debt |
FND-ACC-TRX-020 | low | Credit application checks expiry, but no worker changes the credit to an expired status. An expired credit can therefore remain open and contribute to the customer summary’s available-credit figure. | BR-CAP-ACC-TRX-011-06, CAP-ACC-TRX-017 | Structured evidence | undocumented |
FND-ACC-TRX-021 | medium | Document history is retained, but no transaction route exposes the events and the console history tabs do not load them. Several related record lists are also deferred. | BR-CAP-ACC-TRX-016-08, CAP-ACC-TRX-016 | Structured evidence | debt |
FND-ACC-TRX-022 | medium | The contact summary uses the contact’s own balances while payable-invoice discovery also includes its primary organization. These surfaces describe different sets of obligations. | BR-CAP-ACC-TRX-017-03 | Structured evidence | inconsistency |
FND-ACC-TRX-023 | low | Accounting reads customer identity, affiliation, address and tax-exemption data from CRM tables directly. Those reads depend on schemas outside an explicit customer-data contract. | CAP-ACC-TRX-017, CAP-ACC-TRX-001 | Structured evidence | debt |
FND-ACC-TRX-024 | medium | The pinned routes do not support staff reruns or backfills of aging snapshots. The cited debt record attributes the deferred routes to deployment-stack capacity. | CAP-ACC-TRX-018, BR-CAP-ACC-TRX-018-05 | Structured evidence | debt |
FND-ACC-TRX-025 | low | Twenty-seven published permission keys are not required by a registered route or dataset. Granting those keys alone does not authorize an implemented transaction operation. | CAP-ACC-TRX-016 | Structured evidence | debt |
FND-ACC-TRX-026 | medium | The refund service sends free-text reasons as processor metadata despite the gateway’s stated restriction on personal data. The permitted external reason representation needs a decision. | CAP-ACC-TRX-012, OQ-ACC-TRX-002 | Structured evidence | undocumented |
FND-ACC-TRX-027 | low | The acceptance inventory reflects older service behavior. Its statements about tax addresses, credit customer checks and memo paid-money choices conflict with the pinned implementation. | CAP-ACC-TRX-001, CAP-ACC-TRX-003, CAP-ACC-TRX-011 | Structured evidence | inconsistency |
FND-ACC-TRX-028 | low | The source inventory contains more invoice and payment journeys than browser specifications. The milestone records defer lower-priority browser coverage, leaving those journeys without that level of proof. | JNY-ACC-TRX-001, JNY-ACC-TRX-002, JNY-ACC-TRX-003, JNY-ACC-TRX-004, JNY-ACC-TRX-005 | Structured evidence | debt |
FND-ACC-TRX-029 | low | Configured receipt methods are implemented even though saved customer payment methods are deferred. Legacy method aliases remain accepted without a recorded removal date. | CAP-ACC-TRX-006, BR-CAP-ACC-TRX-006-03 | Structured evidence | inconsistency |
FND-ACC-TRX-030 | low | The service records a payment’s payer, but the console does not let staff enter or inspect it. The payments milestone defers that surface to the broader receipt model. | BR-CAP-ACC-TRX-006-09 | Structured evidence | debt |
FND-ACC-TRX-031 | medium | When the financial-facts receiver is unconfigured, Accounting acknowledges the change event after logging it. That environment has no live Commerce delivery path. | BR-CAP-ACC-TRX-020-07 | Structured evidence | debt |
FND-ACC-TRX-032 | low | The cited implementation records describe deployment-stack capacity as a constraint on additional transaction routes. New route work needs a capacity decision before delivery. | MOD-ACC-TRX, CAP-ACC-TRX-018 | Structured evidence | debt |
FND-ACC-TRX-033 | low | The console provides individual settlement and reversal records but lacks dedicated settlement, reversal and dispute lists. The milestone records defer those navigation surfaces. | CAP-ACC-TRX-009, CAP-ACC-TRX-013, CAP-ACC-TRX-014 | Structured evidence | debt |
FND-ACC-TRX-034 | low | The architecture distinguishes reversible building choices from Andrew’s decisions. Only an explicit approving record can establish confirmed intent; the payments recommendations do not supply that authority. | FEAT-ACC-TRX-01, FEAT-ACC-TRX-02, FEAT-ACC-TRX-03 | Structured evidence | undocumented |
FND-ACC-TRX-035 | high | Payment-plan recommendations and reversible build choices do not establish Product approval; the examination marks the containing artifacts proposed and removes unsupported decision origins. Andrew must settle the remaining intent questions. | MOD-ACC-TRX, OQ-ACC-TRX-004 | Structured evidence | inconsistency |
FND-ACC-TRX-036 | medium | Several compound acceptance scenarios cite tests for only part of their stated checks; a present test title establishes a binding location, not complete proof of every variant. The unasserted variants need explicit tests before approval. | ATS-ACC-TRX-001, ATS-ACC-TRX-019 | Structured evidence | debt |
FND-ACC-TRX-037 | medium | The draft omits the configured service-period requirement at issue, foreign-currency rate selection, and customer-terms locks; the examination adds these to their existing outcomes and proposes proof for the uncovered issue behavior. | CAP-ACC-TRX-001, CAP-ACC-TRX-019 | Structured evidence | undocumented |
FND-ACC-TRX-038 | low | Invoice adjustment explains supporting documents and correction paths of the invoice; it does not need an independent broad concept. The examination folds its facets into Invoice and retains the former concept as superseded. | CON-ACC-TRX-001, CON-ACC-TRX-002 | Structured evidence | inconsistency |
FND-ACC-TRX-039 | low | The draft confuses literal declarations with expanded routes and counts five view files without explaining the plural view file. Coverage is an index of evidence locations, not proof that every behavior has an acceptance assertion. | MOD-ACC-TRX | Structured evidence | inconsistency |
FND-ACC-TRX-040 | low | The draft reserves the wrong actor range and reuses product-catalogue identities for transaction administration and reading. The examination retains the added identities and points shared access roles to the existing books administrator and finance reviewer. | MOD-ACC-TRX | Structured evidence | inconsistency |
FND-ACC-TRX-041 | medium | The Adjust Invoice screen previews and submits through console calls that report the feature as not connected, so the service's amendment of an unposted issued invoice has no staff path, while the invoice editor directs staff to that screen for any change of amounts. | SCR-ACC-TRX-005, SCR-ACC-TRX-004, CAP-ACC-TRX-002, BR-CAP-ACC-TRX-002-01, OQ-ACC-TRX-005 | Structured evidence | defect |
FND-ACC-TRX-042 | low | Invoice, memo and terms commands honour a record lock that refuses updates or deletions, but no transactions operation sets or clears a lock, so the design cannot name who protects a record or how. | DOM-ACC-TRX-006, BR-CAP-ACC-TRX-002-10, BR-CAP-ACC-TRX-019-08, OQ-ACC-TRX-006 | Structured evidence | undocumented |
FND-ACC-TRX-043 | medium | Accounting runs no job reconciler for aging snapshot runs; an execution lost without its failure step stays running past its due time until the overdue alarm is noticed and someone reruns the month. | WF-ACC-TRX-015, STATE-ACC-TRX-013, CAP-ACC-TRX-018 | Structured evidence | debt |
FND-ACC-TRX-044 | low | Aging snapshot rows keep balances in two-decimal major units to match the receivable facts, departing from the decision that every Accounting amount is kept in minor units; both move together when the money library is adopted. | DOM-ACC-TRX-005, ADR-ACC-TRX-009 | Structured evidence | debt |
FND-ACC-TRX-045 | medium | The correctness suite does not prove that each invoice's receivable facts agree with the subledger's receivable control balance, nor that Commerce's order-line position view agrees with the receivable facts. | DOM-ACC-TRX-006, WF-ACC-TRX-014, ADR-ACC-TRX-002 | Structured evidence | debt |
FND-ACC-TRX-046 | low | The Platform standards repository was not readable by this design job; the persistence, queued work, job, record history and row-level security standards are cited through Accounting's own adoption and architecture records, and the verification pass should confirm each against the standard itself. | SVC-ACC-TRX-transactions, RESP-ACC | Structured evidence | undocumented |
FND-ACC-TRX-047 | low | The module asks no model a question, so the design has no inference directory, but the charter does not yet say so in the sentence the conventions require. | MOD-ACC-TRX | Structured evidence | undocumented |
FND-ACC-TRX-048 | low | The invoice adjustment concept is superseded and its facets are designed inside the invoice object, so its matching Domain Object number is deliberately not allocated. | CON-ACC-TRX-002, DOM-ACC-TRX-001 | Structured evidence | inconsistency |
FND-ACC-TRX-049 | low | The record action routes are admitted with the record kind's read authority and the mutation authority is evaluated inside the command, so the gateway's route registry understates what those routes can change. | SVC-ACC-TRX-transactions, BR-CAP-ACC-TRX-016-02 | Structured evidence | undocumented |
FND-ACC-TRX-050 | low | The architecture chapters describe invoice amendment, batch reassignment and reopened document details as branch work, and the payment's frozen method behaviour as designed only, although the pinned service implements them; design evidence relies on the code and tests where they disagree. | DOM-ACC-TRX-001, DOM-ACC-TRX-003, STATE-ACC-TRX-001 | Structured evidence | inconsistency |
FND-ACC-TRX-051 | medium | A settlement converts the pro formas it names before its payment is tendered, and its failure path does not convert them back, so a declined card leaves a quotation as a real invoice with a receivable, unlike a direct tender, which converts only when money lands. | WF-ACC-TRX-008, STATE-ACC-TRX-008, BR-CAP-ACC-TRX-008-08, CAP-ACC-TRX-009 | Structured evidence | defect |
FND-ACC-TRX-066 | medium | Processor refund requests transmit the saved free-text reason without a local minimization or personal-information exclusion step. A person can put unnecessary personal information in that field, so the processor handoff lacks an established purpose-limited representation. | TC-DAT-002, TC-PRV-002, CAP-ACC-TRX-012, WF-ACC-TRX-009, SVC-ACC-TRX-transactions, OQ-ACC-TRX-002 | Structured control evidence | control-gap |
FND-ACC-TRX-067 | medium | Write-off creation has no independent approval step despite the recorded threshold-based approval requirement. Creation permission currently admits the financial change without retaining the required second person’s approval. | TC-AI-005, TC-PI-005, CAP-ACC-TRX-004, WF-ACC-TRX-004, SVC-ACC-TRX-transactions | Structured control evidence | control-gap |
| FND-ACC-TRX-052 | high | The supplied planning corpus remains draft with proposed intent. Its presence does not establish the approval described by the examination brief; Andrew must record the approval before design preparation treats it as settled. | MOD-ACC-TRX | Structured evidence | inconsistency | | FND-ACC-TRX-053 | low | The named design brief is absent from both this checkout and the fetched default-branch tree. The supplied job instructions define this examination, but the originating brief cannot be checked. | MOD-ACC-TRX | Structured evidence | undocumented | | FND-ACC-TRX-054 | medium | A no-op detail edit records no history event, releasing paid money can record events on several payments, and invoice email uses communication deduplication rather than the shared financial retry ledger. The corrected design limits these guarantees to the implemented paths. | DOM-ACC-TRX-006, SVC-ACC-TRX-transactions | Structured evidence | inconsistency | | FND-ACC-TRX-055 | high | A charge lookup by provider reference can fail definitively after its grace period. Lookup by key follows the scheduled human-review path. The planning language that no empty lookup establishes failure needs qualification or an implementation change. | STATE-ACC-TRX-005, WF-ACC-TRX-007, CAP-ACC-TRX-007 | Structured evidence | inconsistency | | FND-ACC-TRX-056 | high | Direct credit application checks expiry and order-type restrictions; settlement selection and application do not. An open credit can therefore be spent through settlement even when the direct command would reject it. Product intent is already stated in planning; the service paths need to agree. | DOM-ACC-TRX-004, WF-ACC-TRX-008, CAP-ACC-TRX-011 | Structured evidence | defect | | FND-ACC-TRX-057 | medium | Memo and write-off record pages do not render detail-edit controls; several record pages use the default full layout and three have no page-layout wrapper. Invoice creation and manual credit issue submit without a confirmation dialog, while adjustment and reversal use inline review steps. The contracts now describe those controls. | SCR-ACC-TRX-002, SCR-ACC-TRX-005, SCR-ACC-TRX-008, SCR-ACC-TRX-013, SCR-ACC-TRX-016 | Structured evidence | inconsistency | | FND-ACC-TRX-058 | low | Transaction records have no custom-field storage, consistent with the recorded opt-in decision. The module registration does not explicitly declare its custom-field capability, so conformance to the current registration contract cannot be established from this repository alone. | SVC-ACC-TRX-transactions | Structured evidence | undocumented | | FND-ACC-TRX-059 | medium | The database freeze is keyed to receivable recognition. A pro forma can be numbered and taxed at issue without that recognition, so its issue alone does not activate the same freeze as a real invoice. Planning language about frozen issued documents needs this distinction. | DOM-ACC-TRX-001, WF-ACC-TRX-001, CAP-ACC-TRX-001 | Structured evidence | inconsistency | | FND-ACC-TRX-060 | medium | The pinned billing service function includes six installment-schedule operations alongside invoice and customer-terms operations. Planned Billing ownership is a target boundary; it does not describe all operations currently served by the Accounting function. | SVC-ACC-TRX-transactions, RESP-ACC | Structured evidence | inconsistency | | FND-ACC-TRX-061 | medium | The cited snapshot test proves rollback of a single-transaction capture. The workflow also permits keyset chunks, but that test does not establish removal of previously committed chunks. The design leaves this recovery guarantee unknown until the shared snapshot implementation and a chunk-failure test are examined. | WF-ACC-TRX-015, DOM-ACC-TRX-005 | Structured evidence | debt |
| FND-ACC-TRX-062 | medium | The purge checks deletion state before each batch, but the available module evidence does not establish exclusion of all concurrent writes by other services. That guarantee depends on Platform lifecycle admission and remains unknown here. | WF-ACC-TRX-018 | Structured evidence | undocumented |
| FND-ACC-TRX-063 | medium | The settlement read route requires settlement read permission plus either payment read or credit-application read permission. The service draft omitted the additional requirement; the contract now records the exact permission expression. | SVC-ACC-TRX-transactions, SCR-ACC-TRX-020 | Structured evidence | inconsistency |
| FND-ACC-TRX-064 | medium | Several design rows used a single test title for compound eligibility, outcome and recovery claims, including allowed outcomes sourced only to refusal tests. The examination retains those test citations but adds implementation sources and labels compound rows observed rather than claiming the selected assertion proves every part. Additional tests remain necessary before treating all variants as proved. | MOD-ACC-TRX | Structured evidence | debt |
| FND-ACC-TRX-065 | medium | Credit availability subtracts reservations, but the status trigger subtracts only applications and refunds. Fully reserved credit can remain open with zero available balance, so the draft’s claim that status follows available balance was incorrect. The corrected object and state model distinguish availability from status; planning needs the same distinction or a service change. | DOM-ACC-TRX-004, STATE-ACC-TRX-011, CAP-ACC-TRX-011 | Structured evidence | inconsistency |
| FND-ACC-TRX-066 | medium | Issue customer bills and numbered quotes has transition, permission, edge coverage awaiting additional scenarios or complete mappings. The structured registers identify unproved state paths, permission combinations, domain invariants and executable scenarios; the combined interaction chain remains proposed. | CAP-ACC-TRX-001, ATS-ACC-TRX-001, ATS-ACC-TRX-001-17 | Structured evidence | coverage-gap | | FND-ACC-TRX-067 | medium | Correct issued bills before posting has transition, validation, edge, concurrency coverage awaiting additional scenarios or complete mappings. The structured registers identify unproved state paths, permission combinations, domain invariants and executable scenarios; the combined interaction chain remains proposed. | CAP-ACC-TRX-002, ATS-ACC-TRX-002, ATS-ACC-TRX-002-11 | Structured evidence | coverage-gap | | FND-ACC-TRX-068 | medium | Adjust billed value with memos has transition, concurrency, invariant coverage awaiting additional scenarios or complete mappings. The structured registers identify unproved state paths, permission combinations, domain invariants and executable scenarios; the combined interaction chain remains proposed. | CAP-ACC-TRX-003, ATS-ACC-TRX-003, ATS-ACC-TRX-003-12 | Structured evidence | coverage-gap | | FND-ACC-TRX-069 | medium | Abandon and restore uncollectable debt has transition, edge, failure, boundary, concurrency, invariant coverage awaiting additional scenarios or complete mappings. The structured registers identify unproved state paths, permission combinations, domain invariants and executable scenarios; the combined interaction chain remains proposed. | CAP-ACC-TRX-004, ATS-ACC-TRX-004, ATS-ACC-TRX-004-07 | Structured evidence | coverage-gap | | FND-ACC-TRX-070 | medium | Prepare and deliver invoice documents has concurrency coverage awaiting additional scenarios or complete mappings. The structured registers identify unproved state paths, permission combinations, domain invariants and executable scenarios; the combined interaction chain remains proposed. | CAP-ACC-TRX-005, ATS-ACC-TRX-005, ATS-ACC-TRX-005-07 | Structured evidence | coverage-gap | | FND-ACC-TRX-071 | medium | Record receipts collected outside Rhythm has transition, permission, concurrency coverage awaiting additional scenarios or complete mappings. The structured registers identify unproved state paths, permission combinations, domain invariants and executable scenarios; the combined interaction chain remains proposed. | CAP-ACC-TRX-006, ATS-ACC-TRX-006, ATS-ACC-TRX-006-10 | Structured evidence | coverage-gap | | FND-ACC-TRX-072 | medium | Collect processor payments and resolve uncertainty has transition, edge coverage awaiting additional scenarios or complete mappings. The structured registers identify unproved state paths, permission combinations, domain invariants and executable scenarios; the combined interaction chain remains proposed. | CAP-ACC-TRX-007, ATS-ACC-TRX-007, ATS-ACC-TRX-007-12 | Structured evidence | coverage-gap | | FND-ACC-TRX-073 | medium | Allocate and relocate received money has transition, permission, edge, failure coverage awaiting additional scenarios or complete mappings. The structured registers identify unproved state paths, permission combinations, domain invariants and executable scenarios; the combined interaction chain remains proposed. | CAP-ACC-TRX-008, ATS-ACC-TRX-008, ATS-ACC-TRX-008-09 | Structured evidence | coverage-gap | | FND-ACC-TRX-074 | medium | Complete invoice settlement with credit and money has transition, concurrency coverage awaiting additional scenarios or complete mappings. The structured registers identify unproved state paths, permission combinations, domain invariants and executable scenarios; the combined interaction chain remains proposed. | CAP-ACC-TRX-009, ATS-ACC-TRX-009, ATS-ACC-TRX-009-12 | Structured evidence | coverage-gap | | FND-ACC-TRX-075 | medium | Record a remitter’s combined customer receipt has rule, transition, edge, concurrency, invariant coverage awaiting additional scenarios or complete mappings. The structured registers identify unproved state paths, permission combinations, domain invariants and executable scenarios; the combined interaction chain remains proposed. | CAP-ACC-TRX-010, ATS-ACC-TRX-010, ATS-ACC-TRX-010-07 | Structured evidence | coverage-gap | | FND-ACC-TRX-076 | medium | Provide and spend customer credit has rule, transition, edge, failure, invariant coverage awaiting additional scenarios or complete mappings. The structured registers identify unproved state paths, permission combinations, domain invariants and executable scenarios; the combined interaction chain remains proposed. | CAP-ACC-TRX-011, ATS-ACC-TRX-011, ATS-ACC-TRX-011-10 | Structured evidence | coverage-gap | | FND-ACC-TRX-077 | medium | Return customer money with accountable refunds has transition, invariant coverage awaiting additional scenarios or complete mappings. The structured registers identify unproved state paths, permission combinations, domain invariants and executable scenarios; the combined interaction chain remains proposed. | CAP-ACC-TRX-012, ATS-ACC-TRX-012, ATS-ACC-TRX-012-12 | Structured evidence | coverage-gap | | FND-ACC-TRX-078 | medium | Record receipts that were voided or returned has transition, boundary, concurrency, invariant coverage awaiting additional scenarios or complete mappings. The structured registers identify unproved state paths, permission combinations, domain invariants and executable scenarios; the combined interaction chain remains proposed. | CAP-ACC-TRX-013, ATS-ACC-TRX-013, ATS-ACC-TRX-013-10 | Structured evidence | coverage-gap | | FND-ACC-TRX-079 | medium | Unwind billed purchases and their collected value has transition, edge, concurrency, invariant coverage awaiting additional scenarios or complete mappings. The structured registers identify unproved state paths, permission combinations, domain invariants and executable scenarios; the combined interaction chain remains proposed. | CAP-ACC-TRX-014, ATS-ACC-TRX-014, ATS-ACC-TRX-014-09 | Structured evidence | coverage-gap | | FND-ACC-TRX-080 | medium | Keep transaction batches and details correct has failure, boundary, concurrency coverage awaiting additional scenarios or complete mappings. The structured registers identify unproved state paths, permission combinations, domain invariants and executable scenarios; the combined interaction chain remains proposed. | CAP-ACC-TRX-015, ATS-ACC-TRX-015, ATS-ACC-TRX-015-09 | Structured evidence | coverage-gap | | FND-ACC-TRX-081 | medium | Find money records and understand available work has edge, failure, concurrency coverage awaiting additional scenarios or complete mappings. The structured registers identify unproved state paths, permission combinations, domain invariants and executable scenarios; the combined interaction chain remains proposed. | CAP-ACC-TRX-016, ATS-ACC-TRX-016, ATS-ACC-TRX-016-08 | Structured evidence | coverage-gap | | FND-ACC-TRX-082 | medium | Explain a customer’s current financial position has edge, failure, concurrency coverage awaiting additional scenarios or complete mappings. The structured registers identify unproved state paths, permission combinations, domain invariants and executable scenarios; the combined interaction chain remains proposed. | CAP-ACC-TRX-017, ATS-ACC-TRX-017, ATS-ACC-TRX-017-08 | Structured evidence | coverage-gap | | FND-ACC-TRX-083 | medium | Preserve and read monthly receivables aging has rule, transition, validation coverage awaiting additional scenarios or complete mappings. The structured registers identify unproved state paths, permission combinations, domain invariants and executable scenarios; the combined interaction chain remains proposed. | CAP-ACC-TRX-018, ATS-ACC-TRX-018, ATS-ACC-TRX-018-08 | Structured evidence | coverage-gap | | FND-ACC-TRX-084 | medium | Maintain customer-specific collection choices has rule, edge coverage awaiting additional scenarios or complete mappings. The structured registers identify unproved state paths, permission combinations, domain invariants and executable scenarios; the combined interaction chain remains proposed. | CAP-ACC-TRX-019, ATS-ACC-TRX-019, ATS-ACC-TRX-019-08 | Structured evidence | coverage-gap | | FND-ACC-TRX-085 | medium | Coordinate financial commands across applications has rule, transition, validation coverage awaiting additional scenarios or complete mappings. The structured registers identify unproved state paths, permission combinations, domain invariants and executable scenarios; the combined interaction chain remains proposed. | CAP-ACC-TRX-020, ATS-ACC-TRX-020, ATS-ACC-TRX-020-09 | Structured evidence | coverage-gap | | FND-ACC-TRX-086 | medium | Several retained scenarios combine inputs and outcomes from multiple test files. The executable register names each contributing assertion, but those bindings do not establish that any single suite executes every branch of the combined scenario. | ATS-ACC-TRX-001, ATS-ACC-TRX-002, ATS-ACC-TRX-003, ATS-ACC-TRX-004, ATS-ACC-TRX-005, ATS-ACC-TRX-006, ATS-ACC-TRX-007, ATS-ACC-TRX-008, ATS-ACC-TRX-009, ATS-ACC-TRX-010, ATS-ACC-TRX-011, ATS-ACC-TRX-012, ATS-ACC-TRX-013, ATS-ACC-TRX-014, ATS-ACC-TRX-015, ATS-ACC-TRX-016, ATS-ACC-TRX-017, ATS-ACC-TRX-018, ATS-ACC-TRX-019, ATS-ACC-TRX-020 | Structured evidence | coverage-gap | | FND-ACC-TRX-087 | medium | No complete executable binding is established for the feature acceptance chains. Their dependent capability scenarios supply component evidence, while the feature chains stay proposed until a full binding is verified. | FAS-ACC-TRX-01, FAS-ACC-TRX-02, FAS-ACC-TRX-03, FAS-ACC-TRX-04, FAS-ACC-TRX-05, FAS-ACC-TRX-06 | Structured evidence | coverage-gap | | FND-ACC-TRX-088 | high | The proposed tests must distinguish key lookup from reference lookup, reservation-adjusted availability from credit status, and direct credit eligibility from settlement eligibility. Declined settlement can retain converted quotes; delivery deduplication also does not prevent repeated history entries. Existing findings remain the home for these implementation departures. | ATS-ACC-TRX-007, ATS-ACC-TRX-009, ATS-ACC-TRX-011, ATS-ACC-TRX-005 | Structured evidence | inconsistency | | FND-ACC-TRX-089 | medium | Registered suites without scenario bindings remain implementation evidence whose specific assertions are not mapped to this capability corpus. Their presence does not close a specification or execution gap, and mock browser suites do not establish service financial integrity. | TST-ACC-TRX-008, TST-ACC-TRX-009, TST-ACC-TRX-018, TST-ACC-TRX-019, TST-ACC-TRX-021, TST-ACC-TRX-023, TST-ACC-TRX-024, TST-ACC-TRX-025, TST-ACC-TRX-026, TST-ACC-TRX-027, TST-ACC-TRX-040, TST-ACC-TRX-044, TST-ACC-TRX-045, TST-ACC-TRX-053, TST-ACC-TRX-057, TST-ACC-TRX-064, TST-ACC-TRX-067, TST-ACC-TRX-068, TST-ACC-TRX-069, TST-ACC-TRX-071, TST-ACC-TRX-074, TST-ACC-TRX-083, TST-ACC-TRX-084, TST-ACC-TRX-085, TST-ACC-TRX-086, TST-ACC-TRX-087, TST-ACC-TRX-089, TST-ACC-TRX-090, TST-ACC-TRX-092, TST-ACC-TRX-093, TST-ACC-TRX-094, TST-ACC-TRX-095, TST-ACC-TRX-096, TST-ACC-TRX-097, TST-ACC-TRX-098, TST-ACC-TRX-099, TST-ACC-TRX-100, TST-ACC-TRX-101, TST-ACC-TRX-102, TST-ACC-TRX-103, TST-ACC-TRX-104, TST-ACC-TRX-106, TST-ACC-TRX-118, TST-ACC-TRX-123, TST-ACC-TRX-128, TST-ACC-TRX-129, TST-ACC-TRX-130, TST-ACC-TRX-133, TST-ACC-TRX-134, TST-ACC-TRX-135, TST-ACC-TRX-136, TST-ACC-TRX-137, TST-ACC-TRX-138, TST-ACC-TRX-139, TST-ACC-TRX-140, TST-ACC-TRX-141, TST-ACC-TRX-142, TST-ACC-TRX-144, TST-ACC-TRX-145, TST-ACC-TRX-146, TST-ACC-TRX-147, TST-ACC-TRX-148, TST-ACC-TRX-149, TST-ACC-TRX-150, TST-ACC-TRX-151, TST-ACC-TRX-152, TST-ACC-TRX-153, TST-ACC-TRX-154, TST-ACC-TRX-155, TST-ACC-TRX-156, TST-ACC-TRX-157, TST-ACC-TRX-158, TST-ACC-TRX-159, TST-ACC-TRX-160, TST-ACC-TRX-161, TST-ACC-TRX-162, TST-ACC-TRX-163, TST-ACC-TRX-164, TST-ACC-TRX-165, TST-ACC-TRX-166, TST-ACC-TRX-167, TST-ACC-TRX-168, TST-ACC-TRX-169, TST-ACC-TRX-170, TST-ACC-TRX-171, TST-ACC-TRX-172, TST-ACC-TRX-173, TST-ACC-TRX-174, TST-ACC-TRX-175, TST-ACC-TRX-176, TST-ACC-TRX-177, TST-ACC-TRX-178, TST-ACC-TRX-179, TST-ACC-TRX-180, TST-ACC-TRX-181, TST-ACC-TRX-182, TST-ACC-TRX-183, TST-ACC-TRX-184, TST-ACC-TRX-185, TST-ACC-TRX-186, TST-ACC-TRX-187, TST-ACC-TRX-188, TST-ACC-TRX-189, TST-ACC-TRX-190, TST-ACC-TRX-191, TST-ACC-TRX-192, TST-ACC-TRX-193, TST-ACC-TRX-194, TST-ACC-TRX-195, TST-ACC-TRX-196, TST-ACC-TRX-197, TST-ACC-TRX-198, TST-ACC-TRX-199, TST-ACC-TRX-200, TST-ACC-TRX-201, TST-ACC-TRX-202, TST-ACC-TRX-203, TST-ACC-TRX-204, TST-ACC-TRX-205, TST-ACC-TRX-207, TST-ACC-TRX-208, TST-ACC-TRX-210, TST-ACC-TRX-212, TST-ACC-TRX-213, TST-ACC-TRX-214, TST-ACC-TRX-215, TST-ACC-TRX-216, TST-ACC-TRX-217, TST-ACC-TRX-218, TST-ACC-TRX-219, TST-ACC-TRX-228, TST-ACC-TRX-233, TST-ACC-TRX-238, TST-ACC-TRX-255, TST-ACC-TRX-259, TST-ACC-TRX-262, TST-ACC-TRX-265, TST-ACC-TRX-266, TST-ACC-TRX-267, TST-ACC-TRX-268, TST-ACC-TRX-269, TST-ACC-TRX-270, TST-ACC-TRX-272, TST-ACC-TRX-273, TST-ACC-TRX-274, TST-ACC-TRX-275, TST-ACC-TRX-276, TST-ACC-TRX-277, TST-ACC-TRX-278, TST-ACC-TRX-279, TST-ACC-TRX-280, TST-ACC-TRX-281, TST-ACC-TRX-282, TST-ACC-TRX-283, TST-ACC-TRX-284, TST-ACC-TRX-285, TST-ACC-TRX-286, TST-ACC-TRX-287, TST-ACC-TRX-288, TST-ACC-TRX-289, TST-ACC-TRX-290, TST-ACC-TRX-291, TST-ACC-TRX-292, TST-ACC-TRX-293, TST-ACC-TRX-294, TST-ACC-TRX-295, TST-ACC-TRX-296, TST-ACC-TRX-297, TST-ACC-TRX-298, TST-ACC-TRX-299, TST-ACC-TRX-300, TST-ACC-TRX-301, TST-ACC-TRX-302, TST-ACC-TRX-303, TST-ACC-TRX-304, TST-ACC-TRX-305, TST-ACC-TRX-306, TST-ACC-TRX-307, TST-ACC-TRX-308, TST-ACC-TRX-309, TST-ACC-TRX-310, TST-ACC-TRX-311, TST-ACC-TRX-312, TST-ACC-TRX-313, TST-ACC-TRX-314, TST-ACC-TRX-315, TST-ACC-TRX-316, TST-ACC-TRX-317, TST-ACC-TRX-318, TST-ACC-TRX-319, TST-ACC-TRX-320, TST-ACC-TRX-321, TST-ACC-TRX-322, TST-ACC-TRX-323, TST-ACC-TRX-324, TST-ACC-TRX-325, TST-ACC-TRX-326, TST-ACC-TRX-327, TST-ACC-TRX-328, TST-ACC-TRX-329, TST-ACC-TRX-330, TST-ACC-TRX-331, TST-ACC-TRX-332, TST-ACC-TRX-333, TST-ACC-TRX-334, TST-ACC-TRX-335, TST-ACC-TRX-336, TST-ACC-TRX-337, TST-ACC-TRX-338, TST-ACC-TRX-339, TST-ACC-TRX-340, TST-ACC-TRX-341, TST-ACC-TRX-342, TST-ACC-TRX-343, TST-ACC-TRX-344, TST-ACC-TRX-345, TST-ACC-TRX-346, TST-ACC-TRX-347, TST-ACC-TRX-348, TST-ACC-TRX-349, TST-ACC-TRX-350, TST-ACC-TRX-351, TST-ACC-TRX-352, TST-ACC-TRX-353, TST-ACC-TRX-354, TST-ACC-TRX-355, TST-ACC-TRX-356, TST-ACC-TRX-357, TST-ACC-TRX-358 | Structured evidence | coverage-gap |
| FND-ACC-TRX-090 | medium | The required testing report name is outside the checker’s accepted examination-report names. The checked checkpoint retains a Partial examination report; producing the requested name requires permission for a narrowly scoped checker compatibility change. | MOD-ACC-TRX | Structured evidence | debt |
Open Questions
| id | question | why_it_matters | options | recommendation | affects |
|---|---|---|---|---|---|
OQ-ACC-TRX-001 | How should staff billing obtain tax when no Commerce order exists? | The current staff workflow depends on Accounting tax calculation while the realignment assigns determination to Commerce. | A: Request a Commerce determination at issue. B: Create a Commerce order for staff billing. C: Retain a separate Accounting calculation for staff billing. | The product should request Commerce’s tax determination and retain the result on the billing record. | BR-CAP-ACC-TRX-001-13, BR-CAP-ACC-TRX-020-10, CAP-ACC-TRX-001, CAP-ACC-TRX-020, FND-ACC-TRX-004 |
OQ-ACC-TRX-002 | What refund reason may Accounting send outside Rhythm? | Free-text reasons can contain personal information that the gateway contract excludes. | A: Send free text with a warning. B: Send a controlled reason code and retain the text internally. C: Omit the processor reason. | The product should send a controlled reason code and retain staff notes within Rhythm. | CAP-ACC-TRX-012, FND-ACC-TRX-026 |
OQ-ACC-TRX-003 | How should Accounting represent a chargeback smaller than the original receipt? | Whole-payment reversal currently reopens obligations beyond the disputed amount. | A: Reverse only the disputed amount, releasing newest applications first. B: Reverse the payment and create a replacement for the undisputed amount. C: Retain whole-payment reversal. | The product should represent partial chargebacks directly and define how they release applications. | BR-CAP-ACC-TRX-013-11, ATS-ACC-TRX-013-09, CAP-ACC-TRX-013, FND-ACC-TRX-006 |
OQ-ACC-TRX-004 | Which implemented payment recommendations does Andrew approve? | The plan’s pending approval does not establish authority for the implemented payment choices. | A: Approve the recommendations together. B: Review each recommendation and its implementation. C: Approve the remainder while separating the chargeback decision. | The product should record Andrew’s decision on each recommendation, including the departures identified by this examination. | FEAT-ACC-TRX-03, FEAT-ACC-TRX-04, FND-ACC-TRX-002 |
OQ-ACC-TRX-005 | How should the console deliver the already approved unposted invoice amendment? | Andrew permitted revision-based amendment and the service implements it, but the console adapters remain disconnected. Delivery needs a choice without re-opening the permission decision. | A: Connect the existing adjustment surface. B: Replace it with a connected amendment surface. C: Keep amendment and memos together with posting-aware eligibility. | The product should connect the approved amendment path and retain memos for correction after posting. | SCR-ACC-TRX-005, CAP-ACC-TRX-002, FND-ACC-TRX-041 |
OQ-ACC-TRX-006 | Who may lock and unlock a transaction document, and through which operation? | Commands honour locks that nothing in this module can set, so protection depends on writes outside any declared operation. | A: Add lock and unlock operations with their own authority and audit. B: Let only Rhythm staff set locks through Platform tooling. C: Remove locks from transaction documents. | The product should add explicit lock and unlock operations with their own authority and history, matching CRM's record protection. | DOM-ACC-TRX-006, FND-ACC-TRX-042 |