QuickBooks Desktop troubleshooting
Fix a QuickBooks IIF Import Error
An IIF import can fail because of the text-file structure or because a record conflicts with data inside the target QuickBooks company file. Start by separating those two categories instead of editing rows blindly.
Check your IIF fileCheck the file structure first
IIF files are tab-separated text files. Transaction imports normally declare !TRNS, !SPL, and !ENDTRNS headers, followed by one TRNS row, one or more SPL rows, and an ENDTRNS row for every transaction. A missing tab or terminator can shift the remaining values into the wrong fields.
- Confirm the file uses tabs, not commas
- Keep header and data columns aligned
- Close every transaction with ENDTRNS
- Use plain numeric amounts without currency symbols
Then read QuickBooks-generated errors
QuickBooks Desktop 2019 and later can create a new failed-record IIF containing comments marked [ERROR]. The comment normally appears immediately before the rejected record. Paste that failed file into the checker to connect the message to a line and extract a numeric error code when one is present.
Company-file errors still need QuickBooks
A browser checker cannot know whether an account, customer, class, item, or tax code exists in your company file. Names must match exactly, and some imports can create unintended records. Back up the company file before every import and review the result afterward.
Frequently asked questions
Does the checker upload my accounting file?
No. The file is read and checked in your browser. Its contents are not sent to PolicyPilot or an AI API.
Can the checker guarantee that QuickBooks will accept the file?
No. It can find structural problems and explain embedded errors, but QuickBooks also validates the file against the target company data and product version.
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.