Excel does have a PDF importer. Data, Get Data, From File, From PDF puts the file through Power Query, and on a ruled financial report it works well. Bank statements are the case it was not designed for. Upload the PDF here and get date, description, debit, credit, and balance already in columns.
Upload your bank statement
Drop file here or click to upload
PDF, JPG, PNG, BMP, HEIC, TIFF, MT940
Uploading...
The Power Query PDF connector is a good piece of engineering aimed at a different document. It looks for table structure on each page and hands you what it finds. A bank statement gives it almost nothing to hold onto.
The From PDF connector ships with Excel for Windows on Microsoft 365. Excel for Mac and Excel on the web do not have it, so a Mac user has to borrow a Windows machine or find another route entirely.
Power Query reads the text layer of a PDF, not the image. If you cannot select the text with your mouse, the connector sees an empty page. Scans and phone photos need OCR first, which the connector does not perform.
Column boundaries in a statement exist only as whitespace, since banks typeset the page for printing. The connector infers columns from spacing, so a long merchant name shifts an amount into the wrong field and you find out at the total.
Navigator lists Table001, Table002, Page001 and so on. A twelve page statement means twelve fragments to append, with the account header and summary box mixed in, before anything is sortable.
When a merchant name wraps to a second printed line, the connector reads it as another row with no date and no amount. Your row count stops matching the statement and the split has to be rejoined by hand.
Power Query steps are positional. Point the same query at next month's statement, where the summary box is one line taller, and the removed-rows and promoted-headers steps land on the wrong lines. Maintaining that is a small ongoing job nobody scoped.
Rather than inferring a table from spacing, it rebuilds the ledger the statement represents, then checks its own work against the closing balance.
Date, description, debit, credit, and balance land in their own columns, ready to sort, filter, and pivot immediately.
A description printed across two lines returns as one transaction, so the row count matches the PDF.
Repeated page headers, balance summaries, and promotional panels are left out. Only transactions reach the sheet.
Scanned statements and phone photos are read directly, in PDF, JPG, PNG, BMP, HEIC, and TIFF, with no separate OCR pass.
It runs in the browser, so there is no connector to find, no Excel version to check, and no Windows machine to borrow.
Export QBO, OFX, QFX, and QIF alongside XLSX and CSV, so the same statement imports into QuickBooks, Xero, or Quicken.
No Navigator, no applied steps, no credit card.
Drop in a PDF or scanned bank statement. Multi page and multi month files are fine.
Tip: Password-protected PDFs are supported.
Every transaction is pulled into structured columns automatically, balance included.
Tip: Scans are read with built-in OCR.
Download the XLSX or CSV and start working. Nothing to unmerge, clean, or reshape first.
Tip: Columns come out reconciliation-ready.
An honest side by side, including where Power Query is clearly the right tool.
Skip the twelve-fragment append on every client statement.
Build workpapers without maintaining a query per bank layout.
Get statement data into Excel without the Windows-only connector.
Pull statement history into Excel for reconciliation and close.
Excel can import a PDF using Data, Get Data, From File, From PDF, which runs the file through Power Query. It works on documents with ruled, well-formed tables. Bank statements usually have no gridlines, wrap descriptions onto second lines, and repeat headers on every page, so the import arrives as page fragments with shifted columns. The connector is also Windows only and cannot read scans.
| What you are comparing | BankXLSX | Excel Power Query PDF import |
|---|---|---|
| Availability | Any browser, Mac or Windows | Excel for Windows on Microsoft 365 |
| Scanned statements | Built-in OCR | Not supported, needs a text layer |
| Output shape | One continuous transaction table | One table object per detected page table |
| Column detection | Rebuilt from statement structure | Inferred from whitespace |
| Wrapped descriptions | Rejoined into one row | Usually split into an extra row |
| Running balance | Preserved as its own column | Present but often misaligned |
| Repeated headers | Stripped automatically | Removed manually with query steps |
| Next month, same query | Upload it, same result | Query steps often need adjusting |
| Accounting exports | QBO, OFX, QFX, QIF, plus XLSX and CSV | Whatever you build in the workbook |
| Best for | Statement PDFs of any layout | Ruled tables in reports you receive repeatedly |
Power Query PDF connector behavior checked in July 2026 against Microsoft documentation. Microsoft ships changes to Excel channels regularly, so confirm availability for your build.
If you want to try the native route first, this is the sequence. In Excel for Windows, go to Data, Get Data, From File, From PDF, and pick the statement. In Navigator, expand the list and preview each Table and Page entry to find the ones holding transactions. Select multiple items, load them into Power Query Editor, then append the queries into one table. Remove the header and summary rows, promote the correct header row, set data types on the date and amount columns, and load to the sheet.
That works, and on a simple one-account statement from a bank with a clean layout it can take five minutes. The reason it does not scale is the last two steps. Removing rows and promoting headers are positional operations, so they assume the summary box is always the same height and the transaction table always starts on the same line. Next month it starts one line lower and the query silently eats a transaction.
Power Query is excellent, and this is not an argument against learning it. If you receive the same structured file every month from the same source, in CSV, XLSX, or a genuinely ruled PDF report, a query is exactly right: build it once, hit refresh, done. It is also the correct tool for the work that comes after conversion, like appending twelve monthly CSV exports, merging a vendor lookup table, or unpivoting a report.
The mismatch is narrow and specific. It is PDF bank statements, where the source layout was designed for a human eye and changes shape from bank to bank and sometimes month to month. Use a converter for that step, then keep using Power Query on the clean output, which is where it stops fighting the document and starts saving you time.
Whichever route you take, run the same three tests before you rely on the sheet. Count the transaction rows against the PDF. Add the opening balance to the sum of all amounts and confirm it equals the closing balance on the last page. Check that debits are signed the same way on page one and page nine. The footing test is the important one, because it is the only check that catches a row that quietly vanished.
Once the data is genuinely in columns, the rest gets easy: categorize the transactions, reconcile against your books, or produce a profit and loss report. Working on a Mac, where the connector does not exist? Our guide to converting a bank statement to Excel on a Mac covers the options, and the step by step Power Query walkthrough has the full Navigator sequence.
Not the import step. Copilot is genuinely useful once clean data sits in a table: it writes formulas, builds a pivot, explains a column, and drafts a chart from a plain English request. It does not have a view of the source PDF, so it cannot tell you the import is eleven transactions short. Feed it an incomplete table and it will analyze the incomplete version confidently, which is the failure you least want before a close or a loan submission.
Excel for Windows can import a PDF through Data, Get Data, From File, From PDF, which uses Power Query. It works on ruled tables. On bank statements the import usually arrives as page fragments with shifted columns and repeated headers that need cleaning up.
The PDF connector ships with Excel for Windows on Microsoft 365 subscriptions. Excel for Mac, Excel on the web, and older perpetual versions do not include it, which is the most common reason the option is not in the Get Data menu.
No. Power Query reads the text layer of a PDF. If you cannot select the text with your mouse, there is nothing for the connector to import. The scan has to be run through OCR first, and Power Query does not perform OCR itself.
On Windows, use Data, Get Data, From File, From PDF, then in Navigator select the Table or Page entries holding transactions, append them in Power Query Editor, remove header rows, set data types, and load. On Mac or with a scan, use a converter instead.
Bank statements have no gridlines, so the connector infers columns from whitespace. A long merchant description pushes an amount past the boundary it guessed, and that value lands in the neighboring column. It shows up as a total that will not add.
Often not without adjustment. Power Query steps are positional, so if the summary box is a line taller or the transaction table starts lower on the page, the removed-rows step deletes the wrong lines. Refresh, then verify the row count every time.
Use a converter built for statements, then verify the footing. Opening balance plus the sum of all transactions should equal the closing balance on the last page. If it ties, the extraction is complete and you can start categorizing rather than auditing.
Yes, just not with the built-in PDF connector, which Excel for Mac does not include. A browser-based converter produces the XLSX or CSV directly, and the resulting file opens in Excel for Mac, Numbers, or Google Sheets without any extra step.
Convert PDF statements straight to Excel.
Why Acrobat exports need a cleanup pass.
OCR for scanned and photographed statements.
Convert PDF statements straight to CSV.
The wider software market, compared.
From the same family of tools
Get started converting bank statements to spreadsheets.
USD
per month
billed as
$288 yearly
Choose speed vs accuracy when extracting
| Base AI Faster | 2,500 pages |
| Pro AI Best accuracy | 500 pages |
Scale statement conversion across your team with automation.
USD
per month
billed as
$888 yearly
Choose speed vs accuracy when extracting
| Base AI Faster | 10,000 pages |
| Pro AI Best accuracy | 2,000 pages |
Enterprise-grade bank statement conversion and controls.
USD
per month
billed as
$ yearly
Choose speed vs accuracy when extracting
| Base AI Faster | pages |
| Pro AI Best accuracy | pages |
