BUYER GUIDE · UPDATED 22 OCTOBER 2026
How to produce an auditable reconciliation break report
An auditable break report links each difference to identifiable inputs, a business key, a rule version and a documented decision. A summary total or green status alone cannot show which records were checked. Agree evidence requirements with the reviewer before the run.
By ShipDataFast. Published ; reviewed .
Keep a run manifest
Record the run ID, timestamp and timezone, source and target filenames or protected identifiers, hashes where appropriate, extraction cut-offs, row counts, rejected rows, key fields, mapping version, transformations and tolerance rules. Keep source files and reports in approved access-controlled storage. A hash identifies an input; it does not prove the input was complete or correct.
A small worked example
| Key | Source | Target | Result |
|---|---|---|---|
| Fund-A / S1 / 2026-10-20 | 100.00 | 100.02 | Value break: delta +0.02 exceeds 0.01 |
| Fund-A / S2 / 2026-10-20 | 50.00 | Absent | Missing in target |
| Fund-A / S3 / 2026-10-20 | Absent | 25.00 | Target only |
| Fund-A / S4 / 2026-10-20 | Two rows | One row | Duplicate source key: resolve before value matching |
Label absent values separately from zero and null. Keep raw and normalised values when a transformation affects the comparison. Do not collapse duplicate keys into an unexplained first match.
Separate finding from acceptance
Give each exception an ID, owner, explanation, evidence link, status and reviewer. An expected difference needs a reason and approval; it remains visible. After correction, retain the rerun and link it to the earlier result. Zero reported breaks means agreement under the tested scope and rules, not proof that all business data is correct.
What should Finance sign?
A decision should identify the run and rules, coverage and exclusions, unresolved exceptions, accepted differences, reviewer and date. This is a practical evidence design, not a guarantee of auditor acceptance or regulatory compliance. Confirm requirements with your own audit and finance owners.
A scoped next step
Recon Check is a service-led first proof: two files, one break report, no charge. Anonymised or sample files are fine. Agree the key, mapping, tolerances, format and safe processing or transfer method before sharing data. Further work is scoped separately. It is separate from the browser tool.