There are four common ways to convert a bank statement to Excel: copy and paste from the PDF, download the activity from the bank, import the PDF with Excel's Get Data from PDF, or run the file through OCR. A scanned statement needs OCR, and every method still needs a balance check.
Copy and paste a bank statement into Excel: when it is enough
Copying and pasting a bank statement into Excel works for a short digital statement with a dozen transactions or so. Select the transaction lines in the PDF viewer, paste them into a sheet, and split the text into columns. Past a page or two, the cleanup takes longer than the copying, and errors start to slip in.
The first problem is that pasted text often lands in a single column. Each line of the statement becomes one cell holding the date, the description and the amounts run together. Excel's Text to Columns wizard can split it, and the steps are in pasting bank statement text into Excel columns.
Splitting on spaces breaks descriptions apart. "ACH PAYMENT RIVERBEND UTILITIES" becomes four cells, and the amount ends up in a different column on every row depending on how many words the description had. Someone then drags cells back into place by hand, which is where transposed digits and missed rows come from.
The second problem is page breaks. Copying one page at a time means repeating the selection, the paste and the split for every page, and checking that the last line of each page made it across. A ten-page statement turns into ten small jobs.
Copy and paste is still the right tool now and then. A preparer who needs the five largest deposits from one month, or a single check number, does not need a full conversion. When the goal is every transaction in a sheet that ties to the statement, one of the other methods is usually faster. The full sequence for that job, including the balance check, is in the guide on converting a bank statement PDF to Excel step by step.
Excel's Get Data from PDF on a bank statement
Excel's Get Data from PDF reads a digital PDF, finds the tables in it and loads the chosen ones into a sheet through Power Query. On a bank statement it usually finds the transaction list, often alongside a summary box and a daily balance table. It needs a PDF with real text, not a scan.
Microsoft's article on importing data from data sources gives the path as Data > Get Data > From File > From PDF. The Navigator then shows the tables it found, and you can load one straight in or choose Transform Data to clean it first. The article lists Excel for Microsoft 365 and Excel 2016 through 2024 among the versions it applies to, and says the PDF connector needs .NET Framework 4.5 or higher.
Power Query handles multi-page statements better than copy and paste. The Power Query PDF connector documentation says a MultiPageTables option, on by default, combines similar tables on consecutive pages into a single table. A statement whose transaction list runs across six pages can come in as one table instead of six.
The same documentation names the main weak spot: multi-line rows. A description that wraps onto a second line may come in as its own row, with no date or amount. The documentation suggests fixing these with operations such as Table.FillDown or Table.Group. On a bank statement, check descriptions with a long payee name or a wire reference first.
Other splits happen where a statement's layout changes mid-document. A statement that lists deposits in one table and checks in another, with a separate electronic debits table, comes in as several tables. That is fine, as long as you load all of them and none twice. The tie-out catches either mistake: beginning balance plus credits minus debits should equal the statement's ending balance.
Get Data from PDF costs nothing extra for anyone who already has a supported version of Excel. It is the method most firms try first, and for clean digital statements from one bank it often holds up.
Which bank statement conversion method works on a scanned file?
Only an OCR-based method can convert a scanned bank statement, because a scan is a picture of a page with no characters in it. Copy and paste selects nothing useful, and a tool that reads text from the PDF has no text to read. OCR, short for optical character recognition, turns the image into characters first.
How to tell the two kinds of file apart, before choosing a method, is covered in the guide to scanned versus digital bank statement PDFs.
Excel has an OCR route of its own. Microsoft's article on inserting data from a picture describes Data > From Picture, choosing Picture From File or Picture From Clipboard, reviewing the results, correcting errors and then selecting Insert Data. The article applies to Excel for Microsoft 365, and its tips say to crop the image to the data you want, avoid images taken at an angle, and keep the image in focus.
That route works one picture at a time, so a scanned multi-page statement means saving or capturing each page as an image first. The review step matters. OCR reads characters, but amounts on a bank statement are where a misread costs most: a 3 read as an 8, or a decimal point lost. The post on bank statement OCR covers the common misreads.
Dedicated converters and document-processing tools also use OCR, often on the whole PDF at once. Whichever route reads the scan, the output still needs the same tie-out as a digital conversion, and the checks in what to test in a bank statement converter apply to all of them.
How long does each bank statement conversion method take?
Time per bank statement depends mostly on the input: a digital PDF from a bank the firm has seen before converts quickly by most methods, and a scan is slow by every method except a dedicated tool. The table below gives rough example estimates for one ten-page statement. Time your own statements before relying on any figure.
| Method | Digital PDF | Scanned PDF | Example time, 10-page statement | Typical errors | Cost |
|---|---|---|---|---|---|
| Copy and paste plus Text to Columns | Yes | No | 45 to 90 minutes | Split descriptions, shifted amounts, rows missed at page breaks | Free |
| Bank download (CSV or spreadsheet) | Not needed | Not needed | 5 minutes, if the period is still available | Period cut off at the download window, different columns from the PDF | Free |
| Excel Get Data from PDF | Yes | No | 15 to 30 minutes | Wrapped descriptions as extra rows, header rows, tables loaded twice | Included with supported Excel versions |
| OCR (Excel Data from Picture or a converter) | Yes | Yes | 20 to 60 minutes with review | Misread digits, lost decimal points, signs on the wrong side | Microsoft 365 subscription, or a converter's fee |
All figures in the table are illustrative examples for planning, not measurements. They include the balance check, because a conversion that has not been tied out is not finished.
The bank download row needs a caveat. It is the fastest by far when it exists, because no conversion happens at all. Banks limit how far back a download goes. U.S. Bank's help page on downloading transactions offers CSV, QFX and QBO files for up to 18 months of history and points to account statements for anything older. Wells Fargo's business online banking page says downloads cover the last 90 days by default, with up to 18 months of activity possibly available.
Error risk rises with every manual step. Copy and paste carries the most, because a person moves every value. Get Data from PDF and OCR move values automatically but introduce their own patterns of error, which is why the tie-out does not get skipped for any of them.
Mixing methods within one client is common and sensible. A year of statements might be nine months from the bank's download, two months through Get Data from PDF because they fall outside the window, and one scanned month through OCR. Keep the same column layout for all twelve sheets, so the months stack into one table at the end without rework.
Volume changes the picture. One statement a month by hand is manageable. Forty clients with three accounts each is 120 statements a month, and the minutes in the table multiply. The guide to bank statement to Excel software for accounting firms looks at what changes at that scale, and free routes for PDF bank statements sets out where the no-cost options stop.
When not to convert a bank statement to Excel at all
Sometimes converting a bank statement to Excel is the wrong job. If the bank can export the same period as a spreadsheet, or the books already pull transactions from a bank feed, the rows exist already. If the engagement needs only the ending balance, reading one number off the statement is enough.
When a bank export covers the period. A spreadsheet download from the bank is the bank's own data, not a reading of a printed page. For any period inside the download window, ask the client for the export instead of the PDF. The post on the export formats banks offer covers CSV, QFX, OFX and Excel downloads.
When the books already have the transactions. A bookkeeping client whose accounting software receives a bank feed already has the transactions in the ledger. The statement's job then is to confirm the ledger, by matching the ending balance and looking for items the feed missed. Converting the whole statement duplicates work the feed did. The QuickBooks, Xero and Excel category covers how statement data and accounting software meet.
When only a balance is needed. Some work needs just the year-end balance of each account, or a single month's ending figure. Read it off the statement and note the page.
When the statement will be reviewed, not analysed. A preparer looking for one unusual deposit can search the PDF for the amount. A full sheet is only worth building if someone will sort, filter or sum it.
When the job does call for full conversion across many clients, it helps to have one tool that reads every kind of statement the firm receives. Schema CPA classifies each page it receives, including bank, savings and loan statements, and the documents section of the homepage lists the categories it reads.