- Can I check a file another converter, or ChatGPT, made from my statement?
- Yes, free and with no account, at /tools/statement-checker. Drop the CSV or Excel file it gave you and type the opening and closing balances printed on the statement. We tell you whether the rows take one to the other, to the cent.
If they don't, we work out from the arithmetic where to look: a transaction that seems to be missing, and which way the money went; a row that would close the gap if it weren't there, such as a copied row; or a row that would close it if it were the other way round. If the file has a running balance, we check every row against it and point at each row where it breaks.
These are candidates, not corrections. Two identical purchases on one day are real, so check each one against the statement before you change anything.
The file is read in your browser and isn't uploaded. It's the same check we run on every statement we convert.
- What does the badge on each file mean — "Matches statement totals", "Running balance agrees", "Doesn't match statement", or "Verify against the statement"?
- After extraction, we check whether the rows we found add up to what your statement says about itself — its opening and closing balance, its own column totals, or the running balance printed beside each row. "Matches statement totals" means they add up to the balances or totals it prints, to the cent.
"Running balance agrees" is for transaction histories — the exports internet banking gives you, rather than monthly statements — which print no totals at all, only a balance on every row. Every row agrees with that balance, so nothing between the first and last row is missing or misread. It's a separate badge because it checks less: the first row's amount, and anything outside the dates the export covers, can't be checked this way.
The running balance is also checked on statements that print totals, because it is checked at every row rather than once at the end, so it can tell you which row something goes wrong at — and it catches a case the totals cannot: a file that is missing transactions whose amounts happen to cancel out.
"Doesn't match statement" means they don't, and we show you exactly which figures disagree. It also appears when the PDF itself is incomplete: if its page numbers say "Page 3 of 8" and the file has seven pages, or one page appears twice, the rows can't be the whole statement even if they add up to what the remaining pages print. "Verify against the statement" means your statement didn't print anything we could check against — no balances, no totals, no running balance — so we're telling you to eyeball it yourself rather than pretending it's fine. It's a common enough outcome that we publish the actual rate across our own test corpus on the benchmark page rather than asking you to take a number on trust.
None of this is the same as an accountant reconciling your account against an independent record; it only checks that what we extracted is internally consistent with what your own statement says.
Edit an amount or delete a row afterward and we re-run the same check automatically, so the badge always reflects what you're about to export — and because that recheck runs entirely in your browser, fixing a flagged row never sends anything back to our servers or creates a new copy of your data there.
- Does ZeroParse use Artificial Intelligence?
- No. Extraction is deterministic and rule-based — the statement's own text layer or OCR output, positional/spatial geometry to recover the transaction table, and pattern-matching parsers, cross-checked with mathematical reconciliation against the totals your statement prints about itself. There are no AI or LLM models anywhere in the pipeline, so there's no AI hallucination risk and nothing about your documents is ever used to train a model.