---
id: TST-ACC-BAT-080
title: Batch integration batch assignment settings
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/batch-assignment-settings.integration.spec.js
implements:
  - ATS-ACC-BAT-011-01
  - ATS-ACC-BAT-011-04
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-011-01
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/integration/services/persistence/batch-assignment-settings.integration.spec.js#refuses
      a 101st rule, by the database’s rule, leaving the previous rules
  - scenario: ATS-ACC-BAT-011-04
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/integration/services/persistence/batch-assignment-settings.integration.spec.js#refuses
      a rule naming another unit’s merchant account, naming the rule
  - scenario: ATS-ACC-BAT-011-04
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/integration/services/persistence/batch-assignment-settings.integration.spec.js#refuses
      a rule naming another unit’s bank account, naming the rule
evidence:
  - provenance: observed
    source: >-
      services-accounting:modules/batches/tests/integration/services/persistence/batch-assignment-settings.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/batch-assignment-settings.integration.spec.js#suite
      header
    note: >-
      Real: PostgreSQL, the persistence services, the execution context and its
      transactions under `rhythm_accounting_app`.
  - provenance: documented
    source: >-
      services-accounting:modules/batches/tests/integration/services/persistence/batch-assignment-settings.integration.spec.js#suite
      header
    note: >-
      Doubled: nothing. Never doubled: the transaction, the version check, the
      triggers, the foreign keys or row-level security.
unbound_scope: null
---

# Batch integration batch assignment settings

## 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

Ordered rules, reference validation, replacement and selection are checked against saved routing configuration. 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.