How to convert a bank statement PDF to Excel (every method compared)

There are seven realistic ways to get a bank statement PDF into Excel: retype it, copy and paste, use Excel’s own PDF import, export from a PDF editor, use a generic online converter, download transactions from your bank instead, or use a converter built for bank statements. The right one depends on how many statements you have, whether they’re scans, and how much checking you can afford.

First: is your PDF digital or scanned?

This decides which methods are even possible. Open the PDF and try to select a single word.

You can highlight and copy text: it’s a digital PDF, generated by the bank. Every method below can work.
The whole page selects as one block, or nothing selects: it’s a scan (or photo) inside a PDF. There’s no text, only an image. Only methods with OCR will work. See why scanned statements are hard to convert.

Method 1: Retype it

Open the PDF on one screen and Excel on the other, and type.

Good for: one short statement, when nothing else is to hand.
Problems: slow, tiring and error-prone. Transposed digits (86.40 typed as 68.40) are the classic mistake, and they don’t show until the balance doesn’t tie out.
Handles scans: yes, since you are the OCR.

If you must, type the running balance too and add a check column, previous balance + amount, so each typo shows up on the row where it happened.

Method 2: Copy and paste

Select the transaction area in your PDF viewer, copy, paste into Excel.

Good for: short, simple digital statements.
Problems: PDF text has no real columns, so pasted data often lands in one column or splits unpredictably. Wrapped descriptions become extra rows. Separate money-in and money-out columns shift. Headers and footers from each page come along.
Handles scans: no.

Excel’s Text to Columns and Paste Special → Text can rescue some pastes. Expect cleanup on every page.

Method 3: Excel’s built-in PDF import

Some versions of Excel can import tables from a PDF directly (in Microsoft 365 for Windows, look under Data → Get Data → From File → From PDF). It detects tables on each page and loads them through Power Query.

Good for: digital statements with clearly ruled tables.
Problems: each page often comes in as a separate table that you have to append. Detection varies by layout. Multi-line descriptions and split amount columns still need fixing. Availability depends on your Excel version and platform.
Handles scans: no; it needs a digital PDF.

Method 4: Export from a PDF editor

Full PDF editors such as Adobe Acrobat (paid versions) can export a PDF to an Excel workbook, and some include OCR for scanned documents.

Good for: occasional conversions if you already pay for the software.
Problems: general-purpose exports try to reproduce the page, not the transactions. Expect merged cells, headers repeated per page, and amounts spread across columns that need consolidating.
Handles scans: with OCR, sometimes. Results vary with scan quality.

Method 5: A generic online PDF-to-Excel converter

Many websites convert any PDF to Excel.

Good for: quick one-offs with non-sensitive documents.
Problems: they aren’t built for statements, so the output usually needs the same cleanup as an editor export. More importantly, you’re uploading a sensitive document. Check where it’s processed, how long it’s kept and whether it’s used for anything else before you upload a bank statement. Our security checklist helps.
Handles scans: some do, with OCR.

Method 6: Don’t convert, download

Many banks let you download recent transactions from online banking as CSV or another data format.

Good for: your own accounts, recent periods.
Problems: downloads often cover only a limited history, so older months may exist only as PDF statements. Columns and date formats differ between banks. And if a client sent you PDFs, you don’t have their online banking.
Handles scans: not applicable.

If this covers what you need, it’s the cleanest option. Use it.

Method 7: A converter built for bank statements

Dedicated tools such as statement.work read a statement as a statement: they know what a transaction row, a running balance and a page header are.

Good for: regular work, many statements, several banks, scans and photos.
Problems: a sensitive upload, so judge the tool’s data handling (statement.work encrypts in transit and at rest, deletes source files after processing on a retention window you control, and never trains on your data). Like any extraction, check the result against the statement.
Handles scans: yes, along with phone photos.

The output is one row per transaction with date, description, amount and running balance in consistent columns, plus a category, exported to Excel, CSV or JSON.

The comparison

Method	Effort per statement	Handles scans	Consistent columns across banks	Main risk
Retype	Very high	Yes	Up to you	Typos
Copy and paste	High	No	No	Shifted columns
Excel PDF import	Medium	No	No	Per-page tables, splits
PDF editor export	Medium	Sometimes	No	Page-shaped output
Generic online converter	Medium	Sometimes	No	Data handling, cleanup
Bank download	Low	n/a	No	Limited history
Statement converter	Low	Yes	Yes	Data handling, still check

Whatever you choose, check it

Every method can drop or misread a line. Three checks catch nearly everything:

Balance check: opening balance + money in − money out = closing balance.
Count check: number of rows equals the number of transactions on the statement.
Running balance chain: each balance equals the previous balance plus that row’s amount. The first broken link points at the problem row.

Which method should you use?

One digital statement, once: copy-paste or Excel’s PDF import.
Your own recent transactions: the bank’s download.
Scans or photos: OCR, either a PDF editor with OCR or a statement converter.
Regular work across clients and banks: a statement converter, for the consistent columns as much as the speed.

For the format question that follows, see CSV vs XLSX.