Import failure checklist

QuickBooks IIF File Not Importing: What to Check

When an IIF file will not import, the fastest path is to check deterministic text-format problems before investigating accounts and names stored inside QuickBooks Desktop.

Check your IIF file

Confirm that it is really an IIF file

Renaming a CSV file to .iif does not convert it. An IIF uses tabs between fields and header rows beginning with an exclamation point. Open the file as plain text: a transaction file should visibly contain !TRNS, !SPL, and !ENDTRNS.

Inspect the transaction blocks

Each TRNS begins a transaction. SPL rows distribute the amount, and ENDTRNS closes the block. Orphan SPL rows, nested TRNS rows, missing terminators, and unbalanced general journals are common reasons to stop before importing.

  • One open TRNS block at a time
  • At least one SPL before ENDTRNS
  • General journal amounts total 0.00
  • ACCNT and AMOUNT values are present

Compare names with the company file

If the structure is valid but the import still fails, compare account, customer, vendor, item, and class names with an export from the target company. Differences in punctuation, hierarchy, account type, or country version can matter.

Frequently asked questions

Should I use “Import it for me. I’ll fix it later”?

Intuit does not recommend bypassing data review because information may be incomplete or incorrect. Fix the reported problems and use the reviewed import path.

Is IIF the same as QuickBooks Online CSV import?

No. IIF is a QuickBooks Desktop format. QuickBooks Online import flows and supported fields are different.

Related IIF guides

QuickBooks and Intuit are trademarks of Intuit Inc. PolicyPilot is an independent tool and is not affiliated with or endorsed by Intuit.