IIF to Excel Converter

Why convert an IIF file to a spreadsheet?

IIF was designed for one reader: QuickBooks Desktop. To every other program — and to every human who opens one in a text editor — an IIF export is a wall of tab-separated codes. Yet IIF files hold data people regularly need outside Desktop: years of transactions for an audit, the detail behind a migration to another accounting system, a client's history in a form an accountant can actually review. Converting the file to Excel or CSV turns the codes into columns anyone can sort, filter, and check.

The conversion is faithful rather than clever. Nothing is summarised away: if the file has 400 transactions with 900 split lines, the spreadsheet has 1,300 rows in the file's own order, with the splits marked so the two kinds of row are never confused.

How an IIF file is built

The split lines are the part most converters drop and the part accountants most need. In QuickBooks' double-entry shape, a transaction's TRNS line touches one account and its SPL lines touch the others, with amounts that mirror each other in sign. Keeping them — labelled, in order, immediately under their transaction — means the spreadsheet can be re-added-up both ways: by transaction, or by account.

The six columns you get

Date — converted from MM/DD/YYYY to yyyy-mm-dd, so sorting works. Type — the IIF transaction type for TRNS rows (CHECK, DEPOSIT, BILL, INVOICE and the rest), or "Split line" for SPL rows. Account — the account the line posts to. Name — the customer, vendor, or payee on the line. Amount — as written, splits keeping their sign. Memo — the line's memo text, word for word.

Desktop format, honestly scoped

IIF belongs to QuickBooks Desktop, and this tool does not pretend otherwise. It reads IIF exports; it does not connect to a Desktop company file, and QuickBooks Online neither produces nor consumes the format. If your data lives in Online, the equivalents are the QBO to CSV converter for Web Connect files and the bank-statement converters for PDFs. Going the other direction — building a Desktop-ready IIF from a spreadsheet — is the CSV to IIF converter's job, with the header blocks and balanced splits a real import requires.

A note on very old IIF files

IIF has been written by decades of QuickBooks versions, and the oldest exports occasionally omit the "!" header lines for some blocks. The converter falls back to the standard column layout Desktop itself uses in that case, so a headerless export still lands in the right columns. If a genuinely unusual variant misplaces a field, the honest check is the totals: the TRNS amounts in the spreadsheet should match the export's own report in Desktop before you rely on the file.