CSV · no upload · no sign-up
Convert a bank statement PDF to CSV
CSV is the format other programs read. That means the details that never matter for a spreadsheet — quoting, encoding, decimal separators — decide whether the file works. They are all handled here, and you can pick the delimiter your tool expects.
Drop your bank statement here
PDF from online banking, or an OFX / QFX export. Click to choose, or paste with Ctrl/⌘+V.
Text-based PDF up to 60 MB / 200 pages, or .ofx / .qfx
The columns you get
Date,Description,Debit,Credit,Amount,Balance
01/04/2025,ACME PAYROLL DEPOSIT,,317.92,317.92,5138.47
01/06/2025,INSURANCE PREMIUM AUTO,806.84,,-806.84,4331.63
01/09/2025,"CHECK #1042, CLEARED",88.50,,-88.50,4243.13Note the quoted third row: a comma inside the description is escaped, not dropped or split into another column.
Built for importers, not just for looks
- RFC 4180 quoting. Commas, quotes and line breaks inside descriptions cannot break the file.
- UTF-8 with BOM. Excel on Windows reads accented merchant names correctly.
- A dot decimal point, always.
1.234,56from a European statement comes out as1234.56. - CRLF line endings, which is what the RFC specifies and what Windows tools expect.
- Comma or semicolon. Choose the delimiter in the toolbar before downloading.
The three things that break bank CSVs
Almost every "the CSV is wrong" problem is one of these, and none of them are about the transactions themselves.
1. The decimal separator
A statement printed in Germany shows 1.234,56. Written straight into a CSV, that is either a string, or a date, or a number one thousand times too large, depending on who reads it. Amounts here are normalised to 1234.56 before they are written, so the file is unambiguous everywhere.
2. The delimiter
Excel's behaviour depends on the machine's regional settings. If your copy expects a semicolon, a comma-separated file lands in one column. Switch the delimiter and it opens correctly. (Or take the .xlsx, which has no delimiter to get wrong.)
3. The date
03/04/2025 is two different days depending on where you are, and a CSV has no way to say which. Export in 2025-04-03 or 03-Apr-2025 when the file is going somewhere you do not control. If the statement itself never proves the order, the converter says so and lets you switch it.
The date format is a dropdown on every download, not a hidden setting — because the right answer depends on where the file is going, not on what the converter prefers.
Questions people actually ask
What exactly is in the CSV?
One header row and one row per transaction. The generic CSV carries Date, Description, Debit, Credit, Amount and Balance. Debit and Credit are always positive numbers in their own columns, and Amount is the signed net movement, so you can use whichever your next step expects.
Why does my CSV open as a single column in Excel?
That is a Windows locale setting, not a broken file. In many European locales Excel expects a semicolon instead of a comma as the separator. The easiest fix is to use File, Open inside Excel and pick the file, then choose "Delimited" and tick comma in the import wizard — or download the Excel workbook instead, which has no delimiter at all.
Are accented characters and currency symbols preserved?
Yes. The CSV is written as UTF-8 with a byte-order mark, which is what makes Excel on Windows read "Café" as "Café" rather than "Café". The BOM is a real byte at the start of the file, and every CSV parser ignores it correctly.
What about commas inside merchant names?
They are quoted properly according to RFC 4180: a field containing a comma, a quote or a line break is wrapped in double quotes, and any internal double quote is doubled. That is the standard every spreadsheet and importer understands.
Should I use the CSV or the Excel workbook?
Use the CSV when a program is going to read the file — an importer, a script, a database. Use the .xlsx when a person is going to read it, because the workbook keeps dates as real dates and numbers as real numbers and adds a Summary sheet recording what was verified.
Are there decimal-comma problems?
No, but only because amounts are normalised before export. Statements printed as 1.234,56 (German, Dutch, and many others) are converted to 1234.56 in the CSV, so the file always uses a dot as the decimal point regardless of what the PDF showed.