How to convert a bank statement PDF to Excel (3 methods compared)

There are three realistic ways to convert a bank statement PDF into an Excel spreadsheet: retype it by hand, use Excel's built-in PDF import, or run it through a dedicated converter. Which one makes sense depends on two things — whether your PDF is digital or scanned, and how much your time is worth.

The short version: for one short, digital statement, Excel's own Get Data → From PDF feature is free and often good enough. For scanned statements, photographed statements, or anything more than a couple of pages a month, automated conversion wins decisively — not just on speed, but on the error rate. Here's the honest breakdown of all three.

Method 1: Retype it manually

The default method, and the one most small businesses quietly still use. Open the PDF on one monitor, Excel on the other, and type.

The problem isn't only the time, although the time is real — a typical statement page holds 15–40 transactions, and a busy business account can run to hundreds of rows per month between dates, descriptions, and amounts. The bigger problem is that manual entry feels accurate while it isn't. Transposed digits (€1,540 becomes €1,450), a skipped row after an interruption, a debit typed without its minus sign — these errors are invisible until something downstream refuses to reconcile, at which point you're re-checking every row anyway.

Manual entry makes sense in exactly one situation: a handful of transactions, once, ever. Beyond that it's the most expensive method on this list, even though it looks free.

Method 2: Excel's built-in PDF import (free, sometimes works)

Since Excel 2016, there's a genuinely useful feature hiding in the ribbon: Data → Get Data → From File → From PDF. Excel scans the PDF, lists the tables it detects, and lets you load one into a sheet via Power Query.

When it works well

Digital PDFs (ones where you can select the text with your cursor) with simple, single-line transactions. If your bank produces a clean tabular layout — one row per transaction, consistent columns — the import can land 90%+ of the data correctly, for free, in a couple of minutes.

Where it breaks

Four places, and they're common:

• Scanned or photographed statements. These are images, not text. Excel finds no tables at all. This is the hard stop — no amount of fiddling helps.
• Multi-line descriptions. Many banks spread the payee, reference and transaction type across two or three lines. Excel reads each line as a separate row, shredding the table. Statements from banks like Barclays or mBank are classic examples.
• Tables split across pages. Each page comes in as a separate table that you stitch together by hand, and column widths often shift between pages.
• Separate debit/credit columns and regional number formats. Statements that split amounts into two columns, or use comma decimals (1.234,56), need manual cleanup formulas after import.

Realistic verdict: budget 10–30 minutes per statement for import plus cleanup, more if the layout is hostile. Fine occasionally; painful monthly.

Method 3: A dedicated statement converter

Purpose-built converters do three things the generic approaches can't. First, they handle scans and photos, because they run OCR tuned for financial documents — decimal alignment, minus signs, currency symbols. Second, they understand statement layouts: multi-line descriptions get folded back into one row, tables continue across pages, debit/credit columns become one signed amount, and regional formats are normalised. Third — and this is the part that matters most — good ones verify the output.

The verification test

Every bank statement contains its own answer key: the opening balance, plus all credits, minus all debits, must equal the closing balance. If a converted spreadsheet satisfies that equation, every amount was read correctly. If it doesn't, something was misread — and you want to be told, not left to discover it at tax time. This is the single most important feature to look for in any converter; extraction without reconciliation is just confident guessing. (It's also the check Statement Mill runs on every file before you download it.)

What to check before trusting one

• Balance verification shown per file, not just claimed in marketing.
• Where files are processed and how long they're kept. Statements are sensitive; prefer tools that never store the file at all over ones with a mere retention policy.
• A real free tier so you can test accuracy on your own bank's statement before paying anything.
• Batch support if you'll ever need a whole year at once.

The three methods side by side

Step by step: the fast path

1. Download the statement as PDF from your internet banking — or scan/photograph the paper one. 2. Upload it to a converter with balance verification (you can try Statement Mill free — 20 pages a month, no card). 3. Check the reconciliation status. 4. Download the .xlsx and get on with the actual work: categorising, reconciling, filing.

Special cases worth knowing

A whole year of statements

Twelve PDFs, one deadline. Convert them as a batch rather than one by one, and make sure the tool deduplicates — overlapping statement periods otherwise produce duplicate rows that quietly inflate your totals.

Multi-currency accounts

Fintech statements from Revolut or Wise hold several currencies in one PDF, each with its own balances. Each currency must reconcile separately, and every row needs a currency tag — otherwise your EUR and USD sum into one meaningless column.

Very old statements

Bank archives often deliver older statements as scans even when recent ones are digital. If your project involves anything beyond the last couple of years, assume OCR will be required and pick your method accordingly.

Frequently asked