Back to blog
How-to··6 min read

How to convert a bank statement PDF to Excel (3 ways)

Three ways to turn a bank statement PDF into a clean Excel spreadsheet — copy-paste, Excel's own import, and automatic parsing — with the tradeoffs of each and how to keep your data private.

A bank statement PDF is easy to read and impossible to work with. The moment you want to total your spending, filter by merchant, or hand the numbers to a spreadsheet, the PDF fights you. This guide covers the three realistic ways to convert a bank statement PDF to Excel — from fully manual to fully automatic — and the tradeoff each one asks you to make.

First: check whether you need to convert at all

Most banks will hand you a CSV, QFX, or OFX export directly from online banking, and when that's available it beats converting a PDF — the data is already structured, so nothing can be misread. Look for a download or export control near the transaction list rather than in the statements section.

The catch, and the reason PDF conversion exists at all:

  • The window is short. CSV export usually covers only recent activity — commonly 90 days to about 18 months. Statement PDFs typically go back further, and they're what you kept when you closed the account.
  • Closed accounts and old years. Once an account is closed, the PDFs you saved are often the only record left.
  • Credit cards are patchier. Plenty of card issuers offer PDFs for years but CSV for months.
  • The CSV can be thinner than the PDF. Some exports drop the running balance, or truncate the descriptor the PDF shows in full.

So: if your bank offers CSV for the period you need, take it. If you need last year, a closed account, or a longer history than the export window, you're converting PDFs — read on.

Is your PDF text or a picture?

This determines which methods can possibly work. Open the PDF and try to select a transaction description with your cursor. If the text highlights, it's a text-based PDF and every method below is available. If nothing highlights — you're dragging a box over an image — the statement is a scan, and only OCR will read it, with the accuracy caveats that implies.

Statements downloaded from a bank's website are nearly always text-based. Scans usually come from photographing paper or printing to image. If you have the choice, re-download from online banking rather than scanning what came in the post — it's the difference between exact figures and best-guess digits.

Method 1: Copy and paste (free, tedious, error-prone)

The zero-tools approach: open the PDF, select the transaction table, copy, and paste into Excel. It sometimes works for a single short statement.

  1. Open the PDF and select the transaction rows. Drag to highlight just the date/description/amount table, not the header or marketing footer.
  2. Paste into Excel. Use Paste Special → Text to avoid importing formatting garbage.
  3. Split the columns. Everything usually lands in one column, so you'll need Data → Text to Columns to break out date, description, and amount.
  4. Fix the wrecked rows by hand. Multi-line descriptions, wrapped merchants, and negative amounts in parentheses all break the alignment.
Copy-paste breaks down fast on real statements. Most bank PDFs use absolute text positioning, so a clean-looking table often pastes as a jumbled single column with amounts detached from their descriptions. Fine for 10 rows; miserable for 200.

Method 2: Excel's built-in PDF import (Power Query)

Modern Excel (Microsoft 365) can import a PDF directly through Power Query, which is a real step up from copy-paste.

  1. Go to Data → Get Data → From File → From PDF and pick your statement.
  2. In the Navigator, choose the table Power Query detected for the transaction pages. Statements often split across several tables — one per page.
  3. Click Transform Data to clean it: remove header rows, set data types, and append the per-page tables into one.
  4. Load the result into a worksheet.

This is the best free option if you already have Microsoft 365 and don't mind learning Power Query. Its weaknesses: it only detects tables it can see (scanned or oddly-formatted statements defeat it), it does nothing to clean up cryptic merchant names, and you get raw rows — no categories, no subscription detection, no merging across months.

One thing it does do well: the query is reusable. Point it at next month's statement and the same cleaning steps replay, which takes the sting out of a recurring job if your bank's layout is stable.

Method 3: Automatic parsing (fastest, and it categorizes)

A purpose-built converter reads the statement structure for you and returns a clean table in seconds. This is what Sortlumo does: you drop in the PDF and it extracts every transaction, normalizes the merchant, assigns a category, and lets you export straight to Excel.

  • No column-splitting. Date, description, merchant, amount, and running balance come out already separated.
  • Merchants are readable. SQ*TARTINE becomes Tartine Bakery; AMZN MKTP US becomes Amazon.
  • Categories are applied. Every row lands in one of 22 spending categories, consistently across statements.
  • Months merge. Upload a year of statements and export one chronological spreadsheet.

There are step-by-step download guides for the big issuers — Chase, Bank of America, American Express, and more on the converter page.

The five things that break after any conversion

Whichever route you take, the same handful of problems show up in the spreadsheet. They're all fixable, and knowing them saves an hour of confusion.

  • Amounts that are text, not numbers. If they left-align and refuse to sum, Excel is treating them as text — usually because of a currency symbol or thousands separator. Strip those with Find & Replace, or wrap in VALUE().
  • Negatives in parentheses. (45.20) means −45.20 in accounting notation, but Excel may read it as text. Replace the brackets with a leading minus before you total anything.
  • Dates as text. Same symptom, and worse consequences — sorting goes alphabetical, so November lands before March. DATEVALUE() or Text to Columns with an explicit date format fixes it.
  • Day/month order. A statement written 03/04 is ambiguous, and an import can silently pick the wrong reading. Check a row you recognize before trusting the whole column.
  • Descriptions split across rows. Long merchant strings wrap in the PDF and arrive as orphaned half-rows with no amount. Merge them back before filtering, or they'll quietly vanish from every total.

Always reconcile before you trust it

The most valuable minute you'll spend: sum your converted amounts and check the total against the statement's own summary box. Deposits and withdrawals should each match. If they don't, a row was dropped or double-counted — and it's far better to learn that now than after you've built a budget on it. The summary box exists precisely to make this check possible.

Turning rows into answers

A spreadsheet of transactions still isn't insight. Two moves get you most of the way: add a category column, then build a PivotTable with category as rows and month as columns. That single view answers “what do I spend on dining, and is it growing?” — which is usually the actual question behind wanting the data in Excel.

Categorizing by hand is the slow part, and it's the part you have to redo every month. A converter that applies categories consistently is doing the work that makes the pivot worth building.

Which method should you use?

  • One statement, one time → Copy-paste, or Power Query if you have 365.
  • Recurring, and you want it clean → An automatic converter. The time saved on the second statement already pays for it.
  • You want spending insight, not just rows → A converter that categorizes and detects subscriptions, so the spreadsheet answers questions instead of just holding data.
  • Your bank offers CSV for the period → Use it. No conversion beats no conversion.

A note on privacy

Plenty of free "PDF to Excel" websites will happily accept your bank statement — and you've just uploaded every transaction to an anonymous server. Before you paste a statement anywhere, check where the file goes. Sortlumo never asks you to link a bank account; your PDF stays encrypted in your account and is deletable at any time. That's the whole reason to prefer a tool built for financial documents over a generic converter.

The same caution applies to the desktop route. A statement emailed to yourself for convenience, or dropped into a shared folder, is a full record of your finances sitting somewhere you weren't thinking about. Wherever it ends up, it deserves the same care as the account itself.