How to import bank statements into QuickBooks (CSV, PDF workarounds and fixes)

QuickBooks is happiest when its bank feed does the work — and useless at exactly the moments you need history most: closed accounts, transactions older than the feed window, unsupported banks, and the client who hands you a year of PDFs. Here's how to get statements in anyway, cleanly.

What QuickBooks actually accepts

• QuickBooks Online — imports CSV (via Banking → Upload transactions) and OFX-family "Web Connect" files (.qbo/.ofx). The feed covers roughly the last 90 days for most banks; anything older arrives by file.
• QuickBooks Desktop — prefers .qbo Web Connect; CSV needs conversion or a third-party importer depending on version.
• Never PDFs. A PDF statement must be converted to CSV or OFX first — that's the step this guide (and our PDF→CSV converter) handles.

The CSV shape QuickBooks wants

QuickBooks Online accepts two CSV layouts, and half of all import errors are layout confusion:

• 3-column: Date, Description, Amount — one signed amount column where negative = money out.
• 4-column: Date, Description, Credit, Debit — two positive columns.

Pick whichever matches your file and tell the import wizard which you're using. Two more rules: dates in one consistent format (QuickBooks asks you to confirm DD/MM vs MM/DD — answer honestly or every date shifts), and no thousands separators or currency symbols inside the amount cells.

PDF statements: the conversion step

Convert each PDF with a converter that re-validates dates and amounts rather than raw OCR — here's why that matters — then reconcile the converted totals against the statement's own opening/closing balances before importing. Our converter outputs a QuickBooks-friendly CSV with the identified merchant in the description, which pays off at the categorisation step below. There are also per-bank converter pages for 5,000+ institutions.

Step-by-step import (QuickBooks Online)

1. Banking (Transactions) → the account tile → Upload transactions.
2. Choose the CSV/OFX file → pick the QuickBooks account it belongs to (create the account first if it's new).
3. Map the columns (3- vs 4-column, date format) → preview.
4. Fix anything red in the preview before importing — it's far cheaper than undoing.
5. Import, then categorise from the For Review tab as usual.

The errors everyone hits (and the fixes)

• Every date is wrong by months — DD/MM vs MM/DD mismatch. Re-import with the correct choice; don't hand-fix hundreds of rows.
• All amounts show as income (or all as expenses) — sign convention flipped. In a 3-column file, money out must be negative; some bank exports use the opposite convention, so negate the column and re-import.
• Duplicates after import — overlap between the file and the live feed window, or between consecutive monthly statements. QuickBooks catches exact matches but misses near-misses. Dedupe before import — overlapping statements are collapsed automatically when you run files through the analyzer first.
• "We can't read your file" — usually encoding or stray header/footer rows. Export a fresh CSV; delete any summary rows above the header.

Doing this at scale

Onboarding a client means many accounts × many months. The workflow that keeps it sane: batch-convert everything first (a zip of statements in one pass), let merchant identification pre-clean the descriptions so For-Review categorisation is fast, then import account by account, oldest first — the whole discipline is laid out in the bookkeeping workflow guide. If a client's books need a specific export shape, the AI transform reshapes columns and date formats with a verifier proving amounts and dates survived intact.