Request receivables aging for the closed month

Purpose

A completed close requests a month-end aging version using the information known at its closing instant.

How It Works

The closing step requests an aging version for the calendar month containing period end. It uses the close instant as the known-at boundary. The request replaces prior versions and explains which month and business unit caused it. Another unit’s overlapping open period makes the requested basis reconstructed. When none remains, the request uses finalized basis. An active aging run currently rolls back finalization and causes a timed wait. The month remains closing while the workflow attempts that step again. The approved plan calls for a different interaction. The product should finish the close without waiting and show requested or ready status. The deployment-contract concern remains documented evidence requiring resolution beyond this module’s pinned code.

Relationships

Finalization makes the aging request with the completed close.
The close record is the separate retained evaluation of that same close.

Show evidence (sources, provenance, origins, pinned commits)

The Formal Contract

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

Outcomes: Reporting receives an aging request tied to the close.The requested basis distinguishes partial workspace closure from closure across all units.
Surfaces: job
Constraints: Transactions owns the aging type and Platform supplies the snapshot ledger.
Intent sources: services-accounting:docs/milestones/plans/ACCT-M4-plan.md#D8. Closing a fiscal period: the closer's name, the A/R snapshot and how long it may take

Controls

20 controls apply, from the corpus control catalogue.

TC-IAM-001 TC-IAM-005 TC-IAM-006 TC-AZ-001 TC-AZ-002 TC-AZ-003 TC-AZ-004 TC-TEN-001 TC-TEN-002 TC-TEN-003 TC-DAT-001 TC-AVL-001 TC-AVL-004 TC-MON-001 TC-MON-002 TC-MON-004 TC-PI-002 TC-PI-003 TC-PI-004 TC-PI-005

Business Rules

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

Id	Rule	Kind	Enforced at	Provenance
`01`must prove Confirmed	Finalization requests a superseding receivables aging version for calendar month end, known at the close instant and explained by the month and unit. origin: Snapshot Architecture agreement of 2026-10-16 (PHASE-2-PLAN §4.1) proved by `ATS-ACC-CLS-015-01`, `ATS-ACC-CLS-015-04`, `TST-ACC-CLS-021`	policy	service	test services-accounting:modules/fiscal-close/tests/integration/services/jobs/close-job.integration.spec.js#requests the A/R aging snapshot of September, reconstructed while gamma still has September open
`02`must prove Confirmed	The requested basis is finalized only when every other unit’s overlapping period is closed; otherwise it is reconstructed. origin: Snapshot Architecture agreement of 2026-10-16 (PHASE-2-PLAN §4.1) proved by `ATS-ACC-CLS-015-01`, `ATS-ACC-CLS-015-04`, `TST-ACC-CLS-021`	calculation	service	test services-accounting:modules/fiscal-close/tests/integration/services/jobs/close-job.integration.spec.js#requests the A/R aging snapshot of September, reconstructed while gamma still has September open
`03`must prove Confirmed	The product should complete closing without waiting for aging and show whether the requested snapshot is pending or ready. ✗ An existing active aging run currently delays finalization. origin: services-accounting:docs/milestones/plans/ACCT-M4-plan.md#D8. Closing a fiscal period: the closer's name, the A/R snapshot and how long it may take proved by `ATS-ACC-CLS-015-02`	policy		documented services-accounting:docs/milestones/plans/ACCT-M4-plan.md#D8. Closing a fiscal period: the closer's name, the A/R snapshot and how long it may take
`04`must prove Confirmed	The current workflow waits sixty seconds before another finalization attempt when an aging run for the month is active, repeating within its sixty-iteration limit. proved by `ATS-ACC-CLS-015-03`, `ATS-ACC-CLS-015-05`, `TST-ACC-CLS-049`	policy	service	test services-accounting:tests/aws/fiscal-close.synth.ts#waits 60 s in a Wait state before finalize asks again for the month’s A/R snapshot
`05` Confirmed	The approved plan records a deployment-contract concern under which a close-trigger request may fail to produce an aging run.	policy	service	documented services-accounting:docs/milestones/plans/ACCT-M4-plan.md#D8. Closing a fiscal period: the closer's name, the A/R snapshot and how long it may take
`06` Confirmed	Finalization retains the requested aging run, version and basis in its output. proved by `ATS-ACC-CLS-015-04`	policy	service	observed services-accounting:modules/fiscal-close/services/jobs/fiscal-close-job-tasks.ts:finalizeClose

Scenarios

Id	Given	When	Then	Provenance
`01`	One unit closes September while another unit still has an overlapping period open.	The first unit finalizes its close.	The aging request uses reconstructed basis; complete workspace closure is the condition for finalized basis.	test services-accounting:modules/fiscal-close/tests/integration/services/jobs/close-job.integration.spec.js#requests the A/R aging snapshot of September, reconstructed while gamma still has September open
`02`	An aging run for September is active.	A September close reaches finalization.	The month remains closing while finalization waits and requests again within the workflow limit.	test services-accounting:tests/aws/fiscal-close.synth.ts#waits 60 s in a Wait state before finalize asks again for the month’s A/R snapshot

Planning

Implementation

Request receivables aging for the closed month ​

Purpose ​

How It Works ​

Relationships ​