Ledger / FinanceDESIGN EXAMPLE

Two files. One clear reconciliation.

Compare two authorised transaction exports. Deliver matched records, unresolved exceptions and a traceable rules log.

01Validate inputs
02Match by agreed rules
03Isolate uncertainty
04Deliver an audit trail

What you provide

Two CSV files, a shared currency, a declared date window, and agreed matching rules.

What you receive

matches.csv with both source row IDs
exceptions.csv with reason codes
summary.md and a versioned rules log

What counts as accepted

All input rows must be accounted for. One-to-one matches cannot reuse rows. Agreed control totals must tie. Ambiguous cases stay unresolved; they are not guessed away.

What is outside scope

No bank login, money movement, general-ledger posting or audit opinion. Complex split matching and new formats require a separate scope.

The sample is a fixture, not a benchmark result. Workflow, model version, reviewer and reproducible test report must be supplied before a verified listing can go live.