---
id: TST-ACC-REC-022
title: Reconciliation commands and views with mocked responses
kind: browser-lifecycle
product_area: accounting
module: reconciliation
revision: 1
status: draft
source_sha:
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: react-console
files:
  - e2e/mock/accounting-reconciliation.mock.spec.ts
implements:
  - ATS-ACC-REC-001-10
  - ATS-ACC-REC-004-07
  - ATS-ACC-REC-011-10
  - ATS-ACC-REC-016-08
  - ATS-ACC-REC-018-10
environment: mock
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 3
isolation: Mock server records used by the browser suite and its selected mock business unit.
evidence:
  - 'react-console:e2e/mock/accounting-reconciliation.mock.spec.ts'
bindings:
  - scenario: ATS-ACC-REC-001-10
    assertions:
      - >-
        react-console:e2e/mock/accounting-reconciliation.mock.spec.ts#Add Payout is a command: the new payout
        is on the list when it is read again
  - scenario: ATS-ACC-REC-004-07
    assertions:
      - >-
        react-console:e2e/mock/accounting-reconciliation.mock.spec.ts#reads the unit's payouts from the
        reconciliation routes
  - scenario: ATS-ACC-REC-011-10
    assertions:
      - >-
        react-console:e2e/mock/accounting-reconciliation.mock.spec.ts#Save Draft and Finalize send the claims,
        the manual item and the finalize command
  - scenario: ATS-ACC-REC-016-08
    assertions:
      - >-
        react-console:e2e/mock/accounting-reconciliation.mock.spec.ts#a second person approves a request to
        accept an exception
  - scenario: ATS-ACC-REC-018-10
    assertions:
      - >-
        react-console:e2e/mock/accounting-reconciliation.mock.spec.ts#Close Readiness reads what
        reconciliation would block
---

# Reconciliation commands and views with mocked responses

## Verification Boundary

This suite uses the console with a mock server. It observes requests, navigation and the rendered responses that the mock supplies.

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

Live request validation, actual persistence, ledger completion and independent approval are outside the mock boundary.

## Real Dependencies and Test Doubles

The console is real and service responses are doubled by the mock server. Mock success is evidence of client behavior only.

## Must Not Be Doubled

The outgoing commands and rendered console controls remain the client under test. Assertions must distinguish mock acknowledgement from live financial completion.