---
id: TST-ACC-TRX-322
title: Accounting payments 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-payments.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 mocked responses.
provenance: test
source: 'react-console:e2e/mock/accounting-payments.mock.spec.ts'
evidence:
  - provenance: test
    source: 'react-console:e2e/mock/accounting-payments.mock.spec.ts'
    assertion_titles:
      - >-
        1. a partial payment leaves the remaining balance on the invoice and
        links the payment
      - >-
        2. a settlement with a payment and a credit creates one payment and one
        separate credit application
      - >-
        2b. changing the payment amount redistributes, and a hand-edited row is
        kept
      - >-
        3. a partial refund reopening the balance leaves the payment partially
        refunded
      - >-
        4. a manual credit applied in part shows Applied and Available, and its
        application is not a payment
      - 5. a credit-only settlement creates a credit application and no payment
      - >-
        6. $500 settled with $150 of credit and a $350 payment records two
        transactions, each with its own detail
      - 7. with Do Not Apply Open Credits only a payment is created
    imports:
      - 'import { expect, test, type Locator, type Page } from "@playwright/test"'
      - 'import { mockUrl, routes, type TenantPath } from "../support/routes"'
    test_double_declarations:
      - ' * MOCK: the Accounting payment flows against the in-memory Accounting service (`lib/accounting/transactions/mock`).'
      - ' * The mock store lives in the browser page, so a full reload resets it. Every step after the first load therefore'
      - 'import { mockUrl, routes, type TenantPath } from "../support/routes"'
      - '  return mockUrl(route, { ...query, mockIdentity: "customer" })'
      - '  await expect(page.getByRole("table", { name: "Outstanding invoice lines" })).toBeVisible()'
      - '  // Client navigation back to the list: a reload would reset the mock store.'
---

# Accounting payments suite

## Verification Boundary

The suite exercises console screens and their requests in a browser with controlled responses. Registration records the existing executable file; it does not report a run or establish product approval.

## What This Suite Proves

The executable assertions exercise this module, but no capability or feature scenario binding is established for this file. Its individual assertion titles remain in the evidence register for subsequent mapping.

## What It Does Not Prove

Controlled browser responses do not establish service authorization, database bounds, processor behavior or financial persistence. An unbound feature chain remains proposed, and this registration carries no execution result.

## Real Dependencies and Test Doubles

The real browser and console components run against suite-controlled data or responses. The evidence register identifies the mock setup; those returned values are assumptions of the screen test.

## Must Not Be Doubled

The screen components, their validation and their outgoing request construction are the verification boundary and must remain real. Service financial integrity needs an additional suite with real persistence.