---
id: TST-ACC-BAT-096
title: Batch integration concurrent posting
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/posting/concurrent-posting.integration.spec.js
implements:
  - ATS-ACC-BAT-013-11
  - ATS-ACC-BAT-016-15
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-013-11
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/integration/services/posting/concurrent-posting.integration.spec.js#makes
      a direct posting wait for the batch, then refuse it as posted, with no
      posting and no entry written
  - scenario: ATS-ACC-BAT-016-15
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/integration/services/posting/concurrent-posting.integration.spec.js#makes
      a direct unposting wait for the batch, then refuse it as open, with its
      posting left unreversed
evidence:
  - provenance: observed
    source: >-
      services-accounting:modules/batches/tests/integration/services/posting/concurrent-posting.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/posting/concurrent-posting.integration.spec.js#suite
      header
    note: >-
      Real: the integration database, the native posting engine and the
      persistence services. Doubled: the concurrent poster, whose transaction is
unbound_scope: null
---

# Batch integration concurrent posting

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

A direct posting or recovery waits for a competing row lock and checks the committed state before proceeding. 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

The application database connection runs the real direct engine. A separate owner connection holds a controlled status mutation open to establish blocking; it does not run a second full posting engine.

## Must Not Be Doubled

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