Period Calendar and Posting Protection: Feature Acceptance Suite
What the Feature Must Do as a Whole
A clean ended current month is viewed by a closer. Read its calendar and actions, close it, then read both again. The completed month is no longer current, the following month becomes current and the completed month can be considered for reopening.
Interactions Between Capabilities
Try posting an ordinary batch with the closed date, move it to the following month, post it, then finalize a reconciliation dated in the closed month. The ordinary refusal leaves no ledger entries; moving the batch permits posting and eligible reconciliation carries a late marker into the following month. The month is current and open with cleared close stamps and an incremented correction count; ordinary correction work can now post. The suite also covers changes in authority and the regression cases that cross these boundaries. Unbound chains remain proposed. The identified executable candidates are recorded in structured evidence until the checker can accept feature-scenario bindings.
Regression Record
| Revision | Change | Scenarios | Why |
|---|---|---|---|
| 1 | initial | all | Establish cumulative acceptance from the landed feature, capability and design evidence. |