Fix QuickBooks Import Errors: 8 QBO, IIF & CSV Problems Solved

Common QuickBooks Import Errors (and Fixes)

Importing transaction files into QuickBooks can fail for a number of reasons. Here are the most common errors and exactly how to fix them.

QBO Import Errors (QuickBooks Online)

"File type not supported"

Cause: You're trying to upload a CSV, Excel, or incorrectly formatted file.

Fix: Make sure your file has the .qbo extension and follows the OFX format. If you only have a CSV, convert it first using a CSV to QBO converter.

"We couldn't read this file"

Cause: The QBO file is malformed — missing required OFX headers or has encoding issues.

Fix:

1. Open the file in a text editor
2. Check that it starts with OFXHEADER:100
3. Ensure there are no extra blank lines before the header
4. Re-save with UTF-8 or ASCII encoding (not UTF-8 with BOM)

"No new transactions were found"

Cause: All transactions in the file have already been imported, or the date range has no new data.

Fix:

• Check the date range in the QBO file (look for <DTSTART> and <DTEND>)
• Make sure you're importing the correct date range
• QuickBooks matches transactions by FITID (unique ID) — duplicate FITIDs are skipped

"Duplicate transactions"

Cause: Overlapping date ranges between imports.

Fix: Always import non-overlapping date ranges. If you accidentally import duplicates, use Banking > For Review to exclude or delete them before accepting.

IIF Import Errors (QuickBooks Desktop)

"There was an error when saving"

Cause: The most common IIF error. Usually caused by account names in the IIF that don't exist in your Chart of Accounts.

Fix:

1. Open the IIF file in a text editor
2. Find the ACCNT fields in TRNS records
3. Make sure those account names exactly match accounts in Lists > Chart of Accounts
4. Account names are case-sensitive in IIF imports

"Unexpected end of file"

Cause: The IIF file is missing the final ENDTRNS marker, or the file got truncated.

Fix: Open in a text editor and check that every TRNS record has a matching ENDTRNS. The file structure should be:

TRNS  [data]
SPL   [data]
ENDTRNS

Transactions import but amounts are wrong

Cause: IIF uses positive numbers for deposits and negative for expenses — some CSV sources have this reversed.

Fix: In your CSV to IIF conversion, check the sign convention. Expenses should be negative, income positive.

CSV Import Errors (QuickBooks Online)

QuickBooks Online can also import CSV directly (Banking > Upload transactions). Common issues:

"We couldn't match your columns"

Cause: QuickBooks couldn't auto-detect Date, Description, or Amount columns.

Fix:

• Use clear column headers: "Date", "Description", "Amount"
• Or manually map columns in the import wizard
• Make sure your date column uses MM/DD/YYYY format

Dates not recognized

Cause: European date format (DD/MM/YYYY) or inconsistent formatting.

Fix: Standardize all dates to MM/DD/YYYY before importing. Excel's TEXT formula helps: =TEXT(A1,"MM/DD/YYYY")

Amount column ignored / all zeros

Cause: Amount column has currency symbols ($) or commas (1,000.00) that QuickBooks can't parse.

Fix: Strip currency symbols and commas from the amount column. In Excel: Find & Replace $ with nothing, and $ with nothing.

General Tips

1. Always use a fresh date range — overlapping imports cause duplicate headaches
2. Back up before importing — especially for IIF imports into QuickBooks Desktop
3. Test with a small file first — import 5–10 transactions before the full statement
4. Check file encoding — save as UTF-8 without BOM, or plain ASCII

Need to Convert First?

If you're getting import errors because your bank only gives you CSV, use our converters:

• [CSV to QBO](/) — for QuickBooks Online
• [CSV to IIF](/csv-to-iif) — for QuickBooks Desktop
• [CSV to QIF](/csv-to-qif) — for Quicken