How to convert a bank statement PDF to Excel or CSV (and check it's right)
Every bank statement PDF eventually needs to become a spreadsheet — for budgeting, reconciliation, a loan application, or your accountant. Here's every way people actually do it, their honest failure modes, and the one habit that catches the mistakes each method makes.
Option 1: Copy and paste
The fastest thing to try. Open the PDF, select the transaction table, copy, paste into Excel or Sheets. It works — until the PDF's underlying text isn't laid out the way it looks on screen. Common failure modes:
- Rows split across two lines because a description wrapped — you get half a transaction on one row and the amount on the next.
- Columns collapse into a single cell, because the PDF has no real table structure, just text positioned to look like one.
- Multi-line descriptions ("CHECK CARD PURCHASE / AMAZON.COM / SEATTLE WA") get glued onto the next transaction's date.
Best for: a single page, an hour to spare, and a willingness to eyeball every row afterward.
Option 2: Excel's Power Query PDF import
Excel (Data → Get Data → From File → From PDF) can detect tables inside a PDF automatically, and it's genuinely good at simple grids. Bank statements aren't simple grids, though — they're often three or four separate "tables" per page (deposits, withdrawals, fees, running balance) with headers and footers Power Query tries to read as data. Expect to spend time deleting phantom rows and re-merging split columns.
Best for: statements with a clean, single-table layout — try selecting the transaction area with your cursor first; if the selection highlights each column cleanly, Power Query has a good shot.
Option 3: Generic online PDF-to-Excel converters
Fast, no formulas required — you upload a PDF, get back an Excel file. The tradeoff is exactly what it sounds like: your bank statement, containing your name, account number, and every transaction, travels to someone else's server. Read the privacy policy and retention window before using one for a financial document. On accuracy, results vary widely by layout — some handle deposit and withdrawal sections correctly, some don't distinguish credits from debits at all, silently making every amount positive.
The one habit that catches every method's mistakes: verify the balance
Whichever method you use, do this before you trust the output: opening balance plus total credits, minus total debits, should equal the closing balance printed on the statement. If it doesn't, something got missed, merged, or double-counted — and now you know to check row by row instead of trusting a spreadsheet with a silent error in it.
In Excel, a formula like =Opening + SUM(Credits) - SUM(Debits) - Closing should land at zero (allow a cent or two for a bank's own rounding). It's the same check bookkeepers run by hand — it takes thirty seconds and catches the overwhelming majority of PDF-to-Excel mistakes.
The automatic version
This is exactly what StatementLift does, without you touching a formula. Drop your PDF in and it parses transactions right in your browser — never uploaded, which you can confirm yourself in DevTools → Network — then runs the opening plus credits minus debits equals closing check on your file automatically, before you ever pay. Capital One and Bank of America presets are verified against real statements; Chase, Wells Fargo, and Citi have tuned presets plus a generic reader that attempts any text-based layout, and a column mapper for anything the automatic read misses. The first 10 rows are always free to preview.