Bank Statement PDF to CSV Converter (OCR)

Convert bank statement PDFs to clean CSV or JSON transactions: date, description, amount, balance. Scanned statements are OCR'd automatically. Import-ready layouts: Xero (dd/mm/yyyy), QuickBooks 3-column, or generic debit/credit/balance. Batch as many statement URLs as you like. $0.04 per page - no subscription, and your statements stay yours: nothing stored, nothing shared.

Quick start

1. Paste direct links to your statement PDFs into Statement PDF URLs. Use direct-download links - a Google Drive or Dropbox share page link returns a web page, not the file.
2. Pick the date convention printed on your statement (AU/UK/NZ day-first, US month-first, or ISO year-first) and the CSV layout you want.
3. Run. Each statement produces its own CSV in the key-value store, plus one combined dataset of every transaction, plus a per-statement summary (OUTPUT) with a reconciliation report.

Example output row

{
  "date": "2026-03-02",
  "description": "EFTPOS WOOLWORTHS SHEARWATER",
  "amount": -142.35,
  "balance": 4857.65,
  "sourceUrl": "https://.../statement-mar.pdf"
}

What it does

• Extracts the text layer from statement PDFs (no OCR needed for bank-generated PDFs)
• Detects transaction lines across common layouts (date / description / amount / balance)
• Gets debits and credits RIGHT: every amount's sign is verified against the statement's own running balance, row by row - an unmarked deposit is never flipped into an expense by a page full of debits
• Skips opening/closing/brought-forward balance lines instead of importing them as phantom transactions
• Reports its own working: each statement's summary counts how many rows reconciled against the running balance, and anything unverifiable is flagged review, never shipped as ok
• Multi-line and dateless continuation lines handled via last-seen-date carry
• Outputs one CSV per statement + a combined dataset of all transactions

What it does NOT do

• No bank logins, no scraping, no storage beyond the run. You supply your own PDFs, they are processed inside YOUR Apify account, and the developer never sees or stores them.
• Scanned (image) statements are OCR'd automatically - and ALWAYS flagged review with a confidence score, because OCR'd figures should be verified against the original before they go anywhere near your books. A scan too poor to read is flagged needs-ocr, not guessed.
• Unrecognised layouts are flagged review with an invitation to send the bank name - each added layout makes the product better for everyone.
• Extracted figures are not financial, tax or accounting advice - verify the reconciliation summary before importing into your books.

Pricing

Pay-per-event: a few cents per statement page actually converted. Statements that fail or need OCR are not charged as converted. No subscription.

Terms of use

Process only statements you own or are authorised to process. Not affiliated with or endorsed by Xero, Intuit QuickBooks, or any bank or accounting vendor named for compatibility.