Bank Statement PDF to CSV
CSV is the lingua franca of transaction data — Excel, Google Sheets, Xero, Wave and almost every accounting or budgeting tool can import it. Turning a bank statement PDF into clean CSV means more than dumping text into commas: dates, amounts and descriptions each need to land in the right column, signs need to be consistent, and multi-line descriptions can’t shatter the layout. Here’s how a good conversion handles that, and how to keep your import from breaking.
Why CSV instead of Excel or QBO?
CSV is plain text with one row per transaction and columns separated by commas — no app required to read it, and nearly every tool can import it. Excel (.xlsx) is great when you want formatting, formulas and multiple sheets; QBO/OFX is the format QuickBooks and legacy software import directly. CSV is the neutral middle ground: maximally portable, easy to inspect, and the safe choice when you’re not sure what the destination tool accepts.
What makes a CSV ‘clean’ and importable?
A clean CSV from a statement has one transaction per row, with date, description, amount and (where available) balance in stable columns. The two things that quietly break imports are inconsistent amount signs (debits vs credits) and multi-line descriptions that split one transaction across rows. StatementSift keeps each transaction on a single row, preserves the column roles it detected, and runs the balance check so you can spot a row that got merged or split before you import.
- One transaction per row — multi-line descriptions are kept together, not split.
- Consistent amount column so debits and credits import with the right sign.
- Export presets (QuickBooks / Xero / Wave style) match common import templates.
- Balance check flags rows that don’t reconcile, so you fix data before importing.
How to convert and import
Drop the statement PDF into StatementSift, let it detect the columns locally, glance at the balance check for red-flagged rows, then export CSV (or a destination-specific preset). In your spreadsheet or accounting tool, use its CSV import and map the columns if asked — date to date, amount to amount, description to memo. Because the conversion runs in your browser, the statement is never uploaded at any point in this flow.
Frequently asked questions
Will my CSV open correctly in Excel and Google Sheets?
Yes. CSV is a universal text format both open natively. If a long account number or date looks odd, that’s the spreadsheet’s auto-formatting, not the data — set the column type to text or date on import.
Why did my CSV import put everything in one column?
That’s usually a delimiter mismatch (the tool expected semicolons, or a regional setting). Re-import and explicitly choose comma as the separator. StatementSift exports standard comma-separated values.
Can I import the CSV into Xero or Wave?
Yes — both accept CSV imports, and the export presets are shaped to match common templates. For QuickBooks, QBO/OFX usually imports more cleanly; StatementSift exports that too.
Updated · StatementSift team