---
id: TST-ACC-TRX-351
title: Financial records across Accounting journey 0696
kind: browser-lifecycle
product_area: accounting
module: transactions
revision: 1
status: draft
source_sha:
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: react-console
files:
  - acceptance/accounting/playwright/journeys/reporting/ACT-ACC-0696.spec.ts
implements: []
implements_parts: []
environment: deployed-dev
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 5
isolation: >-
  Run-marked records and fixture cleanup in the configured development
  workspace; exclusive configuration changes require the suite’s declared
  coordination.
provenance: test
source: >-
  react-console:acceptance/accounting/playwright/journeys/reporting/ACT-ACC-0696.spec.ts
evidence:
  - provenance: test
    source: >-
      react-console:acceptance/accounting/playwright/journeys/reporting/ACT-ACC-0696.spec.ts
    assertion_titles:
      - ACT-ACC-0696
    transaction_operations:
      - >-
        await accounting.post<WireInvoice>(`/invoices/${tenantId}`, {
        business_unit_id: unit.id, currency_code: "USD", bill_to: { kind:
        p.kind, id: p.id }, invoice_date: last.first, due_date: last.day,
        source: "console", memo: `${RUN} ${p.ref}`, lines: [{ product_id:
        unit.products.dues.id, product_type_id: "accounting_product",
        description: `${RUN} ${p.ref}`, quantity: "1.0000", unit_price:
        usd(1000), discount_amount: usd(0), position: 1 }], issue: true,
        batch_id: batch.id, idempotency_key: commandKey(RUN, p.ref) }),
      - '`POST /invoices (${p.ref})`,'
      - >-
        const inv = expectStatus(await
        accounting.get<WireInvoice>(`/invoices/${tenantId}/${party.loser.invoice!.id}`),
        200, "the loser's invoice")
---

# Financial records across Accounting journey 0696

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

A development journey proves only its asserted calls and visible results; shared configuration and unvisited branches remain outside that proof. Registration carries no execution result.

## Real Dependencies and Test Doubles

The browser, configured application and API fixture calls are dependencies. The suite supplies its own marked records; controlled outcomes and shared prerequisites are limited to the declarations in the executable file.

## Must Not Be Doubled

The financial request or visible record under assertion must remain real within the declared environment. Replacing the returned financial position with a predetermined value removes evidence of the Accounting effect.