Bank Statement PDF to Excel: Local Conversion & CSV Guide

Written by Feroz Sheikh · Founder, Doha, Qatar

Updated 2026-09-30. This is a working note for a live tool, not legal, tax, or professional advice.

Select a text-layer bank statement under 25 MB. Enter its password locally if requested. Extract the table, then inspect dates, descriptions, debit, credit, balance and each original source line. Bank-name detection is a label only: extraction uses a generic date and amount parser rather than a bank-certified template. Review every flagged row before enabling Excel or CSV export.

Check the PDF type before extraction. Try selecting and copying one transaction line in your PDF viewer. If the result is readable text, this workflow may be suitable. If the page is only a photographed or scanned image, the bank-statement parser cannot read it directly: a separate OCR step and a careful numerical review are needed. The local English OCR tool has its own smaller limits and is not a bank-certified recognition service. A PDF can also contain a text layer in a visual order different from its row order, so selection alone does not guarantee reliable extraction.

The current bank-statement workspace accepts one PDF below 25 MB and reads at most 40 pages. Split an unusually long statement into consecutive periods before conversion, retain the opening and closing balance for each part, and avoid overlapping transaction dates between files. Enter a password only into the local password field when you already know it and have permission to open the document. The tool does not guess passwords. Close unused browser tabs if a large file exhausts device memory; keep the original until all exports are checked.

Amounts are parsed as complete values, including ungrouped decimals such as 1234.56. When a statement shows an amount and running balance, debit or credit is inferred only if the balance movement matches that amount within one cent. Inconsistent movements are marked for review instead of replacing the transaction with an invented difference. The exported sheet includes reconciliation status and source text.

For example, a previous balance of 10,000.00 followed by an amount of 1,234.56 and a balance of 8,765.44 supports a debit of 1,234.56. If the new balance is 8,000.00, the row is a mismatch; the parser must not silently change the amount to 2,000.00. Check opening balance, missing rows and final balance against the original statement.

Start with a short synthetic or redacted statement while learning the preview. Rows marked review or mismatch remain visible, with the original line beside the output. Acknowledging warnings permits export; it does not certify that the issues were corrected.

Compare the first transaction, the transitions between pages and the final transaction, then reconcile every row before using the spreadsheet. A continuation line or repeated page header may require manual cleanup. Keep the unedited export so changes remain traceable.

For a QuickBooks Online bank-account import, use QuickBooks CSV after reviewing the complete statement. Intuit accepts a three-column Date, Description, Amount file or a four-column Date, Description, Credit, Debit file. This tool exports the three-column version, with negative amounts for money out and positive amounts for money in. Your regular Excel and CSV exports still keep source lines, balances and review status.

Choose the date order used by the source, and confirm the century when it uses two-digit years. The QuickBooks file uses DD/MM/YYYY; choose that format when mapping the upload. Extraction warnings, invalid dates, uncertain transaction directions and balance mismatches block the import export instead of silently dropping transactions. Acknowledging a warning on the ordinary export does not fix the underlying row. Credit-card statements need separate sign and account-type review against Intuit's instructions.

The import file is prepared locally and is limited here to 1,000 transactions and 350 KB. Use English descriptions as required by Intuit. In QuickBooks Online, select the correct bank account, map Date, Description and Amount, inspect the preview, and confirm that no transactions duplicate an earlier import. No bank connection or QuickBooks sign-in is required to prepare this file; this tool does not upload transactions to QuickBooks.

Choose the export for the next task rather than treating all formats as interchangeable. Excel is convenient for inspecting and filtering the full review sheet, while ordinary CSV suits a later data-cleaning workflow. QuickBooks CSV intentionally has a narrower import shape and must be mapped to the correct account and date format. Opening an export successfully proves that the file is readable; it does not prove that every transaction, sign or balance is correct. Do not share statements, generated spreadsheets or screenshots containing account numbers with a public support thread. Use a synthetic example when reporting a parsing problem.

Reference: Intuit UK: Prepare a CSV file for bank upload

Reference: Intuit: Manually upload transactions into QuickBooks Online

Open Bank Statement PDF to Excel

All guides