How to import a bank CSV into QuickBooks Online

Covers the 3 column and 4 column CSV layouts, OFX, and the errors that stop an import · Updated August 2026

QuickBooks Online will import a bank statement as CSV, but it is fussy about the shape of the file, and almost no bank exports it in that shape. This guide covers the two layouts QuickBooks accepts, which one to choose, and the handful of problems that cause most failed imports.

The two CSV layouts QuickBooks accepts

QuickBooks takes either a three column or a four column file. Both need a header row.

LayoutColumnsUse it when
3 columnDate, Description, AmountYour bank gives one signed amount column. Money out must be negative.
4 columnDate, Description, Credit, DebitYour bank splits money in and money out. Each row fills one column and leaves the other blank.

Either works. The four column layout is worth choosing when you want to eyeball the file in a spreadsheet before importing, since money in and money out being visually separate makes a mis-signed row obvious. If in doubt, three column is simpler.

Consider OFX instead

If your bank offers an OFX download, or you can convert to OFX, it is usually the smoother path. OFX carries the date, amount, payee and memo in a structured form, so QuickBooks does not have to ask you to assign columns and there is no ambiguity about date order. The converter outputs OFX alongside both CSV layouts, so you can try OFX first and fall back to CSV.

Importing the file

  1. In QuickBooks Online, go to Transactions, then Bank transactions.
  2. Choose to upload a file, and select your converted CSV or OFX.
  3. Pick the account the transactions belong to.
  4. For CSV, map the columns when prompted, and tell QuickBooks whether the first row is a header.
  5. Review, then import and categorise as usual.

Import a short date range first and check five transactions against your statement before doing a full year. Backing out a bad import of several thousand rows is considerably more work than checking five.

The errors that stop most imports

Dates land in the wrong month

A date like 03/04/2026 is 3 April in the UK, Australia and New Zealand, and 4 March in the US. If your imported transactions cluster oddly, this is why. Read the file as DD/MM and write it in whichever order your QuickBooks region expects.

Everything imports as money in

This happens when a debit and credit file was flattened into one column without applying signs. In the three column layout, money out must be negative. Mapping the two columns as Debit and Credit in the converter produces the correct signs automatically.

The file has more columns than QuickBooks wants

Running balances, account numbers, transaction IDs and bank categories all need to come out. Convert to a clean three or four column file rather than deleting columns by hand in a spreadsheet, which is where accidental row shifts creep in.

Amounts with currency symbols or thousands separators

£1,234.56 inside an unquoted CSV field splits across two columns and shears the row sideways. A proper conversion strips the symbol and separator and quotes any field that needs it.

Duplicates after a bank feed catches up

If your bank feed later re-delivers days you imported manually, exclude the duplicated rows in QuickBooks rather than re-importing the file.

Convert your bank CSV for QuickBooks

Free for single files, runs entirely in your browser, and your statement is never uploaded to a server. There are per-bank guides for NZ, Australian and UK banks, and a separate Xero import guide.

© 2026 StatementShift · Converter · Bank guides