The structured coverage map distinguishes specified examples from missing category coverage. Every required rule names its proving scenarios in the structured rule coverage register. A scenario’s executable binding applies only to the cited assertions; the transition and permission registers retain the combinations that still need explicit proof.
Set customer-default terms, create an 80.00 bill, inspect its transaction row and current summary, then capture month-end aging. Record a backdated 20.00 reduction after the cutoff and read both surfaces again.
Terms establish the due date used for overdue classification; current debt becomes 60.00 while the earlier capture remains 80.00; current transaction rows agree with the summary. The complete chain remains proposed until one executable run proves its combined outcomes.
Coverage
Rulecovered
Transitionnot-applicable
Validationcovered
Permissioncovered
Edgegap: FND-ACC-TRX-082
Failuregap: FND-ACC-TRX-082
Boundarycovered
Concurrencygap: FND-ACC-TRX-082
Invariantcovered
Interactioncovered
Test Scenarios
8 scenarios proving CAP-ACC-TRX-017; 6 bound to an existing test.
01Summary currency groups reconcile with open itemsinvariantapitest
USD and EUR bills coexist with held receipts and credit.
Steps
[
{
"do": "Request current standing.",
"provenance": "test",
"source": "services-accounting:modules/transactions/tests/integration/services/customers/customer-summary.integration.spec.js#it answers, as of today, its two open invoices (owing 9000), the overdue one (4000), the check’s 1000 unapplied, the 1500 credit, a net position of 6500"
}
]
Expected
Currency groups separately explain debt, overdue value, money and net position consistent with as-of items.
[
{
"do": "Calculate the customer summary.",
"provenance": "test",
"source": "services-accounting:modules/transactions/tests/unit/rules/customer-summary.spec.js#it counts an invoice due today as not yet overdue, and one due yesterday as overdue"
}
]
Expected
Only the earlier date contributes to overdue debt.
One contact has primary affiliation and another only secondary affiliation.
Steps
[
{
"do": "Read summaries and payable populations.",
"provenance": "test",
"source": "services-accounting:modules/transactions/tests/integration/services/customers/customer-summary.integration.spec.js#it keeps the contact’s figures its own: Acme’s invoices are not counted in Ivy’s summary (1.0’s balances.js)"
}
]
Expected
Own summary excludes organization debt; primary payables include it and secondary payables do not.
Required-fee billing includes a single bill and two customer bills.
Steps
[
{
"do": "Quote card, check and combined customer tender.",
"provenance": "test",
"source": "services-accounting:modules/transactions/tests/integration/services/invoices/payable-invoices.integration.spec.js#it quotes the card fee of a required invoice by its unit’s rule, on the balance or on the amount tendered, and none for a check"
}
]
Expected
Balance or requested tender determines the card fee, check adds none and combined value pays one fee.
One identity lacks read authority and a customer has no open items.
Steps
[
{
"do": "Request each summary.",
"provenance": "test",
"source": "services-accounting:modules/transactions/tests/e2e/customer-summary.e2e.spec.js#it reads with accounting.invoices.read alone and refuses a principal without it (403 permission_missing)"
}
]
Expected
Unauthorized request fails and authorized empty standing returns no currency groups.
An isolated workspace has eligible customers, products, matching accounts, an open period and two open batches. Each branch owns separate financial records.
Steps
[
{
"do": "Set customer-default terms, create an 80.00 bill, inspect its transaction row and current summary, then capture month-end aging. Record a backdated 20.00 reduction after the cutoff and read both surfaces again.",
"provenance": "proposed",
"source": "services-accounting:modules/transactions/tests/integration/services/customers/customer-summary.integration.spec.js#it answers, as of today, its two open invoices (owing 9000), the overdue one (4000), the check’s 1000 unapplied, the 1500 credit, a net position of 6500; services-accounting:modules/transactions/tests/unit/rules/customer-summary.spec.js#it counts an invoice due today as not yet overdue, and one due yesterday as overdue; rhythm-v2-docs:specs/accounting/transactions/planning/capabilities/CAP-ACC-TRX-017-know-where-a-customer-stands.md#BR-CAP-ACC-TRX-017-01; rhythm-v2-docs:specs/accounting/transactions/planning/capabilities/CAP-ACC-TRX-017-know-where-a-customer-stands.md#BR-CAP-ACC-TRX-017-02; rhythm-v2-docs:specs/accounting/transactions/planning/capabilities/CAP-ACC-TRX-016-find-transactions-and-see-what-can-be-done-next.md#BR-CAP-ACC-TRX-016-06; rhythm-v2-docs:specs/accounting/transactions/planning/capabilities/CAP-ACC-TRX-018-report-receivables-at-a-past-month-end.md#BR-CAP-ACC-TRX-018-02; rhythm-v2-docs:specs/accounting/transactions/planning/capabilities/CAP-ACC-TRX-018-report-receivables-at-a-past-month-end.md#BR-CAP-ACC-TRX-018-05; rhythm-v2-docs:specs/accounting/transactions/planning/capabilities/CAP-ACC-TRX-019-record-a-customer-s-collection-terms.md#BR-CAP-ACC-TRX-019-01; rhythm-v2-docs:specs/accounting/transactions/planning/capabilities/CAP-ACC-TRX-019-record-a-customer-s-collection-terms.md#BR-CAP-ACC-TRX-019-03"
}
]
Expected
Terms establish the due date used for overdue classification; current debt becomes 60.00 while the earlier capture remains 80.00; current transaction rows agree with the summary.
Data
Separate command keys, two customers, invoice lines, receipts and credit; controlled processor outcomes and a fixed calendar where the branch requires them.