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.
Move an unposted invoice and receipt to another eligible batch, inspect actions, then post the destination and attempt invoice amendment and another move.
The earlier moves retain financial value; current eligibility refuses amendment and movement after posting even if a previously read action was enabled. The complete chain remains proposed until one executable run proves its combined outcomes.
Coverage
Rulecovered
Transitioncovered
Validationcovered
Permissioncovered
Edgecovered
Failuregap: FND-ACC-TRX-080
Boundarygap: FND-ACC-TRX-080
Concurrencygap: FND-ACC-TRX-080
Invariantcovered
Interactioncovered
Test Scenarios
9 scenarios proving CAP-ACC-TRX-015; 8 bound to an existing test.
Batches span open, error, closed, posted, period-close and foreign-unit cases.
Steps
[
{
"do": "Check invoice, memo and write-off destinations.",
"provenance": "test",
"source": "services-accounting:modules/transactions/tests/integration/services/batches-for-documents.integration.spec.js#it refuses a system batch, which is period close’s: a transaction batch only (batch_not_open)"
}
]
Expected
Only open and error transaction destinations qualify.
[
{
"do": "Create without explicit batches, close the selected memo batch and create again.",
"provenance": "test",
"source": "services-accounting:modules/transactions/tests/integration/services/batches-for-documents.integration.spec.js#it is refused batch_required once the chosen recurring batch’s active batch is closed (BA-12), naming the reason"
}
]
Expected
Default and kind-specific choices apply, then the closed assignment fails with explanation.
Supported records exist in open and posted batches.
Steps
[
{
"do": "Move eligible records, move into and out of posted context and reselect the current batch.",
"provenance": "test",
"source": "services-accounting:modules/transactions/tests/integration/services/document-edits/reassign-and-edit.integration.spec.js#it is refused batch_not_open on a reassignment out of the batch"
}
]
[
{
"do": "Move the payment and replay its request.",
"provenance": "test",
"source": "services-accounting:modules/transactions/tests/integration/services/document-edits/reassign-and-edit.integration.spec.js#it moves the allocation rows batched with it"
}
]
Expected
Applications move with one event and no receivable difference; replay adds nothing.
[
{
"do": "Change reference and notes, clear optional memo and attempt to clear the credit reason while editing its memo.",
"provenance": "test",
"source": "services-accounting:modules/transactions/tests/integration/services/document-edits/reassign-and-edit.integration.spec.js#it never clears a required field (a credit’s reason), and changes its memo"
}
]
Expected
Payment text changes without money movement; the required reason survives and valid memo changes remain.
An unposted payment and memo face open and uncovered dates.
Steps
[
{
"do": "Move their dates and read historical positions, then select the uncovered period.",
"provenance": "test",
"source": "services-accounting:modules/transactions/tests/integration/services/document-edits/reassign-and-edit.integration.spec.js#it negates the facts on the old accounting date and restates them on the new one, the originals untouched"
}
]
Expected
Opposing entries relocate the position; invalid period selection fails.
[
{
"do": "Request batch and descriptive corrections.",
"provenance": "test",
"source": "services-accounting:modules/transactions/tests/e2e/payments.e2e.spec.js#it is refused the batch and details routes without accounting.payments.update (403)"
}
]
An isolated workspace has eligible customers, products, matching accounts, an open period and two open batches. Each branch owns separate financial records.
Steps
[
{
"do": "Move an unposted invoice and receipt to another eligible batch, inspect actions, then post the destination and attempt invoice amendment and another move.",
"provenance": "proposed",
"source": "services-accounting:modules/transactions/tests/integration/services/batches-for-documents.integration.spec.js#it refuses a system batch, which is period close’s: a transaction batch only (batch_not_open); services-accounting:modules/transactions/tests/integration/services/document-edits/reassign-and-edit.integration.spec.js#it is refused batch_not_open on a reassignment out of the batch; services-accounting:modules/transactions/tests/integration/services/document-edits/reassign-and-edit.integration.spec.js#it moves the allocation rows batched with it; rhythm-v2-docs:specs/accounting/transactions/design/workflows/WF-ACC-TRX-002-amend-re-date-or-void-an-issued-invoice.md#WF-ACC-TRX-002; rhythm-v2-docs:specs/accounting/transactions/design/workflows/WF-ACC-TRX-017-move-a-document-to-another-batch-and-correct-its-details.md#WF-ACC-TRX-017; rhythm-v2-docs:specs/accounting/transactions/planning/capabilities/CAP-ACC-TRX-015-move-a-transaction-to-another-batch-and-correct-its-details.md#BR-CAP-ACC-TRX-015-01; rhythm-v2-docs:specs/accounting/transactions/planning/capabilities/CAP-ACC-TRX-015-move-a-transaction-to-another-batch-and-correct-its-details.md#BR-CAP-ACC-TRX-015-03; rhythm-v2-docs:specs/accounting/transactions/planning/capabilities/CAP-ACC-TRX-015-move-a-transaction-to-another-batch-and-correct-its-details.md#BR-CAP-ACC-TRX-015-04; rhythm-v2-docs:specs/accounting/transactions/planning/capabilities/CAP-ACC-TRX-002-correct-or-cancel-an-issued-invoice-before-its-batch-posts.md#BR-CAP-ACC-TRX-002-04; 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-01; 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-02"
}
]
Expected
The earlier moves retain financial value; current eligibility refuses amendment and movement after posting even if a previously read action was enabled.
Data
Separate command keys, two customers, invoice lines, receipts and credit; controlled processor outcomes and a fixed calendar where the branch requires them.