---
id: TST-ACC-BAT-055
title: Batch API batch actions
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/batch-actions.e2e.spec.js
implements:
  - ATS-ACC-BAT-002-01
  - ATS-ACC-BAT-002-05
  - ATS-ACC-BAT-003-06
  - ATS-ACC-BAT-004-01
  - ATS-ACC-BAT-004-03
  - ATS-ACC-BAT-004-05
  - ATS-ACC-BAT-004-08
  - ATS-ACC-BAT-016-01
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-002-01
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/e2e/batch-actions.e2e.spec.js#refuses
      a caller without accounting.batches.read 403
  - scenario: ATS-ACC-BAT-002-05
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/e2e/batch-actions.e2e.spec.js#refuses
      the actions of a batch the tenant does not have 404
  - scenario: ATS-ACC-BAT-003-06
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/e2e/batch-actions.e2e.spec.js#refuses
      a rename to a name another batch of the unit has 409, name_in_use
  - scenario: ATS-ACC-BAT-004-01
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/e2e/batch-actions.e2e.spec.js#answers
      each status action with the updated batch
  - scenario: ATS-ACC-BAT-004-03
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/e2e/batch-actions.e2e.spec.js#refuses
      unarchiving an open batch 409
  - scenario: ATS-ACC-BAT-004-05
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/e2e/batch-actions.e2e.spec.js#lists
      a read-only caller no action
  - scenario: ATS-ACC-BAT-004-05
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/e2e/batch-actions.e2e.spec.js#refuses
      a read-only caller 403, and the batch stays open
  - scenario: ATS-ACC-BAT-004-05
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/e2e/batch-actions.e2e.spec.js#refuses
      archiving to a caller without accounting.batches.update 403
  - scenario: ATS-ACC-BAT-004-08
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/e2e/batch-actions.e2e.spec.js#refuses
      an action the batch has not 400, naming the actions
  - scenario: ATS-ACC-BAT-004-08
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/e2e/batch-actions.e2e.spec.js#refuses
      a batch_id, which no batch action takes, 400
  - scenario: ATS-ACC-BAT-016-01
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/e2e/batch-actions.e2e.spec.js#refuses
      unposting a batch that is not posted 409
evidence:
  - provenance: observed
    source: 'services-accounting:modules/batches/tests/e2e/batch-actions.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/batch-actions.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/batch-actions.e2e.spec.js#suite
      header
    note: >-
      PostgreSQL. Doubled: the signing key pair, which is the run's own. Every
      call acts in a tenant of the spec's own (`testId`),
unbound_scope: null
---

# Batch API batch actions

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

Available actions, authorization, confirmation metadata, locks and system-type restrictions are checked at their declared entry points. 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.