Short version: An IIF file (Intuit Interchange Format) is QuickBooks Desktop's old tab-delimited text format for importing and exporting lists and some transactions in bulk. It's clunky, has almost no safety net, and only works with Desktop, not QuickBooks Online. It's also still the fastest way to push a large batch of data into a Desktop file, which is exactly why it hasn't died. Use it for bulk work, back up first, and validate before you import.
IIF is one of those tools that's been declared dead more than once and keeps showing up anyway. If you run QuickBooks Desktop and you've ever needed to load a few hundred journal entries or stand up a new file's chart of accounts without typing it all, IIF is probably the answer, with some sharp edges you need to respect.
Strip away the mystique and an IIF file is a plain text file with tab-separated columns. Header rows start with an exclamation point and name the fields; the data rows underneath fill them in. Open one in a text editor and it's just rows and tabs. That simplicity is the whole point: it's a format QuickBooks Desktop can read and write directly, with no API and no add-on.
Two things to fix in your head up front. First, IIF is Desktop only. QuickBooks Online does not import IIF, full stop; it uses CSV and Excel templates. Second, IIF has very little validation. It mostly trusts what you hand it, which is powerful and dangerous in equal measure.
| Good for | Not for |
|---|---|
| Lists: chart of accounts, customers, vendors, items, employees | QuickBooks Online (unsupported) |
| Bulk journal entries and recurring allocations | Transactions with links, like invoices tied to payments |
| Standing up a new Desktop file quickly | One-off entries you could just key in |
| Copying lists between Desktop files | Anything you can't back up and reverse first |
Intuit has had an on-and-off relationship with IIF. List import always worked. Transaction import through IIF was discouraged for a stretch, then Intuit reintroduced an improved, validated IIF import in newer Desktop versions. Through all of it, nothing replaced IIF for one specific job: getting a large batch of data into a Desktop file fast, without buying a third-party tool. That's why it persists. It's not elegant; it's available and it works.
IIF import has no meaningful undo and limited checking. The failure modes are predictable: a typo in an account name creates a brand-new account instead of matching the one you meant; amounts that don't balance post a lopsided entry; opening the file in Excel quietly reformats your dates and strips leading zeros. None of these throw a helpful error. They just land in your file.
Non-negotiable: back up the company file before every IIF import, and spot-check the results against your source after. IIF rewards preparation and punishes the casual click.
And when not to: for QuickBooks Online (use its own tools), for a single entry (just key it), or for linked transactions where IIF's flat structure fights the relationships QuickBooks wants to maintain.
The danger in IIF isn't the format; it's hand-building the file and hoping. The controller's version is a template that enforces the rules before you ever import: columns in the right order, amounts that must balance, account names validated against your chart, dates in the format QuickBooks expects. Build it right once and the import is boring, which is exactly what you want from an import. If you're building journal entries this way, see how to create an IIF file for journal entries for the exact structure.
The IIF Import Field Guide & Checker documents every field and validates your file before you load it. The IIF Toolkit pairs it with the Journal Entry Generator so your bulk entries balance and import clean the first time.
IIF stands for Intuit Interchange Format. It's a tab-delimited text file QuickBooks Desktop uses to import and export lists and some transactions in bulk. Header rows beginning with an exclamation point define the fields, and data rows follow. It works with Desktop only, not QuickBooks Online.
No. IIF is a Desktop format. QuickBooks Online uses CSV and Excel templates and third-party tools instead. An IIF file handed to a QBO company won't load.
With care. IIF has limited validation and no undo, so a bad file can create duplicate accounts or mispost amounts. Back up the company file first, validate the IIF before importing, and spot-check the results. Newer Desktop versions added a pre-import check, but it doesn't replace reviewing your own file.
When you need to move a lot of data into a Desktop file fast: bulk journal entries and recurring allocations, setting up a new file's lists, or copying lists between Desktop files. For one-off entries, key them in. For QuickBooks Online, use its own import tools.
General guidance on working with QuickBooks Desktop, not accounting, tax, or legal advice. Back up your company file before any import. Not affiliated with or endorsed by Intuit Inc. QuickBooks® is a registered trademark of Intuit Inc., used here descriptively only.
Practitioner guides on QuickBooks Desktop, IIF imports, and controller-grade books. One email per guide. Unsubscribe in a click.