---
id: TST-ACC-CLS-012
title: Demonstrated closing screens and confirmation flows
kind: browser-lifecycle
product_area: accounting
module: close
revision: 1
status: draft
source_sha:
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: react-console
files:
  - e2e/mock/accounting-close.mock.spec.ts
implements: []
environment: mock
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 1
isolation: >-
  Each test owns its browser context, demonstration store or supplied transport
  fixtures.
binding_policy: >-
  Each binding identifies the assertions this suite executes; combined scenarios
  may require other bound suites. Existence is not a recorded execution result.
evidence:
  - 'react-console:e2e/mock/accounting-close.mock.spec.ts'
  - provenance: test
    source: 'react-console:e2e/mock/accounting-close.mock.spec.ts'
    assertion_titles:
      - Fiscal period close (mock)
      - 'FAA September is not ready, blocks the close, and lists 23 batches'
      - FAA Education closes after a failed step is retried
      - FAA Foundation closes its last period and the fiscal year
      - The latest closed period is reopened with a reason
      - >-
        Reconciliation treats in transit as non-blocking and an unexplained
        difference as blocking
limitations:
  - >-
    The demonstration includes cost and failure behavior that differs from the
    live service. It does not establish live financial outcomes.
real_dependencies: >-
  The console components or adapters run with demonstration data or supplied
  transport responses. No deployed Accounting, person directory or database is
  exercised.
product_intent: proposed
implementation_evidence: observed
---
# Demonstrated closing screens and confirmation flows

## Verification Boundary

The suite checks console behavior with supplied inputs, demonstration data or transport responses. Its assertions establish that local boundary rather than a deployed Accounting workflow.

## What This Suite Proves

Browser demonstrations inspect blocked batches, warning acknowledgement, typed confirmation, failed-step retry, year completion and reopen reason validation. The data and failure path come from the demonstration store.

## What It Does Not Prove

The demonstration includes cost and failure behavior that differs from the live service. It does not establish live financial outcomes.

## Real Dependencies and Test Doubles

The console components or adapters run with demonstration data or supplied transport responses. No deployed Accounting, person directory or database is exercised.

## Must Not Be Doubled

Keep the component, adapter or pure function under assertion real within this suite. Qualifying financial outcomes requires a separate suite with real Accounting responses, writes and enforced permissions.