Skip to content

Recon Generator

Independent validation that a financial institution's books balance day to day — and when they don't, where to look first. This site is the live training-materials surface rendered against Your Institution (spec_example); the same materials render against your own institution once you swap the L2 YAML.

Accounting is standard. Your institution is not. Recon Generator layers the two — standard double-entry invariants on top of your unique shape (accounts, rails, multi-leg transfer templates, bundling rules, aging caps) — so every way you actually move money is checked against the rules that govern it. Four dashboards split the work across roles, all reading from the same shared base ledger.

Not an ETL tool

Recon Generator validates data; it doesn't move it. Your existing pipeline lands data in <prefix>_transactions and <prefix>_daily_balances (see Data Integration for the column contract), and Recon Generator reads from there. On top of your real data, the test-data generator plants synthetic scenarios so every L1 invariant is exercisable without delaying go-live.

Pick your role

The fastest way in. Each role page tells you which dashboard is yours, what to read first, what concepts to ground, and what not to spend time learning. Start here:

  • For the operator — daily reconciliation. L1 is your primary surface; L2 Flow Tracing is your second tab when an L1 trace ends with "but why is this happening every day?".
  • For the integrator — owns the institution's L2 YAML. L2 Flow Tracing proves your declarations match runtime reality; L2 Hygiene Exceptions is your backlog.
  • For the ETL engineer — owns the projection from upstream systems into the two shared base tables. The L1 dashboard is your debug surface for silent load bugs.
  • For the executive — Money Moved / Transaction Volume / Account Coverage at weekly + monthly + quarterly cadences. Aggregate questions, no triage.
  • For the compliance analyst — AML / SAR investigations. Question-shaped Investigation dashboard: Recipient Fanout, Volume Anomalies, Money Trail, Account Network.

If you don't fit a role

The library shelves the role pages curate from. Jump in directly when you know what you're after.

  • Concepts — banking primitives + L2 model primitives. Every reader benefits from grounding in double-entry, escrow / sweep / vouchering, and the L2 nouns (Account / Rail / Chain / TransferTemplate / LimitSchedule).
  • Walkthroughs — task recipes. "How do I X?" / "Where does this row lead?" / "Which sheet answers Y?". Bucketed by L1 sheets, Investigation, ETL, and Customization.
  • Reference — per-app structural handbooks (L1, L2 Flow Tracing, Investigation, Executives, ETL, Customization), plus the Schema v6 data feed contract and the L1 Invariants catalog.
  • Demo Institution Tour — the L2 model rendered for the demo institution: chart of accounts, rails, transfer templates, chains, limit schedules.
  • API Reference — for building a custom dashboard on the typed tree primitives.