QuickBooks Online CSV Import Errors: 8 Common Fixes (2026 Guide)

You export a CSV from your bank, upload it to QuickBooks Online, and get an error. The error messages are rarely specific: "Some info may be missing from your file", "We can't read this file", or simply a silent failure where no transactions appear. This guide walks through the eight reasons QuickBooks rejects a CSV and exactly what to change.

1. The file is larger than 350 KB

Intuit's help article is explicit: the upload limit is 350 KB. Bank exports that cover a full year almost always cross that line.

Fix: export the bank data in smaller date ranges (monthly or quarterly) and upload each batch separately. QuickBooks merges the transactions into the same account as long as you upload them to the same bank.

2. The column layout does not match one of the two accepted formats

QuickBooks Online accepts exactly two layouts. Anything else triggers the "missing info" error.

Fix: delete any extra columns (running balance, reference number, branch, account number, etc.) and reorder the remaining columns to exactly match one of the two layouts. Or run the file through the QuickBooks CSV converter which lets you pick the layout and keeps only the needed columns.

3. Dates are mixed formats or in a region QuickBooks does not expect

Bank CSVs often contain mixed formats in the date column: some rows in 2026-03-15, others in 3/15/2026, and a few in 15-Mar-26. QuickBooks reads the file row by row and fails on the first row it cannot parse.

Fix: normalize every date to a single format, typically MM/DD/YYYY for US QuickBooks organizations. Do not open the CSV in Excel to fix this. Excel reinterprets dates silently based on your system locale and often strips leading zeros.

4. Amounts contain currency symbols, commas, or CR/DR suffixes

QuickBooks parses the amount cell as a number. These common patterns all fail:

• $1,234.56 dollar sign plus thousand separator
• 1234.56 CR credit suffix
• (1234.56) accounting-style negatives in parentheses
•  1234.56 leading or trailing whitespace

Fix: strip every amount cell down to a plain number with an optional minus sign and a period decimal. A converter that understands these patterns normalizes the amounts for you.

5. Description cells are numeric-only

QuickBooks rejects rows where the description is entirely numeric (for example, "449801" with no words). This happens when banks put the transaction ID in the description column.

Fix:if the only meaningful identifier in the row is numeric, combine it with a word prefix ("Ref 449801") or map the bank's payee/merchant column into Description instead.

6. Hidden characters, blank rows, or UTF-16 encoding

Some banks export CSVs with a UTF-16 byte-order mark, trailing blank rows, or invisible control characters. QuickBooks silently fails on these without saying what is wrong.

Fix: open the file in a plain text editor (VS Code, Notepad, TextEdit), save as UTF-8, and delete any empty rows at the bottom. If the file still fails, running it through a converter re-emits a clean UTF-8 CSV and removes blank rows in the process.

7. Header names do not match Date, Description, Amount exactly

Banks use varied header names: "Posted", "Posting Date", "Transaction Date", "Memo", "Details", "Narration". QuickBooks accepts some variations during the upload mapping step but fails on others.

Fix: rename the header row to the exact QuickBooks labels (Date, Description, Amount or Date, Description, Credit, Debit) before uploading.

8. Credit and Debit both have values on the same row

In the 4-column format, each row should have a value in exactly one of Credit or Debit. The other column must be blank. Some exports put zeros in the unused column, which QuickBooks treats as a valid opposing amount and creates double entries or rejections.

Fix: replace zeros with empty cells in whichever column does not apply to that row. Or use the 3-column format instead and convert Debit/Credit to a single signed Amount column.

After the import: speeding up the For Review tab

QuickBooks Online does not accept a category column in the CSV import. Every imported transaction lands in the For Review tab and needs a category assigned before it posts to the books.

If you are categorizing hundreds of transactions by hand, the Bulk Categorizer assigns a category and Schedule C code to each line in minutes, so you can move through the QuickBooks review screen without stopping to think about each row.