Catching reading mistakes in payment statements
Checks whether the numbers add up, not just whether each field looks plausible.
A working sample we built to show how we would solve a problem like this. It is not a delivered project.
In plain terms
A checker for payment-processor statements that have been read automatically. Instead of eyeballing each field, it checks whether the numbers add up, which catches reading mistakes that look believable on their own. It caught three planted errors in a test statement.
- Checks that totals, fees and deposits reconcile.
- Catches mistakes that look plausible in isolation.
- Shows exactly which figure does not add up.
What this does not claim: Uses a synthetic example statement and a simulated reader output, not real client data.
Technical details
A labelled ground-truth statement is compared with simulated Docparser-style output containing three realistic parsing errors, and reconciliation checks identify each one.
- Python
- JSON
- Docparser-style parse output
Need something like this?
Tell us the problem in your own words. We reply with a plain, practical plan.
Discuss a project like this