--- id: JNY-ACC-BAT-003 title: An administrator configures recurring intake and document routing feature: FEAT-ACC-BAT-02 product_area: accounting module: batches revision: 1 status: draft product_intent: proposed implementation_evidence: observed supersedes: - ACT-ACC-0510 - ACT-ACC-0512 - ACT-ACC-0513 - ACT-ACC-0515 - ACT-ACC-0516 source_sha: react-console: baf6dae382d6f41dce976c7f848667ccc37e076f services-accounting: f47cb263875bbc0c5640fba7dae6785ec32695f8 actor: ACT-ACC-006 goal: Supply successive intake collections and route new documents through the configured choices without repeated manual batch selection. capabilities: - CAP-ACC-BAT-009 - CAP-ACC-BAT-011 - CAP-ACC-BAT-007 - CAP-ACC-BAT-010 - CAP-ACC-BAT-013 screens: - /console/{tenantId}/configuration/accounting/recurringBatches - /console/{tenantId}/configuration/accounting/batchAssignments - /console/{tenantId}/accounting/batches steps: - n: 1 surface: /console/{tenantId}/configuration/accounting/recurringBatches (New Recurring Batch) action: Create dated weekday flows for card and check collections, with late-afternoon rolls. capability: CAP-ACC-BAT-009 expected: Each configuration records its next run and an initial Open collection for today. provenance: test source: react-console:acceptance/accounting/playwright/journeys/batches-posting/ACT-ACC-0510.spec.ts#ACT-ACC-0510 - n: 2 surface: /console/{tenantId}/configuration/accounting/batchAssignments action: Set checks as the default and add a merchant-account card-payment rule. capability: CAP-ACC-BAT-011 expected: Saved settings retain the ordered card rule in the first position. provenance: test source: react-console:acceptance/accounting/playwright/journeys/batches-posting/ACT-ACC-0510.spec.ts#ACT-ACC-0510 - n: 3 surface: evaluateBatchAssignment (Test Transaction panel) action: Evaluate representative card and check facts. capability: CAP-ACC-BAT-011 expected: Card facts select the matching flow; check facts select the default. provenance: test source: services-accounting:modules/batches/tests/e2e/batch-assignment-settings.e2e.spec.js#answers the default with no position when no rule matches - n: 4 surface: /console/{tenantId}/accounting/invoices/new and the payment screens action: Issue an invoice and record both payment kinds without an explicit batch. capability: CAP-ACC-BAT-007 expected: Assignment places each document in the selected current intake collection. provenance: test source: react-console:acceptance/accounting/playwright/journeys/batches-posting/ACT-ACC-0510.spec.ts#ACT-ACC-0510 - n: 5 surface: accounting.recurring-batch.roll (the schedule fires) action: Deliver the configured afternoon occurrence. capability: CAP-ACC-BAT-010 expected: A new Open collection becomes current; the prior collection is closed if populated or removed if empty. provenance: test source: react-console:acceptance/accounting/playwright/journeys/batches-posting/ACT-ACC-0515.spec.ts#ACT-ACC-0515 - n: 6 surface: postBatches (requested by the roll) action: Let the roll submit accounting work for the closed collection. capability: CAP-ACC-BAT-013 expected: Posting completes without a staff request and run history identifies the job. provenance: test source: react-console:acceptance/accounting/playwright/journeys/batches-posting/ACT-ACC-0516.spec.ts#ACT-ACC-0516 alternates: - from_step: 5 condition: Delivery repeats an already-handled occurrence. path: The handler returns the existing result without opening or posting again. outcome: The occurrence retains one resulting collection and posting request. provenance: test source: services-accounting:modules/batches/tests/integration/services/roll/batch-roller.integration.spec.js#opens nothing for the same occurrence delivered again, and answers the same batch failures: - from_step: 1 condition: Today is outside the unit’s configured fiscal calendar. path: Configuration is retained with the initial-intake refusal and no first batch. outcome: Calendar correction is needed before a later intake attempt can succeed. provenance: test source: 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 - from_step: 4 condition: The unit no longer has assignment settings. path: A payment without an explicit batch fails its intake requirement. outcome: Staff must select a batch or have assignment configuration restored. provenance: test source: react-console:acceptance/accounting/playwright/journeys/batches-posting/ACT-ACC-0510.spec.ts#ACT-ACC-0510 - from_step: 6 condition: Automatic posting preparation refuses the retired collection. path: The collection remains Closed and the run retains the reason. outcome: The recorded refusal requires follow-up rather than an assumed successful posting. provenance: observed source: services-accounting:modules/batches/services/auto-post/automatic-posting.ts:prepareAutomaticPosting rules_in_play: - BR-CAP-ACC-BAT-009-03 - BR-CAP-ACC-BAT-009-06 - BR-CAP-ACC-BAT-011-02 - BR-CAP-ACC-BAT-011-07 - BR-CAP-ACC-BAT-011-09 - BR-CAP-ACC-BAT-010-01 - BR-CAP-ACC-BAT-010-03 - BR-CAP-ACC-BAT-010-04 - BR-CAP-ACC-BAT-010-05 - BR-CAP-ACC-BAT-010-06 assertions: - id: AS-JNY-ACC-BAT-003-01 statement: An omitted batch uses the current collection selected by the first matching assignment rule. provenance: test source: react-console:acceptance/accounting/playwright/journeys/batches-posting/ACT-ACC-0510.spec.ts#ACT-ACC-0510 - id: AS-JNY-ACC-BAT-003-02 statement: Successful rolling points configuration to the replacement; a protected prior collection can remain Open. provenance: observed source: services-accounting:modules/batches/services/persistence/batches.ts#closeOrDeleteRolledOutBatch - id: AS-JNY-ACC-BAT-003-03 statement: The collection closed by rolling receives one automatic posting. provenance: test source: react-console:acceptance/accounting/playwright/journeys/batches-posting/ACT-ACC-0516.spec.ts#ACT-ACC-0516 - id: AS-JNY-ACC-BAT-003-04 statement: Run history identifies occurrence outcomes and the related collections and accounting work. provenance: test source: services-accounting:modules/batches/tests/e2e/recurring-batches.e2e.spec.js#answers the run the consumer recorded, every property of it e2e_policy: required e2e_reason: End-to-end acceptance is required to connect saved configuration with assignment, occurrence delivery and automatic accounting work. evidence: - 'Inspected references: Examined pinned react-console (baf6dae3): acceptance/accounting/journeys/batches-posting/ACT-ACC-0510.json, 0512, 0513, 0515, 0516 and the Playwright specs of 0510, 0515, 0516; components/configuration/recurring-batches/**, components/configuration/batch-assignment/**.' - services-accounting at f47cb263: 'Inspected references: docs/accounting/recurring-batches.md; step-level capability citations.' proved_by: [] --- # An administrator configures recurring intake and document routing ## Story Supply successive intake collections and route new documents through the configured choices without repeated manual batch selection. The cited steps show how the relevant capabilities connect. Documented walkthrough expectations remain distinct from tested behavior, and the alternative paths identify where staff need a different workflow.