---
generated_by: tools/trace-sync.mjs
module: MOD-ACC-TRX
generated_at: 2026-10-23
---

# Transactions: Traceability

Generated from the test side of the corpus (CONVENTIONS §15). Do not edit: run `node tools/trace-sync.mjs accounting/transactions`.

## Rules and Their Proof

| Capability | Rule | Must prove | Proving scenarios | Executable suites (latest result) |
|---|---|---|---|---|
| CAP-ACC-TRX-001 | `BR-CAP-ACC-TRX-001-01` A draft replacement requires the version last read and replaces the document as a whole; a stale version leaves it unchanged. | yes | ATS-ACC-TRX-001-01, ATS-ACC-TRX-001-17 | TST-ACC-TRX-065 (not-run) |
| CAP-ACC-TRX-001 | `BR-CAP-ACC-TRX-001-02` Changing a draft’s business unit or currency requires creating another draft. | yes | ATS-ACC-TRX-001-02 | TST-ACC-TRX-065 (not-run) |
| CAP-ACC-TRX-001 | `BR-CAP-ACC-TRX-001-03` Invoice lines require active sellable products from the invoice’s unit, prices in its currency, and a currency supported by that unit; invalid input creates no draft. | yes | ATS-ACC-TRX-001-03 | TST-ACC-TRX-046 (not-run), TST-ACC-TRX-222 (not-run) |
| CAP-ACC-TRX-001 | `BR-CAP-ACC-TRX-001-04` Amounts use whole currency minor units, line extensions round once half away from zero, totals sum those rounded lines, and discounts cannot exceed extensions. | yes | ATS-ACC-TRX-001-04 | TST-ACC-TRX-010 (not-run), TST-ACC-TRX-046 (not-run), TST-ACC-TRX-061 (not-run) |
| CAP-ACC-TRX-001 | `BR-CAP-ACC-TRX-001-05` An explicit due date takes precedence over requested or customer-default terms, otherwise the invoice date applies; the due date cannot precede the invoice date. | yes | ATS-ACC-TRX-001-05, ATS-ACC-TRX-019-08 | TST-ACC-TRX-046 (not-run), TST-ACC-TRX-047 (not-run) |
| CAP-ACC-TRX-001 | `BR-CAP-ACC-TRX-001-06` A supplied service period includes both dates, with its end on or after its start. | yes | ATS-ACC-TRX-001-06 | TST-ACC-TRX-062 (not-run) |
| CAP-ACC-TRX-001 | `BR-CAP-ACC-TRX-001-07` Issue requires at least one line, an open fiscal period and an eligible batch selected explicitly or by assignment rules; refusal leaves the draft unnumbered. | yes | ATS-ACC-TRX-001-07, ATS-ACC-TRX-001-17, ATS-ACC-TRX-020-09 | TST-ACC-TRX-056 (not-run) |
| CAP-ACC-TRX-001 | `BR-CAP-ACC-TRX-001-08` Invoice numbering begins at one million within the workspace and permits gaps while preventing duplicates. | yes | ATS-ACC-TRX-001-08, ATS-ACC-TRX-001-18 | TST-ACC-TRX-052 (not-run), TST-ACC-TRX-056 (not-run) |
| CAP-ACC-TRX-001 | `BR-CAP-ACC-TRX-001-09` General ledger accounts are selected and frozen at posting, so missing account setup does not prevent issue. | yes | ATS-ACC-TRX-001-09 | TST-ACC-TRX-056 (not-run), TST-ACC-TRX-231 (not-run) |
| CAP-ACC-TRX-001 | `BR-CAP-ACC-TRX-001-10` Ordinary writes cannot change issued commercial content or delete an issued real invoice; the supported amendment path remains available for eligible unposted lines. | yes | ATS-ACC-TRX-001-10, ATS-ACC-TRX-001-17 | TST-ACC-TRX-022 (not-run) |
| CAP-ACC-TRX-001 | `BR-CAP-ACC-TRX-001-11` Invoice status follows its monetary position, with an outstanding amount keeping it open and a zero-total invoice becoming paid immediately. | yes | ATS-ACC-TRX-001-11 | TST-ACC-TRX-056 (not-run), TST-ACC-TRX-063 (not-run), TST-ACC-TRX-236 (not-run) |
| CAP-ACC-TRX-001 | `BR-CAP-ACC-TRX-001-12` A pro forma receives an invoice number without a batch or receivable, converts once while retaining that number, and can be deleted only before conversion; drafts can also be deleted. | yes | ATS-ACC-TRX-001-12, ATS-ACC-TRX-001-17, ATS-ACC-TRX-020-09 | TST-ACC-TRX-048 (not-run), TST-ACC-TRX-056 (not-run), TST-ACC-TRX-220 (not-run) |
| CAP-ACC-TRX-001 | `BR-CAP-ACC-TRX-001-13` Issue freezes tax calculated from the line’s class and applicable billing or shipping address, exempts eligible organizations, and refuses taxable staff invoices lacking an address. | yes | ATS-ACC-TRX-001-13 | TST-ACC-TRX-054 (not-run), TST-ACC-TRX-055 (not-run), TST-ACC-TRX-232 (not-run) |
| CAP-ACC-TRX-001 | `BR-CAP-ACC-TRX-001-14` Creation selects the requested card-fee policy or the unit default, and issue freezes the choice of none, required or optional. | yes | ATS-ACC-TRX-001-14 | TST-ACC-TRX-002 (not-run) |
| CAP-ACC-TRX-001 | `BR-CAP-ACC-TRX-001-15` With mandatory service periods enabled, an automatically deferred line lacking its period prevents issue before a number is allocated. | yes | ATS-ACC-TRX-001-15 |  |
| CAP-ACC-TRX-001 | `BR-CAP-ACC-TRX-001-16` Issue preserves a stored exchange rate, otherwise selects the inverse dated unit rate, and keeps no rate when neither is available. | yes | ATS-ACC-TRX-001-16 |  |
| CAP-ACC-TRX-002 | `BR-CAP-ACC-TRX-002-01` Staff can amend a live issued invoice before posting by adding lines, changing unapplied lines and correcting its commercial details. | yes | ATS-ACC-TRX-001-17, ATS-ACC-TRX-002-01, ATS-ACC-TRX-002-11, ATS-ACC-TRX-005-07 | TST-ACC-TRX-010 (not-run), TST-ACC-TRX-039 (not-run), TST-ACC-TRX-224 (not-run) |
| CAP-ACC-TRX-002 | `BR-CAP-ACC-TRX-002-02` A line carrying a payment, credit, memo or write-off cannot be removed or repriced through an amendment. | yes | ATS-ACC-TRX-002-02 | TST-ACC-TRX-039 (not-run) |
| CAP-ACC-TRX-002 | `BR-CAP-ACC-TRX-002-03` Amendment advances the revision, records the receivable difference and change event, and recalculates tax only on added or repriced lines; rendered revisions appear from the second onward. | yes | ATS-ACC-TRX-001-17, ATS-ACC-TRX-002-01, ATS-ACC-TRX-005-07 | TST-ACC-TRX-010 (not-run), TST-ACC-TRX-039 (not-run), TST-ACC-TRX-224 (not-run) |
| CAP-ACC-TRX-002 | `BR-CAP-ACC-TRX-002-04` A posting, posted or downloaded batch prevents invoice amendment, date changes and voiding, leaving a correcting memo as the remedy. | yes | ATS-ACC-TRX-002-03, ATS-ACC-TRX-002-04, ATS-ACC-TRX-002-11, ATS-ACC-TRX-015-09 | TST-ACC-TRX-039 (not-run) |
| CAP-ACC-TRX-002 | `BR-CAP-ACC-TRX-002-05` Changing terms derives a due date from the invoice date unless the request supplies one, and no permitted due date precedes the invoice date. | yes | ATS-ACC-TRX-002-05 | TST-ACC-TRX-049 (not-run) |
| CAP-ACC-TRX-002 | `BR-CAP-ACC-TRX-002-06` Before voiding, descriptive details and terms can change together, with any invalid part rejecting the whole request. | yes | ATS-ACC-TRX-002-06 | TST-ACC-TRX-049 (not-run), TST-ACC-TRX-050 (not-run) |
| CAP-ACC-TRX-002 | `BR-CAP-ACC-TRX-002-07` An issued invoice can move its dates into an open period before posting, with correcting receivable entries; the console provides no date-change control. | yes | ATS-ACC-TRX-002-07 | TST-ACC-TRX-010 (not-run), TST-ACC-TRX-039 (not-run) |
| CAP-ACC-TRX-002 | `BR-CAP-ACC-TRX-002-08` Voiding requires a reason and an invoice with no payment, credit, memo or write-off applied, whether draft or issued. | yes | ATS-ACC-TRX-002-08 | TST-ACC-TRX-066 (not-run), TST-ACC-TRX-221 (not-run) |
| CAP-ACC-TRX-002 | `BR-CAP-ACC-TRX-002-09` An issued invoice’s void preserves its commercial amounts, voids its lines and offsets the remaining receivable on today’s date; the void cannot be undone. | yes | ATS-ACC-TRX-002-08 | TST-ACC-TRX-066 (not-run), TST-ACC-TRX-221 (not-run) |
| CAP-ACC-TRX-002 | `BR-CAP-ACC-TRX-002-10` An update lock prevents invoice mutations, while a deletion lock prevents removal alone. | yes | ATS-ACC-TRX-002-09 | TST-ACC-TRX-058 (not-run) |
| CAP-ACC-TRX-002 | `BR-CAP-ACC-TRX-002-11` Issue and amendment require adjust authority, details and terms require update authority, and voiding requires the separate void authority. | yes | ATS-ACC-TRX-002-10 | TST-ACC-TRX-010 (not-run), TST-ACC-TRX-234 (not-run) |
| CAP-ACC-TRX-003 | `BR-CAP-ACC-TRX-003-01` Memos target an issued real invoice and its own lines; drafts, void invoices and unconverted quotes are ineligible. | yes | ATS-ACC-TRX-003-01 | TST-ACC-TRX-034 (not-run), TST-ACC-TRX-220 (not-run), TST-ACC-TRX-237 (not-run) |
| CAP-ACC-TRX-003 | `BR-CAP-ACC-TRX-003-02` Saving a memo issues it immediately using its kind’s numbering sequence beginning at one million; no draft stage is available. | yes | ATS-ACC-TRX-002-11, ATS-ACC-TRX-003-02 | TST-ACC-TRX-034 (not-run), TST-ACC-TRX-035 (not-run), TST-ACC-TRX-225 (not-run) |
| CAP-ACC-TRX-003 | `BR-CAP-ACC-TRX-003-03` Credit cannot exceed the line’s outstanding value plus releasable paid money, and an excessive credit rolls back every associated write. | yes | ATS-ACC-TRX-002-11, ATS-ACC-TRX-003-03 | TST-ACC-TRX-022 (not-run), TST-ACC-TRX-034 (not-run), TST-ACC-TRX-229 (not-run) |
| CAP-ACC-TRX-003 | `BR-CAP-ACC-TRX-003-04` Crediting paid value releases only the needed allocations, starting with the newest payment, and retains that value as unapplied money rather than paying a refund. | yes | ATS-ACC-TRX-003-04, ATS-ACC-TRX-003-12, ATS-ACC-TRX-008-09, ATS-ACC-TRX-011-10, ATS-ACC-TRX-012-12, ATS-ACC-TRX-014-09 | TST-ACC-TRX-033 (not-run), TST-ACC-TRX-230 (not-run) |
| CAP-ACC-TRX-003 | `BR-CAP-ACC-TRX-003-05` The memo form always releases paid value under the freeing rule and offers no alternative treatment. | no |  |  |
| CAP-ACC-TRX-003 | `BR-CAP-ACC-TRX-003-06` Fully credited lines become cancelled; the invoice becomes cancelled when memos eliminate its total, while a partial reduction remains open until settled. | yes | ATS-ACC-TRX-003-05, ATS-ACC-TRX-003-12 | TST-ACC-TRX-034 (not-run) |
| CAP-ACC-TRX-003 | `BR-CAP-ACC-TRX-003-07` A debit memo creates zero-priced invoice lines carrying the added charge, increasing the balance beyond the invoice’s original total. | yes | ATS-ACC-TRX-003-06 | TST-ACC-TRX-035 (not-run), TST-ACC-TRX-227 (not-run) |
| CAP-ACC-TRX-003 | `BR-CAP-ACC-TRX-003-08` Credit tax is apportioned from the gross reduction using the original tax proportions, while debit tax is calculated anew and added to the requested charge. | yes | ATS-ACC-TRX-003-07 | TST-ACC-TRX-036 (not-run) |
| CAP-ACC-TRX-003 | `BR-CAP-ACC-TRX-003-09` Voiding requires a reason and adds dated negating lines restoring the invoice’s position; repeated voids and memo deletion are unavailable. | yes | ATS-ACC-TRX-003-08 | TST-ACC-TRX-003 (not-run), TST-ACC-TRX-034 (not-run), TST-ACC-TRX-226 (not-run) |
| CAP-ACC-TRX-003 | `BR-CAP-ACC-TRX-003-10` A debit memo cannot be voided for more than its added line still owes after later credits. | yes | ATS-ACC-TRX-003-09 | TST-ACC-TRX-035 (not-run) |
| CAP-ACC-TRX-003 | `BR-CAP-ACC-TRX-003-11` A memo defaults to today, uses an open period no earlier than the invoice’s accounting date, and enters an explicitly selected or assigned batch. | yes | ATS-ACC-TRX-003-10 | TST-ACC-TRX-034 (not-run) |
| CAP-ACC-TRX-003 | `BR-CAP-ACC-TRX-003-12` Creating and voiding use the memo kind’s create and update authorities respectively; read access grants inspection without actions. | yes | ATS-ACC-TRX-003-11 | TST-ACC-TRX-003 (not-run) |
| CAP-ACC-TRX-004 | `BR-CAP-ACC-TRX-004-01` Write-offs apply only to an issued real invoice’s own outstanding lines, and an excessive or ineligible write-off leaves every record unchanged. | yes | ATS-ACC-TRX-004-01, ATS-ACC-TRX-004-07 | TST-ACC-TRX-131 (not-run) |
| CAP-ACC-TRX-004 | `BR-CAP-ACC-TRX-004-02` Partial write-offs leave outstanding lines open, fully abandoned lines become written off, and an unpaid invoice with a write-off and no balance becomes written off. | yes | ATS-ACC-TRX-004-02 | TST-ACC-TRX-131 (not-run) |
| CAP-ACC-TRX-004 | `BR-CAP-ACC-TRX-004-03` The requested direct or allowance method overrides the unit default; only allowance treatment can name an allowance account belonging to that unit. | yes | ATS-ACC-TRX-004-03 | TST-ACC-TRX-131 (not-run) |
| CAP-ACC-TRX-004 | `BR-CAP-ACC-TRX-004-04` Write-off creation does not require resolved ledger accounts because posting selects the applicable accounts. | yes | ATS-ACC-TRX-004-03 | TST-ACC-TRX-131 (not-run) |
| CAP-ACC-TRX-004 | `BR-CAP-ACC-TRX-004-05` Reversal creates a new numbered write-off dated today with opposite lines, restores the invoice and marks the original reversed; neither document can be reversed again. | yes | ATS-ACC-TRX-004-04, ATS-ACC-TRX-004-07 | TST-ACC-TRX-020 (not-run), TST-ACC-TRX-131 (not-run) |
| CAP-ACC-TRX-004 | `BR-CAP-ACC-TRX-004-06` Payment arriving for abandoned debt requires reversal of the write-off before application to the restored invoice. | no |  |  |
| CAP-ACC-TRX-004 | `BR-CAP-ACC-TRX-004-07` The product should require another person’s approval above unit thresholds, initially zero; this recorded requirement remains deferred. | yes | ATS-ACC-TRX-004-05 |  |
| CAP-ACC-TRX-004 | `BR-CAP-ACC-TRX-004-08` Creation requires write-off create authority and reversal requires update authority; readers receive no mutation actions. | yes | ATS-ACC-TRX-004-06 | TST-ACC-TRX-020 (not-run) |
| CAP-ACC-TRX-005 | `BR-CAP-ACC-TRX-005-01` Rendering selects the invoice template, then the unit template, then the built-in design; a missing, inactive or inappropriate named template is refused. | yes | ATS-ACC-TRX-005-01 | TST-ACC-TRX-060 (not-run) |
| CAP-ACC-TRX-005 | `BR-CAP-ACC-TRX-005-02` Each rendering produces fresh HTML from the invoice without retaining a rendered copy. | yes | ATS-ACC-TRX-001-17, ATS-ACC-TRX-005-02, ATS-ACC-TRX-005-07 | TST-ACC-TRX-007 (not-run) |
| CAP-ACC-TRX-005 | `BR-CAP-ACC-TRX-005-03` E-mail delivery rejects drafts and requires an invoice that has been issued. | yes | ATS-ACC-TRX-005-03 | TST-ACC-TRX-051 (not-run) |
| CAP-ACC-TRX-005 | `BR-CAP-ACC-TRX-005-04` Delivery uses the contact’s primary address unless the sender provides up to ten valid recipients; absent recipients prevent sending, including an organization with no explicit recipients. | yes | ATS-ACC-TRX-005-03, ATS-ACC-TRX-005-08 | TST-ACC-TRX-051 (not-run) |
| CAP-ACC-TRX-005 | `BR-CAP-ACC-TRX-005-05` Sending requires a distinct retry key, repeats only once under that key and occurs separately from invoice creation. | yes | ATS-ACC-TRX-005-04, ATS-ACC-TRX-005-07 | TST-ACC-TRX-051 (not-run) |
| CAP-ACC-TRX-005 | `BR-CAP-ACC-TRX-005-06` The communication submission and delivery event commit together, with a failed submission leaving neither record. | yes | ATS-ACC-TRX-001-17, ATS-ACC-TRX-005-05, ATS-ACC-TRX-005-07 | TST-ACC-TRX-051 (not-run) |
| CAP-ACC-TRX-005 | `BR-CAP-ACC-TRX-005-07` Read authority permits document viewing, while e-mail authority is separately required for sending. | yes | ATS-ACC-TRX-005-06 | TST-ACC-TRX-007 (not-run) |
| CAP-ACC-TRX-006 | `BR-CAP-ACC-TRX-006-01` Received money must be positive and denominated in a currency supported by its business unit. | yes | ATS-ACC-TRX-006-01 | TST-ACC-TRX-012 (not-run), TST-ACC-TRX-081 (not-run) |
| CAP-ACC-TRX-006 | `BR-CAP-ACC-TRX-006-02` A method must exist, be active and support the selected channel; a required reference applies to direct method selection except imports, while legacy aliases retain reference-free entry. | yes | ATS-ACC-TRX-006-02 | TST-ACC-TRX-078 (not-run) |
| CAP-ACC-TRX-006 | `BR-CAP-ACC-TRX-006-03` During compatibility support, retired method values map to configured methods, and conflicting direct and alias selections are rejected. | no |  |  |
| CAP-ACC-TRX-006 | `BR-CAP-ACC-TRX-006-04` Offline receipts require a bank account in the receipt’s unit and currency. | yes | ATS-ACC-TRX-006-03 | TST-ACC-TRX-081 (not-run) |
| CAP-ACC-TRX-006 | `BR-CAP-ACC-TRX-006-05` A receipt requires an eligible explicit batch or an assignment-rule selection; failure to find either records nothing. | yes | ATS-ACC-TRX-006-04 | TST-ACC-TRX-077 (not-run), TST-ACC-TRX-081 (not-run) |
| CAP-ACC-TRX-006 | `BR-CAP-ACC-TRX-006-06` Offline receipts succeed immediately, default to today and use an accounting date covered by an open fiscal period. | yes | ATS-ACC-TRX-006-05 | TST-ACC-TRX-081 (not-run) |
| CAP-ACC-TRX-006 | `BR-CAP-ACC-TRX-006-07` The payment sequence begins at one million and allows unused numbers. | yes | ATS-ACC-TRX-006-06 | TST-ACC-TRX-081 (not-run) |
| CAP-ACC-TRX-006 | `BR-CAP-ACC-TRX-006-08` Unallocated value remains on the receipt and reduces the customer’s net debt until someone explicitly turns it into credit. | yes | ATS-ACC-TRX-006-07, ATS-ACC-TRX-006-10, ATS-ACC-TRX-008-09, ATS-ACC-TRX-011-10 | TST-ACC-TRX-081 (not-run), TST-ACC-TRX-239 (not-run) |
| CAP-ACC-TRX-006 | `BR-CAP-ACC-TRX-006-09` An offline receipt may identify a different payer by CRM identity or name; that write-once attribution does not expand the eligible invoice population. | yes | ATS-ACC-TRX-006-08 | TST-ACC-TRX-079 (not-run) |
| CAP-ACC-TRX-006 | `BR-CAP-ACC-TRX-006-10` Recorded method, behavior, amount, customer and cash destination cannot be changed. | yes | ATS-ACC-TRX-006-09, ATS-ACC-TRX-006-10, ATS-ACC-TRX-011-10 | TST-ACC-TRX-078 (not-run) |
| CAP-ACC-TRX-006 | `BR-CAP-ACC-TRX-006-11` The payment form prevents mixed-currency invoice selection and filters bank choices to the payment currency. | no |  |  |
| CAP-ACC-TRX-007 | `BR-CAP-ACC-TRX-007-01` Processor tenders require an active merchant account in the payment’s unit and currency; hosted processor fields collect the instrument, and Accounting does not retain its token. | yes | ATS-ACC-TRX-007-01 | TST-ACC-TRX-082 (not-run), TST-ACC-TRX-258 (not-run) |
| CAP-ACC-TRX-007 | `BR-CAP-ACC-TRX-007-02` Financial eligibility and planned allocations are checked before the charge call, preventing rejected input from reaching the processor. | yes | ATS-ACC-TRX-007-02 | TST-ACC-TRX-082 (not-run), TST-ACC-TRX-241 (not-run) |
| CAP-ACC-TRX-007 | `BR-CAP-ACC-TRX-007-03` An intent is committed before charging, and its identity limits the attempt to one charge and one recorded payment. | yes | ATS-ACC-TRX-007-02, ATS-ACC-TRX-007-12, ATS-ACC-TRX-008-09, ATS-ACC-TRX-009-12, ATS-ACC-TRX-020-09 | TST-ACC-TRX-082 (not-run), TST-ACC-TRX-241 (not-run) |
| CAP-ACC-TRX-007 | `BR-CAP-ACC-TRX-007-04` A definite decline or unreachable charge fails the intent and releases the request key for another attempt without recording collected money. | yes | ATS-ACC-TRX-007-03 | TST-ACC-TRX-082 (not-run) |
| CAP-ACC-TRX-007 | `BR-CAP-ACC-TRX-007-05` Captured money is always recorded, allocations shrink to the lines’ current balances, and excess remains unapplied. | yes | ATS-ACC-TRX-007-04, ATS-ACC-TRX-008-09 | TST-ACC-TRX-082 (not-run), TST-ACC-TRX-254 (not-run) |
| CAP-ACC-TRX-007 | `BR-CAP-ACC-TRX-007-06` An uncertain processor response leaves the intent processing, and retrying the request performs a lookup instead of another charge. | yes | ATS-ACC-TRX-007-05, ATS-ACC-TRX-007-12, ATS-ACC-TRX-009-12, ATS-ACC-TRX-011-10, ATS-ACC-TRX-012-12, ATS-ACC-TRX-020-09 | TST-ACC-TRX-015 (not-run), TST-ACC-TRX-082 (not-run), TST-ACC-TRX-253 (not-run) |
| CAP-ACC-TRX-007 | `BR-CAP-ACC-TRX-007-07` Scheduled lookups follow the environment cadence and require a definite answer; exhausted unresolved lookups raise an attention item for human review. | yes | ATS-ACC-TRX-007-06 | TST-ACC-TRX-076 (not-run) |
| CAP-ACC-TRX-007 | `BR-CAP-ACC-TRX-007-08` Human resolution requires an unresolved attempt already in review and either records failure or creates the payment once using the confirmed processor reference. | yes | ATS-ACC-TRX-007-07 | TST-ACC-TRX-076 (not-run) |
| CAP-ACC-TRX-007 | `BR-CAP-ACC-TRX-007-09` An intent whose processor cannot be queried is abandoned after twenty-four hours and logged as an error. | yes | ATS-ACC-TRX-007-08 | TST-ACC-TRX-082 (not-run) |
| CAP-ACC-TRX-007 | `BR-CAP-ACC-TRX-007-10` Electronic checks remain pending until clearing is confirmed, then succeed; a returned debit creates an ACH-return reversal. | yes | ATS-ACC-TRX-007-09, ATS-ACC-TRX-007-12, ATS-ACC-TRX-013-10 | TST-ACC-TRX-075 (not-run), TST-ACC-TRX-080 (not-run), TST-ACC-TRX-082 (not-run) |
| CAP-ACC-TRX-007 | `BR-CAP-ACC-TRX-007-11` Only Rhythm staff can use the system route to mark an electronic check settled; customer administrators are refused. | yes | ATS-ACC-TRX-007-10 | TST-ACC-TRX-011 (not-run) |
| CAP-ACC-TRX-007 | `BR-CAP-ACC-TRX-007-12` The processor’s electronic-check capability controls whether bank-account entry appears beside card entry, and electronic checks are eligible wherever cards are. | yes | ATS-ACC-TRX-007-11 | TST-ACC-TRX-127 (not-run), TST-ACC-TRX-271 (not-run) |
| CAP-ACC-TRX-007 | `BR-CAP-ACC-TRX-007-13` Card captures create reconciliation items immediately, while bank-debit captures become eligible when clearing completes. | yes | ATS-ACC-TRX-007-09 | TST-ACC-TRX-075 (not-run), TST-ACC-TRX-080 (not-run), TST-ACC-TRX-082 (not-run) |
| CAP-ACC-TRX-007 | `BR-CAP-ACC-TRX-007-14` Production processor work uses the Integration Platform gateway; the superseded Stripe options and webhook remain exposed and report missing configuration where keys are absent. | no |  |  |
| CAP-ACC-TRX-008 | `BR-CAP-ACC-TRX-008-01` Allocations target issued eligible invoice lines in the payment’s unit and currency; drafts and void invoices cannot receive money. | yes | ATS-ACC-TRX-004-07, ATS-ACC-TRX-008-01, ATS-ACC-TRX-010-07 | TST-ACC-TRX-081 (not-run) |
| CAP-ACC-TRX-008 | `BR-CAP-ACC-TRX-008-02` Every allocation path restricts payment to the receipt’s own customer until a later multi-customer model is implemented. | yes | ATS-ACC-TRX-008-02, ATS-ACC-TRX-010-07 | TST-ACC-TRX-072 (not-run) |
| CAP-ACC-TRX-008 | `BR-CAP-ACC-TRX-008-03` A line target receives its stated amount, while an invoice target distributes the amount by line payment priority up to each outstanding balance. | yes | ATS-ACC-TRX-008-03 | TST-ACC-TRX-070 (not-run), TST-ACC-TRX-081 (not-run) |
| CAP-ACC-TRX-008 | `BR-CAP-ACC-TRX-008-04` Allocation cannot exceed either a line’s balance or the payment’s available money, including concurrent attempts protected by database constraints. | yes | ATS-ACC-TRX-003-12, ATS-ACC-TRX-004-07, ATS-ACC-TRX-006-10, ATS-ACC-TRX-007-12, ATS-ACC-TRX-008-04, ATS-ACC-TRX-008-09, ATS-ACC-TRX-009-12, ATS-ACC-TRX-020-09 | TST-ACC-TRX-070 (not-run), TST-ACC-TRX-256 (not-run) |
| CAP-ACC-TRX-008 | `BR-CAP-ACC-TRX-008-05` Allocation history accepts additions only; taking money away requires an opposite entry referring to the original. | yes | ATS-ACC-TRX-008-05, ATS-ACC-TRX-008-09 | TST-ACC-TRX-070 (not-run) |
| CAP-ACC-TRX-008 | `BR-CAP-ACC-TRX-008-06` Reallocation negates selected live applications and applies the resulting available money to new targets atomically; an already reversed application is ineligible. | yes | ATS-ACC-TRX-003-12, ATS-ACC-TRX-006-10, ATS-ACC-TRX-008-06, ATS-ACC-TRX-008-09 | TST-ACC-TRX-070 (not-run), TST-ACC-TRX-242 (not-run) |
| CAP-ACC-TRX-008 | `BR-CAP-ACC-TRX-008-07` Only live payments can be allocated; voided, returned and charged-back receipts have no usable money. | yes | ATS-ACC-TRX-007-12, ATS-ACC-TRX-008-07 | TST-ACC-TRX-070 (not-run) |
| CAP-ACC-TRX-008 | `BR-CAP-ACC-TRX-008-08` The first payment against an issued pro forma recognizes it as a real invoice within the same operation. | yes | ATS-ACC-TRX-008-08 | TST-ACC-TRX-081 (not-run) |
| CAP-ACC-TRX-008 | `BR-CAP-ACC-TRX-008-09` Later allocation chooses the requested batch, otherwise the payment’s still-open batch, otherwise the unit’s assigned batch. | no |  |  |
| CAP-ACC-TRX-009 | `BR-CAP-ACC-TRX-009-01` Settlement creation requires settlement, payment and credit-application create authority together; reading requires settlement read plus payment or application read authority. | yes | ATS-ACC-TRX-009-01 | TST-ACC-TRX-017 (not-run) |
| CAP-ACC-TRX-009 | `BR-CAP-ACC-TRX-009-02` Settlement targets must share its customer, unit and currency, remain outstanding and receive no more than their current balance. | yes | ATS-ACC-TRX-009-02, ATS-ACC-TRX-009-03 | TST-ACC-TRX-126 (not-run) |
| CAP-ACC-TRX-009 | `BR-CAP-ACC-TRX-009-03` Settlement uses named credits first in request order, then other eligible customer credits oldest first, up to fifty, unless automatic credit use is disabled. | yes | ATS-ACC-TRX-006-10, ATS-ACC-TRX-008-09, ATS-ACC-TRX-009-04, ATS-ACC-TRX-009-12, ATS-ACC-TRX-011-10 | TST-ACC-TRX-126 (not-run), TST-ACC-TRX-240 (not-run) |
| CAP-ACC-TRX-009 | `BR-CAP-ACC-TRX-009-04` Chosen credit is reserved until the payment outcome, preventing competing settlements from spending it and releasing it on failure. | yes | ATS-ACC-TRX-008-09, ATS-ACC-TRX-009-05, ATS-ACC-TRX-009-12, ATS-ACC-TRX-009-13, ATS-ACC-TRX-011-10, ATS-ACC-TRX-020-09 | TST-ACC-TRX-124 (not-run), TST-ACC-TRX-126 (not-run), TST-ACC-TRX-252 (not-run) |
| CAP-ACC-TRX-009 | `BR-CAP-ACC-TRX-009-05` Credits can complete settlement alone; any supplied payment must be positive, and a payment supplied after full credit coverage is retained entirely unapplied with that outcome disclosed. | yes | ATS-ACC-TRX-006-10, ATS-ACC-TRX-009-06 | TST-ACC-TRX-125 (not-run), TST-ACC-TRX-126 (not-run) |
| CAP-ACC-TRX-009 | `BR-CAP-ACC-TRX-009-06` Overpayment remains unapplied or follows the configured credit policy, can explicitly become credit, or is rejected before writes when refusal is requested. | yes | ATS-ACC-TRX-009-07 | TST-ACC-TRX-126 (not-run) |
| CAP-ACC-TRX-009 | `BR-CAP-ACC-TRX-009-07` Required or accepted optional card fees apply the unit’s percentage, fixed amount and minimum once across eligible tender value through a separate fee invoice settled with the tender. | yes | ATS-ACC-TRX-009-08 | TST-ACC-TRX-122 (not-run) |
| CAP-ACC-TRX-009 | `BR-CAP-ACC-TRX-009-08` A declined required fee or missing required fee configuration blocks charging; offline money is fee-free and bank debits are fee-free when excluded by the unit rule. | yes | ATS-ACC-TRX-009-09 | TST-ACC-TRX-122 (not-run) |
| CAP-ACC-TRX-009 | `BR-CAP-ACC-TRX-009-09` A definite charge failure releases credit reservations, voids the fee invoice and permits a fresh settlement attempt under the same key. | yes | ATS-ACC-TRX-007-12, ATS-ACC-TRX-009-05, ATS-ACC-TRX-009-10 | TST-ACC-TRX-122 (not-run), TST-ACC-TRX-124 (not-run), TST-ACC-TRX-126 (not-run), TST-ACC-TRX-252 (not-run) |
| CAP-ACC-TRX-009 | `BR-CAP-ACC-TRX-009-10` Uncertain tender outcomes leave settlement pending; a settlement with no started payment fails after a day and releases reserved credit. | yes | ATS-ACC-TRX-007-12, ATS-ACC-TRX-009-11, ATS-ACC-TRX-009-12, ATS-ACC-TRX-012-12, ATS-ACC-TRX-013-10, ATS-ACC-TRX-020-09 | TST-ACC-TRX-126 (not-run) |
| CAP-ACC-TRX-009 | `BR-CAP-ACC-TRX-009-11` Settlement, receipt, applications and intent retain reciprocal references for following the work across records. | no | ATS-ACC-TRX-009-12 |  |
| CAP-ACC-TRX-009 | `BR-CAP-ACC-TRX-009-12` The console distributes credit before payment against the oldest invoices, selects the default open batch and blocks review until validation succeeds. | no |  |  |
| CAP-ACC-TRX-010 | `BR-CAP-ACC-TRX-010-01` Remittance entry, reading and voiding require both the remittance and matching payment authorities; expected-invoice lookup additionally requires invoice read authority. | yes | ATS-ACC-TRX-010-01 | TST-ACC-TRX-014 (not-run) |
| CAP-ACC-TRX-010 | `BR-CAP-ACC-TRX-010-02` Expected remittances list outstanding invoices whose orders identify that remitter. | no |  |  |
| CAP-ACC-TRX-010 | `BR-CAP-ACC-TRX-010-03` Receipt total equals the selected lines plus an explicitly stated remainder; omitted remainder is never calculated automatically. | yes | ATS-ACC-TRX-010-02 | TST-ACC-TRX-111 (not-run) |
| CAP-ACC-TRX-010 | `BR-CAP-ACC-TRX-010-04` Remittances accept offline methods only and enforce applicable reference requirements. | yes | ATS-ACC-TRX-010-03 | TST-ACC-TRX-111 (not-run) |
| CAP-ACC-TRX-010 | `BR-CAP-ACC-TRX-010-05` Each unique target belongs to the stated member, unit and currency and receives no more than its outstanding value. | yes | ATS-ACC-TRX-010-04, ATS-ACC-TRX-010-07 | TST-ACC-TRX-111 (not-run) |
| CAP-ACC-TRX-010 | `BR-CAP-ACC-TRX-010-06` Entry atomically creates a payment for each member and an unapplied remainder payment for the remitter; any invalid line rejects the entire receipt. | yes | ATS-ACC-TRX-010-05, ATS-ACC-TRX-010-07 | TST-ACC-TRX-014 (not-run), TST-ACC-TRX-110 (not-run) |
| CAP-ACC-TRX-010 | `BR-CAP-ACC-TRX-010-07` Voiding requires a reason, reverses all generated payments and restores invoices, but fails after external reuse of money, posting or an earlier void. | yes | ATS-ACC-TRX-010-06, ATS-ACC-TRX-010-07 | TST-ACC-TRX-112 (not-run) |
| CAP-ACC-TRX-010 | `BR-CAP-ACC-TRX-010-08` Remittance requests contain no more than two hundred and fifty lines. | no | ATS-ACC-TRX-010-08 |  |
| CAP-ACC-TRX-010 | `BR-CAP-ACC-TRX-010-09` The product should replace the interim per-member payment split with a single receipt allocated across customers in the later receipt milestone. | no |  |  |
| CAP-ACC-TRX-011 | `BR-CAP-ACC-TRX-011-01` Manually issued credit identifies the customer, unit, currency, reason and that unit’s liability and expense accounts. | yes | ATS-ACC-TRX-011-01 | TST-ACC-TRX-004 (not-run), TST-ACC-TRX-037 (not-run) |
| CAP-ACC-TRX-011 | `BR-CAP-ACC-TRX-011-02` Payment-backed credit inherits the payment’s customer, unit and currency and transfers no more than its unapplied value out of the payment while the credit remains live. | yes | ATS-ACC-TRX-003-12, ATS-ACC-TRX-008-09, ATS-ACC-TRX-011-02, ATS-ACC-TRX-011-10, ATS-ACC-TRX-013-10, ATS-ACC-TRX-014-09 | TST-ACC-TRX-037 (not-run), TST-ACC-TRX-247 (not-run) |
| CAP-ACC-TRX-011 | `BR-CAP-ACC-TRX-011-03` Available credit equals issued value less applications, refunds and reservations; positive balance is open, zero is used, and database checks prevent overspending. | yes | ATS-ACC-TRX-007-12, ATS-ACC-TRX-008-09, ATS-ACC-TRX-009-12, ATS-ACC-TRX-011-03, ATS-ACC-TRX-011-10, ATS-ACC-TRX-012-12 | TST-ACC-TRX-037 (not-run), TST-ACC-TRX-256 (not-run) |
| CAP-ACC-TRX-011 | `BR-CAP-ACC-TRX-011-04` Only a numbered batched credit application puts credit on invoice lines, using payment-style target selection and producing paid status when a line is settled. | yes | ATS-ACC-TRX-007-12, ATS-ACC-TRX-009-12, ATS-ACC-TRX-011-04, ATS-ACC-TRX-014-09 | TST-ACC-TRX-037 (not-run) |
| CAP-ACC-TRX-011 | `BR-CAP-ACC-TRX-011-05` Credit can settle invoices belonging to its own customer only. | yes | ATS-ACC-TRX-011-05 | TST-ACC-TRX-037 (not-run), TST-ACC-TRX-257 (not-run) |
| CAP-ACC-TRX-011 | `BR-CAP-ACC-TRX-011-06` Application rejects credit after its expiry date or outside its permitted order type, although no worker marks credits expired. | yes | ATS-ACC-TRX-011-06 | TST-ACC-TRX-037 (not-run) |
| CAP-ACC-TRX-011 | `BR-CAP-ACC-TRX-011-07` Concurrent applications serialize so they cannot both consume the same remaining credit. | yes | ATS-ACC-TRX-011-03 | TST-ACC-TRX-037 (not-run), TST-ACC-TRX-256 (not-run) |
| CAP-ACC-TRX-011 | `BR-CAP-ACC-TRX-011-08` Undoing an application creates one dated opposing application with a reason, restores the credit and invoice balances, and prevents a second reversal. | yes | ATS-ACC-TRX-011-07 | TST-ACC-TRX-037 (not-run), TST-ACC-TRX-246 (not-run) |
| CAP-ACC-TRX-011 | `BR-CAP-ACC-TRX-011-09` Voiding requires unused, unreserved and unrefunded credit before posting; payment-backed credit then restores its source payment’s available value. | yes | ATS-ACC-TRX-011-08, ATS-ACC-TRX-011-10, ATS-ACC-TRX-013-10 | TST-ACC-TRX-037 (not-run) |
| CAP-ACC-TRX-011 | `BR-CAP-ACC-TRX-011-10` Eligible customer credit is presented oldest first within its unit and currency. | no |  |  |
| CAP-ACC-TRX-011 | `BR-CAP-ACC-TRX-011-11` Credit operations use credit authorities, while application and reversal use credit-application authorities. | yes | ATS-ACC-TRX-011-09 | TST-ACC-TRX-004 (not-run) |
| CAP-ACC-TRX-011 | `BR-CAP-ACC-TRX-011-12` Application rows and database-maintained credit amounts cannot be directly edited by the application role. | no |  |  |
| CAP-ACC-TRX-012 | `BR-CAP-ACC-TRX-012-01` Refund requests identify positive refundable value and cannot exceed available unapplied money, remaining application value or credit balance. | yes | ATS-ACC-TRX-011-10, ATS-ACC-TRX-012-01 | TST-ACC-TRX-109 (not-run) |
| CAP-ACC-TRX-012 | `BR-CAP-ACC-TRX-012-02` A request reserves its unapplied source money until success, cancellation or failure, preventing concurrent application, credit creation or another refund from using it. | yes | ATS-ACC-TRX-011-10, ATS-ACC-TRX-012-02, ATS-ACC-TRX-012-12 | TST-ACC-TRX-107 (not-run) |
| CAP-ACC-TRX-012 | `BR-CAP-ACC-TRX-012-03` Processor money returns through its original merchant account unless the source lacks a processor reference or a processor refund has already been declined. | yes | ATS-ACC-TRX-003-12, ATS-ACC-TRX-012-03, ATS-ACC-TRX-013-10, ATS-ACC-TRX-014-09 | TST-ACC-TRX-105 (not-run) |
| CAP-ACC-TRX-012 | `BR-CAP-ACC-TRX-012-04` Refunding an application removes its paid value; a default credit memo preserves settlement, while an explicit reopen choice restores the debt. | yes | ATS-ACC-TRX-012-04 | TST-ACC-TRX-109 (not-run), TST-ACC-TRX-249 (not-run) |
| CAP-ACC-TRX-012 | `BR-CAP-ACC-TRX-012-05` Where workspace approval is enabled, requests wait and only a different person can approve them. | yes | ATS-ACC-TRX-012-05 | TST-ACC-TRX-109 (not-run), TST-ACC-TRX-250 (not-run) |
| CAP-ACC-TRX-012 | `BR-CAP-ACC-TRX-012-06` Execution requires requested status, cancellation requires an unpaid refund and a reason, and paid or cancelled refunds are final. | yes | ATS-ACC-TRX-012-06 | TST-ACC-TRX-109 (not-run) |
| CAP-ACC-TRX-012 | `BR-CAP-ACC-TRX-012-07` Offline execution moves money immediately and derives partially refunded or refunded payment status from the accumulated amount. | yes | ATS-ACC-TRX-012-07 | TST-ACC-TRX-109 (not-run), TST-ACC-TRX-248 (not-run) |
| CAP-ACC-TRX-012 | `BR-CAP-ACC-TRX-012-08` Processor refunds are recorded before the external call; definite rejection or nonreceipt fails the refund and restores applications and reservations. | yes | ATS-ACC-TRX-007-12, ATS-ACC-TRX-012-08, ATS-ACC-TRX-012-12, ATS-ACC-TRX-020-09 | TST-ACC-TRX-108 (not-run), TST-ACC-TRX-109 (not-run), TST-ACC-TRX-251 (not-run) |
| CAP-ACC-TRX-012 | `BR-CAP-ACC-TRX-012-09` Unknown or pending processor outcomes keep the refund processing with money held until confirmed by lookup, event or human resolution, without abandonment. | yes | ATS-ACC-TRX-007-12, ATS-ACC-TRX-009-12, ATS-ACC-TRX-012-09, ATS-ACC-TRX-012-12, ATS-ACC-TRX-013-10, ATS-ACC-TRX-014-09, ATS-ACC-TRX-020-09 | TST-ACC-TRX-042 (not-run), TST-ACC-TRX-108 (not-run), TST-ACC-TRX-109 (not-run), TST-ACC-TRX-264 (not-run) |
| CAP-ACC-TRX-012 | `BR-CAP-ACC-TRX-012-10` Only check refunds can carry a check number. | no |  |  |
| CAP-ACC-TRX-012 | `BR-CAP-ACC-TRX-012-11` Refunding card-paid value also returns its proportional processing fee rounded downward and credits the fee invoice. | yes | ATS-ACC-TRX-012-10 | TST-ACC-TRX-122 (not-run) |
| CAP-ACC-TRX-012 | `BR-CAP-ACC-TRX-012-12` Request and cancellation require create authority, approval and execution require their distinct sensitive authorities, and immediate execution requires both create and execute. | yes | ATS-ACC-TRX-012-11 | TST-ACC-TRX-013 (not-run) |
| CAP-ACC-TRX-012 | `BR-CAP-ACC-TRX-012-13` The product should expose the workspace’s refund-approval setting in the console; only the service currently provides it. | no |  |  |
| CAP-ACC-TRX-013 | `BR-CAP-ACC-TRX-013-01` Payment void and reversal use separate sensitive authorities and both require an explanation. | yes | ATS-ACC-TRX-013-01 | TST-ACC-TRX-011 (not-run), TST-ACC-TRX-012 (not-run) |
| CAP-ACC-TRX-013 | `BR-CAP-ACC-TRX-013-02` Reversal type follows the payment behavior: offline receipts allow void and, if bounce-enabled, bounced check; processor receipts allow void, bank return and chargeback. | yes | ATS-ACC-TRX-013-02 | TST-ACC-TRX-078 (not-run), TST-ACC-TRX-080 (not-run) |
| CAP-ACC-TRX-013 | `BR-CAP-ACC-TRX-013-03` A successful reversal negates live allocations, restores invoice debt and leaves the payment voided, returned or charged back with no available value. | yes | ATS-ACC-TRX-006-10, ATS-ACC-TRX-007-12, ATS-ACC-TRX-013-03, ATS-ACC-TRX-013-04, ATS-ACC-TRX-013-10, ATS-ACC-TRX-020-09 | TST-ACC-TRX-070 (not-run), TST-ACC-TRX-080 (not-run), TST-ACC-TRX-243 (not-run), TST-ACC-TRX-244 (not-run) |
| CAP-ACC-TRX-013 | `BR-CAP-ACC-TRX-013-04` A payment permits at most one nonfailed reversal, and voiding preserves the payment record. | yes | ATS-ACC-TRX-006-10, ATS-ACC-TRX-013-03, ATS-ACC-TRX-013-10 | TST-ACC-TRX-080 (not-run), TST-ACC-TRX-244 (not-run) |
| CAP-ACC-TRX-013 | `BR-CAP-ACC-TRX-013-05` Any nonvoid credit derived from a payment blocks its reversal, including a fully used credit. | yes | ATS-ACC-TRX-011-10, ATS-ACC-TRX-013-04, ATS-ACC-TRX-013-10 | TST-ACC-TRX-070 (not-run), TST-ACC-TRX-080 (not-run), TST-ACC-TRX-243 (not-run) |
| CAP-ACC-TRX-013 | `BR-CAP-ACC-TRX-013-06` Processor void precedes local reversal, and a settled charge rejects voiding in favor of refunding. | yes | ATS-ACC-TRX-007-12, ATS-ACC-TRX-009-12, ATS-ACC-TRX-012-12, ATS-ACC-TRX-013-05, ATS-ACC-TRX-013-10 | TST-ACC-TRX-080 (not-run), TST-ACC-TRX-245 (not-run) |
| CAP-ACC-TRX-013 | `BR-CAP-ACC-TRX-013-07` A completed processor reversal adds its negative reconciliation item. | yes | ATS-ACC-TRX-013-05 | TST-ACC-TRX-080 (not-run), TST-ACC-TRX-245 (not-run) |
| CAP-ACC-TRX-013 | `BR-CAP-ACC-TRX-013-08` Reversing payment of a processing-fee invoice credits that fee invoice in full. | yes | ATS-ACC-TRX-013-06 | TST-ACC-TRX-122 (not-run) |
| CAP-ACC-TRX-013 | `BR-CAP-ACC-TRX-013-09` A dispute requires a live card or bank payment and an amount no greater than its total, and can close once with a won, lost or closed outcome. | yes | ATS-ACC-TRX-013-07 | TST-ACC-TRX-080 (not-run) |
| CAP-ACC-TRX-013 | `BR-CAP-ACC-TRX-013-10` Losing a chargeback closes the dispute and reverses the payment together; losing an inquiry alone leaves the payment untouched. | yes | ATS-ACC-TRX-013-08 | TST-ACC-TRX-011 (not-run), TST-ACC-TRX-073 (not-run), TST-ACC-TRX-080 (not-run) |
| CAP-ACC-TRX-013 | `BR-CAP-ACC-TRX-013-11` The product should restrict lost-chargeback reversal to the disputed amount; the current implementation reverses the whole payment. | yes | ATS-ACC-TRX-013-09 |  |
| CAP-ACC-TRX-013 | `BR-CAP-ACC-TRX-013-12` Processor events can create and close disputes, with repeat delivery prevented from applying the outcome twice. | no |  |  |
| CAP-ACC-TRX-014 | `BR-CAP-ACC-TRX-014-01` Billing reversal requires an issued real invoice and its own eligible line quantities or values; invalid lifecycle, unrelated lines and excessive reversal are refused. | yes | ATS-ACC-TRX-014-01 | TST-ACC-TRX-117 (not-run) |
| CAP-ACC-TRX-014 | `BR-CAP-ACC-TRX-014-02` The operation first credits unused line value and releases no-longer-needed paid value back to the contributing payments. | yes | ATS-ACC-TRX-003-12, ATS-ACC-TRX-014-02, ATS-ACC-TRX-014-09 | TST-ACC-TRX-117 (not-run) |
| CAP-ACC-TRX-014 | `BR-CAP-ACC-TRX-014-03` A cancellation fee creates a separate invoice paid using credit derived from one contributing payment’s released money. | yes | ATS-ACC-TRX-011-10, ATS-ACC-TRX-014-02, ATS-ACC-TRX-014-09 | TST-ACC-TRX-117 (not-run) |
| CAP-ACC-TRX-014 | `BR-CAP-ACC-TRX-014-04` The selected remainder treatment issues credit or requests a refund per contributing payment; processor refunds execute immediately and offline refunds await staff. | yes | ATS-ACC-TRX-003-12, ATS-ACC-TRX-011-10, ATS-ACC-TRX-014-03, ATS-ACC-TRX-014-09 | TST-ACC-TRX-116 (not-run), TST-ACC-TRX-117 (not-run), TST-ACC-TRX-261 (not-run) |
| CAP-ACC-TRX-014 | `BR-CAP-ACC-TRX-014-05` Financial preparation commits atomically and an invalid step leaves nothing; external refund execution afterward can remain unresolved. | yes | ATS-ACC-TRX-012-12, ATS-ACC-TRX-014-04, ATS-ACC-TRX-014-09, ATS-ACC-TRX-020-09 | TST-ACC-TRX-117 (not-run) |
| CAP-ACC-TRX-014 | `BR-CAP-ACC-TRX-014-06` Preview calculates the same per-payment and refund-payer results and retains no records, but document-number allocations still advance. | yes | ATS-ACC-TRX-014-05 | TST-ACC-TRX-113 (not-run), TST-ACC-TRX-117 (not-run), TST-ACC-TRX-260 (not-run) |
| CAP-ACC-TRX-014 | `BR-CAP-ACC-TRX-014-07` Billing adjustments book immediately; unresolved processor refunds keep reversal pending, successful refunds complete it, and failed or staff-payable refunds produce completion with an exception. | yes | ATS-ACC-TRX-012-12, ATS-ACC-TRX-014-06, ATS-ACC-TRX-020-09 | TST-ACC-TRX-114 (not-run), TST-ACC-TRX-115 (not-run) |
| CAP-ACC-TRX-014 | `BR-CAP-ACC-TRX-014-08` Reversed card-paid value also releases and credits its share of the processing-fee invoice. | yes | ATS-ACC-TRX-014-07 | TST-ACC-TRX-122 (not-run) |
| CAP-ACC-TRX-014 | `BR-CAP-ACC-TRX-014-09` Creation, preview and reading require reversal create, preview and read authorities respectively. | yes | ATS-ACC-TRX-014-08 | TST-ACC-TRX-017 (not-run) |
| CAP-ACC-TRX-015 | `BR-CAP-ACC-TRX-015-01` A destination must be an open or in-error transaction batch in the record’s unit; closed, posted, period-close and foreign-unit destinations are refused. | yes | ATS-ACC-TRX-002-11, ATS-ACC-TRX-003-12, ATS-ACC-TRX-004-07, ATS-ACC-TRX-015-01, ATS-ACC-TRX-015-09 | TST-ACC-TRX-030 (not-run) |
| CAP-ACC-TRX-015 | `BR-CAP-ACC-TRX-015-02` Without explicit batch selection, the unit’s assignment rules choose an active recurring batch for the record kind, and unusable or absent assignment is refused. | yes | ATS-ACC-TRX-015-02 | TST-ACC-TRX-030 (not-run) |
| CAP-ACC-TRX-015 | `BR-CAP-ACC-TRX-015-03` Eligible records move only between unposted batches of the same unit; posting, posted and downloaded batches block movement, while selecting the current batch is a no-op. | yes | ATS-ACC-TRX-002-11, ATS-ACC-TRX-003-12, ATS-ACC-TRX-004-07, ATS-ACC-TRX-006-10, ATS-ACC-TRX-015-03, ATS-ACC-TRX-015-09, ATS-ACC-TRX-016-08 | TST-ACC-TRX-039 (not-run) |
| CAP-ACC-TRX-015 | `BR-CAP-ACC-TRX-015-04` Moving a receipt also moves allocations sharing its batch and records an audit event without changing receivable value. | yes | ATS-ACC-TRX-006-10, ATS-ACC-TRX-015-04, ATS-ACC-TRX-015-09, ATS-ACC-TRX-016-08 | TST-ACC-TRX-039 (not-run) |
| CAP-ACC-TRX-015 | `BR-CAP-ACC-TRX-015-05` Drafts and void records cannot move, and quotes receive no batch until conversion. | yes | ATS-ACC-TRX-015-05 | TST-ACC-TRX-039 (not-run) |
| CAP-ACC-TRX-015 | `BR-CAP-ACC-TRX-015-06` Supported reference, memo and note fields remain editable and can be cleared, but required reasons cannot become blank. | yes | ATS-ACC-TRX-015-06 | TST-ACC-TRX-012 (not-run), TST-ACC-TRX-039 (not-run) |
| CAP-ACC-TRX-015 | `BR-CAP-ACC-TRX-015-07` Unposted date corrections require an open period and append opposing old-date and replacement new-date receivable entries. | yes | ATS-ACC-TRX-015-07 | TST-ACC-TRX-039 (not-run) |
| CAP-ACC-TRX-015 | `BR-CAP-ACC-TRX-015-08` Each record kind’s update authority governs movement and details, and payment Edit Details is connected in the console. | yes | ATS-ACC-TRX-015-08 | TST-ACC-TRX-003 (not-run), TST-ACC-TRX-012 (not-run) |
| CAP-ACC-TRX-016 | `BR-CAP-ACC-TRX-016-01` Available actions reflect permission and lifecycle eligibility; blocked preconditions display a disabled reason and read-only access exposes no mutations. | yes | ATS-ACC-TRX-001-17, ATS-ACC-TRX-015-09, ATS-ACC-TRX-016-01, ATS-ACC-TRX-016-08 | TST-ACC-TRX-010 (not-run), TST-ACC-TRX-132 (not-run) |
| CAP-ACC-TRX-016 | `BR-CAP-ACC-TRX-016-02` Execution rechecks permission and current command eligibility, rejecting an action when intervening changes make it invalid. | yes | ATS-ACC-TRX-001-17, ATS-ACC-TRX-015-09, ATS-ACC-TRX-016-02, ATS-ACC-TRX-016-08 | TST-ACC-TRX-010 (not-run) |
| CAP-ACC-TRX-016 | `BR-CAP-ACC-TRX-016-03` Console money workflows disabled by access show an explanation rather than disappearing. | yes | ATS-ACC-TRX-016-03 | TST-ACC-TRX-209 (not-run), TST-ACC-TRX-263 (not-run) |
| CAP-ACC-TRX-016 | `BR-CAP-ACC-TRX-016-04` Foreign-workspace records appear absent and cannot be changed through the reader’s workspace. | yes | ATS-ACC-TRX-016-04 | TST-ACC-TRX-003 (not-run), TST-ACC-TRX-010 (not-run), TST-ACC-TRX-235 (not-run) |
| CAP-ACC-TRX-016 | `BR-CAP-ACC-TRX-016-05` Main invoice, payment, credit and refund lists provide newest-first filtered pages with validated cursors; memo and write-off lists are scoped to their invoice. | no |  |  |
| CAP-ACC-TRX-016 | `BR-CAP-ACC-TRX-016-06` Financial Transactions combines transaction kinds with customer context, display status and open value, using zero for inactive payments and credits. | yes | ATS-ACC-TRX-016-05, ATS-ACC-TRX-016-08, ATS-ACC-TRX-017-08, ATS-ACC-TRX-020-09 | TST-ACC-TRX-029 (not-run) |
| CAP-ACC-TRX-016 | `BR-CAP-ACC-TRX-016-07` Dataset reads require their query authority and isolate workspace data; read-only policies include those authorities. | yes | ATS-ACC-TRX-016-06 | TST-ACC-TRX-028 (not-run) |
| CAP-ACC-TRX-016 | `BR-CAP-ACC-TRX-016-08` Commands retain append-only document events with actor, transition, reason and retry key, while public history routes and screens remain absent. | yes | ATS-ACC-TRX-016-07, ATS-ACC-TRX-020-09 | TST-ACC-TRX-091 (not-run) |
| CAP-ACC-TRX-016 | `BR-CAP-ACC-TRX-016-09` Platform exports include invoices, receipts, credits, adjustments, events, aging snapshots and processor-reference datasets. | no |  |  |
| CAP-ACC-TRX-017 | `BR-CAP-ACC-TRX-017-01` Today’s customer summary groups invoice debt, overdue debt, unapplied receipts, credit and net position by currency using the same receivable entries as aging. | yes | ATS-ACC-TRX-010-07, ATS-ACC-TRX-016-08, ATS-ACC-TRX-017-01, ATS-ACC-TRX-017-08, ATS-ACC-TRX-018-08 | TST-ACC-TRX-038 (not-run) |
| CAP-ACC-TRX-017 | `BR-CAP-ACC-TRX-017-02` Debt becomes overdue after its due date, so amounts due today remain current. | yes | ATS-ACC-TRX-017-02, ATS-ACC-TRX-017-08, ATS-ACC-TRX-019-08 | TST-ACC-TRX-143 (not-run) |
| CAP-ACC-TRX-017 | `BR-CAP-ACC-TRX-017-03` A contact summary excludes organization figures even though its payable list includes the primary organization’s outstanding invoices. | yes | ATS-ACC-TRX-017-03 | TST-ACC-TRX-038 (not-run), TST-ACC-TRX-059 (not-run) |
| CAP-ACC-TRX-017 | `BR-CAP-ACC-TRX-017-04` The summary separately identifies unapplied receipts from another payer while retaining them within total unapplied money; remitter remainder belongs to the remitter. | no | ATS-ACC-TRX-010-07 |  |
| CAP-ACC-TRX-017 | `BR-CAP-ACC-TRX-017-05` Payable lists contain outstanding issued real invoices oldest first, excluding drafts, voids and quotes, with card and bank-debit eligibility. | yes | ATS-ACC-TRX-017-04 | TST-ACC-TRX-059 (not-run) |
| CAP-ACC-TRX-017 | `BR-CAP-ACC-TRX-017-06` Fee quotes apply the unit rule once to eligible tender value and produce no fee for checks or fee-free policies. | yes | ATS-ACC-TRX-017-05 | TST-ACC-TRX-059 (not-run) |
| CAP-ACC-TRX-017 | `BR-CAP-ACC-TRX-017-07` Invoice read authority is sufficient for financial standing, and customers without open items return no currency groups even if CRM does not know them. | yes | ATS-ACC-TRX-017-06 | TST-ACC-TRX-005 (not-run), TST-ACC-TRX-038 (not-run) |
| CAP-ACC-TRX-017 | `BR-CAP-ACC-TRX-017-08` The product should expose payment-plan standing and let Billing pause collection through a hold; neither behavior is implemented. | yes | ATS-ACC-TRX-017-07 |  |
| CAP-ACC-TRX-018 | `BR-CAP-ACC-TRX-018-01` After a month closes in the workspace calendar, scheduled planning creates its first snapshot version once for each eligible workspace. | yes | ATS-ACC-TRX-018-01 | TST-ACC-TRX-120 (not-run) |
| CAP-ACC-TRX-018 | `BR-CAP-ACC-TRX-018-02` Capture records month-end debt and negative unapplied money as known at that cutoff, excluding later-recorded backdated transactions. | yes | ATS-ACC-TRX-017-08, ATS-ACC-TRX-018-02, ATS-ACC-TRX-018-08, ATS-ACC-TRX-020-09 | TST-ACC-TRX-119 (not-run), TST-ACC-TRX-120 (not-run) |
| CAP-ACC-TRX-018 | `BR-CAP-ACC-TRX-018-03` Snapshot items retain document and customer labels and classify debt into current, thirty-day bands through one hundred and twenty days, then older debt, with a separate unapplied bucket. | yes | ATS-ACC-TRX-018-03 | TST-ACC-TRX-001 (not-run), TST-ACC-TRX-120 (not-run) |
| CAP-ACC-TRX-018 | `BR-CAP-ACC-TRX-018-04` Publication requires successful validation and reconciled totals; failed capture rolls back its rows and schedules another attempt. | yes | ATS-ACC-TRX-018-04 | TST-ACC-TRX-120 (not-run) |
| CAP-ACC-TRX-018 | `BR-CAP-ACC-TRX-018-05` Published data remains immutable; rerunning creates a new current version on publication while preserving superseded rows by run. | yes | ATS-ACC-TRX-017-08, ATS-ACC-TRX-018-05, ATS-ACC-TRX-018-08, ATS-ACC-TRX-020-09 | TST-ACC-TRX-120 (not-run) |
| CAP-ACC-TRX-018 | `BR-CAP-ACC-TRX-018-06` Month reads expose published data only, explain unavailable runs and reject a cursor when newer publication would mix versions. | yes | ATS-ACC-TRX-018-06, ATS-ACC-TRX-018-08 | TST-ACC-TRX-001 (not-run) |
| CAP-ACC-TRX-018 | `BR-CAP-ACC-TRX-018-07` Aging and dataset reads require their corresponding authorities and isolate workspace records. | yes | ATS-ACC-TRX-018-07 | TST-ACC-TRX-001 (not-run), TST-ACC-TRX-120 (not-run) |
| CAP-ACC-TRX-018 | `BR-CAP-ACC-TRX-018-08` Credit applications reduce both invoice and credit open items on their date rather than creating a third item; reversal restores both on its own date. | no |  |  |
| CAP-ACC-TRX-019 | `BR-CAP-ACC-TRX-019-01` A contact or organization without saved terms receives marked defaults, and each party can have at most one saved terms record. | yes | ATS-ACC-TRX-017-08, ATS-ACC-TRX-019-01, ATS-ACC-TRX-019-08 | TST-ACC-TRX-006 (not-run), TST-ACC-TRX-088 (not-run) |
| CAP-ACC-TRX-019 | `BR-CAP-ACC-TRX-019-02` Creation omits a version and replacement requires the version read; duplicate creation and stale saves fail, while omitted settings revert to defaults. | yes | ATS-ACC-TRX-019-02, ATS-ACC-TRX-019-08 | TST-ACC-TRX-088 (not-run) |
| CAP-ACC-TRX-019 | `BR-CAP-ACC-TRX-019-03` Collection choices use fixed vocabularies, allow-lists permit at most fifty unique options with empty meaning unrestricted, and default payment terms must be active within the workspace. | yes | ATS-ACC-TRX-017-08, ATS-ACC-TRX-019-03, ATS-ACC-TRX-019-09 | TST-ACC-TRX-088 (not-run) |
| CAP-ACC-TRX-019 | `BR-CAP-ACC-TRX-019-04` Removing terms restores default behavior, and a stale version prevents deletion. | yes | ATS-ACC-TRX-019-04 | TST-ACC-TRX-088 (not-run) |
| CAP-ACC-TRX-019 | `BR-CAP-ACC-TRX-019-05` Payment terms referenced as a customer default are protected from deletion. | yes | ATS-ACC-TRX-019-05 | TST-ACC-TRX-088 (not-run) |
| CAP-ACC-TRX-019 | `BR-CAP-ACC-TRX-019-06` Terms read and manage authorities are separate, and Commerce can retrieve terms through its billing service at checkout. | yes | ATS-ACC-TRX-019-06, ATS-ACC-TRX-019-08 | TST-ACC-TRX-006 (not-run) |
| CAP-ACC-TRX-019 | `BR-CAP-ACC-TRX-019-07` The product should provide a staff editor for customer terms; the current console only shows them alongside financial standing. | no |  |  |
| CAP-ACC-TRX-019 | `BR-CAP-ACC-TRX-019-08` An update lock blocks replacing or deleting customer terms, while a deletion-only lock blocks removal. | yes | ATS-ACC-TRX-019-07 | TST-ACC-TRX-088 (not-run) |
| CAP-ACC-TRX-020 | `BR-CAP-ACC-TRX-020-01` Commerce authenticates as its own registered service identity through separately restricted billing, tender, reversal and tax functions; unknown identities are denied. | yes | ATS-ACC-TRX-014-09, ATS-ACC-TRX-019-08, ATS-ACC-TRX-020-01, ATS-ACC-TRX-020-09 | TST-ACC-TRX-016 (not-run), TST-ACC-TRX-206 (not-run) |
| CAP-ACC-TRX-020 | `BR-CAP-ACC-TRX-020-02` Service-created records identify the service actor and preserve the originating person when supplied. | yes | ATS-ACC-TRX-001-17, ATS-ACC-TRX-016-08, ATS-ACC-TRX-020-02, ATS-ACC-TRX-020-09 | TST-ACC-TRX-121 (not-run) |
| CAP-ACC-TRX-020 | `BR-CAP-ACC-TRX-020-03` A retry key replays the stored result for the same command body, rejects altered reuse and remains reusable after a refused command commits nothing. | yes | ATS-ACC-TRX-001-17, ATS-ACC-TRX-008-09, ATS-ACC-TRX-014-09, ATS-ACC-TRX-020-03, ATS-ACC-TRX-020-09 | TST-ACC-TRX-052 (not-run), TST-ACC-TRX-223 (not-run) |
| CAP-ACC-TRX-020 | `BR-CAP-ACC-TRX-020-04` Retry-key ownership spans the workspace, preventing another actor from executing an independent command under a used key. | yes | ATS-ACC-TRX-020-04 | TST-ACC-TRX-052 (not-run), TST-ACC-TRX-081 (not-run), TST-ACC-TRX-211 (not-run) |
| CAP-ACC-TRX-020 | `BR-CAP-ACC-TRX-020-05` Racing identical requests execute the financial effect once, although a competing request can receive a lifecycle refusal rather than a replay. | yes | ATS-ACC-TRX-007-12, ATS-ACC-TRX-020-05, ATS-ACC-TRX-020-09 | TST-ACC-TRX-052 (not-run) |
| CAP-ACC-TRX-020 | `BR-CAP-ACC-TRX-020-06` Receivable history records each monetary change and reconstructs both current balances and earlier positions at their known-time cutoff. | yes | ATS-ACC-TRX-016-08, ATS-ACC-TRX-020-06, ATS-ACC-TRX-020-09 | TST-ACC-TRX-043 (not-run) |
| CAP-ACC-TRX-020 | `BR-CAP-ACC-TRX-020-07` Transactional receivable events retry failed configured delivery, but acknowledge and log events when Commerce has no configured receiver. | yes | ATS-ACC-TRX-020-07 | TST-ACC-TRX-031 (not-run), TST-ACC-TRX-032 (not-run) |
| CAP-ACC-TRX-020 | `BR-CAP-ACC-TRX-020-08` Platform-routed processor events are consumed transactionally by identity, so redelivery changes nothing and unrelated or unknown payments are ignored. | yes | ATS-ACC-TRX-007-12, ATS-ACC-TRX-012-12, ATS-ACC-TRX-013-10, ATS-ACC-TRX-020-08, ATS-ACC-TRX-020-09 | TST-ACC-TRX-016 (not-run), TST-ACC-TRX-041 (not-run) |
| CAP-ACC-TRX-020 | `BR-CAP-ACC-TRX-020-09` The order-line position view supplies Commerce with invoiced, settled, credited, refunded and abandoned amounts. | no |  |  |
| CAP-ACC-TRX-020 | `BR-CAP-ACC-TRX-020-10` Accounting still serves Commerce tax quotes despite the recorded transfer of tax determination to Commerce. | no |  |  |
| CAP-ACC-TRX-020 | `BR-CAP-ACC-TRX-020-11` Deletion purges transaction data before dependent configuration and refuses to purge an active workspace. | no |  |  |

## Where Each Capability Lives

| Capability | Repository | Role | Paths |
|---|---|---|---|
| (no capability carries repositories[] yet) | | | |

## Features and Journeys

| Artifact | Proof |
|---|---|
| FEAT-ACC-TRX-01 Invoicing | FAS-ACC-TRX-01 |
| FEAT-ACC-TRX-02 Invoice Adjustments | FAS-ACC-TRX-02 |
| FEAT-ACC-TRX-03 Receiving Payments | FAS-ACC-TRX-03 |
| FEAT-ACC-TRX-04 Credits, Refunds and Returned Money | FAS-ACC-TRX-04 |
| FEAT-ACC-TRX-05 Customer Balances and Receivables Reporting | FAS-ACC-TRX-05 |
| FEAT-ACC-TRX-06 Transaction Records and Connected Systems | FAS-ACC-TRX-06 |
| JNY-ACC-TRX-001 Bill a member and settle the resulting debt | no product acceptance scenario |
| JNY-ACC-TRX-002 Settle with credit and correct receipt placement | no product acceptance scenario |
| JNY-ACC-TRX-003 Collect a phone payment and resolve a missing response | no product acceptance scenario |
| JNY-ACC-TRX-004 Approve an overpayment return and retain the remainder | no product acceptance scenario |
| JNY-ACC-TRX-005 Cancel paid ticket value and follow its return | no product acceptance scenario |
| JNY-ACC-TRX-006 Bill, collect and unwind an order through service calls | no product acceptance scenario |

## Gaps

- none