Rhythm 2.0 Specifications

Appearance

CAP-ACC-BAT-005Arrange automatic close and posting

Markdown

CAP-ACC-BAT-005

Arrange automatic close and posting

Markdown
  • DocumentDraft
  • Product intentProposed
  • ImplementationObserved

Planning

Feature
FEAT-ACC-BAT-01
Exercised by
FAS-ACC-BAT-01-03
Key concepts
CON-ACC-BAT-001, CON-ACC-BAT-003
Actors
ACT-ACC-012, ACT-ACC-014
Depends on
CAP-ACC-BAT-001, CAP-ACC-BAT-013
Related
CAP-ACC-BAT-003, CAP-ACC-BAT-010
Proved by
ATS-ACC-BAT-005

Implementation

Executable suites
TST-ACC-BAT-085, TST-ACC-BAT-086

KindCapabilityProduct areaAccountingModuleBatch ManagementRevision1

Read atservices-accounting f47cb263react-console baf6dae3

Arrange automatic close and posting ​

Purpose ​

A scheduled close keeps routine posting moving without a staff member initiating each run.

How It Works ​

Staff set an automatic-close date and time while working with an Open batch. Rhythm retains a schedule for that occurrence. Scheduled work checks the batch again before acting. A successful close prepares automatic posting and starts it after commit. If preparation is refused, the recorded outcome explains why the closed batch still needs attention. A later batch change can cancel the schedule before it runs.

Relationships ​

  • Prerequisite: Collect a business unit’s documents in a new batch, which addresses the connected batch work.
  • Prerequisite: Run and monitor a batch posting job, which addresses the connected batch work.
  • Related outcome: Correct batch details before posting, which addresses the connected batch work.
  • Related outcome: Advance a scheduled stream and post its predecessor, which addresses the connected batch work.

The Formal Contract

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

Outcomes
Scheduled retirement records whether closing and posting preparation could proceed.
Surfaces
consoleapijob
Constraints
Occurrence handling checks the current batch state when delivery is repeated.
Intent sources
services-accounting:docs/migrations/transaction-processing/batches/README.md#D13: automatic posting (Andrew, 2026-10-16)

Controls

27 controls apply, from the corpus control catalogue.

TC-IAM-001 TC-IAM-002 TC-IAM-004 TC-IAM-005 TC-IAM-006 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-DAT-001 TC-DAT-004 TC-LOG-004 TC-LOG-005 TC-AVL-001 TC-AVL-004 TC-MON-001 TC-MON-002 TC-MON-004 TC-PI-001 TC-PI-002 TC-PI-003 TC-PI-004 TC-PI-005

Permissions

KeyChecked atScope
accounting.batches.createapitenant
accounting.batches.updateapitenant

Business Rules

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

IdRuleKindEnforced atProvenance
01must prove
Proposed
An Open batch can schedule its close using an offset-bearing instant or a date interpreted as local midnight, with one occurrence at that local minute.
proved by ATS-ACC-BAT-001-12, ATS-ACC-BAT-005-01, ATS-ACC-BAT-005-06, TST-ACC-BAT-085, TST-ACC-BAT-086
policyapi, servicetest
services-accounting:modules/batches/tests/integration/services/persistence/batches.integration.spec.js#keeps a one-occurrence schedule of the batch at that minute, in the tenant’s zone
02must prove
Proposed
The scheduled close acts only on an existing Open batch and skips a missing batch or one whose state has changed.
proved by ATS-ACC-BAT-005-02, TST-ACC-BAT-085
lifecycleservicetest
services-accounting:modules/batches/tests/integration/services/persistence/batches.integration.spec.js#skips a run whose batch is no longer open
03must prove
Proposed
After closing, scheduled work prepares the posting request in the same transaction and starts the job after commit.
origin: services-accounting:docs/migrations/transaction-processing/batches/README.md#D13: automatic posting (Andrew, 2026-10-16)
proved by ATS-ACC-BAT-005-03, ATS-ACC-BAT-005-10, ATS-ACC-BAT-013-16, TST-ACC-BAT-085
lifecycleservicetest
services-accounting:modules/batches/tests/integration/services/persistence/batches.integration.spec.js#submits one posting job of the closed batch, in its unit, for the tenant’s customer (D13)
04must prove
Proposed
Redelivery of a completed close occurrence creates no additional close or posting.
origin: services-accounting:docs/migrations/transaction-processing/batches/README.md#D13: automatic posting (Andrew, 2026-10-16)
proved by ATS-ACC-BAT-005-03, ATS-ACC-BAT-005-09, ATS-ACC-BAT-010-10, TST-ACC-BAT-085
invariantservicetest
services-accounting:modules/batches/tests/integration/services/persistence/batches.integration.spec.js#posts nothing more when the same occurrence runs again: the batch is no longer open
05must prove
Proposed
Manual close, archive or removal of the close time cancels the automatic close, and deletion removes its schedule.
proved by ATS-ACC-BAT-003-13, ATS-ACC-BAT-004-10, ATS-ACC-BAT-005-04, ATS-ACC-BAT-005-07, ATS-ACC-BAT-005-08, TST-ACC-BAT-085
lifecycleservicetest
services-accounting:modules/batches/tests/integration/services/persistence/batches.integration.spec.js#removes the schedule and the time when the batch is closed
06must prove
Proposed
If posting preparation after a completed close is refused, the batch remains Closed and the run explains the refusal; document-generation errors in a subsequent posting can leave it in Error.
origin: services-accounting:docs/migrations/transaction-processing/batches/README.md#D13: automatic posting (Andrew, 2026-10-16)
proved by ATS-ACC-BAT-005-05
policyserviceobserved
services-accounting:modules/batches/services/auto-post/automatic-posting.ts:prepareAutomaticPosting
07must prove
Proposed
The product should reject an automatic close time earlier than the current time.
proved by ATS-ACC-BAT-005-11
validationapiunknown
FND-ACC-BAT-005

Scenarios

IdGivenWhenThenProvenance
01Staff arrange a late-afternoon automatic close for the daily batch.The scheduled occurrence is handled.The work closes the batch and prepares automatic posting.observed
services-accounting:modules/batches/services/persistence/batches.ts:closeBatchOnSchedule; services-accounting:modules/batches/services/auto-post/automatic-posting.ts:prepareAutomaticPosting
02Staff archive a batch before its automatic-close time.That previously selected time arrives.The cancelled schedule produces no automatic close.test
services-accounting:modules/batches/tests/integration/services/persistence/batches.integration.spec.js#drops an archived batch’s automatic close, as an automatic close is kept only on an open batch

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