How to Get Bank Transactions Into a Spreadsheet

You need last month's transactions in a spreadsheet. Your bank gives you a PDF. Here's the practical route from one to the other, including the step most people skip. Verifying the output is right.

First: check whether your bank offers CSV directly

Before converting anything, look in your online banking for a CSV, OFX, or QIF export option. Many banks have one buried under "Download", "Export", or a small icon near the transaction list. If it's there, use it. Data straight from the source will always be more reliable than anything extracted from a PDF afterwards.

Convert from PDF when: the export only goes back a few months and you need older data, the bank offers PDF statements only, you're working from a statement someone else sent you, or you need a specific statement period the export tool won't produce.

Step 1. Confirm your PDF has a text layer

Open the PDF and try to select a transaction description with your cursor. If it highlights like normal text, you're fine. If nothing selects, or the page behaves like one flat image, it's a scan. And it needs OCR before any converter can read it. See scanned vs. Digital PDFs for more on the difference.

Statements downloaded directly from online banking are essentially always text-based. Ones that have been printed and re-scanned, or photographed, are not.

Step 2. Convert

Load the PDF into a converter. If the statement contains anything you'd rather not hand to a third party. And a bank statement usually does, prefer one that works in your browser rather than uploading to a server. Our converter does this; you can verify it by disconnecting from the internet after the page loads and converting anyway.

Step 3. Check the output before you use it (don't skip this)

This is the step that separates usable data from a slow-motion error. Four checks, in order of how much they catch:

Does it reconcile?

If your statement has a running balance column, every transaction amount should equal the difference between consecutive balances. This is arithmetic your bank already did, so it's a genuine correctness check rather than a guess. A good converter runs it automatically and flags rows that fail. If yours doesn't, spot-check five rows by hand.

Do the dates look right?

The single most dangerous failure is date misreading. 03/04/2026 means March 4th in the US and 4th March in the UK, and software that picks wrong shifts transactions by months without any visible error. Check a transaction you remember and confirm the date matches. Watch especially for dates where both numbers are 12 or under. Those are the ambiguous ones.

Are the signs right?

Money out should be negative, money in positive (or in correctly-labeled separate columns). Scan for anything obviously backwards. A payroll deposit showing as negative, a card purchase as positive.

Is the row count right?

Count the transactions on the last page of the PDF and check the converter found that many. Missing rows are easy to overlook, especially where a statement has section headers or subtotals interrupting the table.

Step 4. Clean up in the spreadsheet

Once the CSV is open:

• Format the date column as a date, not text, so sorting works properly.
• Check the amount column is numeric. If sums don't work, there's usually a stray currency symbol or a non-breaking space.
• Add a category column if you're doing bookkeeping. This is the part that needs a human. Leave it to the end, once the raw data is trustworthy.

A note on multiple accounts

Convert each account separately and add an "Account" column before combining them. Merging first and trying to work out later which transaction came from where is much harder than it sounds, especially when two accounts have similar transaction descriptions.

Photographed or scanned statements have no text layer to read. The searchable PDF tool adds one, and the statement converter can also recognize a scan directly.