Common QuickBooks Online Import Errors and How to Fix Them

QuickBooks Online's CSV import is forgiving compared to its desktop predecessor, but it's not infinitely flexible. When imports fail, the error messages tend to be cryptic. Here's a reference guide to the most common errors and what they actually mean.

"The file doesn't match the format we accept"

QBO is rejecting the file outright. Causes:

• Wrong file extension. QBO accepts .csv, .qbo, or .qfx files. .xlsx works for some account types but not others. If you saved your Excel file as .xlsx, try Save As CSV first.
• Encoding issues. If the CSV was generated by a tool that uses UTF-16 or Windows encoding, QBO may not parse it. Re-save as UTF-8 CSV.
• Special characters in the file. Some banks include characters like € or fancy quotes in transaction descriptions. These can break the parser. Find/replace them out before importing.

"We can't find this transaction's date"

QBO is rejecting the date column. The date format must be MM/DD/YYYY. Anything else fails:

• "3/14/2026" usually works (single-digit months/days OK)
• "03/14/2026" works
• "14/03/2026" fails (DD/MM/YYYY)
• "March 14, 2026" fails
• "2026-03-14" fails
• "14-Mar-26" fails

Fix: In Excel, select the date column, Format Cells → Custom → type mm/dd/yyyy → OK. Save as CSV.

"This transaction has no amount"

The amount column is empty or contains non-numeric data:

• Currency symbols ($, €) in the amount field. Strip them.
• Thousands separators (commas) for European-format numbers (1.234,56 instead of 1,234.56). Reformat.
• Empty cells from a continuation row that didn't get merged properly.

Fix: In Excel, find/replace "$" with nothing in the amount column. Then verify no cells are blank.

"My deposits and withdrawals are reversed"

The sign convention is backwards. QBO's 3-column format expects debits (money out) as negative and credits (money in) as positive. If your output shows withdrawals as positive numbers, QBO will treat them as deposits and inflate your balance.

Fix: Either re-run the conversion with proper sign handling, or in Excel use =-A1 to flip the column. Better long-term: use the 4-column format (Date, Description, Credit, Debit) where the sign convention is explicit.

"Some transactions were skipped as duplicates"

QBO's duplicate detection caught items that already exist in the account — usually because:

• You're re-importing a statement you've imported before
• The bank feed already pulled some of these transactions before you uploaded the CSV
• Multiple QBO accounts are pulling from the same bank account (rare, but happens)

This is usually correct behavior — QBO is protecting you from double-counting. Review the "skipped" list to confirm they're true duplicates.

"The file uploaded but no transactions appeared"

The file uploaded but the import didn't process. Causes:

• You clicked away from the import screen before confirming the column mapping.
• The CSV had a header row but no data rows.
• All transactions were silently skipped as duplicates.

Fix: Re-upload the file and walk all the way through the import workflow to the confirmation screen.

"Bank balance doesn't match book balance after import"

The import succeeded but your QBO bank balance doesn't tie to the statement balance. Causes:

• Some transactions were skipped (check the import log).
• Sign convention was wrong on some transactions.
• A duplicate import caused some transactions to count twice (rare but possible if you imported a partial CSV then a full one).

Fix: Reconcile against the statement. See our QBO reconciliation guide for the process.

"Description text is getting truncated"

QBO truncates transaction descriptions at 4,000 characters. Some banks (Citi, particularly) include massive ACH descriptors that push past this. The description gets cut off mid-text.

Usually not a real problem (the truncated text is rarely needed), but if you're tracking specific descriptor codes, trim the descriptions to relevant content before import.

"Categories aren't being assigned"

QBO doesn't auto-categorize on CSV import — only on bank feed pulls. After import, you'll need to either:

• Categorize manually transaction by transaction
• Apply bank rules (set up via Bookkeeping → Rules) and run them across the imported batch

If you have 100+ recurring transactions per import, bank rules are essential. Spending 30 minutes upfront to build rules saves hours of categorization later.

The general approach to import errors

When an import fails, work through this checklist:

1. Open the CSV in Excel and verify it has exactly the columns QBO expects (Date, Description, Amount or Date, Description, Credit, Debit)
2. Confirm date format is MM/DD/YYYY
3. Confirm amounts have no currency symbols or thousand-separators
4. Confirm sign convention (debits negative for 3-column)
5. Confirm no blank rows in the data
6. Save as CSV (not .xlsx) in UTF-8 encoding
7. Re-attempt import

For details on the import workflow itself, see our PDF-to-QBO walkthrough.