QuickBooks Online CSV import errors: what each one means and how to fix it

QuickBooks Online's Upload from file is strict about CSVs. A file that opens perfectly well in Excel can still be rejected, or import with dates and amounts in the wrong places. Almost every failure comes down to one of the problems below, and each one has a fix you can make in a few minutes.

If you're setting up an import for the first time, start with how to import a bank CSV into QuickBooks Online. This post is for when it has already gone wrong.

QuickBooks can't read the columns

QuickBooks Online wants either three columns (Date, Description and Amount) or four (Date, Description, Credit and Debit). Intuit's troubleshooting help says that if the columns aren't mapped properly, QuickBooks won't be able to read the data.

The fix is to make the file match exactly:

• Delete every other column: running balance, transaction type, check number, category, anything else your bank adds.
• Delete any rows above the headings, such as account details or a title.
• Rename the headings to Date, Description and Amount (or Credit and Debit). Intuit also asks that the Credit and Debit headings don't include the word "amount".

Amounts are formatted as currency

If the amount cells are formatted as Currency in Excel, the saved CSV can carry currency symbols and thousands separators that QuickBooks doesn't expect. Intuit's fix: select the amount column, right-click, choose Format Cells, and change Currency to General. Then save as CSV again.

While you're there, check for zeros. QuickBooks asks for any cell containing only 0 to be left blank. In Excel, use Find and Replace: find 0, replace with nothing, and tick Match entire cell contents so 10 and 100 are left alone.

The dates don't match the format you chose

During the upload, QuickBooks asks which date format the file uses. If the file's dates don't match that choice, the import fails or the dates come in wrong. Intuit recommends using one format throughout, and dd/mm/yyyy in particular.

In Excel, select the date column and choose Short Date from the Number format menu so every date is written the same way. Some banks add the day of the week, as in "20/11/2025 TUE". Split that into its own column or remove it, because QuickBooks can't read it as a date.

Special characters in descriptions

According to Intuit, special characters in a description can stop the whole file from importing. Use Find and Replace (Ctrl+H) to swap them for plain text. Line breaks inside a description, where a bank's memo wraps onto a second line, are worth fixing the same way.

Your file only has money going out

This one is easy to miss. With a four-column file (separate Credit and Debit), a file containing only money-out transactions can fail to import. Intuit's workaround is to add one dummy money-in line, then untick it on the review screen before you finish, so it never reaches your books.

You're importing into a subaccount

Intuit lists importing into a subaccount as a current limitation of Upload from file. Their suggestions are to connect the subaccount to its own bank feed, or to enter those transactions by hand.

The file is too big, or not in English

Upload from file takes up to 1,000 lines and 350 KB per file, and the file has to be in English. For a long history, split the file into a few smaller ones and upload them one after another.

Saved on a Mac

Intuit asks Mac users to save the file as a Windows CSV. In Excel for Mac that's the "Windows Comma Separated (.csv)" option in Save As.

Skip the cleanup

Every fix above is something the free bank CSV to QuickBooks converter does for you. It keeps only the columns QuickBooks wants, writes every date in one format, removes zeros, uses Windows line endings, and splits files over 1,000 lines or 350 KB into parts. It runs in your browser, so the file isn't uploaded anywhere.

If your bank gave you an OFX, QFX or QBO file instead, the OFX and QFX viewer shows what's wrong with it and can export the same QuickBooks CSV. And if you only have PDF statements, the statement converter turns them into a CSV that has been checked against the statement's closing balance.