---
id: SCR-ACC-BAT-005
title: Recurring batches configuration
route: '/console/{tenantId}/configuration/accounting/recurringBatches'
surface: console
product_area: accounting
module: batches
revision: 1
status: draft
design_intent: proposed
implementation_evidence: observed
inference: []
source_sha:
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
  services-accounting: f47cb263875bbc0c5640fba7dae6785ec32695f8
purpose: >-
  Maintain scheduled intake streams and inspect the history of their occurrence
  outcomes.
supports:
  - JNY-ACC-BAT-003
  - CAP-ACC-BAT-009
  - CAP-ACC-BAT-010
permission: >-
  accounting.recurring-batches.read with Accounting application access; create,
  update and delete each need their administrator key
entry_from:
  - Configuration › Accounting › Recurring Batches
exits_to:
  - The stream editor within the same configuration area
  - '/console/{tenantId}/configuration/accounting/batchAssignments'
displays:
  - field: >-
      Stream collection with unit, human schedule, next and most recent
      occurrence and activity
    source: listRecurringBatches (DOM-ACC-BAT-001 recurring stream facets)
  - field: 'Stream editor containing labels, templates, schedule and activity controls'
    source: getRecurringBatch
  - field: Generated next-batch examples from saved preview or local draft examples
    source: previewRecurringBatchRoll once saved; a console example before
  - field: Upcoming occurrence preview supplied by the scheduling integration
    source: The maintenance module's schedule preview
  - field: Reverse-chronological roll outcomes
    source: listRecurringBatchRuns
actions:
  - label: New Recurring Batch
    operation_id: createRecurringBatch
    permission: accounting.recurring-batches.create
    confirm: false
  - label: Save
    operation_id: updateRecurringBatch
    permission: accounting.recurring-batches.update
    confirm: false
  - label: Activate or Deactivate
    operation_id: updateRecurringBatch
    permission: accounting.recurring-batches.update
    confirm: false
  - label: Delete
    operation_id: deleteRecurringBatch
    permission: accounting.recurring-batches.delete
    confirm: true
states:
  - empty
  - loading
  - error
  - read-only
  - inactive
validation:
  - BR-CAP-ACC-BAT-009-02
  - BR-CAP-ACC-BAT-009-03
  - BR-CAP-ACC-BAT-009-04
  - BR-CAP-ACC-BAT-009-06
  - BR-CAP-ACC-BAT-009-08
  - BR-CAP-ACC-BAT-009-09
  - BR-CAP-ACC-BAT-009-10
  - BR-CAP-ACC-BAT-009-12
  - BR-CAP-ACC-BAT-010-10
patterns:
  - PageLayout standard width for the collection and full width for editing
  - Row action menus and confirmed destructive removal
  - BatchTemplateField with generated examples
  - Shared schedule editor and occurrence preview
  - RunHistory with outcome status badges
component: >-
  components/configuration/recurring-batches/recurring-batches-list.tsx (list),
  recurring-batch-editor.tsx (editor), run-history.tsx, batch-template-field.tsx
evidence:
  - >-
    react-console at baf6dae3: components/configuration/recurring-batches/**;
    lib/configuration/recurring-batches.ts, areas.ts;
    lib/accounting/configuration/client.ts
  - >-
    services-accounting at f47cb263:
    modules/batches/aws/api/recurring-batches.routes.ts,
    recurring-batches.schemas.ts
controls: [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-DAT-004, TC-LOG-001, TC-LOG-002, TC-LOG-003, 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-004, TC-PI-005]
---

# Recurring batches configuration

## What the Screen Is For

Administrators define successive intake collections here and inspect whether scheduled rolling has completed. Stream activity controls future occurrences rather than directly changing the current collection eligibility.

## What It Shows and Lets People Do

The collection can be narrowed by business unit, activity and search. The editor combines naming templates with schedule controls and previews. Saving active configuration attempts its first collection, while run history explains later occurrence outcomes and predecessor posting preparation. Delete uses a confirmation dialog and dependency refusal handling.

## States and Errors

Version conflicts require a fresh read. In-use streams cannot be removed, and the deletion dialog retains the service explanation. The adapter and editor omit both response-only first-batch refusal and schedule pause reason; this contract therefore makes no claim those recovery explanations are visible.

## Patterns It Must Respect

The list uses standard PageLayout width and the editor full width. Template examples, schedule preview, outcome badges and destructive confirmation are the observed patterns.