Rhythm 2.0 Specifications

Appearance

CAP-ACC-CLS-005Resolve ledger work that prevents closing

Markdown

CAP-ACC-CLS-005

Resolve ledger work that prevents closing

Markdown
  • DocumentDraft
  • Product intentConfirmed
  • ImplementationObserved

Planning

Feature
FEAT-ACC-CLS-02
Exercised by
FAS-ACC-CLS-02-01, FAS-ACC-CLS-02-03, FAS-ACC-CLS-02-04
Key concepts
CON-ACC-CLS-002
Actors
ACT-ACC-015, ACT-ACC-012
Journeys
JNY-ACC-CLS-002
Depends on
CAP-ACC-CLS-004
Related
CAP-ACC-CLS-003
Proved by
ATS-ACC-CLS-005

Implementation

Executable suites
TST-ACC-CLS-004, TST-ACC-CLS-035, TST-ACC-CLS-036, TST-ACC-CLS-038, TST-ACC-CLS-041, TST-ACC-CLS-043, TST-ACC-CLS-046

KindCapabilityProduct areaAccountingModuleMonth-End ClosingRevision1

Read atservices-accounting f47cb263react-console baf6dae3

Resolve ledger work that prevents closing ​

Purpose ​

Finance staff identify unfinished period and ledger work before the posting boundary becomes final.

How It Works ​

The controller first addresses calendar work before tackling ledger work. The checklist identifies earlier periods that remain outstanding and shows whether the selected month has ended. Batch results explain what to do for each unposted state. Archived batches require restoration and posting. The close’s own system batches are excluded so a reopened month can close again. Transaction results identify documents without a suitable posted batch. Each item distinguishes an absent batch from unfinished or failed posting. Staff open those records, resolve the cause and evaluate readiness again. Customer names are currently absent from these results.

Relationships ​

  • Readiness combines these checks with the other closing conditions.
  • The posting boundary protects the period after this outstanding work is resolved.

The Formal Contract

The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.

Outcomes
The checklist exposes transactions that have not reached a posted batch.Staff can locate each outstanding record and the work it requires.
Surfaces
consoleapi
Intent sources
services-accounting:docs/milestones/plans/ACCT-M4-plan.md#4a row 73 (class A: period ended, batches posted, transactions accounted)

Controls

18 controls apply, from the corpus control catalogue.

TC-IAM-001 TC-IAM-002 TC-IAM-004 TC-IAM-005 TC-AZ-001 TC-AZ-002 TC-AZ-003 TC-AZ-004 TC-AZ-006 TC-TEN-001 TC-TEN-002 TC-TEN-003 TC-LOG-002 TC-LOG-003 TC-LOG-004 TC-PI-001 TC-PI-002 TC-PI-005

Permissions

KeyChecked atScope
accounting.fiscal-periods.readapitenant

Business Rules

9 rules, 8 to be proved before approval. A rule's product intent is derived from its origin: 9 confirmed by a product decision, the rest inheriting this capability's confirmed.

IdRuleKindEnforced atProvenance
01must prove
Confirmed
The prior-periods check blocks for every earlier month that is not closed and presents those months in date order.
origin: fiscal-close design L2 (Rhythm 1.0 CLOSE-2 kept)
proved by ATS-ACC-CLS-005-01, TST-ACC-CLS-043
validationservicetest
services-accounting:modules/fiscal-close/tests/unit/readiness/period-rules.spec.js#is blocked by a period of an earlier year, and counts every one oldest first
02must prove
Confirmed
The ended-period check passes only after the month’s final day in the workspace time zone and identifies the first eligible closing date.
✓ September becomes eligible for the ended-period check on October’s first day.✗ The final day of September still fails the ended-period check.
origin: services-accounting:docs/milestones/plans/ACCT-M4-plan.md#4a row 73 (class A: period ended; departs from Rhythm 1.0, design R1)
proved by ATS-ACC-CLS-005-01, TST-ACC-CLS-043
validationservicetest
services-accounting:modules/fiscal-close/tests/unit/readiness/period-rules.spec.js#is blocked on the period’s last day
03must prove
Confirmed
The batches check blocks for batches in the period that are neither posted nor downloaded and includes their count in its explanation.
origin: services-accounting:docs/milestones/plans/ACCT-M4-plan.md#4a row 73 (class A: batches posted)
proved by ATS-ACC-CLS-005-02, ATS-ACC-CLS-005-04, ATS-ACC-CLS-005-05, TST-ACC-CLS-004, TST-ACC-CLS-036, TST-ACC-CLS-038, TST-ACC-CLS-041
validationservicetest
services-accounting:modules/fiscal-close/tests/integration/services/readiness/evaluate-readiness.integration.spec.js#blocks on each failing check with its headline: 23 batches must be posted
04must prove
Confirmed
Archived batches prevent closure even though the earlier product allowed them.
origin: fiscal-close FC2-3 departure (archived batches block; no recorded ruling)
proved by ATS-ACC-CLS-005-02, ATS-ACC-CLS-005-04, TST-ACC-CLS-004, TST-ACC-CLS-036, TST-ACC-CLS-038, TST-ACC-CLS-041
validationservicetest
services-accounting:modules/fiscal-close/tests/unit/carried/fiscal-years/logic/validate-period-closing-batches.spec.js#2.0: is blocked by the archived batch of 1.0's baseline, which 1.0 let through
05must prove
Confirmed
Outstanding batches identify the next action for their state, including closing, posting, waiting, retrying or restoring.
proved by ATS-ACC-CLS-005-02, TST-ACC-CLS-036, TST-ACC-CLS-038, TST-ACC-CLS-041
policyservicetest
services-accounting:modules/fiscal-close/tests/unit/readiness/batches-posted.spec.js#names the action each unposted status requires
06must prove
Confirmed
Deferred revenue and cost of goods sold system batches owned by the close are excluded from outstanding batches, including after reopening.
proved by ATS-ACC-CLS-005-02, TST-ACC-CLS-036, TST-ACC-CLS-038, TST-ACC-CLS-041
policyservicetest
services-accounting:modules/fiscal-close/tests/unit/readiness/batches-posted.spec.js#never counts the close’s own open system batches, deferred revenue and COGS, as unposted
07must prove
Confirmed
The transactions check includes eligible invoices, payments, credits, credit applications, refunds, memos and write-offs dated in the period when their batch is absent, unposted or failed; draft and pro forma invoices are excluded.
origin: services-accounting:docs/milestones/plans/ACCT-M4-plan.md#4a row 73 (class A: transactions accounted)
proved by ATS-ACC-CLS-005-03, ATS-ACC-CLS-005-04, ATS-ACC-CLS-005-05, TST-ACC-CLS-004, TST-ACC-CLS-035, TST-ACC-CLS-046
validationservicetest
services-accounting:modules/fiscal-close/tests/integration/services/persistence/unaccounted-transactions.queries.integration.spec.js#answers every kind, mapped whole, by date with each reason
08must prove
Confirmed
Each outstanding transaction identifies its posting problem and links to the corresponding record.
proved by ATS-ACC-CLS-005-03, TST-ACC-CLS-035, TST-ACC-CLS-046
policyservicetest
services-accounting:modules/fiscal-close/tests/unit/readiness/transactions-accounted.spec.js#routes each kind to its own record
09
Confirmed
Outstanding transactions return no customer name in the current readiness response.
policyserviceobserved
services-accounting:modules/fiscal-close/services/readiness/transactions-accounted.ts:ruleTransactionsAccounted

Scenarios

IdGivenWhenThenProvenance
01September contains twenty-three open batches and an invoice without a batch.Readiness runs on October’s third day.Batch and transaction checks expose the outstanding work while the ended-period check passes.test
services-accounting:modules/fiscal-close/tests/integration/services/readiness/evaluate-readiness.integration.spec.js#names the open earlier period, the unaccounted invoice and reconciliation’s blocker unchanged
02October’s final day has not passed.Staff evaluate October.The ended-period check prevents closure until November’s first day.test
services-accounting:modules/fiscal-close/tests/integration/services/readiness/evaluate-readiness.integration.spec.js#blocks October, which has not ended

The Markdown files under specs/ in rhythmsoftware/rhythm-v2-docs are the canonical source of truth. This reader is a generated, read-only projection of them.

Rhythm Software