---
id: TST-ACC-CLS-045
title: 'Payment findings, policy and captured context'
kind: unit
product_area: accounting
module: close
revision: 1
status: draft
source_sha:
  services-accounting: f47cb263875bbc0c5640fba7dae6785ec32695f8
repository: services-accounting
files:
  - modules/fiscal-close/tests/unit/readiness/reconciliation-checks.spec.js
implements:
  - ATS-ACC-CLS-006-01
  - ATS-ACC-CLS-006-02
  - ATS-ACC-CLS-006-04
  - ATS-ACC-CLS-010-02
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 1
isolation: The suite owns in-memory inputs and declaration 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:
  - >-
    services-accounting:modules/fiscal-close/tests/unit/readiness/reconciliation-checks.spec.js
  - provenance: test
    source: >-
      services-accounting:modules/fiscal-close/tests/unit/readiness/reconciliation-checks.spec.js
    assertion_titles:
      - 'readiness: the reconciliation rules'
      - payment_reconciliation
      - >-
        is blocked by a blocker, its findings the items unchanged, blockers
        first
      - >-
        shows the blockers, the warnings and reconciliation’s in-transit money
        as its figures
      - >-
        warns, never blocks, with warnings alone (funds in transit are a timing
        difference)
      - passes with neither
      - bank_verification
      - 'passes, advisory, with no unverified payout'
      - >-
        warns, advisory, for unverified payouts when the tenant does not require
        verification
      - >-
        blocks, required, for an unverified payout when the tenant requires
        verification
      - >-
        passes, required, when the tenant requires verification and every payout
        is verified
      - year_end_review
      - passes when no other period of the year has a finding
      - 'warns, advisory, listing the findings of every other period'
      - the reconciliation section
      - >-
        maps each payment state to a bucket of the same name, its amount
        flattened
      - >-
        maps an accepted exception to an approved one: requested and approved by
        and at
      - carries the clearing lines with the merchant account’s name
      - 'is unavailable, not ready and empty when the assessment could not run'
      - 'names the display state from the findings, worst first'
real_dependencies: >-
  The suite calls pure rules, mappings or declarations with supplied inputs and
  test contexts. No deployed workflow is exercised.
product_intent: proposed
implementation_evidence: observed
---
# Payment findings, policy and captured context

## Verification Boundary

The suite exercises pure rules, mappings or declarations with supplied inputs. It checks those functions directly rather than executing a complete close.

## What This Suite Proves

Pure assertions retain payment findings, transit amounts and verification policy outcomes. Summary mapping preserves payment states, exception participants and named clearing lines, and reports an unavailable assessment.

## What It Does Not Prove

This register records assertion scope without claiming a passing run or complete coverage of every rule and scenario variant.

## Real Dependencies and Test Doubles

The suite calls pure rules, mappings or declarations with supplied inputs and test contexts. No deployed workflow is exercised.

## Must Not Be Doubled

Run the production rule, mapper or declaration being asserted. Supplied inputs are appropriate here; they do not establish database, public API or deployed workflow behavior.