---
id: TST-ACC-BAT-089
title: Batch integration recurring batches
kind: integration
product_area: accounting
module: batches
revision: 1
status: draft
product_intent: proposed
implementation_evidence: observed
source_sha:
  services-accounting: f47cb263875bbc0c5640fba7dae6785ec32695f8
repository: services-accounting
files:
  - >-
    modules/batches/tests/integration/services/persistence/recurring-batches.integration.spec.js
implements:
  - ATS-ACC-BAT-009-02
  - ATS-ACC-BAT-009-03
  - ATS-ACC-BAT-009-06
  - ATS-ACC-BAT-009-08
  - ATS-ACC-BAT-009-09
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 5
isolation: >-
  The suite owns its test workspace or fixed integration fixtures in the
  prepared local database.
assertion_sources:
  - scenario: ATS-ACC-BAT-009-02
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/integration/services/persistence/recurring-batches.integration.spec.js#answers
      the whole record under the id its name suggests, with its schedule inline
      and its next run
  - scenario: ATS-ACC-BAT-009-03
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/integration/services/persistence/recurring-batches.integration.spec.js#refuses
      a schedule that would run more often than once every 24 hours, leaving the
      recurring batch and its schedule unchanged
  - scenario: ATS-ACC-BAT-009-06
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/integration/services/persistence/recurring-batches.integration.spec.js#enables
      the schedule, clearing the pause and the failure count
  - scenario: ATS-ACC-BAT-009-08
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/integration/services/persistence/recurring-batches.integration.spec.js#refuses
      409 for the default, saying the settings name it as their default and in
      which rule
  - scenario: ATS-ACC-BAT-009-08
    provenance: test
    source: >-
      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
  - scenario: ATS-ACC-BAT-009-09
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/integration/services/persistence/recurring-batches.integration.spec.js#deletes
      its schedule’s run history
evidence:
  - provenance: observed
    source: >-
      services-accounting:modules/batches/tests/integration/services/persistence/recurring-batches.integration.spec.js
    note: >-
      The executable file is inspected at the pinned revision; duration is an
      unmeasured planning estimate.
  - provenance: documented
    source: >-
      services-accounting:modules/batches/tests/integration/services/persistence/recurring-batches.integration.spec.js#suite
      header
    note: >-
      Real: PostgreSQL, the persistence services, the schedules library's
      repository, the execution context and its transactions
  - provenance: documented
    source: >-
      services-accounting:modules/batches/tests/integration/services/persistence/recurring-batches.integration.spec.js#suite
      header
    note: >-
      under `rhythm_accounting_app`. Doubled: nothing. Never doubled: the
      transaction, the version check, the triggers, the foreign
unbound_scope: null
---

# Batch integration recurring batches

## Verification Boundary

This suite exercises the imported batch services or storage against the prepared local database. It does not imply that a deployed workflow is contacted.

## What This Suite Proves

Creation, date changes, unit naming, version conflicts, locks and named lifecycle actions are checked together with scheduled-close and deletion effects. The assertion anchors identify the supported portions of the bound scenarios.

## What It Does Not Prove

Local assertions do not establish deployment configuration, remote delivery guarantees, or unasserted lifecycle and concurrency paths.

## Real Dependencies and Test Doubles

PostgreSQL and the exercised persistence or accounting functions are real. Controlled clocks, imported test fixtures and any suite-specific doubles delimit the asserted behavior.

## Must Not Be Doubled

The database constraints, transaction boundaries and exercised accounting functions must remain real when qualifying the asserted persistence or generation behavior.