---
id: TST-ACC-REC-047
title: Settlement financial identity and resolution constraints
kind: integration
product_area: accounting
module: reconciliation
revision: 1
status: draft
source_sha:
  services-accounting: f47cb263875bbc0c5640fba7dae6785ec32695f8
repository: services-accounting
files:
  - modules/reconciliation/tests/integration/db/settlement-items.table.integration.spec.js
implements:
  - ATS-ACC-REC-005-02
  - ATS-ACC-REC-005-03
  - ATS-ACC-REC-005-07
  - ATS-ACC-REC-005-09
  - ATS-ACC-REC-007-01
  - ATS-ACC-REC-010-03
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 5
isolation: Suite-owned workspace fixtures and deterministic records removed by suite cleanup.
evidence:
  - 'services-accounting:modules/reconciliation/tests/integration/db/settlement-items.table.integration.spec.js'
bindings:
  - scenario: ATS-ACC-REC-005-02
    assertions:
      - >-
        services-accounting:modules/reconciliation/tests/integration/db/settlement-items.table.integration.spec.js#refuses
        a second item with the same source key (INV-10)
  - scenario: ATS-ACC-REC-005-03
    assertions:
      - >-
        services-accounting:modules/reconciliation/tests/integration/db/settlement-items.table.integration.spec.js#refuses
        a negative capture
      - >-
        services-accounting:modules/reconciliation/tests/integration/db/settlement-items.table.integration.spec.js#refuses
        a positive refund
      - >-
        services-accounting:modules/reconciliation/tests/integration/db/settlement-items.table.integration.spec.js#refuses
        a zero adjustment
  - scenario: ATS-ACC-REC-005-07
    assertions:
      - >-
        services-accounting:modules/reconciliation/tests/integration/db/settlement-items.table.integration.spec.js#refuses
        a change to the amount (write-once)
      - >-
        services-accounting:modules/reconciliation/tests/integration/db/settlement-items.table.integration.spec.js#refuses
        a change to the kind (write-once)
      - >-
        services-accounting:modules/reconciliation/tests/integration/db/settlement-items.table.integration.spec.js#fills
        in a processor payout reference once evidence names it
      - >-
        services-accounting:modules/reconciliation/tests/integration/db/settlement-items.table.integration.spec.js#refuses
        to change a processor payout reference once set
      - >-
        services-accounting:modules/reconciliation/tests/integration/db/settlement-items.table.integration.spec.js#refuses
        the application role a delete (no DELETE privilege)
  - scenario: ATS-ACC-REC-005-09
    assertions:
      - >-
        services-accounting:modules/reconciliation/tests/integration/db/settlement-items.table.integration.spec.js#refuses
        a manual capture: a person enters fees, reserves and adjustments only
  - scenario: ATS-ACC-REC-007-01
    assertions:
      - >-
        services-accounting:modules/reconciliation/tests/integration/db/settlement-items.table.integration.spec.js#refuses
        a split whose parts do not total the item
  - scenario: ATS-ACC-REC-010-03
    assertions:
      - >-
        services-accounting:modules/reconciliation/tests/integration/db/settlement-items.table.integration.spec.js#refuses
        an adjustment without its GL account
---

# Settlement financial identity and resolution constraints

## Verification Boundary

This suite exercises record constraints and database security using the application role and suite-owned fixtures. Direct writes isolate database enforcement from command behavior.

## What This Suite Proves

The executable assertions identified in the binding records supply the registered scenario observations. When a scenario names several suites, this suite supplies its listed assertions and does not independently establish every clause.

## What It Does Not Prove

Deployed infrastructure, live console behavior and shared scheduling delivery are outside this local boundary.

## Real Dependencies and Test Doubles

PostgreSQL, migrations and the exercised production code are real. Fixtures supply the financial world and caller context; deterministic setup and owner-side inspection do not replace database enforcement.

## Must Not Be Doubled

The exercised database constraints, transactional services and route enforcement remain real. Replacing them would remove the boundary this suite registers.