Upload a batch of bank statements, bring transactions into date order, and inspect overlapping rows before downloading one Excel workbook. Every row keeps the name of its source file.
2–10 files · PDFs or clear scans · each file up to 10 MB
Select 2–10 PDFs or clear images. Each file is converted separately and its pages count toward your allowance. We combine rows by transaction date in your browser.
PDF, PNG or JPG · each up to 10 MB
A merged workbook should make it easier to audit a year or a quarter, not hide where a transaction came from. The workspace converts each uploaded file separately, then sorts all extracted rows by valid transaction date. The Source file column and a separate Source files sheet make the chain back to the original statement visible.
Select between two and ten PDF, PNG or JPG statements in a single batch. Each file uses the same extraction endpoint and the same per-page allowance as an ordinary conversion. A multi-page PDF consumes one allowance page for each page it contains. The interface stops at a failed file and keeps already completed results visible, so you know what was charged and what can be reviewed.
Rows with valid ISO dates are sorted from earliest to latest. For rows sharing a date, the original file order and row order are preserved. If the printed date cannot be safely interpreted, the row stays in the result but moves to the end of the preview, with a count asking you to inspect it. We do not silently invent an accounting date.
A possible duplicate is flagged when rows from different files share the same date, signed amount, normalized description and reference. This is deliberately conservative; repeated legitimate charges can still look alike, and differently described overlap may not be detected. No row is deleted automatically. Compare flagged rows with both originals and choose whether to exclude the later copy from the workbook.
For bookkeeping or analysis, a clean-looking total is not enough. Statement boundaries, account identity and row provenance all matter.
A bank may repeat an item on adjacent statements, change a pending transaction into a posted one, or split a single purchase into several settlements. Identical-looking date and amount combinations are only clues. This tool does not certify duplicates or recalculate running balances across source files. The balance column remains the figure from the original statement row.
Scanned statements can introduce reading errors. Look for low-confidence fields and extraction warnings, especially around page breaks and faint reference numbers. For a more focused source comparison, use bank statement OCR first. The downloadable workbook retains source filenames so that corrections and exclusions can be traced later. Keep copies of the original bank-issued files with your records.
Explore fictional statement examplesTry the fictional two-file sample without consuming pages to see how a boundary overlap is shown.
Yes. Select two to ten files, convert them, review the dated preview and download a single Excel .xlsx workbook. Each source PDF may have multiple pages, subject to your available page allowance. The workbook also records the original filename for each transaction.
No. The tool flags likely overlaps between different files, but leaves every row in place by default. The same amount can occur more than once legitimately. Tick Exclude this row only after checking the original statements. Excluded rows are omitted from the download, not deleted from your bank documents.
Processing stops on that file and reports the reason. Earlier successful files remain visible and their pages have already counted toward your allowance. You can review those results, but at least two successfully converted sources are required for a merged download.
The tool permits it but warns when known account endings or currencies differ. It does not convert exchange rates or reconcile balances between accounts. If you need account-level totals, merge each account and currency separately or add your own grouping after export.