--- id: FAS-ACC-BAT-02 feature: FEAT-ACC-BAT-02 product_area: accounting module: batches revision: 1 status: proposed product_intent: proposed source_sha: services-accounting: f47cb263875bbc0c5640fba7dae6785ec32695f8 react-console: baf6dae382d6f41dce976c7f848667ccc37e076f rhythm-v2-docs: 37405d50d1465ea0571a66095d98ebec4db04175 capabilities: - CAP-ACC-BAT-009 - CAP-ACC-BAT-010 - CAP-ACC-BAT-011 scenarios: - id: FAS-ACC-BAT-02-01 title: Recurring configuration supplies selectable intake kind: behaviour exercises: - CAP-ACC-BAT-009 - CAP-ACC-BAT-010 - CAP-ACC-BAT-011 relies_on: - ATS-ACC-BAT-009-05 - ATS-ACC-BAT-010-01 - ATS-ACC-BAT-011-06 preconditions: An isolated unit has fiscal coverage and no routing settings. steps: - do: >- Create active Daily and Cards streams, save Daily as default and Cards as a card rule, then evaluate invoice and card-payment facts. expect: >- Each stream identifies an Open intake batch; invoice facts select Daily and card facts select Cards. provenance: proposed source: >- rhythm-v2-docs:specs/accounting/batches/design/tests/ATS-ACC-BAT-009-keep-a-recurring-batch-that-rolls-on-a-schedule.md#ATS-ACC-BAT-009-05; rhythm-v2-docs:specs/accounting/batches/design/tests/ATS-ACC-BAT-010-roll-to-the-next-batch-on-schedule-and-post-the-one-it-replaces.md#ATS-ACC-BAT-010-01; rhythm-v2-docs:specs/accounting/batches/design/tests/ATS-ACC-BAT-011-route-a-business-unit-s-new-transactions-to-the-right-batch.md#ATS-ACC-BAT-011-06 expected: >- Each stream identifies an Open intake batch; invoice facts select Daily and card facts select Cards. negative: false data_needs: >- An isolated workspace, business unit and owned fixtures matching the stated accounting setup. bound_to: [] provenance: proposed source: >- rhythm-v2-docs:specs/accounting/batches/design/tests/ATS-ACC-BAT-009-keep-a-recurring-batch-that-rolls-on-a-schedule.md#ATS-ACC-BAT-009-05; rhythm-v2-docs:specs/accounting/batches/design/tests/ATS-ACC-BAT-010-roll-to-the-next-batch-on-schedule-and-post-the-one-it-replaces.md#ATS-ACC-BAT-010-01; rhythm-v2-docs:specs/accounting/batches/design/tests/ATS-ACC-BAT-011-route-a-business-unit-s-new-transactions-to-the-right-batch.md#ATS-ACC-BAT-011-06 - id: FAS-ACC-BAT-02-02 title: Rolling changes the target of subsequent assignment kind: interaction exercises: - CAP-ACC-BAT-009 - CAP-ACC-BAT-010 - CAP-ACC-BAT-011 relies_on: - ATS-ACC-BAT-009-05 - ATS-ACC-BAT-010-03 - ATS-ACC-BAT-011-07 preconditions: >- Daily is active and selected by default; its current batch contains an invoice. steps: - do: >- Roll Daily, issue another invoice without a batch and inspect both invoice references and the run outcome. expect: >- The earlier invoice stays in the retired collection; the later invoice names replacement intake and the run identifies predecessor accounting. provenance: proposed source: >- rhythm-v2-docs:specs/accounting/batches/design/tests/ATS-ACC-BAT-009-keep-a-recurring-batch-that-rolls-on-a-schedule.md#ATS-ACC-BAT-009-05; rhythm-v2-docs:specs/accounting/batches/design/tests/ATS-ACC-BAT-010-roll-to-the-next-batch-on-schedule-and-post-the-one-it-replaces.md#ATS-ACC-BAT-010-03; rhythm-v2-docs:specs/accounting/batches/design/tests/ATS-ACC-BAT-011-route-a-business-unit-s-new-transactions-to-the-right-batch.md#ATS-ACC-BAT-011-07 expected: >- The earlier invoice stays in the retired collection; the later invoice names replacement intake and the run identifies predecessor accounting. negative: false data_needs: >- An isolated workspace, business unit and owned fixtures matching the stated accounting setup. bound_to: [] provenance: proposed source: >- rhythm-v2-docs:specs/accounting/batches/design/tests/ATS-ACC-BAT-009-keep-a-recurring-batch-that-rolls-on-a-schedule.md#ATS-ACC-BAT-009-05; rhythm-v2-docs:specs/accounting/batches/design/tests/ATS-ACC-BAT-010-roll-to-the-next-batch-on-schedule-and-post-the-one-it-replaces.md#ATS-ACC-BAT-010-03; rhythm-v2-docs:specs/accounting/batches/design/tests/ATS-ACC-BAT-011-route-a-business-unit-s-new-transactions-to-the-right-batch.md#ATS-ACC-BAT-011-07 - id: FAS-ACC-BAT-02-03 title: Deactivation retains intake until reactivation kind: lifecycle exercises: - CAP-ACC-BAT-009 - CAP-ACC-BAT-010 - CAP-ACC-BAT-011 relies_on: - ATS-ACC-BAT-009-06 - ATS-ACC-BAT-010-07 - ATS-ACC-BAT-011-07 preconditions: Daily has an Open active batch and is the routing default. steps: - do: >- Deactivate Daily, issue into default intake, deliver stale scheduled work and reactivate with the current version. expect: >- Inactivity disables future runs without blocking eligible current intake; stale delivery opens nothing and reactivation returns its first-batch result. provenance: proposed source: >- rhythm-v2-docs:specs/accounting/batches/design/tests/ATS-ACC-BAT-009-keep-a-recurring-batch-that-rolls-on-a-schedule.md#ATS-ACC-BAT-009-06; rhythm-v2-docs:specs/accounting/batches/design/tests/ATS-ACC-BAT-010-roll-to-the-next-batch-on-schedule-and-post-the-one-it-replaces.md#ATS-ACC-BAT-010-07; rhythm-v2-docs:specs/accounting/batches/design/tests/ATS-ACC-BAT-011-route-a-business-unit-s-new-transactions-to-the-right-batch.md#ATS-ACC-BAT-011-07 expected: >- Inactivity disables future runs without blocking eligible current intake; stale delivery opens nothing and reactivation returns its first-batch result. negative: false data_needs: >- An isolated workspace, business unit and owned fixtures matching the stated accounting setup. bound_to: [] provenance: proposed source: >- rhythm-v2-docs:specs/accounting/batches/design/tests/ATS-ACC-BAT-009-keep-a-recurring-batch-that-rolls-on-a-schedule.md#ATS-ACC-BAT-009-06; rhythm-v2-docs:specs/accounting/batches/design/tests/ATS-ACC-BAT-010-roll-to-the-next-batch-on-schedule-and-post-the-one-it-replaces.md#ATS-ACC-BAT-010-07; rhythm-v2-docs:specs/accounting/batches/design/tests/ATS-ACC-BAT-011-route-a-business-unit-s-new-transactions-to-the-right-batch.md#ATS-ACC-BAT-011-07 - id: FAS-ACC-BAT-02-04 title: Read and administrator routing privileges remain separate kind: permission exercises: - CAP-ACC-BAT-009 - CAP-ACC-BAT-010 - CAP-ACC-BAT-011 relies_on: - ATS-ACC-BAT-009-11 - ATS-ACC-BAT-011-09 preconditions: A reader has application access and recurring and routing read grants. steps: - do: >- Read streams, runs and preview; evaluate facts; attempt stream replacement and routing save and deletion. expect: >- Read and evaluation operations succeed while administrator writes return 403 without changing configuration. provenance: proposed source: >- rhythm-v2-docs:specs/accounting/batches/design/tests/ATS-ACC-BAT-009-keep-a-recurring-batch-that-rolls-on-a-schedule.md#ATS-ACC-BAT-009-11; rhythm-v2-docs:specs/accounting/batches/design/tests/ATS-ACC-BAT-011-route-a-business-unit-s-new-transactions-to-the-right-batch.md#ATS-ACC-BAT-011-09 expected: >- Read and evaluation operations succeed while administrator writes return 403 without changing configuration. negative: true data_needs: >- An isolated workspace, business unit and owned fixtures matching the stated accounting setup. bound_to: [] provenance: proposed source: >- rhythm-v2-docs:specs/accounting/batches/design/tests/ATS-ACC-BAT-009-keep-a-recurring-batch-that-rolls-on-a-schedule.md#ATS-ACC-BAT-009-11; rhythm-v2-docs:specs/accounting/batches/design/tests/ATS-ACC-BAT-011-route-a-business-unit-s-new-transactions-to-the-right-batch.md#ATS-ACC-BAT-011-09 - id: FAS-ACC-BAT-02-05 title: Stream removal follows routing references kind: regression exercises: - CAP-ACC-BAT-009 - CAP-ACC-BAT-010 - CAP-ACC-BAT-011 relies_on: - ATS-ACC-BAT-009-08 - ATS-ACC-BAT-009-09 - ATS-ACC-BAT-011-09 preconditions: >- Default and two ordered rules reference isolated streams with unused intake. steps: - do: >- Try removing referenced streams, delete routing settings, then remove the unused streams. expect: >- Reference refusals identify the default or rule positions; removing routing releases stream deletion and owned scheduling cleanup. provenance: proposed source: >- rhythm-v2-docs:specs/accounting/batches/design/tests/ATS-ACC-BAT-009-keep-a-recurring-batch-that-rolls-on-a-schedule.md#ATS-ACC-BAT-009-08; rhythm-v2-docs:specs/accounting/batches/design/tests/ATS-ACC-BAT-009-keep-a-recurring-batch-that-rolls-on-a-schedule.md#ATS-ACC-BAT-009-09; rhythm-v2-docs:specs/accounting/batches/design/tests/ATS-ACC-BAT-011-route-a-business-unit-s-new-transactions-to-the-right-batch.md#ATS-ACC-BAT-011-09 expected: >- Reference refusals identify the default or rule positions; removing routing releases stream deletion and owned scheduling cleanup. negative: true data_needs: >- An isolated workspace, business unit and owned fixtures matching the stated accounting setup. bound_to: [] provenance: proposed source: >- rhythm-v2-docs:specs/accounting/batches/design/tests/ATS-ACC-BAT-009-keep-a-recurring-batch-that-rolls-on-a-schedule.md#ATS-ACC-BAT-009-08; rhythm-v2-docs:specs/accounting/batches/design/tests/ATS-ACC-BAT-009-keep-a-recurring-batch-that-rolls-on-a-schedule.md#ATS-ACC-BAT-009-09; rhythm-v2-docs:specs/accounting/batches/design/tests/ATS-ACC-BAT-011-route-a-business-unit-s-new-transactions-to-the-right-batch.md#ATS-ACC-BAT-011-09 evidence: - source: CAP-ACC-BAT-009 provenance: documented note: >- Feature-level scenarios compose the capability outcomes; no complete executable binding is inferred from isolated assertions. - source: CAP-ACC-BAT-010 provenance: documented note: >- Feature-level scenarios compose the capability outcomes; no complete executable binding is inferred from isolated assertions. - source: CAP-ACC-BAT-011 provenance: documented note: >- Feature-level scenarios compose the capability outcomes; no complete executable binding is inferred from isolated assertions. --- # Recurring intake and assignment: Feature Acceptance Suite ## What the Feature Must Do as a Whole Recurring configuration and routing form one continuing intake arrangement. The suite checks both the selected stream and the collection that actually receives a document. ## Interactions Between Capabilities Rolling changes the active collection used by routing. Deactivation and deletion are revisited with routing references so configuration cannot appear usable when its intake or ownership has changed. ## Regression Record | Revision | Change | Scenario | Why | |---|---|---|---| | 1 | initial | all | Establish cumulative feature acceptance from the pinned planning and design outcomes. |