Home/Formats/Bank Statement to CSV
Converter · PDF Statement → CSV

Bank statement
to CSV.

Convert a PDF bank or credit-card statement into a clean CSV of dated transactions — Date, Description, and a signed Amount — ready for QuickBooks, Xero, or Excel. A balance-reconciliation check flags any row that doesn't tie out before you trust it.

Free preview · $15 full file · 20 MB · batch of 5 · Files auto-deleted after 1 hour.

01 — Convert Ready

Drop PDF statement files here, or click to browse.

PDF statement → CSV · up to 5 files · 20 MB each

No signup · Private upload · Files deleted after 1 hour

⌘↵ to run Files deleted after 1 hour

Why convert a statement to CSV?

How it works

  1. Open the converter. No registration is required.
  2. Upload the statement. Drag and drop your PDF, or browse from your device.
  3. Convert to CSV. Choose the CSV target format and click Convert.
  4. Download and review. Preview the extracted rows, unlock the full CSV (one-time $15), review any flagged rows, then use it in QuickBooks, Xero, or Excel.

What gets flagged

Before the CSV is handed back, a deterministic reconciliation check runs. It flags the statement for review when:

Flagged rows are surfaced for you to review — never silently exported as correct. That review step is the difference between a converter you can trust with your books and one that just dumps the text and hopes.

Good for

Check whether you need a converter at all

Before converting a PDF, look at your bank's download options. Most major banks let you export activity directly as CSV, QFX, or OFX, and a native export is always more reliable than reading it back out of a PDF — the numbers come from the bank's own records rather than from text laid out on a page.

The catch is that those exports usually cover only a recent window. Converting the PDF is the right move when:

If you can download a CSV straight from your bank, do that instead. This tool exists for the statements where you can't.

How the reconciliation check works

Reading numbers out of a PDF can go wrong quietly: a column can be misread, a wrapped line can split a transaction in two, a minus sign rendered as a dash can be dropped. The risk isn't a crash — it's a file that looks fine and is wrong. So every converted statement runs three deterministic checks before you see it:

  1. Running balance. When the statement prints a balance on each line, every row is verified as the previous balance plus that row's amount. A row where those disagree is flagged with the expected and actual figures.
  2. Opening plus transactions equals closing. Independent of per-line balances: the opening balance plus the sum of every parsed amount has to equal the printed closing balance. This catches a transaction dropped entirely, which a per-row check cannot see.
  3. Date ordering. Dates are checked for parsing correctly and running in order. Out-of-order dates are a soft flag — some statements legitimately group by transaction type — but they're worth a look.

Flagged rows are kept, not deleted. The row still appears in the CSV and the statement is marked as needing review, naming the checks that failed, so you can compare against the original before importing. Nothing that fails a check is presented as verified. If the arithmetic doesn't tie out, you find out here rather than during a reconciliation three weeks later.

FAQ

What columns are in the CSV? A dated transaction table: Date, Description, and a signed Amount (money out is negative). Imports cleanly into QuickBooks Online and opens in Excel or Sheets.

How do I know the data is accurate? A balance-reconciliation check compares opening plus transactions against the closing balance and verifies running balances, flagging anything that doesn't tie out.

Does it work on any bank? It reads born-digital PDF statements across many common layouts. If a layout can't be read, it tells you rather than producing a wrong CSV. Scanned image statements aren't supported yet.

Is my statement safe to upload? Files are deleted after 1 hour, never used to train any AI model, and we never connect to your bank. All transfers are encrypted. This is a conversion utility, not financial or accounting advice.

What happens to rows that don't reconcile? They're flagged, not dropped. The row still appears in your CSV, but the statement is marked as needing review with the specific checks that failed, so you can compare against the original before importing. Nothing that fails the balance check is passed off as verified.

Can I open the CSV in Excel or Google Sheets first? Yes. The output is a plain UTF-8 CSV — open it in Excel, Google Sheets, or Numbers to sort, total, or correct anything before importing into QuickBooks or Xero.

Related