---
id: TST-ACC-BAT-063
title: Batch API system batches
kind: api-lifecycle
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/e2e/system-batches.e2e.spec.js
implements:
  - ATS-ACC-BAT-001-08
  - ATS-ACC-BAT-004-07
  - ATS-ACC-BAT-006-05
  - ATS-ACC-BAT-007-01
  - ATS-ACC-BAT-013-06
  - ATS-ACC-BAT-016-07
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-001-08
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/e2e/system-batches.e2e.spec.js#refuses
      creating a batch of a system type 409 system_batch
  - scenario: ATS-ACC-BAT-004-07
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/e2e/system-batches.e2e.spec.js#offers
      an administrator no action for the system batch
  - scenario: ATS-ACC-BAT-004-07
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/e2e/system-batches.e2e.spec.js#refuses
      the action close 409 system_batch
  - scenario: ATS-ACC-BAT-004-07
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/e2e/system-batches.e2e.spec.js#leaves
      the batch unchanged after every refused action
  - scenario: ATS-ACC-BAT-006-05
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/e2e/system-batches.e2e.spec.js#refuses
      DELETE 409 system_batch, the batch still there
  - scenario: ATS-ACC-BAT-007-01
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/e2e/system-batches.e2e.spec.js#refuses
      issuing a draft into the system batch 409 batch_not_open, the draft left a
      draft
  - scenario: ATS-ACC-BAT-013-06
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/e2e/system-batches.e2e.spec.js#answers
      a posting naming the system batch with its job, and the job fails with the
      refusal
  - scenario: ATS-ACC-BAT-016-07
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/e2e/system-batches.e2e.spec.js#answers
      an unposting naming the system batch with its job, and the job fails with
      the refusal
evidence:
  - provenance: observed
    source: 'services-accounting:modules/batches/tests/e2e/system-batches.e2e.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/e2e/system-batches.e2e.spec.js#suite
      header
    note: >-
      Real: the composed handler (the dispatcher, the tenant access gate, the
      application access and licence steps), the routes, the
  - provenance: documented
    source: >-
      services-accounting:modules/batches/tests/e2e/system-batches.e2e.spec.js#suite
      header
    note: >-
      signed context's verification, the persistence services, the posting jobs
      (inline runner), the native posting engine, the close functions
  - provenance: documented
    source: >-
      services-accounting:modules/batches/tests/e2e/system-batches.e2e.spec.js#suite
      header
    note: >-
      and PostgreSQL. Doubled: the signing key pair, which is the run's own; the
      periods' status writer (the fixture's owner sets
unbound_scope: null
---

# Batch API system batches

## Verification Boundary

This suite invokes the composed Accounting dispatcher locally against the prepared database. It exercises request mapping, declared authorization checks and the asserted persistence results.

## What This Suite Proves

Ordinary creation, modification, lifecycle and recovery operations refuse fiscal system collections without changing them. 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.