The 9am scan — every L1 SHOULD-constraint violation across all 12 invariant views: balance (drift, ledger drift, overdraft, limit breach, expected EOD balance, balance cadence gap), chain/cardinality (chain parent disagreement, XOR group violation, fan-in disagreement, multi-XOR violation), and time (stuck pending, stuck unbundled), scoped to the most recent business day in the data. Replaces v5's ar_unified_exceptions matview with a live UNION; no REFRESH contract. KPI tracks total open count; bar chart breaks down by check_type; detail table sorts by magnitude so the biggest variances surface first.
Open Exceptions
Total count of L1 SHOULD-constraint violations in the picker's date window across all 12 invariant checks.
Exceptions by Check Type
How open exceptions in the date window distribute across the 12 L1 invariants. Spikes in one check kind point at a recurring error class to investigate first. Log-scale Y axis: the dominant check kind would otherwise swamp the rarer ones — log scale lets you read all 10 at once.
Exception Detail
Every violation in the picker's date window. Sorted by dollar magnitude (largest first) so the biggest variances are the top rows. Transfer-keyed checks (chain / XOR / fan-in) carry a count instead of an amount and sort below. Left-click the account to narrow Drift to that account; right-click → View Daily Statement to open the per-account-day walk.
Institution Context Sasquatch National Bank's combined treasury + merchant-acquiring view. SNB runs a Cash Management Suite (CMS) for commercial customer DDAs and ZBA cash concentration, AND a merchant-acquiring service that processes card-network sales for retail merchants and pays them out via ACH / wire / check. The L2 instance below covers both surfaces in one model — the L1 dashboard renders treasury invariants (drift, overdraft, limit breach), the L2 flow-tracing dashboard surfaces merchant-acquiring pipeline structure (XOR payout vehicles, TransferKey-grouped settlement cycles, external card-network aggregation).
About this sheet
L1 Exceptions aggregates every L1 SHOULD-constraint violation across the date picker's window. One row per violation, across all kinds -- drift, overdraft, limit breach, expected EOD balance breach, pending aging, unbundled aging.
Drill from a row to the source sheet for that kind to see the formal SHOULD-constraint, the full column shape, and the remediation guidance specific to that violation:
Drift -- internal sub-ledger doesn't match the bank's cumulative net.
Overdraft -- internal account went negative.
Limit Breach -- outbound flow exceeded the rail's cap.
Pending Aging -- transaction stuck in Pending past its rail's max.
Unbundled Aging -- posted leg not bundled into an AggregatingRail past the cap.
Expected EOD Balance Breach -- an account day declared an expected EOD balance the stored balance didn't match.
For supersession-audit diagnostics (which are not SHOULD-violations themselves), see the Supersession Audit sheet.