---
id: TST-ACC-REC-072
title: Settlement financial identity and resolution inspection
kind: integration
product_area: accounting
module: reconciliation
revision: 1
status: draft
source_sha:
  services-accounting: f47cb263875bbc0c5640fba7dae6785ec32695f8
repository: services-accounting
files:
  - modules/reconciliation/tests/integration/services/persistence/settlement-items.queries.integration.spec.js
implements:
  - ATS-ACC-REC-006-02
  - ATS-ACC-REC-006-03
  - ATS-ACC-REC-006-04
  - ATS-ACC-REC-006-05
  - ATS-ACC-REC-006-06
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/services/persistence/settlement-items.queries.integration.spec.js
bindings:
  - scenario: ATS-ACC-REC-006-02
    assertions:
      - >-
        services-accounting:modules/reconciliation/tests/integration/services/persistence/settlement-items.queries.integration.spec.js#names
        the grace of the merchant account’s override and the payment a capture came from
  - scenario: ATS-ACC-REC-006-03
    assertions:
      - >-
        services-accounting:modules/reconciliation/tests/integration/services/persistence/settlement-items.queries.integration.spec.js#answers
        an operational batch’s items
      - >-
        services-accounting:modules/reconciliation/tests/integration/services/persistence/settlement-items.queries.integration.spec.js#answers
        the items whose customer label contains the search, whatever its case
  - scenario: ATS-ACC-REC-006-04
    assertions:
      - >-
        services-accounting:modules/reconciliation/tests/integration/services/persistence/settlement-items.queries.integration.spec.js#counts
        and totals the items by state, processor and currency at the date
      - >-
        services-accounting:modules/reconciliation/tests/integration/services/persistence/settlement-items.queries.integration.spec.js#summarizes
        a processor’s items alone
  - scenario: ATS-ACC-REC-006-05
    assertions:
      - >-
        services-accounting:modules/reconciliation/tests/integration/services/persistence/settlement-items.queries.integration.spec.js#offers
        the free payout dated on its expected date, in the list
      - >-
        services-accounting:modules/reconciliation/tests/integration/services/persistence/settlement-items.queries.integration.spec.js#offers
        it in the detail too
  - scenario: ATS-ACC-REC-006-06
    assertions:
      - >-
        services-accounting:modules/reconciliation/tests/integration/services/persistence/settlement-items.queries.integration.spec.js#answers
        the same literal state for every item on Friday 2026-10-09, the expected date, by the SQL and by the
        rule
      - >-
        services-accounting:modules/reconciliation/tests/integration/services/persistence/settlement-items.queries.integration.spec.js#answers
        the same literal state for every item on Monday 2026-10-12, Columbus Day, by the SQL and by the rule
      - >-
        services-accounting:modules/reconciliation/tests/integration/services/persistence/settlement-items.queries.integration.spec.js#answers
        the same literal state for every item on Thursday 2026-10-15, past the grace, by the SQL and by the
        rule
---

# Settlement financial identity and resolution inspection

## Verification Boundary

This suite calls production services over the real test database. Fixture setup may write records directly; the exercised commands and queries retain their normal database enforcement.

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