Bank statement converter that shows its proof

What it converts

Tallyscope reads text PDFs, scanned PDFs, password-protected PDFs and photos (JPG, PNG, TIFF and similar) with built-in OCR. It also reads CSV and other delimited text, Excel files (XLSX, XLS, ODS), and the structured bank formats OFX and QFX, QIF, SWIFT MT940 and ISO 20022 camt.053. You can mix them: a PDF from one account, a CSV from another and an OFX download from a third all land in the same table.

There is no template per bank. The reader finds the transaction table by its headers (recognised in about 15 languages) and by where dates and numbers sit on the page, so a layout it has never seen is still read the same way. We do not promise that every document will convert perfectly; instead, the tool tells you how sure it is.

Why a converter needs a checker

Most converters give you a spreadsheet and stop. If a digit was misread or a column shifted, you find out later, usually when a total does not match. Statements carry a built-in answer key: the running balance printed next to each row. Tallyscope uses it. For every row it checks that the previous balance plus the amount equals the next balance, which proves both the amount and whether it was money in or out.

The result is an honest status for each statement: Verified, Partly verified, Needs review or Unverified. Rows that disagree with the balances are flagged, and the amount the balance implies is offered as a one-click fix. The status is never upgraded without arithmetic evidence. How verification works has a worked example.

How it works in three steps

1. Add files. Drag them into the page. Up to 10 files at once on the Free plan.
2. Review. Scan the merged table, filter it, open any row to see the source details and fix flagged rows.
3. Export. Download CSV (the Free plan includes the first 25 rows), or Excel, PDF and JSON on a paid plan.

Your files stay on your device

Parsing and OCR run inside the browser tab. The statement files are not uploaded to a server and nothing is stored after you close the tab. Details are on converting without uploading. The one exception is optional and off by default: the AI assistant can read a masked version of your table if you switch that on, and it is a paid feature.

What you get in the export

The table has the date, statement, account, description, category, currency, debit, credit, amount, balance, the amount in your chosen currency, whether the row counts in totals, and any flags. The Excel file adds a Statements sheet (opening, credits, debits, closing, reconciliation status) and a Summary sheet. Exports neutralise spreadsheet formulas, so a description that begins with an equals sign cannot execute when you open the file.

When to use something else

If a statement has neither a running balance nor printed totals, as with some credit card exports, Tallyscope cannot prove it and marks it Unverified. It still extracts the rows, with the direction of each amount taken from headers, signs and wording. Very blurry or low-resolution scans can also leave rows wrong; those rows are flagged rather than guessed.

Ready to try it? Open the converter or compare plans.