---
id: TST-ACC-BAT-070
title: Batch integration posting period guard
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/close/posting-period-guard.integration.spec.js
implements:
  - ATS-ACC-BAT-013-05
  - ATS-ACC-BAT-016-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-013-05
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/integration/services/close/posting-period-guard.integration.spec.js#refuses
      the batch action `post` (`period_not_open`), submitting no job
  - scenario: ATS-ACC-BAT-013-05
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/integration/services/close/posting-period-guard.integration.spec.js#fails
      the job with the refusal naming the period and its state
  - scenario: ATS-ACC-BAT-013-05
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/integration/services/close/posting-period-guard.integration.spec.js#holds
      the period row FOR SHARE for the rest of the caller's transaction
  - scenario: ATS-ACC-BAT-016-04
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/integration/services/close/posting-period-guard.integration.spec.js#refuses
      the batch action `unpost` (`period_not_open`), submitting no job
  - scenario: ATS-ACC-BAT-016-04
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/integration/services/close/posting-period-guard.integration.spec.js#fails
      the unposting job on its check step with the refusal
  - scenario: ATS-ACC-BAT-016-04
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/integration/services/close/posting-period-guard.integration.spec.js#leaves
      the batch posted, its posting unreversed
evidence:
  - provenance: observed
    source: >-
      services-accounting:modules/batches/tests/integration/services/close/posting-period-guard.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/close/posting-period-guard.integration.spec.js#suite
      header
    note: >-
      Real: the integration database, the configuration, products and
      transaction services, the posting jobs (inline runner), the ported
  - provenance: documented
    source: >-
      services-accounting:modules/batches/tests/integration/services/close/posting-period-guard.integration.spec.js#suite
      header
    note: '(`support/close-world.js`, `setPeriodStatus`). Doubled: nothing.'
unbound_scope: null
---

# Batch integration posting period guard

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

Ordinary posting and recovery refusal is checked both before submission and during execution, including shared fiscal-period locking. 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.