Configure recurring batch streams

Purpose

Administrators establish repeatable streams of batches for routine financial work.

How It Works

An administrator names a stream, chooses its unit and defines the generated batch labels. They also select a schedule and review its next occurrence. Saving active configuration attempts to supply the first batch immediately. A refused first-batch plan is reported without discarding the configuration. Administrators can stop future rolls while preserving the current batch. Replacement and deletion check versions and dependencies before changing the setup.

Relationships

Related outcome: Advance a scheduled stream and post its predecessor, which addresses the connected batch work.
Related outcome: Assign new documents to the appropriate batch stream, which addresses the connected batch work.
Related outcome: Remove an unused batch safely, which addresses the connected batch work.

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: Administrators can maintain recurring intake configuration and see whether initial intake is available.
Surfaces: consoleapi
Constraints: Accounting scheduling owns occurrence claiming, stored runs and automatic pause.

Controls

26 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-005 TC-AZ-006 TC-TEN-001 TC-TEN-002 TC-TEN-003 TC-TEN-004 TC-DAT-001 TC-DAT-004 TC-LOG-001 TC-LOG-002 TC-LOG-003 TC-LOG-004 TC-LOG-005 TC-PI-001 TC-PI-002 TC-PI-003 TC-PI-005

Permissions

Key	Checked at	Scope
`accounting.recurring-batches.read`	api	tenant
`accounting.recurring-batches.create`	api	tenant
`accounting.recurring-batches.update`	api	tenant
`accounting.recurring-batches.delete`	api	tenant
`accounting.application.access`	api	tenant

Business Rules

14 rules, 13 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.

Id	Rule	Kind	Enforced at	Provenance
`01`must prove Proposed	A recurring configuration retains its original business unit and schedule identity. proved by `ATS-ACC-BAT-009-01`, `TST-ACC-BAT-061`, `TST-ACC-BAT-066`	invariant	service, database	test services-accounting:modules/batches/tests/e2e/recurring-batches.e2e.spec.js#answers 409 to a change of business unit
`02`must prove Proposed	Creating recurring configuration requires a unit, name, batch-name template and schedule, derives an omitted reference from the name and refuses a reference already in use. proved by `ATS-ACC-BAT-009-02`, `TST-ACC-BAT-061`, `TST-ACC-BAT-089`	validation	api, service, database	test services-accounting:modules/batches/tests/e2e/recurring-batches.e2e.spec.js#answers 400 naming schedule to a body without one
`03`must prove Proposed	A recurring schedule cannot roll more frequently than once per twenty-four hours. proved by `ATS-ACC-BAT-009-03`, `TST-ACC-BAT-061`, `TST-ACC-BAT-089`	validation	service	test services-accounting:modules/batches/tests/e2e/recurring-batches.e2e.spec.js#answers 400 to a schedule that would run more often than once a day
`04`must prove Proposed	Name and code templates can read only batch date, unit and currency plus the recurring configuration’s reference and name, rejecting invalid templates or unknown variables. proved by `ATS-ACC-BAT-009-04`, `TST-ACC-BAT-061`, `TST-ACC-BAT-131`	validation	service	test services-accounting:modules/batches/tests/e2e/recurring-batches.e2e.spec.js#answers 400 naming batch_code_template to a template using a variable a batch template does not provide
`05` Proposed	An omitted schedule zone defaults to the workspace zone, and reads expose the next occurrence, schedule description, latest run and any pause reason.	calculation	service	test services-accounting:modules/batches/tests/e2e/recurring-batches.e2e.spec.js#answers every field as written, the schedule in the tenant’s zone, its next run and its sentence, and no last run
`06`must prove Proposed	Active creation and reactivation attempt the first batch immediately, while a refused first-batch plan leaves the configuration saved with its explanation. proved by `ATS-ACC-BAT-006-08`, `ATS-ACC-BAT-009-05`, `ATS-ACC-BAT-009-13`, `ATS-ACC-BAT-009-16`, `ATS-ACC-BAT-013-20`, `TST-ACC-BAT-060`, `TST-ACC-BAT-116`	lifecycle	service	test services-accounting:modules/batches/tests/integration/services/roll/batch-roller.integration.spec.js#saves a recurring batch whose first batch is refused, with the refusal and no batch
`07`must prove Proposed	Deactivation disables future rolls without closing the existing active batch, and reactivation enables scheduling and clears its pause. proved by `ATS-ACC-BAT-009-06`, `ATS-ACC-BAT-009-14`, `ATS-ACC-BAT-010-11`, `TST-ACC-BAT-061`, `TST-ACC-BAT-089`	lifecycle	service	test services-accounting:modules/batches/tests/e2e/recurring-batches.e2e.spec.js#answers no next run once deactivated
`08`must prove Proposed	Replacement requires the saved version, rejects missing or stale versions and recomputes the next occurrence from the save time. proved by `ATS-ACC-BAT-009-07`, `TST-ACC-BAT-061`	validation	service	test services-accounting:modules/batches/tests/e2e/recurring-batches.e2e.spec.js#answers 409 StaleObject to a replacement at the version first read
`09`must prove Proposed	A default assignment or assignment rule referencing the recurring configuration prevents its deletion and identifies that reference. proved by `ATS-ACC-BAT-009-08`, `ATS-ACC-BAT-009-15`, `ATS-ACC-BAT-011-12`, `TST-ACC-BAT-061`, `TST-ACC-BAT-089`	invariant	service, database	test services-accounting:modules/batches/tests/e2e/recurring-batches.e2e.spec.js#answers 409 naming the settings and how they name it
`10`must prove Proposed	Deletion removes the configuration’s schedule, runs and unused active batch, but refuses removal while another generated batch remains. proved by `ATS-ACC-BAT-009-09`, `TST-ACC-BAT-089`, `TST-ACC-BAT-116`	lifecycle	service, database	test services-accounting:modules/batches/tests/integration/services/roll/batch-roller.integration.spec.js#takes its empty active batch with it
`11`must prove Proposed	A business unit cannot be deleted while recurring configurations still reference it. proved by `ATS-ACC-BAT-009-10`, `TST-ACC-BAT-061`	invariant	database	test services-accounting:modules/batches/tests/e2e/recurring-batches.e2e.spec.js#answers 409 naming recurring batches
`12`must prove Proposed	Accounting access and read permission govern recurring records, history and preview, while create, replace and delete each require their administrator write permission. proved by `ATS-ACC-BAT-009-11`, `TST-ACC-BAT-059`	permission	api, console	test services-accounting:modules/batches/tests/e2e/batches-security.e2e.spec.js#is refused the create 403 permission_missing
`13`must prove Proposed	The recurring list sorts by name, supports unit, activity and name-or-reference search, and limits each page to two hundred records. proved by `ATS-ACC-BAT-009-17`	validation	api, service	test services-accounting:modules/batches/tests/e2e/recurring-batches.e2e.spec.js#answers 400 to a limit above 200
`14`must prove Proposed	The documented renderer contract produces trimmed single-line names and codes within its subject limit of 998 characters. proved by `ATS-ACC-BAT-009-12`	validation	service	documented services-accounting:modules/batches/services/rules/recurring-batch-rules.ts (renderer contract in file header)

Scenarios

Id	Given	When	Then	Provenance
`01`	The unit’s calendar covers the current date.	An administrator saves an active weekday card stream with a date-based batch name.	Its first batch is Open and the recurring response describes the next run.	test services-accounting:modules/batches/tests/e2e/batches.e2e.spec.js#answers the recurring batch’s first batch as its active batch: open, named for today, of the recurring batch
`02`	Two assignment rules reference the card stream.	The administrator deletes that recurring configuration.	The refusal identifies the rules and preserves the configuration and schedule.	test services-accounting:modules/batches/tests/integration/services/persistence/recurring-batches.integration.spec.js#refuses 409 for a recurring batch two rules name, listing their positions

Planning

Implementation

Configure recurring batch streams ​

Purpose ​

How It Works ​

Relationships ​