--- id: CON-ACC-BAT-002 name: Recurring Batch feature: FEAT-ACC-BAT-02 product_area: accounting module: batches revision: 1 status: superseded product_intent: proposed implementation_evidence: observed source_sha: services-accounting: f47cb263875bbc0c5640fba7dae6785ec32695f8 react-console: baf6dae382d6f41dce976c7f848667ccc37e076f definition: Recurring configuration supplies successive batch collections for a unit and connects scheduling with document assignment; this superseded grouping now belongs to Batch. owned_by: MOD-ACC-BAT synonyms: - rolling batch - batch stream not_to_be_confused_with: - An individual intake collection - Billing’s recurring invoice generation facets: - name: Roll timing meaning: Describes recurrence, local time and time zone within the supported frequency. used_for: Supplying the next intake collection at the configured occurrence. - name: Generated labels meaning: Uses supported date, unit, currency and configuration variables for names and codes. used_for: Giving successive collections predictable labels. - name: Current intake target meaning: Identifies the batch presently referenced by recurring configuration. used_for: Receiving assigned transactions into the selected collection. - name: Initial intake attempt meaning: Records the first batch or the reason activation could not create it. used_for: Making newly activated configuration usable or diagnosable. - name: Scheduling activation meaning: Controls future occurrences while leaving the existing collection available. used_for: Pausing intake turnover without discarding the current batch. - name: Occurrence record meaning: Retains plans and outcomes with the opened and replaced batches and posting request. used_for: Investigating successful, skipped and failed rolls. - name: Routing configuration meaning: Defines a unit default and ordered transaction and account criteria. used_for: Selecting recurring intake when no explicit batch is supplied. relationships: - to: CON-ACC-BAT-001 statement: Rolling supplies a replacement collection and retires the prior intake target through the applicable workflow. provenance: test source: services-accounting:modules/batches/tests/integration/services/roll/batch-roller.integration.spec.js#opens the new batch, dated the occurrence’s local date in Denver, and points the recurring batch at it - to: CON-ACC-BAT-003 statement: A roll can request ordinary posting for the collection it closes. provenance: test source: 'services-accounting:modules/batches/tests/integration/services/roll/batch-roller.integration.spec.js#posts the previous batch the roll leaves closed: one posting job of it, named in the run’s outcome' lifecycle: - state: active meaning: Occurrences are enabled for the configured flow. how_it_changes: Deactivation stops them; repeated failures can pause the schedule. - state: paused meaning: Scheduling has stopped after failures while configuration remains active. how_it_changes: Correcting the cause and cycling activation clears the pause. - state: inactive meaning: Occurrences are disabled while the current collection remains available. how_it_changes: Reactivation attempts initial intake. acted_on_by: - CAP-ACC-BAT-009 - CAP-ACC-BAT-010 - CAP-ACC-BAT-011 visible_to: - ACT-ACC-006 - ACT-ACC-007 evidence: - 'Examined pinned services-accounting (f47cb263): db/recurring-batches.table.ts, batch-assignment-settings.table.ts, batch-assignment-rules.table.ts, batch-assignment-vocabularies.ts, services/persistence/recurring-batches.ts, batch-assignment-settings.ts, services/roll/**, services/rules/batch-assignment-rules.ts, services/assignment/default-batch.ts; docs/accounting/recurring-batches.md.' - 'Examined pinned react-console (baf6dae3): components/configuration/recurring-batches/**, components/configuration/batch-assignment/**; acceptance inventory CAP-ACC-BAT-005 to 007.' supersedes: [] --- # Recurring Batch ## What It Is Recurring Batch is retained here as a superseded concept. The current planning model treats recurring configuration as a group of Batch facets. This historical entry explains the earlier grouping so readers can understand the retained identifier and the references inherited from previous work. The useful product idea remains a standing arrangement that supplies successive collections for a business unit. Its schedule and assignment configuration organize the flow of documents into batches, while each individual batch remains the accounting collection staff inspect and post. ## What It Is Not Recurring configuration is not a source document, ledger entry or separate accounting book. It does not mean a document has been posted, nor does saving configuration establish that the next run will succeed. A configured flow and its current batch are distinct records with different responsibilities. Treating recurrence as a facet avoids presenting schedule maintenance as an independent broad business noun while preserving the capabilities that maintain and operate it. ## How It Is Used An administrator establishes the unit’s recurring intake arrangements and describes how each successive collection should be named. Assignment settings select those arrangements when a document does not name a batch explicitly. Staff then work with the selected collection through ordinary document and batch experiences. Scheduling handles occurrences and records their outcomes. The roll workflow determines what happens to the prior collection and how the replacement becomes the current intake target. Run history is useful when the expected collection is missing or an occurrence fails. It connects the attempted occurrence to its plan, resulting batches and requested accounting work. Preview helps an administrator inspect upcoming work without representing it as a completed roll. Activation and scheduling state also need separate interpretation: a configuration can still exist even when its schedule is paused or no current batch is available. The retained concept therefore points readers toward the capabilities for configuration, rolling and assignment rather than promising an uninterrupted stream. ## Its Facets Schedule describes timing and local context. Templates describe labels derived for each collection. Current-batch selection identifies the intake target, while initial creation describes the attempt to make a newly activated arrangement usable. Activation controls scheduling. History explains completed, skipped and failed occurrences. Assignment settings describe the ordered choices that select a recurring arrangement for a transaction. All of these facets now have their conceptual home under Batch. Their operational detail remains in the relevant capabilities, and their evidence remains attached to the corresponding rules and scenarios. Supersession changes the planning grain without discarding those distinctions or allocating replacement identifiers. ## How It Relates Batch is the active concept that absorbs this grouping. Posting handles the accounting work requested when rolling retires a populated collection. Document intake uses assignment choices while retaining the document’s own lifecycle. Accounting scheduling supplies delivery and run management at the module boundary; recurrence does not redefine that shared mechanism. ## What It Could Become The product should present recurrence as the configuration of a batch flow, with clear links to the current collection and run history. It should explain when scheduling is paused and when first-batch creation needs attention. Those improvements remain recommendations, and this superseded concept should not become a second home for new rules.