Non-visual mirror Northstar Home · no customer data

One Payment, Four Stories

Did each sale, settlement and refund reach the right amount, status and destination?

Narrative sequence

  1. Four witnesses — One fictional payment retains identity while four system witnesses appear.
  2. Candidate alignment — Candidate copies align on reference, amount, date, status and destination.
  3. Exception closure — Exact matches close; duplicates, late records, orphans and wrong destinations stay open.
  4. False pass — The amount/date baseline falsely passes a payment posted to the wrong ledger account.
  5. Tightened key — Destination and category tighten the key and overturn the false pass.
  6. Separate economics — Revenue, cash and contribution remain separate quantities.
  7. Exception lanes — Mature exceptions enter resolve, investigate or UNKNOWN lanes.
Every value encoded by the visual
EvidenceValueStatus / meaning
Bank ↔ ERPmatchamount + date
Bank ↔ Gatewaymatchreference
Bank ↔ Ledgerreviewdestination
Exception 014R48,620human review

Trivial baseline

Coarse matcher: amount and date agree, so the payment is treated as reconciled.

Sensitivity

Extend the settlement maturity window and toggle destination, category and status dimensions; timing-only differences shrink while wrong postings remain.

Strongest counter-case

A difference may be timing, while a match on amount and date may still hide a wrong account.

Verdict

SURVIVES: destination-aware exception. DOWNGRADED: gross exceptions are not recoverable savings.

Synthetic example. Deterministic fictional records; not customer data or achieved customer results.