StatementSnap

Any bank statement → clean Excel, CSV, or QuickBooks file. Balances verified.

Convert a bank statement to CSV

Drop a PDF statement below and download a CSV: one row per transaction, one signed amount column, UTF-8, and quoted the way the format actually specifies rather than the way that works until a description contains a comma.

CSV is the format everything accepts, which is exactly why a badly written one is so expensive — it imports without complaint and puts the wrong numbers in the wrong fields.

Drag a PDF bank statement here, or tap to choose a file

PDF only · up to 25 MB · up to 60 pages

What the file looks like

Header row, then one row per transaction, in statement order:

date,description,amount,balance,type,category
2026-04-03,"CARD PURCHASE HARDWARE STORE",-120.45,879.55,debit,Supplies
2026-04-15,"DIRECT DEPOSIT EMPLOYER PAYROLL",2500.00,3379.55,credit,Income
2026-04-22,"MONTHLY SERVICE FEE",-35.55,3344.00,debit,Bank fees
2026-04-28,"TRANSFER FROM SAVINGS, THANK YOU",400.00,3725.80,credit,Transfer

Note the last row: the comma inside the description is why the field is quoted. A converter that does not quote it turns that line into six columns instead of five, and every value after it lands one column left of where it belongs.

The check that happens before you download

A CSV gives you no way to tell whether a transaction was dropped. The file is just as valid with 40 rows as with 41, and nothing in it says which is right. So before the export button unlocks, StatementSnap adds every amount to the opening balance and compares the result with the closing balance printed on the statement.

If they match to the cent, the badge is green and you can be confident nothing was missed. If they do not, you get told — and shown which rows are suspect — rather than handed a file that looks fine.

Opening it without breaking it

  • Excel: Data → From Text/CSV, set encoding to UTF-8 and delimiter to comma. Do not double-click the file.
  • Google Sheets: File → Import → Upload, and leave the separator on Detect automatically. It handles UTF-8 correctly with no setting to change.
  • Numbers: opens it directly and gets both the encoding and the delimiter right.

Questions

My CSV opened in Excel with everything in one column. What happened?
You double-clicked it. Excel opens a double-clicked CSV using the list separator from your Windows regional settings, which in much of Europe is a semicolon — so a comma-separated file lands in a single column. Import it instead: Data → From Text/CSV, which lets you set the delimiter and the encoding. That is a quirk of how Excel opens files, not a defect in the file.
Which encoding is the file?
UTF-8. Bank descriptions carry accented characters, currency symbols and the occasional dash that is not a hyphen, and anything narrower mangles them. If a program asks you to pick an encoding on import, choose UTF-8.
What happens to descriptions containing commas?
They are wrapped in double quotes, which is the CSV standard, and quotes inside a description are doubled. A description like PAYMENT, THANK YOU comes through as one field rather than splitting into two columns halfway down the file — which is how a CSV silently shifts every column to the right for a handful of rows.
Can I use the CSV to import into accounting software?
Usually yes, though most tools want you to map their columns to ours on the first import. If the destination is QuickBooks specifically, a QBO file is a better fit than a CSV — it carries the account and transaction ids the CSV cannot.
Are the amounts one column or two?
One, signed: money out is negative, money in is positive. Statements print two columns because they are designed to be read, not imported, and almost every destination expects a single signed amount. The direction is derived from the statement's own layout rather than guessed from the description.

Other formats

Looking for your bank specifically? 150 institutions have their own download instructions — see the list.