Follow a final-month close into the next calendar year. Read the current month and its authorization; close it, then read the calendar and execution history. The final month’s result agrees with year standing, the next current month and the recorded run. The interaction scenario names related capabilities and the workflows it exercises in its structured evidence.
Coverage
Rulecovered
Transitioncovered
Validationcovered
Permissioncovered
Edgegap: FND-ACC-CLS-057
Failuregap: FND-ACC-CLS-057
Boundarycovered
Concurrencygap: FND-ACC-CLS-057
Invariantcovered
Interactioncovered
Test Scenarios
8 scenarios proving CAP-ACC-CLS-001; 5 bound to an existing test.
01Locate the current period across yearsruleapitest
A unit has eleven closed months and a clean final month, with future years available.
Steps
Read the current month and its authorization; close it, then read the calendar and execution history.
Expected
The final month’s result agrees with year standing, the next current month and the recorded run.
Data
A unit has eleven closed months and a clean final month, with future years available.
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/periods/period-calendar.integration.spec.js#marks the first period not closed current, the next year’s January,services-accounting:modules/fiscal-close/tests/integration/services/persistence/fiscal-periods.integration.spec.js#becomes closed exactly when its twelfth period closes
07Read calendars on each side of the year limitboundaryapinegativeproposed