Failed-import file explainer
How to Read a QuickBooks IIF Error Line
QuickBooks can place an [ERROR] comment immediately before a rejected IIF record. The message is useful, but opening a large tab-separated file in a text editor makes it difficult to connect errors to the correct transaction.
Check your IIF fileFind the [ERROR] comment and next record
The comment line begins with a semicolon, so it is not itself transaction data. The affected TRNS, SPL, list, or other record normally follows it. The checker reports both line numbers so you can repair the correct row.
Treat numeric codes as context, not a complete diagnosis
A code such as 11288 can accompany an account-name problem, but the message and target company data still matter. Do not replace names based only on a code found on another website. Compare the rejected value with the receiving QuickBooks file.
Re-check before re-importing
After correcting the failed record, run the full file through the structural checker. Back up the company file, import through the reviewed workflow, and verify the resulting accounts and transaction totals.
Frequently asked questions
Should I delete the [ERROR] comment?
The comment explains the failure. Correct the related record first. A normalized copy may remove mechanical formatting issues, but it does not claim to resolve the QuickBooks error.
Why does an account error need the company file?
IIF contains the account name, but only the target company file knows whether that name exists, what type it has, and whether another list entry conflicts with it.
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.