Explainers
Is OCR accurate for bank statements?
OCR is good enough to save you hours of retyping and not good enough to trust blind. Whether it got a statement right is not a matter of opinion: the bank printed the balances, and every row either adds up to them or doesn't.
Updated · 4 min read
The honest answer
It depends on the page. A clear, flat, well-lit, straight scan of a printed statement usually reads well. A skewed phone photo of a creased page in dim light reads worse. Any single accuracy figure quoted for "OCR" hides that range, which is why Signavos doesn't quote one.
The useful question is not "how accurate is OCR?" but "is this statement right?" That one has a definite answer, page by page, and you can get it without retyping anything.
What goes wrong, and why
| Error | Example | Usual cause |
|---|---|---|
| Look-alike characters | 0 read as O, 1 as I or l, 5 as S, 8 as 3 | Blur, low resolution, worn print |
| Lost decimal point or comma | 1,250.00 read as 125000 | Small print, dust, compression |
| Merged or split columns | An amount lands in the description | Skewed page, curled paper, tight columns |
| Missing row | A transaction near a fold disappears | Crease, shadow, page cut off at the edge |
| Garbled description | TESC0 ST0RES 2l4 | Same as above; harmless to totals but worth a skim |
Most of these come from the picture, not the software. OCR sees pixels. If the pixels are blurred, angled or in shadow, the characters are ambiguous, and the reader has to guess.
How to check OCR results
A bank statement checks itself. Opening balance + money in − money out = closing balance, and most statements print a running balance after each transaction or each day. A misread amount breaks that arithmetic at the very next printed balance. A dropped row does too.
Signavos runs that check on every page of every conversion, OCR or not:
- ✅ Ties out: every OCR row on the page is confirmed by a balance the bank printed.
- ⚠️ Mismatch: at least one row disagrees with a printed balance. Those rows are red, so you know exactly which lines to compare with the page. Pages that fail are not charged.
- Unverified: the page prints nothing to check against. Scanned pages OCR cannot verify are free, and you should spot-check them yourself.
On top of the balance check, every OCR row is labelled Read by OCR: in the preview, as a note on the row in the Excel file, and on the conversion certificate. CSV, OFX and QBO files stay clean for import into accounting software. The full method, including how to run the same check yourself in a spreadsheet, is in how to check a bank statement conversion is accurate.
The balance check can't catch a misread description, because descriptions don't affect totals. Skim payee names on anything you will file.
How to get better OCR results
- Use the bank's PDF if there is one. A downloaded statement is text, not an image, and needs no OCR at all.
- Scan rather than photograph if you can, at around 300 DPI.
- If you photograph, lay the page flat, use even daylight, hold the phone straight above it and let it focus.
- Don't crop through rows, and include the pages with the opening and closing balances.
- Retake the failing page, not the whole statement, when the balance check flags one.
Step-by-step guides: scanned statements and photos and screenshots.
Privacy: who else sees your statement?
A bank statement shows your balance, your income, your rent and every shop you use. Where the OCR runs decides who gets a copy.
| Approach | What happens to the file |
|---|---|
| Cloud OCR API | The converter sends your pages to a third-party OCR provider, under that provider's terms and retention rules |
| Self-hosted OCR | The pages are read on the converter's own servers; no outside OCR provider receives them |
Signavos uses self-hosted OCR. Your statement is read on Signavos's own servers, and no third-party OCR service sees it. Uploaded statements and their outputs are deleted after 24 hours, and the original pictures from a photo upload are never stored.
Whatever converter you use, ask the question directly: is the OCR done in-house, or sent to someone else's API? If the privacy page doesn't say, assume the second.
Frequently asked questions
- How accurate is OCR on bank statements?
- It depends on the image. Clear, flat, straight pages read well; blurry or skewed photos read worse. Rather than trust a percentage, check each page against the balances printed on it.
- How do I know if OCR misread a number?
- Add each row to the opening balance and compare with every running balance the bank printed. A misread amount breaks the next balance. Signavos does this on every page and marks the rows that disagree in red.
- Can OCR read handwritten bank statements?
- Bank statements are printed, and that is what OCR reads well. Handwritten notes or highlighter on the page make nearby numbers harder to read, so use a clean copy if you have one.
- Is it safe to use OCR on a bank statement?
- It depends where the OCR runs. Some tools send your file to a third-party OCR API. Signavos reads it on its own servers, and deletes the statement and its output after 24 hours.
- Do I pay if OCR gets a page wrong?
- Not on Signavos. Pages that fail the balance check are not charged, and scanned pages OCR cannot verify are free. The preview is always free.
Send your next document without a subscription.
Upload a PDF, place the fields, send. Your recipient signs without an account and you pay per signature — nothing renews.
Start paying per signature