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.
Payment review feeds both the readiness verdict and retained close evidence. The proposed sequence carries the assessed context into a successful close and examines later reconciliation separately. An additional specified interaction follows incomplete payment posting into execution revalidation.
Coverage
Rulecovered
Transitionnot-applicable
Validationgap: FND-ACC-CLS-062
Permissioncovered
Edgegap: FND-ACC-CLS-062
Failurecovered
Boundarycovered
Concurrencygap: FND-ACC-CLS-062
Invariantgap: FND-ACC-CLS-062
Interactioncovered
Test Scenarios
8 scenarios proving CAP-ACC-CLS-006; 6 bound to an existing test.
01Preserve reconciliation findings and timing figuresruleunitnegativetest
An ended month has accepted payment exceptions and a following open month.
Steps
Review payment findings; close the month, read its captured payment context, then finalize an eligible late reconciliation effect.
Expected
Retained context describes the evaluated close; the late effect uses the following open month and cannot rewrite the captured evidence.
Data
An ended month has accepted payment exceptions and a following open month.
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/unit/readiness/reconciliation-checks.spec.js#is blocked by a blocker, its findings the items unchanged, blockers first,services-accounting:modules/fiscal-close/tests/unit/readiness/reconciliation-checks.spec.js#names the display state from the findings, worst first
06Change bank-verification policy only as an administratorpermissionbrowsernegativeproposed