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.
The combined review joins calendar, ledger, payment and recognition assessments. Its interaction case changes underlying work after an earlier review and asks for a fresh assessment before execution. A standalone review does not establish a stable financial snapshot across concurrent changes.
Coverage
Rulecovered
Transitionnot-applicable
Validationgap: FND-ACC-CLS-060
Permissioncovered
Edgegap: FND-ACC-CLS-060
Failurecovered
Boundarycovered
Concurrencygap: FND-ACC-CLS-060
Invariantcovered
Interactioncovered
Test Scenarios
10 scenarios proving CAP-ACC-CLS-004; 9 bound to an existing test.
01Compute verdicts without treating absence as successruleunittest
An ended month has ledger work, a payment finding and a due schedule with incomplete accounts.
Steps
Review each supporting section; resolve those causes, reread readiness, then change ledger evidence before the job revalidates.
Expected
The overall review responds to each section, and execution uses its own evaluation rather than the earlier screen result.
Data
An ended month has ledger work, a payment finding and a due schedule with incomplete accounts.
Source
rhythm-v2-docs:specs/accounting/close/design/workflows/WF-ACC-CLS-005-evaluate-a-month-s-close-readiness.md#What It Does,services-accounting:modules/fiscal-close/tests/unit/readiness/readiness-verdict.spec.js#is not ready for a required check pending: missing evidence never passes,services-accounting:modules/fiscal-close/tests/unit/readiness/readiness-verdict.spec.js#lists a month’s close in order,services-accounting:docs/fiscal-close/README.md#3. Readiness checks (month-end)
09Refuse readiness without read authoritypermissionapinegativetest