---
id: TST-COM-FUL-028
title: Financial facts handler
kind: integration
product_area: commerce
module: fulfillment
revision: 1
status: draft
source_sha:
  services-commerce: c8b66a98e2490617aec38ba5c8165dd9bd0a8f9b
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: services-commerce
files:
  - modules/fulfillment/tests/integration/services/facts/financial-facts-handler.integration.spec.js
implements:
  - ATS-COM-FUL-007-04
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 3
isolation: >-
  Run-created workspace identifiers and fixture records in the prepared test database; concurrency
  cases own their extra connections.
evidence:
  - repository: services-commerce
    path: >-
      modules/fulfillment/tests/integration/services/facts/financial-facts-handler.integration.spec.js
    test_titles:
      - shows the payment on the order once the payment event is received
      - shows the credit memo on the order once the credit event is received
      - shows the refund on the order once the refund event is received
      - leaves every mirror as it was for an event about an invoice line Commerce does not know
      - >-
        holds the refund pending at the processor, not failed, and counts no failed attempt (COMM-M1
        R7-2)
      - >-
        completes the amendment on the books while the refund is pending at the processor (COMM-M1
        R7-2)
      - completes the adjustment once the refund event is received
    scenario_anchors:
      - >-
        services-commerce:modules/fulfillment/tests/integration/services/facts/financial-facts-handler.integration.spec.js#holds
        the refund pending at the processor, not failed, and counts no failed attempt (COMM-M1 R7-2)
---

# Financial facts handler

## Verification Boundary

This suite checks financial facts handler against the prepared PostgreSQL database. Its entry points are the persistence and service functions used by the tests.

## What This Suite Proves

The bound scenarios identify the assertions this suite contributes. Source anchors retain the exact test cases; where a capability scenario has several contributing suites, a single binding does not imply that every branch runs here.

## What It Does Not Prove

Direct service and persistence calls do not establish the full HTTP permission contract, deployed scheduling or browser behavior. No execution result is claimed by this register.

## Real Dependencies and Test Doubles

The database and imported Commerce persistence services are real. Fixtures create the records owned by this run. Financial facts are supplied by a local fixture provider. Accounting command responses use the suite’s fixture port. Time-sensitive cases use a controlled clock where the source fixture supplies one.

## Must Not Be Doubled

Keep the database constraints, row visibility and persistence writes real when claiming this integration coverage. A canned repository response cannot replace the boundary being checked.