An IIF import error in QuickBooks Desktop is reported in a results window that counts what imported and what failed, plus a new IIF file holding only the failed lines with an ERROR note on each. Open that file, fix the header rows, account names or amounts it flags, save it as tab-delimited text and import just that file.
Reading the IIF import error report in QuickBooks Desktop
In QuickBooks Desktop 2019 and later, the error report does more than say "failed". Intuit's article on the improved IIF import in QuickBooks Desktop 2019 and later says the tool scans the file for errors, shows how many records imported or failed, and creates a new IIF file of the failed records with the errors described.
That second file is the useful part. It is not a log you read and throw away. It is a ready-made copy of every line that did not make it in, so you can correct those lines and import them without touching the ones that already landed.
Where to find it
The import runs from File > Utilities > Import > IIF Files. When the scan finds problems, the results window offers a Review now option, which opens the failed-records file. Intuit's article says to search that file for the word ERROR to find each problem.
What the counts tell you
Read the two numbers before opening anything:
- Everything failed. A whole-file failure usually means the header rows are wrong, or the file is not tab-delimited at all. Start with the next section.
- Most lines imported, a few failed. The structure is fine. The failures are row problems, most often an account name or a list name that does not exist.
- Everything imported. That is not proof the data is right. The section on clean imports with wrong data explains why.
An example of a failed-records file
The file below is an example. The account names and amounts are made up, and the exact wording QuickBooks writes next to a failed line varies, so search for ERROR rather than for a fixed phrase.
!TRNS TRNSTYPE DATE ACCNT NAME AMOUNT MEMO
!SPL TRNSTYPE DATE ACCNT NAME AMOUNT MEMO
!ENDTRNS
TRNS DEPOSIT 03/18/2026 Operating Checking Example Catering Co 1250.00 March event
SPL DEPOSIT 03/18/2026 Catering Sales Example Catering Co -1250.00 March event
ENDTRNS
Here the error note points at "Operating Checking", an account name that does not match the chart of accounts, which is spelled "Checking - Operating" in this example company. The fix is one cell.
Which IIF header rows cause an import error?
Header rows cause the failures that stop a whole file. Intuit's IIF overview and Import Kit page says a transaction file usually has three header lines in the first three rows, starting with !TRNS, !SPL and !ENDTRNS, and that their spelling and placement must be correct to avoid errors.
The header rows are not decoration. They tell QuickBooks which column holds which field for every line below them. A TRNS line is read against the !TRNS header, and an SPL line against the !SPL header. If a header names AMOUNT in the sixth column and the data puts the amount in the seventh, QuickBooks reads the memo as a number and fails.
Check these points with the file open in a text editor:
- The first three rows start with
!TRNS,!SPLand!ENDTRNS, in that order, with nothing above them. - The exclamation marks are there. A spreadsheet can strip or quote them.
- The column names after each header are spelled the way Intuit's sample files spell them.
- Each data row has the same number of columns as its header.
- The separators are tabs. Intuit's overview describes IIF files as tab-separated text, so a file saved as comma-separated will fail even if it looks right in Excel.
The fifth point catches people who build the file in a spreadsheet. Excel shows a CSV and a tab-delimited file the same way on screen. Only the save format decides which one you get.
IIF account names that miss the chart of accounts
Account names are the most common reason single lines fail, and they can also do quiet damage. Intuit's IIF overview says every account in the file should exist in QuickBooks before import, and warns that a missing account will be created as a new bank account. A typo can add an account you never wanted.
So an account-name mismatch has two possible results. With the 2019 and later tool, the line may come back in the failed-records file. In other cases, QuickBooks may create the account and post to it, so the import looks successful while the money sits in a stray bank account.
A table of causes and fixes
The table below lists the account and list problems worth checking. The examples are illustrative.
| Problem in the file | Example | Fix |
|---|---|---|
| Account spelled differently | Office Supply vs Office Supplies |
Copy the exact name from the chart of accounts |
| Subaccount without its parent | Utilities vs Overhead:Utilities |
Use the full parent:child path |
| Name that does not exist as a customer or vendor | Example Paper Co not in the vendor list |
Add the name first, or correct the spelling |
| Account type that does not fit the transaction | A card charge posted against a checking account | Point the line at the right account |
The last row has a cousin in bank files. When a QBO file meant for a credit card is imported into a bank account, QuickBooks complains about the type rather than the name. The post on a QBO file account type mismatch covers that version.
After the import, open the chart of accounts and sort by type. Any bank account you do not recognise, with a name close to a real expense or income account, is a typo the import turned into a new account.
Why does an IIF file import with no error yet post wrong data?
An IIF file can import cleanly and still be wrong, because the format checks very little. Intuit's IIF overview says IIF imports have only limited error checking, and that an incorrect format may cause an error or may import incorrectly with no error. Intuit also says to check the data carefully after every import.
Clean-but-wrong imports usually come from one of these:
- Signs reversed. In an IIF transaction, the
TRNSandSPLamounts must be equal and opposite. A file that flips both still balances, so it imports, but every deposit becomes a withdrawal. - Dates read in the wrong order. A day-first date such as 04/03/2026 in a month-first company file lands a month away from where it belongs.
- The right amount on the wrong account. A column shift that still lands a valid account name in the account column can post to the wrong place.
- Duplicates. Importing the same file twice posts its lines twice.
The check that catches all four is a balance comparison. After the import, open the bank register and compare its balance on the last date in the file with the bank statement's balance on that date. The same idea applies in other software, and the post on a Xero statement balance that is wrong after import shows what a mismatch usually means there.
Intuit's overview also notes that it does not offer assisted technical support for creating or importing IIF files. That makes your own after-import check the only safety net.
Correcting the failed-records IIF file for a second import
Fix the failed-records file, not the original. It holds only the lines that did not import, so importing it adds the missing lines without duplicating the ones already posted. Intuit's 2019 and later article describes this flow: review the file, correct the errors, save it and import the corrected file.
Follow these steps:
- From the results window, choose Review now to open the failed-records file.
- Search for ERROR and read the note on each flagged line.
- Fix the cause in the file. Where the cause is a missing account or name, create it in QuickBooks first, then match the spelling exactly.
- Save. If the editor asks whether to keep the tab-delimited format, keep it.
- Close the "File not imported" window in QuickBooks.
- Go to File > Utilities > Import > IIF Files and import the corrected file.
- Check the counts. If anything fails again, repeat with the new failed-records file.
People moving from Desktop to QuickBooks Online meet a similar pattern there, but for journal entries rather than IIF. The guide to a journal entry import error in QuickBooks Online covers the rules that version enforces.
When an IIF import error means restoring the backup
Restoring the backup is the right move when the import posted lines that are wrong, not just missing. Intuit's guide to importing and exporting data in QuickBooks Desktop says you cannot undo an import and advises a backup before any import, so the backup is the only clean undo.
Restore instead of fixing forward when:
- The balance check fails and you cannot see why.
- A typo created stray bank accounts with transactions in them.
- The file imported twice.
- Signs or dates are wrong across many lines.
Deleting hundreds of posted lines by hand is slower than a restore and easier to get wrong. The one cost of a restore is any work entered after the backup, so tell anyone else using the file before you do it.
If the IIF file was built from a bank statement, the bank side is often easier to bring in as a Web Connect file. SimpleBankConvert is being built to turn a PDF bank statement into a QBO file, and its homepage shows what the file will contain. Accounts are not open yet.