Headers and tabs
Missing !TRNS, !SPL, !ENDTRNS, undeclared record types, duplicate fields, and extra columns.
Browser-local QuickBooks Desktop preflight
Upload or paste an IIF file. Find malformed headers, broken transaction blocks, invalid values, unbalanced journals, and QuickBooks-generated error lines before importing again.
QuickBooks Desktop · Tab-separated · Maximum 5 MB
What it checks
The checker handles deterministic problems visible in the text file and clearly labels everything that still requires QuickBooks Desktop.
Missing !TRNS, !SPL, !ENDTRNS, undeclared record types, duplicate fields, and extra columns.
Orphan splits, nested transactions, missing ENDTRNS rows, empty distributions, and unbalanced journals.
Missing accounts or amounts, non-numeric values, and dates that need locale-specific review.
QuickBooks [ERROR] comments, numeric codes, affected record lines, and actionable next steps.
Important boundary
QuickBooks validates imports against the receiving company file. A local checker cannot know whether account, customer, vendor, class, item, or tax-code names exist or have compatible types.
Always back up the company file before importing and inspect the imported records afterward. PolicyPilot is not affiliated with or endorsed by Intuit.
No. IIF is a QuickBooks Desktop import/export format. QuickBooks Online CSV and app-integration workflows use different formats and validation rules.
Not without access to the target QuickBooks company file. The checker can confirm that ACCNT is present and structurally aligned, but only QuickBooks can validate the exact account, customer, vendor, item, tax code, or class.
Only a UTF-8 byte-order mark and internal blank lines. It does not rewrite names, dates, accounts, transaction types, or amounts.
QuickBooks and Intuit are trademarks of Intuit Inc. This independent tool is not affiliated with, sponsored by, or endorsed by Intuit.