Fix QuickBooks CSV and QBO Import Errors (Every Common Cause)

Almost every QuickBooks import failure produces one of three messages, and none of them names the actual problem. Work down this list in order; the causes are roughly in frequency order.

"The file you selected is not supported"

Wrong extension, or a renamed file

QuickBooks Online accepts .csv, .qbo, .qfx and .ofx. Renaming a .txt to .csv is fine; renaming an .xlsx to .csv is not — it is still a zip archive inside, and the import reads the bytes, not the name. Re-save from your spreadsheet with Save as CSV.

An Excel file with one sheet too many

Exporting a workbook to CSV saves only the active sheet. If the transactions are on sheet two, you have exported a page of headings. Check that the file you are uploading actually contains rows.

Too many columns

A CSV import has to be three columns (date, description, amount) or four (date, description, credit, debit). A bank export with a balance, a category and a status has to be cut down first. The CSV column rules cover the layout in detail.

The file is too large

QuickBooks Online documents a 350 KB limit for CSV uploads and a 1,000-transaction cap for a Web Connect upload. Split the file by month and import the parts.

OL-221 and OL-222

These are parsing errors: QuickBooks opened the file and could not make sense of it.

An unrecognised date format

Mixed formats in one column, or a format QuickBooks does not expect, stops the parse. Normalise the column to a single format before converting. European day-first dates are a frequent offender in files that have been through a spreadsheet with non-US locale settings.

A stray character in an amount

Currency symbols, thousands separators and parenthesised negatives such as (45.00) all have to become plain signed numbers. Non-breaking spaces pasted in from a web page are invisible and just as fatal.

An edited .qbo file

Opening a Web Connect file in a spreadsheet and saving it breaks the structure — line endings, the header block, sometimes the encoding. Always re-convert from the original CSV rather than editing the .qbo.

A missing description

Every transaction needs a name. Rows where the description is blank — common in summary or adjustment lines — will fail the file. Delete those rows or give them a label.

"You've already imported this file" or nothing appears

The file really was imported

Check the For review tab and the account you chose, not the one you meant. Nothing is posted until you accept, so imported-but-invisible usually means "in a different account".

The FITIDs matched an earlier import

Web Connect files carry a unique id per transaction, and QuickBooks skips ids it has seen. That is the anti-duplicate mechanism working — see what is inside a .qbo file.

Dates outside the range QuickBooks will accept

Transactions dated in the future, or before your company's start date, can be silently dropped. Check the first and last dates in the preview before converting.

Everything imported, but backwards

The account type is wrong

A credit card statement imported into a bank account inverts your mental model of every line. Bank accounts and card accounts are different structures inside a .qbo file: pick the right one before downloading, not after.

The bank exports charges as positive

American Express is the classic case — a charge is a positive number. The Amex guide covers the flip. Citi and Capital One instead split charges and payments into two columns, which the Citi guide explains.

Processor fees were never separated

PayPal, Stripe and Square report gross and fee on one line and pay you the net. If your deposits never match, that is usually why — see the PayPal guide.

When the file is fine and QuickBooks still refuses

A Web Connect file identifies its institution with an Intuit bank id. If a converted file is rejected outright while a bank's own download works, that id is the first thing to change: the converter on this site exposes it in the account settings, and trying another is a ten-second experiment. Beyond that, importing a shorter date range is the quickest way to find out whether the problem is the file or a single bad row inside it.