How to Convert a Bank Statement PDF to Excel (2026 Guide)

A PDF is a presentation format, not a transaction-data format. To use bank statement rows in Excel, you need to extract the table, review the result against the source statement, and only then use it for reconciliation, bookkeeping, or import.

Use a native bank export first

Before converting a PDF, check the transaction-download area in online banking. If the bank offers CSV, OFX, QBO, QFX, or another structured format accepted by your accounting software, use that export first. It already separates transaction fields and removes an avoidable extraction step.

Use PDF conversion when the bank supplies only a PDF, the native export does not cover the required historical period, or you need an Excel copy for review. Download the original digital PDF where possible, include every statement page, and remove password protection before uploading.

Three practical conversion methods

Method 1: Automated statement extraction

A purpose-built converter can identify transaction rows and prepare dates, descriptions, debits, credits, and balances for spreadsheet export. The result still needs review because document layout and image quality vary.

1. Open the PDF to Excel converter.
2. Upload the original PDF. Unlock encrypted files first.
3. Wait for extraction to complete and open the transaction preview.
4. Compare the preview with the source using the checklist below.
5. Download Excel, CSV, QBO, OFX, QIF, or JSON as required.

This method is useful for multi-page statements, batches, and scans that need text recognition. A digital PDF usually produces cleaner text and table structure than a scan.

Method 2: Excel Power Query

Recent desktop versions of Excel can import tables from many digital PDFs through Power Query. In Excel, open the Data tab, choose Get Data, select From File and then From PDF. Select candidate tables in the Navigator and use Transform Data to fix headers, remove repeated page headings, assign data types, and combine page tables.

Power Query works best when the PDF contains selectable text and consistent table boundaries. It does not remove the need to check whether descriptions wrapped onto another line, whether debits and credits were assigned correctly, or whether each page was included. Scanned image-only PDFs may need text recognition before Power Query can find a useful table.

Method 3: Manual entry or copy and paste

For a short statement, you can create Date, Description, Debit, Credit, and Balance columns and enter each row manually. Copy and paste may help with digital PDFs, but PDF reading order often merges columns or places wrapped descriptions on separate rows.

Manual entry gives you control over each row, but it still needs a second check. Work page by page, mark the last completed transaction, and reconcile totals before using the spreadsheet.

Review converted output before import

Treat the spreadsheet as a draft until it matches the source statement. Use these checks:

• Row count: account for every transaction row and exclude repeated page headers or totals.
• Date range: confirm the first and last transaction dates and check day/month interpretation.
• Opening and closing totals: compare balances where the statement provides them.
• Signed amounts: confirm withdrawals and deposits use the convention required by the destination.
• Source-row spot checks: compare several dates, descriptions, amounts, and running balances across different pages.
• Duplicates: check overlap with bank feeds and files already imported into the destination account.

If a balance does not reconcile, find the first row where the spreadsheet and statement diverge. Common causes are a missing wrapped description row, a debit placed in the credit column, a page omitted during extraction, or a subtotal imported as a transaction.

A worked reconciliation check

Use the synthetic Excel sample to practise the review: an opening balance of 500.00, credits of 1000.00 and debits of 130.50 should close at 1369.50. If the converted sheet closes at 1374.50, the 5.00 difference directs you to look for a missing fee, duplicated credit or incorrect amount. Matching the final balance alone does not prove all rows are correct: offsetting errors can cancel out.

The Excel exporter derives columns from extracted fields; it is not a fixed import template. Confirm numbers are numeric and inspect the Date, Description, Debit, Credit and Balance fields when present. For an accounting import with one Amount column, a debit of 125.50 becomes -125.50 and a credit of 1000.00 stays positive. The Xero mapping example shows the four exported columns.

Power Query users should compare each page's row count before combining tables and check wrapped descriptions. Microsoft's PDF connector documentation describes Navigator, Transform Data and handling multi-line rows. These are review methods, not promises that any one extraction method will recover every row.

For original statement downloads and local checks, see India, South Africa and N26, including its native CSV option.

Why scans need extra checks

A scan stores each page as an image. Text recognition must infer characters and table boundaries, so low resolution, skew, shadows, stamps, handwriting, and compression can change the result. Dates and decimal points deserve particular attention.

Use a straight, legible scan and confirm that no page is cropped. If you can download a digital PDF from the bank instead, prefer it. Digital PDFs usually contain selectable text and more consistent positioning. Password-protected PDFs must be unlocked before either automated extraction or most desktop import tools can read them.

Choose the output for the next step

• Excel (.xlsx): useful for review, formulas, filters, and reconciliation work.
• CSV (.csv): useful for software that maps date, description, and amount columns.
• QBO, OFX, or QIF: use only when the destination product and account workflow support that format.
• JSON: useful for structured application or API workflows.

Always check the destination application's current import documentation. Supported formats, navigation labels, account requirements, and duplicate handling can change by product and version.

Frequently asked questions

Should I use a native bank export instead of converting a PDF?

Yes, when the bank offers a structured export accepted by your destination. It avoids an extra extraction step. Convert the PDF when a suitable native export is unavailable.

What should I check after conversion?

Compare the row count, date range, signed amounts, and available opening or closing totals. Spot-check transaction descriptions and amounts on multiple pages.

Do scanned statements work?

They can be processed, but scans need more review because text recognition is affected by image quality and page alignment. Use the digital statement download when possible.

Can I use a password-protected statement?

Unlock or remove encryption from the PDF first. A conversion tool cannot read a file that remains password protected.