---
id: TST-ACC-BKS-183
title: Configuration Participant 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/maintenance/tests/integration/services/participants/configuration-participant.integration.spec.js
implements:
  - ATS-ACC-BKS-019-01
  - ATS-ACC-BKS-019-02
  - ATS-ACC-BKS-019-03
  - ATS-ACC-BKS-019-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 isolated workspace identities and database fixtures; cleanup
  removes only its seeded records.
assertion_bindings:
  - scenario: ATS-ACC-BKS-019-01
    source: >-
      services-accounting:modules/maintenance/tests/integration/services/participants/configuration-participant.integration.spec.js#answers
      provision done, having written the tenant’s five system payment methods
      (WP-01)
  - scenario: ATS-ACC-BKS-019-01
    source: >-
      services-accounting:modules/maintenance/tests/integration/services/participants/configuration-participant.integration.spec.js#answers
      verifyProvisioned ready once the system payment methods are there
  - scenario: ATS-ACC-BKS-019-02
    source: >-
      services-accounting:modules/maintenance/tests/integration/services/participants/configuration-participant.integration.spec.js#empties
      the tables child first, the business unit taking its currencies with it
  - scenario: ATS-ACC-BKS-019-02
    source: >-
      services-accounting:modules/maintenance/tests/integration/services/participants/configuration-participant.integration.spec.js#resumes
      to done when it is called again
  - scenario: ATS-ACC-BKS-019-03
    source: >-
      services-accounting:modules/maintenance/tests/integration/services/participants/configuration-participant.integration.spec.js#refuses
      a tenant that is not being deleted
  - scenario: ATS-ACC-BKS-019-03
    source: >-
      services-accounting:modules/maintenance/tests/integration/services/participants/configuration-participant.integration.spec.js#removes
      nothing from a tenant it refused
  - scenario: ATS-ACC-BKS-019-03
    source: >-
      services-accounting:modules/maintenance/tests/integration/services/participants/configuration-participant.integration.spec.js#refuses
      a tenant whose deletion was cancelled part way through
  - scenario: ATS-ACC-BKS-019-04
    source: >-
      services-accounting:modules/maintenance/tests/integration/services/participants/configuration-participant.integration.spec.js#leaves
      the other tenant’s rows exactly as they were, table for table
unmapped: false
evidence:
  - provenance: test
    source: >-
      services-accounting:modules/maintenance/tests/integration/services/participants/configuration-participant.integration.spec.js
execution_notes: >-
  The file exists at the pinned revision; this registration records no execution
  result.
---

# Configuration Participant integration suite

## Verification Boundary

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

## What This Suite Proves

The individual assertion references identify the acceptance outcomes this file exercises. When a scenario spans several suites, this file supplies only its listed assertions; qualification must include the other bindings and any recorded coverage finding.

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