---
id: TST-ACC-BAT-079
title: Batch integration ledger purge
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/lifecycle/ledger-purge.integration.spec.js
implements:
  - ATS-ACC-BAT-017-05
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-017-05
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/integration/services/lifecycle/ledger-purge.integration.spec.js#refuses
      the participant’s purge of a live tenant, with nothing removed
  - scenario: ATS-ACC-BAT-017-05
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/integration/services/lifecycle/ledger-purge.integration.spec.js#removes
      every batch posting table’s rows, the ledger’s first among them, and
      answers done with nothing left
  - scenario: ATS-ACC-BAT-017-05
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/integration/services/lifecycle/ledger-purge.integration.spec.js#lets
      configuration be purged once the posting tables are gone, leaving no row
      of the tenant in any tenant table
evidence:
  - provenance: observed
    source: >-
      services-accounting:modules/batches/tests/integration/services/lifecycle/ledger-purge.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/lifecycle/ledger-purge.integration.spec.js#suite
      header
    note: >-
      Real: PostgreSQL, the well-known objects seeded into a tenant of the
      suite's own, the posting and unposting jobs through the local
  - provenance: documented
    source: >-
      services-accounting:modules/batches/tests/integration/services/lifecycle/ledger-purge.integration.spec.js#suite
      header
    note: >-
      runner, the participants, the batched delete, the definer function and the
      tenant state check. Doubled: nothing.
unbound_scope: null
---

# Batch integration ledger purge

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

Guarded cleanup is checked against the workspace deletion state and the order that removes accounting records. 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.