How to Save a Bank Statement as a CSV File

If you need your bank transactions in a spreadsheet or accounting tool, a CSV file is usually the format that imports cleanly. The question is how to get one. There are two paths, and which you use depends entirely on what your bank gives you. This guide walks through both, then shows you how to check that the CSV is correct before you rely on it.

A CSV (comma-separated values) file is just plain text: one transaction per line, with the fields separated by commas. If you want the deeper background on the format and why accounting platforms favor it, see what a CSV export is for. Here we focus on the practical steps of producing one.

Path 1: Export a CSV directly from online banking

Many banks let you download transactions as a CSV without ever touching a PDF. If yours does, this is the cleaner route, because the data comes straight from the bank's records rather than being read off a document.

The exact menus differ from bank to bank, so treat the following as a general pattern rather than exact button names:

1. Sign in to online banking or your bank's app. Desktop browsers usually expose more export options than mobile apps, so start there if you have the choice.
2. Open the account whose transactions you want. Look at the account activity or transaction history view, not the statements section — those two are often separate.
3. Set a date range. Pick the period you need (a month, a quarter, a tax year). Some banks cap how far back you can export in one go, so you may need several exports for a long history.
4. Find the download or export control. It is commonly labeled "Download," "Export," or shown as a small download icon near the transaction list.
5. Choose CSV as the format. You will often see several options — CSV, Excel (XLSX), an accounting format (e.g. QBO/QFX), or PDF. Select CSV.
6. Save the file somewhere you can find it, and open it to confirm it contains the rows you expected.

A few honest caveats. Not every bank offers a CSV option at all, and some only offer it on the web and not in the app. The columns you get also vary: one bank might give you a single signed amount column, another might give separate debit and credit columns, and the date format is rarely your choice. That is fine — your accounting tool can usually map columns during import — but it is worth knowing the output is not standardized across banks.

If you find a CSV export, you can often skip straight to the verification step further down.

Path 2: Convert a PDF statement to CSV

Plenty of banks only hand you a PDF statement, with no CSV option anywhere in the interface. A PDF is built for reading and printing, not for importing — the transactions look like a table to your eye, but underneath they are just positioned text, which is why you cannot simply open a PDF in a spreadsheet and get clean columns.

You have two ways across that gap.

Manual retyping or copy-paste. You can open the PDF and type each transaction into a spreadsheet, or copy and paste the table. For a handful of transactions this is workable. For a full statement it is slow and error-prone: pasted text tends to merge columns, split descriptions across lines, and quietly scramble dates. Every mistake is one you then have to catch later.

A converter that reads the PDF for you. A dedicated tool detects the transaction table in the statement and writes out structured rows — a date column, a description column, and an amount column — already aligned and consistently formatted. This avoids the retyping errors and is more practical for a multi-page statement.

To take this route, open the bank statement converter, upload your PDF, and export a CSV. The date, description, and amount columns come out aligned, so the file is ready for the verification step below rather than needing cleanup first.

Whichever method you use, the goal is the same: a plain CSV with one clean row per transaction.

Verify the columns before you trust the file

A CSV is only useful if the data inside it is right. Whether you exported it from the bank or converted it from a PDF, take a minute to check it before importing it anywhere. Open the file in a spreadsheet program and look for the following.

• A header row on the first line. The first line should name the columns (such as Date, Description, Amount) with the transaction rows directly below. If the bank prepended an account summary, blank lines, or a trailing total row, delete those so the file is header plus transactions only.
• One consistent date format. Every row should use the same date format. Mixed formats are a common cause of import errors, and MM/DD/YYYY versus DD/MM/YYYY confusion can silently swap the day and month. YYYY-MM-DD is the least ambiguous if you get to choose.
• Intact descriptions. Each transaction should keep its full description on one line. If a memo contains a comma (for example, a company name), it should be wrapped in double quotes so the comma does not split the field into two columns.
• A sensible amount column. Confirm money out and money in are represented the way your tool expects — either a single signed column (negative for debits) or separate debit and credit columns. Plain numbers like 1200.50 import more reliably than $1,200.50.
• Totals that match the statement. This is the most important check. Add up the amounts in the CSV and compare the sum, and the opening and closing balances, against the original statement. If the totals match, your rows are almost certainly complete and correct.

Spend the extra minute on that last check in particular. A CSV that imports without an error message can still be missing rows or carrying a misread amount, and the only way to catch that is to reconcile the file against the statement it came from.

Which path to use

If your bank offers a CSV export, use it — the data is coming straight from the source. If you only have a PDF, convert it rather than retype it, then verify the columns the same way. Either route ends in a clean transaction CSV you can import with confidence, as long as you check the totals before you do.