---
id: TST-ACC-REC-043
title: Investigation and acceptance records 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/reconciliation-exceptions.table.integration.spec.js
implements:
  - ATS-ACC-REC-015-02
  - ATS-ACC-REC-015-09
  - ATS-ACC-REC-016-01
  - ATS-ACC-REC-016-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: Suite-owned workspace fixtures and deterministic records removed by suite cleanup.
evidence:
  - >-
    services-accounting:modules/reconciliation/tests/integration/db/reconciliation-exceptions.table.integration.spec.js
bindings:
  - scenario: ATS-ACC-REC-015-02
    assertions:
      - >-
        services-accounting:modules/reconciliation/tests/integration/db/reconciliation-exceptions.table.integration.spec.js#refuses
        a second open exception with the dedupe key of an open one
  - scenario: ATS-ACC-REC-015-09
    assertions:
      - >-
        services-accounting:modules/reconciliation/tests/integration/db/reconciliation-exceptions.table.integration.spec.js#refuses
        a resolved exception without its resolution
      - >-
        services-accounting:modules/reconciliation/tests/integration/db/reconciliation-exceptions.table.integration.spec.js#refuses
        a change of kind (RHF01)
      - >-
        services-accounting:modules/reconciliation/tests/integration/db/reconciliation-exceptions.table.integration.spec.js#refuses
        a change of dedupe_key (RHF01)
  - scenario: ATS-ACC-REC-016-01
    assertions:
      - >-
        services-accounting:modules/reconciliation/tests/integration/db/reconciliation-exceptions.table.integration.spec.js#accepts
        an accepted warning with no approver
  - scenario: ATS-ACC-REC-016-05
    assertions:
      - >-
        services-accounting:modules/reconciliation/tests/integration/db/reconciliation-exceptions.table.integration.spec.js#refuses
        an accepted blocker with no approver
      - >-
        services-accounting:modules/reconciliation/tests/integration/db/reconciliation-exceptions.table.integration.spec.js#refuses
        an approver who is the acceptance’s own requester
      - >-
        services-accounting:modules/reconciliation/tests/integration/db/reconciliation-exceptions.table.integration.spec.js#refuses
        an approver who is the exception’s own resolver
      - >-
        services-accounting:modules/reconciliation/tests/integration/db/reconciliation-exceptions.table.integration.spec.js#refuses
        an accepted warning with an approver
      - >-
        services-accounting:modules/reconciliation/tests/integration/db/reconciliation-exceptions.table.integration.spec.js#refuses
        an acceptance request on a warning
      - >-
        services-accounting:modules/reconciliation/tests/integration/db/reconciliation-exceptions.table.integration.spec.js#accepts
        an accepted blocker with its request and an approver other than its requester and resolver
---

# Investigation and acceptance records 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.