Bank Statement to CSV

Excel is for reading and working on the numbers. CSV is for moving them into something else: Google Sheets, a budgeting app, an accounting package, a database or a script. Almost every import screen accepts CSV, which is why the CSV here is deliberately plain — one table, one header row, no merged cells, no summary rows mixed in with transactions.

The balance checks and the statement summary are left out of the CSV on purpose. An importer that finds a "Closing balance" row in the middle of the data will happily turn it into a transaction. They are in the Excel workbook instead.

• Date — year-month-day when the statement makes the year clear, which every importer understands and which sorts correctly.
• Description — as printed, with wrapped lines joined.
• Money out and Money in — two columns, for software that wants them separately.
• Amount — one signed column, money in positive and money out negative, for software that wants a single amount.
• Balance — the running balance where the statement prints one.
• Page and Check — where the row came from, and why it was flagged, if it was.

The file is UTF-8 with a byte-order mark, so accented merchant names survive opening in Excel. Any description starting with =, + or @ is prefixed so a spreadsheet cannot treat it as a formula.

Upload a bank statement — the PDF your bank emailed, a scan, or phone photos of the pages — and every transaction comes back as a row: date, description, money out, money in, a signed amount and the running balance. Transactions from every page land in one table, so a twelve-page statement is one list, not twelve fragments to stitch together.

Then comes the part that matters: the tool checks its own work. It adds up what it read and compares the result with the balances printed on the statement. When they agree to the cent, you know no transaction was skipped, doubled or misread. When they do not, it tells you by how much and flags the rows where the running balance breaks, so you check three lines instead of three hundred.

Two independent checks run on every statement.

1. Opening + money in − money out = closing. The opening and closing balances are read from the statement's summary or its first and last lines. If the transactions read in between do not produce the closing balance exactly, something is missing or wrong, and the difference is shown.
2. Row by row. Where the statement prints a running balance, each one must equal the previous balance plus that line's money in minus its money out. A break points straight at the problem: the flagged row, or the one just above it.

The arithmetic is done in whole cents, never in floating point, so a check cannot pass by rounding. Statements listed newest-first are recognised, and so are card and loan statements, where the balance is money owed and runs the other way.

A passing check proves the amounts are complete. It does not prove every description was read perfectly — a misspelt merchant name does not change a balance — so skim the descriptions before you rely on them.

The Excel workbook has three sheets:

• Transactions — one row per transaction, in the order printed, with the page it came from and a Check column that says why a row was flagged.
• Balance checks — each check, whether it passed, and the numbers behind it.
• Statement summary — bank, the last four digits of the account, period, currency, opening and closing balances, totals, and whether it reconciles.

Amounts are stored as numbers, not text, so SUM works straight away. Dates are written as year-month-day when the statement makes the year clear, which sorts correctly everywhere. The CSV holds only the Transactions table, one rectangular sheet, because that is what accounting software expects to import.

Upload several PDFs at once — twelve monthly statements, say — and they come back in one workbook with a Statement column, plus a summary row for each.

A PDF downloaded from online banking already contains its text. That text is read in place, with each amount kept in the column it was printed in, which is why this path is the most accurate: the tool never has to guess whether 42.35 was money in or money out.

A scanned statement, or photos of printed pages, is read from the image. That works well on a flat, straight, well-lit page. It struggles with faint thermal-style printing, pages shot at an angle, and folds across the amount columns. The balance check is your safety net here: if a digit was misread, the running balance breaks at that row.

Photos uploaded together are treated as the pages of one statement, in the order you chose them. Each PDF is its own statement.

It is built for current, checking and savings account statements, and reads card and loan statements too. It is not built for investment or brokerage statements, where a row is a holding rather than a movement of cash. Password-protected PDFs need the password removed first — the tool will not try to get around it.

It has not been tested against a named list of banks, and this page will not pretend otherwise. Statement layouts vary enormously; what the tool offers instead is a result you can verify. If the checks pass, the numbers are complete. If they fail on your bank's layout, the job tells you so plainly.

Statements are sensitive, so here is exactly what happens. The uploaded file is sent to the reading model and deleted from storage when the job ends, whether it succeeded or not. Only the last four digits of an account number are kept. The transactions you see are stored with your job so the download still works if you come back later; email hello@sonomir.com to have a job deleted. Nothing you upload is ever published.

The first 2 pages a day are free, with the balance checks, and you can copy every row you see. That is enough to see whether the tool reads your bank's layout correctly before you pay anything.

Past that, pages are 5 credits each — about 19 to 25 cents, depending on the pack — and the Excel download is 4 credits once per job. A six-page statement is 20 credits for the four pages past the free two, plus 4 for the workbook: 24 credits, roughly a dollar. Credits never expire, there is no subscription, and a job that fails is not charged.