The table maps each required rule to its specified cases or an explicit finding. Category coverage describes the specification; executable bindings and recorded run results establish different kinds of evidence. Proposed cases remain unqualified.
Aging belongs to Reporting, while closing requests and retains its reference. The interaction cases compare that request with the closed month and later correction. Request creation is distinct from completed report computation, and the nonwaiting product expectation remains unproved.
Coverage
Rulegap: FND-ACC-CLS-071
Transitioncovered
Validationgap: FND-ACC-CLS-071
Permissionnot-applicable
Edgegap: FND-ACC-CLS-071
Failurecovered
Boundarycovered
Concurrencygap: FND-ACC-CLS-071
Invariantgap: FND-ACC-CLS-071
Interactioncovered
Test Scenarios
5 scenarios proving CAP-ACC-CLS-015; 2 bound to an existing test.
01Request reconstructed aging during partial closureinteractionapitest
Two units overlap the same calendar month and one remains open.
Steps
Close the first unit, inspect its captured close outputs and aging request, then reopen and close it again.
Expected
Each close records its own requested version and basis; a requested version is distinguishable from completed report computation.
Data
Two units overlap the same calendar month and one remains open.
Source
rhythm-v2-docs:specs/accounting/close/design/workflows/WF-ACC-CLS-001-close-a-month.md#What It Does,services-accounting:modules/fiscal-close/tests/integration/services/jobs/close-job.integration.spec.js#requests the A/R aging snapshot of September, reconstructed while gamma still has September open,services-accounting:modules/fiscal-close/tests/integration/services/jobs/close-job.integration.spec.js#requests the A/R aging snapshot of September, reconstructed while gamma still has September open,services-accounting:modules/fiscal-close/services/jobs/fiscal-close-job-tasks.ts:finalizeClose
05Exhaust contention without a completed closefailureapinegativeproposed