Convert a Bank Statement PDF to CSV

A bank statement PDF becomes a CSV by extracting every posted transaction into five columns, date, description, amount, type (debit or credit), and running balance, then writing those rows as comma-separated text. Upload the PDF above, confirm the preview, and download the file. Most statements convert in under ten seconds, and the first five pages each month are free with no account.

What the converter reads out of your PDF

The parser targets the transaction table, not the marketing and legal text around it. For each row it isolates the posting date, the full description line (including check numbers and reference codes), the signed amount, whether the line is money in or money out, and the balance after that transaction where the bank prints one.

Descriptions frequently contain commas, "SQ *BLUE BOTTLE, OAKLAND CA" is one field, not three. The converter wraps any field containing a comma, quote, or line break in double quotes per the CSV standard, RFC 4180, so the column count stays correct when Excel parses it. Dates are normalized to a consistent format so sorting works numerically instead of alphabetically.

What a CSV file actually is, and how ours is built

CSV stands for comma-separated values, and despite the name it is just plain text with a few rules. Each line is one record, fields within a line are separated by commas, and the first line is an optional header naming the columns. The format was finally written down as RFC 4180 in 2005, after decades of programs each doing their own slightly different thing, and that document is the reference our output follows. The header row we emit names the columns explicitly, for example Date, Description, Amount, Type, Balance, so any tool that maps columns has clear labels to work from.

The rules that matter most in practice are about special characters. RFC 4180 says a field that contains a comma, a double quote, or a line break has to be enclosed in double quotes, and a literal double quote inside that field is escaped by doubling it. So a payee that prints as JET2.COM "HOLIDAYS" becomes "JET2.COM ""HOLIDAYS""" in the file. This sounds pedantic, but it is the single most common reason a CSV imports with the wrong number of columns elsewhere, and getting it right is what keeps every row aligned. We quote only the fields that need it, which keeps the file compact while staying spec-correct.

One more structural detail: line endings. RFC 4180 specifies a carriage return plus line feed between records, the convention Windows tools expect. Spreadsheets on macOS and Linux read either style, so the file opens cleanly regardless of where you downloaded it. The result is a file that is small, human-readable in any text editor, and parseable by code in one line, which is exactly why CSV remains the lingua franca of financial data.

Delimiters, encoding, and the edge cases that break other tools

Most CSV problems are not in the obvious data, they are in the boring details around it. Three in particular trip up generic exporters.

The delimiter is not always a comma. In many European locales the comma is the decimal separator, so 1.234,56 means one thousand two hundred thirty-four and fifty-six hundredths. Spreadsheets in those locales expect a semicolon as the field delimiter to avoid the clash. A file that uses commas as both the decimal point and the field separator is ambiguous and will misalign. Our amounts use a period as the decimal separator and a comma only as the field delimiter, the configuration RFC 4180 describes, so the columns never collide. If your copy of Excel is set to a comma-decimal locale and splits the file wrong on open, use the From Text/CSV importer and pick the delimiter manually rather than double-clicking.

Encoding decides whether names survive. A CSV is text, and text needs an encoding. We write UTF-8, the universal standard, so accented and non-Latin payee names from HDFC, ICICI, SBI, and European banks come through intact instead of turning into garbled characters. The one wrinkle is that older versions of Excel on Windows assume a legacy code page unless the file carries a byte-order mark or you import it explicitly as UTF-8. If you see strange symbols where an accent should be, that is the cause, and the From Text/CSV path lets you choose UTF-8 and fix it in one click.

Numbers that look like text, and text that looks like numbers. A long account or reference number can be read by Excel as a giant number and shown in scientific notation, while a value like 00123 loses its leading zeros. These are spreadsheet display behaviors, not flaws in the file. Importing the relevant columns as text preserves them exactly.

Which apps open the file without extra steps

A standards-compliant CSV is the most portable financial format there is. It opens directly in every spreadsheet tool and imports into nearly all accounting software through a column-mapping step.

Two of these deserve step-by-step detail because they are where most people take the CSV next.

Importing into Excel cleanly. Double-clicking the file works, but the controlled path is the Data tab, then From Text/CSV (Get & Transform). Excel shows a preview where you confirm the delimiter is a comma, set the file origin to UTF-8, and click Transform Data to set any account-number column to text before loading. This avoids both the scientific-notation problem and any locale mismatch in one pass. Once loaded, the data lands as a proper table you can sort, filter, and total.

Importing into QuickBooks Online. Go to Transactions or Banking, choose Upload from file, and select the CSV. QuickBooks asks you to map your columns to its fields, Date, Description, and either one Amount column or separate Money In and Money Out columns. Our single signed Amount column with a Type flag satisfies either mapping. Pick the account to import into, review the matched transactions, and confirm. If you would rather skip mapping entirely, the QBO format imports natively. The same upload-then-map pattern works for Xero, Wave, and Sage, with the one caveat that some of them want a single Amount column with negatives for debits rather than a separate Type column, which the file already supports.

Converting many statements at once

One statement is a quick job. A year of statements, or statements for several accounts, is where a repeatable workflow matters. The cleanest approach is to convert each statement to CSV with the same column layout, then stack them. Because every file we produce uses the identical header row and the same date and sign conventions, you can open the first CSV and paste the data rows (skipping the repeated header) from each subsequent file underneath, or use your spreadsheet's combine feature, and end up with one continuous ledger spanning every cycle.

This consistency is the real payoff of a normalized export. If you instead copy and paste straight out of twelve PDFs, you get twelve subtly different layouts, some with split debit and credit columns, some with a balance column and some without, and merging them becomes a manual cleanup job. Converting first means the merge is mechanical. For ongoing monthly work across many statements, credit packs bring the per-page cost below the desktop converters while keeping every file in the same shape, so your year-end consolidation is a paste rather than a project.

CSV, Excel, QBO, OFX, or QIF, which export fits your job?

Pick CSV when you want maximum flexibility and plan to analyze or reshape the data yourself. Pick a structured format when a specific app expects it.

If your destination is QuickBooks, the QBO converter skips the mapping step entirely. For everything spreadsheet-based, CSV is the right call.

Troubleshooting a CSV that does not look right

If the file opens with everything jammed into one column, your spreadsheet split it on the wrong delimiter. This is almost always a locale issue: open the file through the From Text/CSV or Import path instead of double-clicking, and choose comma as the delimiter. If accented or non-Latin characters show as boxes or odd symbols, the encoding was guessed wrong, set the import to UTF-8 and they will resolve. If a long account or reference number shows in scientific notation or has lost its leading zeros, the column was read as a number; reimport that column as text. If two transactions seem to have merged into one row or a row has a blank date, the original PDF wrapped a long description across two visual lines; our parser stitches those back together, so a clean reconvert usually fixes a row that a copy-paste broke. And if the running balance does not tie out, confirm your bank actually printed a balance column, since not every layout does, and check that you have not accidentally sorted the rows out of date order, which makes the running balance look wrong even when the data is correct.

The fastest path from PDF to spreadsheet

Drop the PDF on the tool, scan the preview to confirm the rows look right, choose CSV, and download. If a column looks off, switch the export format or open the file with your spreadsheet's text-import wizard to set column types. For recurring work across many statements, credit packs bring the per-page cost below the desktop converters while keeping everything in the browser.