Convert bank statement PDF to CSV

We read the PDF page by page. For text-based statements — the kind most banks send — we match the transaction grid against the bank's known layout. For scanned statements, we run OCR first and then extract. The output has the same shape either way: one row per transaction, four columns, no worksheet formatting baggage.

The free tier covers the first 5 pages of any file. That's the full document for most single-month personal checking statements. Longer files unlock for $2.99 per document, or you can pick a monthly plan on the pricing page.

No name, email, or card before the preview. Upload, see the extraction, then decide whether to pay.

One convention for the Amount column: positive for money in, negative for money out. We don't split into separate Debit and Credit columns by default because most downstream tools prefer the single signed column. If you need the split, a toggle in the output panel switches it with one click.

Balance is the running balance printed on the statement. Some banks only print balance on the last row of each day — in that case we forward-fill so every row has a value. That's a quiet difference from most converters and the reason reconciliation tools stop complaining about empty cells.

A dedicated parser knows where a specific bank places value dates, how it wraps long merchant names, and whether it splits withdrawals and deposits across two columns. When your bank has its own page under /convert/[bank]-to-csv, we've already tuned for those quirks.

The generic parser is the first stop for unsupported or newly redesigned statements. It looks at the first page, infers the column positions, then applies that template across the rest of the file. If it fails, you get a "we couldn't read this" message and the free-tier credit isn't used.

We don't gate the preview. You see what the CSV will look like before you pay anything. If the extraction is wrong, don't buy.

The paid options:

• Pay-per-document — starting from $2.99. One statement, unlocked immediately, no recurring charge.
• Starter — $29/month, 500 pages. Rolls over once.
• Professional — $49/month, 1,000 pages. Batch upload included.
• Business — $79/month, 5,000 pages. Batch upload + API access

Most users stay on the free tier or buy one document at a time. Monthly plans make sense for bookkeepers handling multiple clients or anyone processing statements regularly. Start with pay-per-doc and upgrade when you hit a second or third purchase in the same month.

Faded scans are fine as long as the OCR can read the amount column. If the ink is genuinely unreadable, we tell you which pages failed so you know to rescan rather than returning a half-broken CSV.

Password-protected files: paste the password during upload. We use it once to decrypt, extract, then discard. The password is never stored.

Merged-cell statements from Barclays, HSBC UK, and HDFC are where we've spent the most engineering time. A single transaction on those banks can wrap across two or three visual rows. We stitch them back into one CSV row instead of treating each line as its own transaction.

What we flag for review instead of silently fixing: transactions with currency symbols buried in the description, and rows where the amount column is empty on the PDF. Those need a human eye.

One thing worth knowing: if you close the tab before downloading, the CSV is still held for 24 hours. Reopen the URL you got and it's there. After 24 hours it's gone and not recoverable on our side.

If you're a bookkeeper or accountant processing client statements, the security and compliance page is the one your compliance reviewer will want. It carries the full policy language — retention, access controls, sub-processors, and region.