OpenChainGraph Suite · ART-516 · Government & Public-Money Payment Evidence

Daily Reconciliation Attestation

Attests that a daily reconciliation duty was discharged over a population you declare — not a matcher. You supply the declared population, the matched / unmatched / partially-matched counts and totals your reconciliation run already produced, the exception list, and the prior period's carried-forward exceptions. This tool checks whether the population reconciles in both count and value, whether any open exception has aged past your declared tolerance, and whether any prior-period exception disappeared without a documented resolution. Emits a hash-anchored OpenChainGraph v0.4 artifact. Region-portable: every fact below is an input you declare, never a hardcoded country, currency, or scheme.

Population completeness, count and value Exception ageing against a declared tolerance Carried-forward exception continuity

🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.

⚠ This tool does not perform the reconciliation match itself — you run that separately and declare the outcome here. It does not decide whether any underlying control has been met; it is an arithmetic attestation over the figures you supply for one cycle. It computes once when you press the button, stores nothing, runs on no schedule, and retains nothing.

Cycle

The demo figures below are synthetic and already loaded, so you can press Run without entering anything of your own. Load the vanished-exception demo to see the flag this tool exists to catch.

Reconciliation date (ISO yyyy-mm-dd)

As-of (ISO yyyy-mm-dd, your input, never a clock read)

Currency

Declared population — record count

Declared population — control total (minor units)

Ageing tolerance (days, for open exceptions)

Matched / unmatched / partially-matched (from your reconciliation run)

Matched: count / total (minor units)

Unmatched: count / total (minor units)

Partially matched: count / total (minor units)

Open exceptions this cycle (JSON array: exception_id, reason_code, opened_date, amount_minor_units) Prior period's carried-forward exceptions (JSON array, or [] if none, or omit the field entirely if unknown — absence is NOT the same as an empty list) Documented resolutions for prior exceptions that closed (JSON array: exception_id, resolution_reason)

Open exceptions

Continuity vs prior period

Rejected inputs

Rationale

Execution Hash (SHA-256)

What this does not do

It does not match transactions, parse a bank statement, or compute which records reconcile — ART-258, 565, 09, and 55 already do that. It does not verify that the figures you supply are complete or accurate, and a clean attestation is not a determination that any underlying control has been met — it is an arithmetic result over the cycle you declared. Where the prior period's exception set is not supplied at all, continuity is reported as unverifiable, never as a false clean.

Prior art it does not duplicate: ART-470 (single-axis source-vs-extract completeness for one AML lookback cycle, no exception-continuity dimension) and ART-258 (parses one camt.053 statement's balance equation, no population or exception concept). Part of the government-payment-lifecycle chain alongside the programme's other reconciliation and audit-evidence nodes as they ship.