Record balance
A record balance is the check that every input record is accounted for: each one is parsed, skipped by a named rule, or quarantined with a reason. If the three counts do not add up to the number of records received, something was lost silently, and the run cannot be trusted.
How it works
A record balance compares the count declared at intake with what came out. An illustrative run:
input records 10000
parsed 7800
skipped by rule 2130 rule: health-check pings
quarantined 70 reason: unknown message shape
check 7800 + 2130 + 70 = 10000 balanced
Every skipped record names its rule. Every quarantined record keeps its stage and reason, so a person can look at it later.
Why it matters
A reconciliation that reads only what it understands looks clean while dropping the hard cases. On one anonymised merchant day the balance was 1.5 million = 1,187,215 parsed + 329,997 skipped + 9,635 quarantined. The quarantine share was 0.6%. Reconora checks this balance on every run, and the package manifest declares the record count in advance.
How to spot it
Count the lines in your input files. Count the rows in your reconciliation output. If the numbers differ, ask where the difference went and whether anyone wrote down why. A process that cannot answer has no record balance.
Related terms
Quarantine · Normalisation · Merchant log · Tamper-evident audit trail · Methodology
Try it on one day of your data
One day of your data, reconciled, and the report stays with you whether or not you continue.
Updated