Tallyproof

Guides

Bank statement PDF to Excel: what works and what to watch for

Excel is where a lot of statement work ends up: sorting expenses for a tax return, building a cash flow, or tidying transactions before they go to a bookkeeper. Getting a PDF statement into a spreadsheet is the easy part. Getting it in without Excel quietly changing dates, numbers and reference codes takes a little more care.

This guide covers Excel’s built-in PDF import, the CSV route, and the formatting problems that catch people out.

Option 1: Excel’s Get Data from PDF

Excel can read tables from a PDF through Power Query: Data > Get Data > From File > From PDF. It shows the tables it has detected on each page, and you load the ones you want into a sheet.

It’s worth trying if you have it, and the file never leaves your computer. But know its limits:

Option 2: Convert to CSV, then bring it into Excel

The other route is to convert the statement to a CSV file first, then open that in Excel. With Tallyproof, the PDF is read in your browser and not uploaded, every row is checked against the running balance printed on the statement, and rows that don’t add up are highlighted before you download anything. Choose CSV (Excel, Google Sheets) as the format. One statement at a time is free.

Then comes the part that trips people up: how you open the CSV.

Don’t just double-click the CSV

When you open a .csv file directly, Excel uses its current default settings to decide what each column is (Microsoft). For bank transactions those guesses can be wrong in ways that are easy to miss.

The safer way is Data > From Text/CSV. You get a preview, and you can set each column’s type before the data lands in the sheet. For a column that must stay exactly as written, such as a reference number, set the type to Text in the Power Query editor (Microsoft).

Date pitfalls

Dates are the most common problem.

The cleanest fix is to export dates in a form Excel can’t misread. Tallyproof lets you choose the date format before downloading, including year-month-day (2026-04-03), which can’t be confused between day-first and month-first.

Number pitfalls

Leading zeros

Excel strips leading zeros from anything that looks like a number, so a reference like 000123 becomes 123 (Microsoft). That matters for cheque numbers, invoice references and account numbers in descriptions.

In Microsoft 365 and Excel 2024, you can turn this off under File > Options > Data > Automatic Data Conversion (on a Mac, Excel > Preferences > Edit). The same settings control converting long numbers to scientific notation and turning strings of letters and numbers into dates (Microsoft). In older versions, import those columns as Text using From Text/CSV.

Formulas hiding in descriptions

A CSV cell that begins with =, +, - or @ can be treated by a spreadsheet as a formula rather than text. This is known as CSV or formula injection, and it’s a security issue when a file contains text that came from someone else (OWASP). Bank descriptions often include text other people typed, such as a payment reference. If Excel shows a security warning about links or external content when you open a statement file, don’t enable it. Check the cell first.

Check the totals once it’s in Excel

After importing, two quick formulas tell you whether anything was lost along the way:

  1. =SUM() of the signed amount column should equal the closing balance minus the opening balance on the statement.
  2. =COUNT() of the amount column should equal the number of transactions in the PDF. Count them page by page if you need to.

If both agree, and the dates pass the ISNUMBER test, the spreadsheet is a faithful copy. For more ways to test a conversion, see how to check a converted bank statement is accurate. If you’re heading to accounting software rather than a spreadsheet, see the differences between CSV, OFX and QIF.

Sources

Checked on 2 October 2026.

Convert a statement now