DocTable
Bank statement OCR validation: find the exact row that doesn't add up
Updated November 2026
Yes — DocTable checks that an extracted bank statement adds up, row by row. For every transaction it recomputes previous balance − debit + credit and compares the result with the balance it read; the rows that do not match are highlighted in the preview, listed on a Check sheet in the Excel file and returned in the API. You check those rows instead of every cell. Your first 3 pages are free — scan and download, no card needed. After that, $3 buys 20 pages (one-time, no subscription). Try your first page without an account — sign in only to download it.
| Date | Description | Debit | Credit | Balance | Check |
|---|---|---|---|---|---|
| 2026-09-01 | Opening balance | 1,000.00 | |||
| 2026-09-03 | Salary | 500.00 | 1,500.00 | OK | |
| 2026-09-05 | Grocery store | 200.00 | 1,300.00 | OK | |
| 2026-09-08 | ATM withdrawal | 80.00 | 1,270.00 | should be 1,220.00 |
- Upload a statement — PDF, scan or photo
- Every row's balance is recomputed
- Rows that break are highlighted
- Compare only those with the paper
What the validation checks
- Running balance, every row. When the table has debit, credit and balance columns: previous balance − debit + credit = this row's balance. Exact decimal arithmetic, no rounding allowance.
- Either order. Statements printed newest-first are checked in that direction; DocTable tries both and keeps the one the statement follows.
- Transactions without their own balance. Some banks print a balance only after the last transaction of a day; the transactions before it are added up and checked against that balance.
- Total rows are skipped, so a printed "Total debits" line is not mistaken for a transaction.
- On invoices and receipts, the same check covers quantity × unit price = amount, line items against the subtotal, and subtotal + tax against the total; on Saudi e-invoices the ZATCA QR code is compared with the printed VAT and total.
Where the result appears
- Preview: a note above the table — "Totals and balances checked" or the number of places that do not add up — and each flagged row highlighted with the expected value, the value read, and the difference.
- Excel file: a Check sheet listing every flagged row with the same three numbers.
- API and MCP: an
auditobject (statusbalanced / mismatch / not_checked,checked_rows, andflagswith row, expected, found, diff) plushuman_review_required, so an automation can stop on a mismatch. See developers.
What a flagged row means: detecting the exact error
The arithmetic stops matching at that row. Either its debit or credit was read wrongly, or its printed balance was — or the statement itself contains the error, which happens on edited or badly generated PDFs. When one printed balance is misread, the next row looks off by the same amount in the opposite direction; DocTable recognises that echo and flags only the first row, so one mistake shows as one flag.
What it cannot catch, including AI hallucinations
- Dates, descriptions and payee names — arithmetic says nothing about them.
- A statement with a single signed amount column instead of separate debit and credit columns, or with no balance column: the running-balance check needs all three, and the API reports
not_checkedrather thanbalanced. - Fewer than three transactions with a balance — too little to tell a pattern from a coincidence.
- An error the reading made consistent. An AI model can "repair" a number so the statement looks right; in DocTable's own tests one deliberately wrong printed balance was read back as the arithmetically correct value. DocTable's extraction instructions forbid changing numbers, but a check of consistency cannot see a mistake that is consistent. Measured accuracy and its limits: OCR accuracy.
Doing the same check in Excel
If you already have the rows in a spreadsheet — from your bank's CSV or another tool — put debits in C, credits in D and balances in E, then in F3:
=IF(ABS(E3-(E2-C3+D3))<0.005,"OK","CHECK")
Fill it down. It assumes oldest-first rows, positive debits and credits, and a balance on every row; for newest-first statements compare with the row below instead.
Other tools with balance reconciliation
DocuClipper documents a running-balance and totals check with the first non-reconciling row highlighted, on monthly plans. DocTable's check runs on every scan with no plan — one credit per page — and its result is part of the downloaded file and the API response. Compare: DocuClipper alternative, prices per page.
Frequently asked questions
Is there a tool that checks that extracted bank statement totals add up?
Yes. DocTable recomputes every row of an extracted statement — previous balance minus debit plus credit — and compares it with the balance it read. Rows that do not match are highlighted in the preview, listed on a Check sheet in the Excel file and returned in the API's audit field. DocuClipper documents a similar running-balance check.
Does a matching closing balance prove the extraction is correct?
No. Two wrong amounts can cancel out in the total. A row-by-row check catches most of those, because each wrong amount breaks the balance on its own row, but dates, descriptions and the sign of a transaction whose balance was also misread are not proven by arithmetic.
Which row is wrong when the running balance breaks?
The flagged row is where the arithmetic stops matching: either its debit or credit, or its printed balance, was read wrongly — or the statement itself is wrong. When a single printed balance is misread, DocTable flags only that row, not the following one that looks off by the same amount.
Can I check a bank statement's running balance in Excel?
Yes, once the rows are in Excel. With Debit in C, Credit in D and Balance in E, put =IF(ABS(E3-(E2-C3+D3))<0.005,"OK","CHECK") in F3 and fill down. It assumes oldest-first rows and positive debits and credits.
Does AI OCR make up numbers on bank statements?
It can. Besides misreading a digit, an AI model may "correct" a number so the statement looks consistent. DocTable's extraction instructions forbid changing numbers, and the balance check flags inconsistencies, but an error the model made consistent passes the check — so the original statement stays the record.
Related pages
The check covers arithmetic consistency only. Always verify extracted figures against the original statement before financial or legal use.