---
id: TST-ACC-TRX-112
title: Void remittance suite
kind: integration
product_area: accounting
module: transactions
revision: 1
status: draft
source_sha:
  services-accounting: f47cb263875bbc0c5640fba7dae6785ec32695f8
repository: services-accounting
files:
  - >-
    modules/transactions/tests/integration/services/remittances/void-remittance.integration.spec.js
implements:
  - ATS-ACC-TRX-010-06
implements_parts:
  - scenario: ATS-ACC-TRX-010-06
    assertion: >-
      it voids every payment it made, taking their allocations back and
      returning the remainder
    provenance: test
    source: >-
      services-accounting:modules/transactions/tests/integration/services/remittances/void-remittance.integration.spec.js#it
      voids every payment it made, taking their allocations back and returning
      the remainder
  - scenario: ATS-ACC-TRX-010-06
    assertion: 'it reopens the invoices it paid, each owing its 180.00 again'
    provenance: test
    source: >-
      services-accounting:modules/transactions/tests/integration/services/remittances/void-remittance.integration.spec.js#it
      reopens the invoices it paid, each owing its 180.00 again
  - scenario: ATS-ACC-TRX-010-06
    assertion: 'it refuses the void: remittance_payment_allocated'
    provenance: test
    source: >-
      services-accounting:modules/transactions/tests/integration/services/remittances/void-remittance.integration.spec.js#it
      refuses the void: remittance_payment_allocated
  - scenario: ATS-ACC-TRX-010-06
    assertion: 'it refuses the void: remittance_posted'
    provenance: test
    source: >-
      services-accounting:modules/transactions/tests/integration/services/remittances/void-remittance.integration.spec.js#it
      refuses the void: remittance_posted
  - scenario: ATS-ACC-TRX-010-06
    assertion: 'it refuses a second void: remittance_not_recorded'
    provenance: test
    source: >-
      services-accounting:modules/transactions/tests/integration/services/remittances/void-remittance.integration.spec.js#it
      refuses a second void: remittance_not_recorded
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 3
isolation: >-
  Suite-marked records in the prepared local test database; fixture teardown
  removes owned records.
provenance: test
source: >-
  services-accounting:modules/transactions/tests/integration/services/remittances/void-remittance.integration.spec.js
evidence:
  - provenance: test
    source: >-
      services-accounting:modules/transactions/tests/integration/services/remittances/void-remittance.integration.spec.js
    assertion_titles:
      - voidRemittance (integration)
      - 'a remittance of two members and a remainder, voided'
      - >-
        voids every payment it made, taking their allocations back and returning
        the remainder
      - 'reopens the invoices it paid, each owing its 180.00 again'
      - 'marks the remittance voided with its reason, by the caller'
      - answers the voided remittance with its voided payments
      - writes the void’s document event after the record’s
      - voids each payment under the void’s derived key
      - 'refuses a second void: remittance_not_recorded'
      - a remittance whose remainder was allocated since
      - 'refuses the void: remittance_payment_allocated'
      - >-
        changes nothing: the payments, the invoices and the remittance stay as
        they were
      - a remittance whose payments were posted
      - 'refuses the void: remittance_posted'
      - changes nothing
    imports:
      - 'const { sql } = require(''drizzle-orm'');'
      - 'const { stage } = require(''@rhythmsoftware/macroservice-testing/stage'');'
      - >-
        const { recordRemittance, voidRemittance } =
        require('../../../../services/remittances/remittance-commands');
      - >-
        const { allocatePayment } =
        require('../../../../services/payments/payment-allocate');
      - '} = require(''../../remittances-fixtures'');'
      - "\t\t\tconst { invoices } = world.require();"
      - "\t\t\tconst { remittance } = voided.require();"
      - "\t\t\tconst { remittance } = voided.require();"
      - "\t\t\tconst { remittance } = voided.require();"
      - "\t\t\tconst { answer } = voided.require();"
      - "\t\t\tconst { remittance } = voided.require();"
      - "\t\t\tconst { remittance } = voided.require();"
      - "\t\t\tconst { remittance } = voided.require();"
      - "\t\t\tconst { invoices, own } = world.require();"
      - "\t\t\tconst { refusal } = refused.require();"
      - "\t\t\tconst { remittance, before } = refused.require();"
      - "\t\t\tconst { invoices } = world.require();"
      - "\t\t\tconst { refusal } = refused.require();"
      - "\t\t\tconst { remittance, before } = refused.require();"
    test_double_declarations: []
---

# Void remittance suite

## Verification Boundary

The suite exercises transaction commands and database protections in the local prepared test environment. Registration records the existing executable file; it does not report a run or establish product approval.

## What This Suite Proves

Its cited assertions contribute evidence for whole-receipt void requires untouched money. The structured assertion bindings identify which parts of combined scenarios it executes.

## What It Does Not Prove

Local commands and route invocations do not establish deployed routing, live processor guarantees or the complete staff browser experience. An unbound feature chain remains proposed, and this registration carries no execution result.

## Real Dependencies and Test Doubles

The suite uses the imported commands, route handlers or persistence code against the local test database. Fixture helpers supply accounting context; any stepped clock, dummy processor or substituted external client is retained in the evidence declarations.

## Must Not Be Doubled

The command or persistence behavior under assertion and its relevant database protections must remain real. Substituting the final financial result removes evidence of transactional effects.