---
id: TST-ACC-TRX-358
title: Receipt and reconciliation screen suite
kind: browser-lifecycle
product_area: accounting
module: transactions
revision: 1
status: draft
source_sha:
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: react-console
files:
  - e2e/mock/accounting-reconciliation.mock.spec.ts
implements: []
implements_parts: []
environment: mock
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 5
isolation: A browser context and suite-controlled responses.
provenance: test
source: 'react-console:e2e/mock/accounting-reconciliation.mock.spec.ts'
evidence:
  - provenance: test
    source: 'react-console:e2e/mock/accounting-reconciliation.mock.spec.ts'
    assertion_titles:
      - reads the unit's payouts from the reconciliation routes
      - >-
        Add Payout is a command: the new payout is on the list when it is read
        again
      - >-
        Save Draft and Finalize send the claims, the manual item and the
        finalize command
      - a finalized reconciliation is reversed with a reason
      - Mark Bank Verified is a command on the payout
      - a second person approves a request to accept an exception
      - Close Readiness reads what reconciliation would block
    transaction_operations: []
---

# Receipt and reconciliation screen suite

## Verification Boundary

This existing browser suite reaches Transactions records while exercising another Accounting concern. Registration records its financial calls and assertions without claiming that the complete surrounding workflow belongs to Transactions.

## What This Suite Proves

The recorded assertions supply implementation evidence for financial records used by the surrounding workflow. No exact capability or feature scenario binding is established, so this file does not close a specification coverage gap.

## What It Does Not Prove

Mock data does not establish service permissions, financial persistence or processor outcomes. Registration carries no execution result.

## Real Dependencies and Test Doubles

The browser and screen components are real, while controlled responses supply the financial records assumed by the screen test.

## Must Not Be Doubled

The financial request or visible record under assertion must remain real within the declared environment. A separate suite with real persistence is needed for a financial-integrity claim.