
Bank statement · 2 pages
Read the transaction grid in order. Check debit and credit columns, wrapped descriptions, and balances across page breaks.
Bank statement OCR has to preserve the transaction grid. Descriptions wrap, debit and credit formats vary and a balance repeated at the top of a page can look like another transaction. Every amount needs its direction and row context.
Do not judge the result by how tidy the spreadsheet looks. Compare opening and closing balances with the source, then use transaction movement to find missing rows, sign errors and repeated page headers.
Dynamite Docs
Dynamite DocsRead the institution, masked account number, holder, currency, and statement period.
Identify date, value date, description, reference, debit, credit, amount, and running balance columns.
Attach continuation lines to the correct transaction instead of creating false rows.
Compare row count, balance sequence, and opening-to-closing movement before export.
Structured output
Dynamite DocsA neat spreadsheet is not proof that every statement row was read correctly.
Implementation guide
Define the transaction schema before processing a large statement set. Banks may use separate debit and credit columns, a signed amount column or transaction codes. Preserve the original evidence while normalizing those formats into a consistent direction for Excel, CSV or an API.
Match every extracted row to a source row. Wrapped descriptions, brought-forward balances and repeated headers are common sources of false transactions. Keep the page number with each record so a reviewer can return to the exact statement line instead of searching the whole PDF.
Finish with arithmetic. Compare the opening balance, transaction movement and closing balance when the statement provides enough information. A balanced result does not prove that every description is right, but a mismatch is a strong reason to stop the import and inspect missing, duplicated or reversed amounts.
Use decimal types or strings for money. Do not pass currency values through binary floating-point arithmetic.
Return a normalized transaction direction while retaining the original debit, credit, or sign evidence for review.
Prepare statement activity for matching against a ledger.
Search and sample transactions while retaining page references to the statement.
Recover transactions from scanned or image-only bank archives.
Free OCR tools
Upload one supported file and review the extraction before creating an account. Pick the tool that matches the document and output.
Yes. Clear, consistently aligned pages work best. Crooked scans and low-resolution descriptions increase review work.
The extractor reads column position, signs, labels, and balance movement. You should still reconcile the sequence before import.
Remove the password locally first. The extraction pipeline cannot read an encrypted PDF without its password.
Keep reading
Extract scanned PDF text, fields, and tables with AI OCR in Dynamite Docs. Compare uncertain values with the source before exporting reviewed data.
Read guideExtract borderless and multi-page tables with AI OCR in Dynamite Docs. Review columns, wrapped text, and continued rows before spreadsheet export.
Read guideExtract fields and tables from low-resolution or skewed scans with AI in Dynamite Docs. Check uncertain values and page order before exporting.
Read guideConnected Accounting & Document Automation
Can we save optional cookies?
Essential cookies keep you signed in. With your permission, optional analytics cookies and masked session replays help us understand usage and diagnose errors. Privacy policy. Change your choice anytime in Cookie settings.