---
id: TST-ACC-BAT-115
title: Batch integration write off policy
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/write-off-policy.integration.spec.js
implements:
  - ATS-ACC-BAT-014-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-014-04
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/integration/services/posting/write-off-policy.integration.spec.js#echo
      (direct, bad_debt_expense): the receivable credited, write-off expense
      debited to the product’s write-off account
  - scenario: ATS-ACC-BAT-014-04
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/integration/services/posting/write-off-policy.integration.spec.js#foxtrot
      (direct, revenue_reversal): the receivable credited, the revenue account
      the invoice posted to debited (1.0’s direct method)
  - scenario: ATS-ACC-BAT-014-04
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/integration/services/posting/write-off-policy.integration.spec.js#golf
      (allowance): the receivable credited, the unit’s allowance default
      debited, bad-debt expense untouched
  - scenario: ATS-ACC-BAT-014-04
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/integration/services/posting/write-off-policy.integration.spec.js#fails
      the batch naming the write-off, the allowance purpose and the unit;
      nothing posts, not even the invoice
  - scenario: ATS-ACC-BAT-014-04
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/integration/services/posting/write-off-policy.integration.spec.js#posts
      the reversal as the mirror of the write-off’s entry: the write-off expense
      account credited, the receivable debited
evidence:
  - provenance: observed
    source: >-
      services-accounting:modules/batches/tests/integration/services/posting/write-off-policy.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/write-off-policy.integration.spec.js#suite
      header
    note: >-
      Real: the integration database, the configuration and product persistence,
      the invoice and write-off commands, the native
  - provenance: documented
    source: >-
      services-accounting:modules/batches/tests/integration/services/posting/write-off-policy.integration.spec.js#suite
      header
    note: 'posting engine. Doubled: nothing.'
unbound_scope: null
---

# Batch integration write off policy

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

Different write-off treatments select their respective accounts and a later reversal mirrors the recorded original choice. 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.