What the IIF inspector checks
The parser reads the file as tab-separated text, retains exact physical line numbers, and connects each data row to the most recent matching header. It reports missing headers, duplicate header columns, non-empty extra columns, changing header layouts, unknown row types, mixed line endings, and character-decoding replacement marks. Transaction rows are then grouped from TRNS through zero or more SPL rows to ENDTRNS.
Transaction balance and consistency
For each block, the worksheet parses plain decimal AMOUNT values and checks whether the TRNS amount plus every SPL amount totals zero within half a cent. It also compares non-empty split dates and transaction types with the main row, requires a main account and a distribution account or item, exposes incomplete blocks, and identifies exact repeated transaction signatures. Positive and negative file totals are descriptive; they do not decide debit or credit meaning for every transaction type.
References are an inventory, not a company-file lookup
The account, name, class, and item lists help spot spelling and capitalization differences within the source file. The browser has no access to the destination QuickBooks company, so it cannot know whether a referenced account, customer, vendor, class, sales-tax item, or inventory item exists or is the correct type. List rows bundled into the IIF are counted, but a name appearing there is not treated as approval.
Import and accounting boundary
A clean audit does not guarantee that QuickBooks Desktop will accept the file or post it as intended. IIF behavior varies by QuickBooks Desktop edition, country version, transaction type, preferences, existing lists, tax setup, and import method. This page does not reproduce Intuit's complete proprietary validation, verify accounting treatment, detect an earlier import in a company file, rewrite the source, or support QuickBooks Online. Back up the company file, use Intuit's current import guidance and sample files, test a small batch, and reconcile the result in QuickBooks.
Frequently asked questions
Why must the columns be separated by tabs?
IIF is a tab-separated text format. A comma-separated export with an .iif extension is still not IIF. The inspector shows missing headers or malformed rows rather than guessing a different delimiter.
Does zero net mean the transaction is correct?
No. It only shows that the numeric TRNS and SPL amounts offset. Account types, signs, names, items, tax fields, dates, and business meaning still need review.
Can this find duplicate imports already in QuickBooks?
No. It can flag exact duplicates inside the inspected file, but it cannot read the destination company file or its import history.
Will the tool repair my IIF?
No. Accounting data is too contextual for silent repair. The audit CSV preserves source lines and findings so corrections can be made deliberately in the originating system or a controlled copy.
Authoritative IIF references
Intuit describes IIF as ASCII tab-separated text and documents common list and transaction headers in its IIF overview, import kit, and sample-file guide. Intuit also warns that importing IIF provides limited error checking and recommends reviewing data after import. Follow its current QuickBooks Desktop IIF import and backup instructions.
Inspect a COBOL copybook · Parse a fixed-width file · Browse legacy-data tools