What is IIF Format?

Intuit introduced the IIF format in the mid-1990s alongside early versions of QuickBooks for Windows. The format was designed to solve a specific problem: how to bulk-import structured accounting data — transactions, journal entries, chart of accounts, customer lists, vendor lists, and inventory items — into QuickBooks without manually entering each record through the user interface.

Unlike QIF, which was built for Quicken's personal finance model (single-entry bookkeeping), IIF was designed around QuickBooks' double-entry accounting system. Every IIF transaction must balance: the sum of the TRNS amount and all SPL amounts must equal zero. This constraint mirrors the fundamental accounting equation and makes IIF suitable for journal entries, invoices, and other professional bookkeeping operations.

IIF remained the primary data interchange format for QuickBooks Desktop through the 2000s and 2010s. Accountants used it extensively for data migration between clients, batch transaction preparation in Excel, and programmatic journal entry generation. Third-party applications exported IIF files to feed data into QuickBooks.

With the rise of QuickBooks Online, Intuit moved away from IIF. QuickBooks Online does not support IIF import at all, preferring CSV uploads and API-based integrations. However, QuickBooks Desktop — still used by millions of businesses — continues to support IIF import through File > Utilities > Import > IIF Files. For Desktop users, IIF remains a powerful tool for bulk data operations.

An IIF file is plain text with tab-delimited columns. It begins with header rows (prefixed with !) that define the column layout for transaction and split lines. Data rows follow, grouped into transaction blocks using three record types: TRNS (main transaction), SPL (split/counterpart), and ENDTRNS (end marker).

Each transaction block must balance — the TRNS amount plus all SPL amounts must sum to zero. In the first example above, the TRNS line debits Business Checking for -1,250.00 and the SPL line credits Rent Expense for +1,250.00. The sum is zero, satisfying double-entry requirements.

The header rows (!TRNS, !SPL, !ENDTRNS) define the column positions for subsequent data rows. QuickBooks reads these headers to understand which column contains the date, account name, amount, and other fields. The order of columns in the header determines the order of values in the data rows.

A single transaction can have multiple SPL lines. This is how IIF handles split transactions — for example, a single check payment that covers multiple expense categories. Each SPL line represents one leg of the split, and all amounts (TRNS plus all SPL lines) must sum to zero.

Batch journal entries. Accountants preparing monthly adjusting entries, year-end accruals, or reclassifications often build IIF files in Excel. This allows them to prepare and review dozens of journal entries offline before importing them into the client's QuickBooks file in a single operation.

Data migration. When moving a client from one QuickBooks company file to another — or from a competing system to QuickBooks Desktop — IIF provides a structured way to transfer the chart of accounts, customer list, vendor list, item list, and historical transactions.

Third-party integrations. Payroll processors, point-of-sale systems, and inventory management applications that predate modern APIs often export IIF files. The accountant downloads the IIF from the third-party system and imports it into QuickBooks Desktop to record payroll journal entries, sales summaries, or inventory adjustments.

List imports. Beyond transactions, IIF supports importing lists: customers (!CUST), vendors (!VEND), items (!INVITEM), and accounts (!ACCNT). This is particularly useful when setting up a new company file with hundreds of customers or inventory items.

IIF files are plain text with tab-delimited columns, so you can open them in any text editor to inspect the raw TRNS/SPL records. You can also open IIF files directly in Excel or Google Sheets — the tab delimiters will automatically separate into columns — though the TRNS/SPL/ENDTRNS structure makes the raw view hard to interpret.

For clean, structured analysis, convert IIF to a proper tabular format. FinanceConvert's IIF to CSV converter parses the TRNS and SPL records and produces clean columns with dates, account names, amounts, and memos. Split entries are aggregated into a single memo field. The IIF to Excel converter does the same with native Excel date and currency formatting.

For importing into QuickBooks Desktop, use File > Utilities > Import > IIF Files. Note that QuickBooks Online does not support IIF — you need to convert to CSV first and use the banking import feature.

Tab corruption. The single most common IIF problem is spaces replacing tabs. IIF requires actual tab characters (\t, ASCII 9) as column delimiters. When users edit IIF files in text editors that convert tabs to spaces, or when email clients strip tabs from attachments, the resulting file is unreadable by QuickBooks. Always verify your editor preserves tabs.

Split balance validation. QuickBooks requires that TRNS + SPL amounts sum to exactly zero for each transaction block. A rounding error of even one cent will cause the import to fail. When building IIF files in Excel, ensure that the SPL amount is calculated as the exact negation of the TRNS amount, not an independent calculation that might introduce floating-point drift.

Date format sensitivity. QuickBooks Desktop expects dates in M/D/YY or M/D/YYYY format (American convention). European date formats (D/M/YYYY) will either fail or — worse — be silently misinterpreted, posting transactions to the wrong dates. There is no header flag to specify the date convention.

Character encoding issues. IIF files are expected to be in Windows-1252 or ASCII encoding. UTF-8 files with a byte order mark (BOM) or characters outside the Windows-1252 range can cause QuickBooks to display garbled text or reject the file. Remove the BOM and convert to ANSI encoding before import.

Account name mismatches. The ACCNT values in an IIF file must exactly match account names in the QuickBooks company file (case-sensitive in some versions). A mismatch means QuickBooks will either create a new unwanted account or reject the transaction. Export your chart of accounts and cross-reference before importing.