---
id: TST-ACC-BKS-096
title: Payment Terms integration suite
kind: integration
product_area: accounting
module: books
revision: 1
status: draft
source_sha:
  services-accounting: f47cb263875bbc0c5640fba7dae6785ec32695f8
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: services-accounting
files:
  - >-
    modules/books/tests/integration/services/persistence/payment-terms.integration.spec.js
implements: []
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 isolated workspace identities and database fixtures; cleanup
  removes only its seeded records.
assertion_bindings: []
unmapped: true
evidence:
  - provenance: test
    source: >-
      services-accounting:modules/books/tests/integration/services/persistence/payment-terms.integration.spec.js
execution_notes: >-
  The file exists at the pinned revision; this registration records no execution
  result.
---

# Payment Terms integration suite

## Verification Boundary

The suite exercises books configuration against the migrated local database. Its fixtures and transaction contexts determine the records and service paths under test.

## What This Suite Proves

The suite has executable assertions within this module’s implementation boundary, but no complete acceptance scenario is mapped to them yet. Its empty implementation list makes that remaining work explicit.

## What It Does Not Prove

Local database execution does not prove deployed infrastructure, external provider availability or console behavior. No result is claimed for the pinned revision until the suite runs and its evidence is reviewed.

## Real Dependencies and Test Doubles

PostgreSQL, migrations and the exercised persistence paths are real. Test-owned execution contexts, clocks and local Platform records supply deterministic setup; the file’s imports and fixtures identify any additional doubles.

## Must Not Be Doubled

The database constraints, transaction paths and production persistence functions named by the assertions must remain real. A memory store cannot establish the recorded database proof.