--- id: FAS-ACC-CLS-02 title: Readiness Review acceptance feature: FEAT-ACC-CLS-02 product_area: accounting module: close revision: 1 status: proposed product_intent: proposed source_sha: services-accounting: f47cb263875bbc0c5640fba7dae6785ec32695f8 react-console: baf6dae382d6f41dce976c7f848667ccc37e076f capabilities: - CAP-ACC-CLS-004 - CAP-ACC-CLS-005 - CAP-ACC-CLS-006 - CAP-ACC-CLS-007 scenarios: - id: FAS-ACC-CLS-02-01 title: Clear ledger causes through the combined review kind: behaviour exercises: - CAP-ACC-CLS-004 - CAP-ACC-CLS-005 relies_on: - ATS-ACC-CLS-004-01 - ATS-ACC-CLS-005-02 - ATS-ACC-CLS-005-03 preconditions: >- An ended month has open, archived and failed batches with unposted documents. steps: >- Inspect both ledger checks, resolve the batches and post the documents, then reread the overall review. expected: >- Both ledger sections clear and the whole review permits closing when no other required work remains. negative: false data_needs: >- An ended month has open, archived and failed batches with unposted documents. bound_to: [] provenance: proposed source: >- react-console:acceptance/accounting/playwright/journeys/reconciliation-close/ACT-ACC-0616.spec.ts#ACT-ACC-0616 finding: FND-ACC-CLS-076 binding_note: >- The source journey contains the intended assertions, but an earlier expectation conflicts with the pinned service; the complete chain is not established. - id: FAS-ACC-CLS-02-02 title: Expose finalized payment work that has not reached the ledger kind: interaction exercises: - CAP-ACC-CLS-004 - CAP-ACC-CLS-006 relies_on: - ATS-ACC-CLS-004-01 - ATS-ACC-CLS-006-01 preconditions: >- A clean month receives a payout finalized through reconciliation while its required posting remains incomplete. steps: >- Compare payment readiness before and after payout finalization; inspect the combined review and submit a direct close. expected: >- Finalization replaces the payout finding with incomplete-posting blockers; the combined review is not ready and execution fails revalidation. negative: true data_needs: >- A clean month receives a payout finalized through reconciliation while its required posting remains incomplete. bound_to: [] provenance: proposed source: >- react-console:acceptance/accounting/playwright/journeys/reconciliation-close/ACT-ACC-0626.spec.ts#ACT-ACC-0626 finding: FND-ACC-CLS-079 binding_note: >- The source journey expects operational posting to leave reconciliation requests incomplete, although the pinned posting implementation supports reconciliation entries. Its later close-refusal chain is not established as executable proof. - id: FAS-ACC-CLS-02-03 title: Review corrections and due revenue after reopening kind: lifecycle exercises: - CAP-ACC-CLS-004 - CAP-ACC-CLS-005 - CAP-ACC-CLS-007 relies_on: - ATS-ACC-CLS-005-03 - ATS-ACC-CLS-007-01 preconditions: >- The latest closed month is reopened and receives a correction invoice with deferred revenue. steps: >- Review its unposted batch and transaction, complete posting, then reread the whole review and recognition preview. expected: >- Ledger checks pass after correction posting and the recognition preview shows the due share; the overall review is ready. negative: false data_needs: >- The latest closed month is reopened and receives a correction invoice with deferred revenue. bound_to: - TST-ACC-CLS-002 provenance: test source: >- react-console:acceptance/accounting/playwright/journeys/reconciliation-close/ACT-ACC-0614.spec.ts#ACT-ACC-0614 - id: FAS-ACC-CLS-02-04 title: Keep financial evidence stable while caller authority changes kind: permission exercises: - CAP-ACC-CLS-004 - CAP-ACC-CLS-005 - CAP-ACC-CLS-006 - CAP-ACC-CLS-007 relies_on: - ATS-ACC-CLS-004-07 - ATS-ACC-CLS-006-01 - ATS-ACC-CLS-007-01 preconditions: A clean ended month is read by a reader and an authorized closer. steps: Compare every check for both callers and inspect the close control. expected: >- The financial checks have the same outcomes; the authority check changes the overall verdict and whether Close is usable. negative: true data_needs: A clean ended month is read by a reader and an authorized closer. bound_to: - TST-ACC-CLS-007 provenance: test source: >- react-console:acceptance/accounting/playwright/journeys/reconciliation-close/ACT-ACC-0619.spec.ts#ACT-ACC-0619 - id: FAS-ACC-CLS-02-05 title: Preserve warning classification across payment and recognition review kind: regression exercises: - CAP-ACC-CLS-004 - CAP-ACC-CLS-006 - CAP-ACC-CLS-007 relies_on: - ATS-ACC-CLS-004-02 - ATS-ACC-CLS-006-03 - ATS-ACC-CLS-007-02 preconditions: >- A month has an advisory bank-verification warning and due multi-currency schedules, including a future entry. steps: >- Review all sections with verification advisory, then make verification required and reread the combined review. expected: >- The advisory concern permits warning review; requiring verification introduces a required blocker without changing the recognition date or currency calculations. negative: true data_needs: >- A month has an advisory bank-verification warning and due multi-currency schedules, including a future entry. bound_to: [] provenance: proposed source: - ATS-ACC-CLS-004-02 - ATS-ACC-CLS-006-03 - ATS-ACC-CLS-007-02 finding: FND-ACC-CLS-075 evidence: - >- Testing hierarchy: Andrew ruling of 2026-10-23, rhythm-v2-docs:specs/CONVENTIONS.md#5.3 Feature Acceptance Suite. - >- react-console:acceptance/accounting/playwright/journeys/reconciliation-close/ACT-ACC-0616.spec.ts#ACT-ACC-0616 - >- react-console:acceptance/accounting/playwright/journeys/reconciliation-close/ACT-ACC-0626.spec.ts#ACT-ACC-0626 - >- react-console:acceptance/accounting/playwright/journeys/reconciliation-close/ACT-ACC-0614.spec.ts#ACT-ACC-0614 - >- react-console:acceptance/accounting/playwright/journeys/reconciliation-close/ACT-ACC-0619.spec.ts#ACT-ACC-0619 - ATS-ACC-CLS-004-02 - ATS-ACC-CLS-006-03 - ATS-ACC-CLS-007-02 --- # Readiness Review: Feature Acceptance Suite ## What the Feature Must Do as a Whole This suite examines the combined readiness review rather than treating each checklist section as a separate outcome. It connects ledger completion, payment assessment, recognition preview and caller authority. A controller uses the review to understand outstanding work before requesting a close, including changes introduced by correction. ## Interactions Between Capabilities The bound correction case connects posting completion to cleared ledger checks and a due-revenue preview. The authority case compares the same financial work for a reader and closer. The incomplete-payment chain remains proposed because its source journey assumes obsolete posting behavior. Warning-policy changes and the broader ledger-resolution chain also retain explicit gaps. ## Regression Record | Revision | Change | Scenarios | Why | |---|---|---|---| | 1 | initial | all | Specify the feature’s combined outcomes and distinguish executable assertions from proposed chains. |