Convert PDF Bank Statement to CSV

Free PDF to CSV converter for bank statements. The output uses a standard header row, ISO dates, RFC 4180 quoting, and UTF-8 encoding — drop straight into QuickBooks, Xero, Wave, or any data pipeline.

See How It Works
Free first conversion 1,000+ banks supported Files deleted in 24h

How to convert a PDF bank statement to CSV

  1. Download your bank statement as a PDF from your online banking portal.
  2. Drop the PDF into the upload box above (or click to browse). Files up to 25 MB are supported.
  3. Wait 10–30 seconds while our OCR + AI engine reads the layout and extracts every transaction.
  4. Download the CSV file. The first conversion every 24 hours is free.

Why CSV?

CSV is the lowest common denominator. Almost every accounting tool, ERP, and analytics platform imports it. We produce a UTF-8 CSV with a standard header row, RFC 4180-compliant quoting, and ISO 8601 date formatting.

  • Standard header row: Date, Description, Debit, Credit, Balance, Reference
  • RFC 4180-compliant quoting — descriptions with commas, quotes, or newlines never break the parse
  • UTF-8 encoded — international characters and currency symbols preserved
  • ISO 8601 dates (YYYY-MM-DD) — no Excel reinterpretation as US/UK formats
  • Imports cleanly into QuickBooks Online, Xero, Wave, FreshBooks, Sage, and NetSuite

What gets extracted from your statement

  • Transaction date (normalised to YYYY-MM-DD)
  • Description, payee, and reference where available
  • Debit and credit amounts in separate, signed columns
  • Running balance, where the statement shows one
  • Statement period, opening balance, and closing balance
  • Account holder name and account number (header only)

Convert CSV for any bank

Our parser is bank-agnostic — it reads the layout of your statement directly rather than relying on a hand-written template per bank. That's how we support 1,000+ banks worldwide. Common ones below:

CSV conversion FAQ

What CSV dialect do you produce?

RFC 4180: comma-separated, double-quote-quoted fields, CRLF line endings, UTF-8 with no BOM. This is the dialect QuickBooks, Xero, Excel, and Python's csv module all expect.

Why doesn't QuickBooks recognise my CSV import?

QuickBooks CSV import requires Date, Description, and Amount columns at minimum. Our CSV includes them. If QuickBooks still rejects, switch to QBO export — it carries stable transaction IDs and imports without manual mapping.

Can I customize the column order?

Yes — paid plans let you map columns to the exact schema your downstream tool expects. The default schema works for 90%+ of accounting tools.