---
id: TST-COM-ORD-094
title: The money mirror
kind: integration
product_area: commerce
module: orders
revision: 1
status: draft
source_sha:
  services-commerce: c8b66a98e2490617aec38ba5c8165dd9bd0a8f9b
repository: services-commerce
files:
  - modules/orders/tests/integration/services/mirror/refresh-money-mirror.integration.spec.js
implements:
  - ATS-COM-ORD-010-05
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 2
isolation: The suite creates its own test workspace records and removes them using the fixture cleanup.
evidence:
  - provenance: test
    source: >-
      services-commerce:modules/orders/tests/integration/services/mirror/refresh-money-mirror.integration.spec.js
    test_cases:
      - >-
        writes the mirror of the billed order from the view: paid counts the credit application once, the rest
        their columns
      - 'writes an all-zero mirror for an order with no billed line, and raises nothing'
      - >-
        raises accepted_without_invoice_line on the billed line the view lacks, one open row counting both
        findings, and still writes the mirror it could derive
      - raises mirror_mismatch on the order when its invoice is void
scenario_coverage:
  - scenario: ATS-COM-ORD-010-05
    test_cases:
      - >-
        raises accepted_without_invoice_line on the billed line the view lacks, one open row counting both
        findings, and still writes the mirror it could derive
      - raises mirror_mismatch on the order when its invoice is void
    scope: >-
      The cited cases exercise the scenario’s listed fixture outcomes; this register makes no verified
      conformance claim.
dependency_evidence:
  provenance: test
  source: >-
    services-commerce:modules/orders/tests/integration/services/mirror/refresh-money-mirror.integration.spec.js
  declared_by_test: >-
    PostgreSQL (the stand-in view), the persistence services, the execution context under
    `rhythm_commerce_app`, P4's exceptions. Doubled: Accounting's rows (planted as the owner), the clock
    (fixed).
---

# The money mirror

## Verification Boundary

The suite exercises persistence or workflow operations against the local integration database.

## What This Suite Proves

The registered cases check the money mirror with their fixture records and assertions. Scenario bindings name only the examples those cases exercise.

## What It Does Not Prove

A registered file supplies no run result or verified conformance by itself. Local fixtures do not establish deployed cross-service behavior or complete browser journeys.

## Real Dependencies and Test Doubles

PostgreSQL and the exercised Commerce persistence or workflow code are real. Remote service records, clocks and transports follow the suite’s fixtures.

## Must Not Be Doubled

The database constraints, role restrictions, locks and transactions exercised by this suite must use PostgreSQL.