Free IIF to Excel Converter for QuickBooks Desktop
Turn a supported QuickBooks IIF file into a structured Excel workbook you can review, filter, clean, analyze, share, or prepare for another workflow.
If your team repeatedly receives an IIF, converts it to Excel, cleans columns, reshapes data, and uploads it somewhere else, conversion may only be the middle step.
Choose your file
Drop your .IIF file here
Your file is never uploaded. We never receive it or store it.
One Workbook, One Sheet per Section
Taking a QuickBooks IIF to Excel means moving several tables at once, because an IIF file is not one table: it is a stack of them in a single document, each introduced by a header line beginning with an exclamation mark and each with its own set of columns. A workbook holds all of them at the same time, so nothing has to be chosen and nothing is left out.
The transactions come out as one sheet, with every line item sitting beside the date, payee, reference and memo of the transaction it belongs to. Sort it, filter it or pivot it, and it behaves like the accounting record it was taken from.
Chart of accounts, customers, vendors, employees, items and classes each get their own tab, named after the record type they came from. Which sections a file happens to contain is the file's business; the workbook simply carries a tab for each one the reader finds.
- Transactions (the sheet shown below)
- ACCNT
- CUST
- VEND
- INVITEM
- CLASS
| SPL.ACCNT | SPL.AMOUNT | TRNS.DOCNUM |
|---|---|---|
| Supplies | 300.00 | 00417 |
| Text | A number | Text, and it keeps the zero |
Each cell is typed in the file before Excel ever opens it, so nothing is inferred. Amounts total on open, and a reference number keeps every digit it started with.
Why Text Import Loses Your Data
Excel's own import wizard guesses at a file that is several tables, not one.
One Layout for Every Table
The Text Import wizard applies a single column layout to the whole file. An IIF holds several tables with different columns, so the chart of accounts collides with the transaction lines and a column stops meaning what its heading says.
It Rewrites Values on the Way In
This is the expensive one. Account numbers lose their leading zeros, anything shaped like a date becomes one, and long reference numbers turn into scientific notation. The rewriting is silent, and it has already happened by the time the sheet is in front of you.
The Header Rows Land in Your Data
A line beginning with an exclamation mark is a record definition rather than a row, and the wizard has no way to know that. Renaming the file to .csv or .txt changes nothing either: the structure is inside the file, not in its extension.
The Amounts Arrive as Numbers
Every cell is typed in the file itself, before Excel ever gets a chance to guess.
SUM Works the Moment It Opens
A column whose name ends in AMOUNT, QNTY, PRICE, COST, OBAMOUNT, BALANCE or LIMIT is written as a numeric cell. No leading apostrophes, no Text-to-Columns, and no re-typing a column before you can total it.
Everything Else Stays Text
On purpose, and that is the whole trick. A document number, an account number or a long reference is written exactly as the file had it, so 00417 keeps its leading zeros and a reference number stays a reference number rather than becoming 4.17E+02.
A Real .xlsx Workbook
Genuine Office Open XML, the same format Excel itself saves, rather than a delimited text file wearing a spreadsheet extension. It opens in Excel 2007 and later, Google Sheets, LibreOffice and Numbers with no compatibility warning.
What an IIF File Is
Intuit Interchange Format: tab-separated text QuickBooks Desktop uses for supported list and transaction workflows.
Lists
Current Intuit guidance describes native IIF export for lists, which is where most of these files come from: the chart of accounts, customers, vendors, employees, items and classes.
Transaction Files
Intuit's guidance is that general transactions can be imported by IIF but are not produced by the standard export workflow, so a transaction file usually arrives from payroll, a third-party application or another system built to feed QuickBooks.
Mixed Structures
One file can carry several headers and several schemas at once, each with a different set of columns beneath it. A payroll export that also brings its own account list is a single file with two shapes inside it.
How to Convert IIF to Excel
Four steps. The file is read inside your browser, so nothing is uploaded and nothing is stored.
Drop Your .IIF
An .iif or .txt export from QuickBooks Desktop, or the file a payroll or third-party system handed you. It is read where it sits, so there is no upload and no sign-up.
.iif · .txt
Choose How the Transactions Sit
Combining is on by default: each line item appears with its transaction's date, payee and reference repeated alongside it. Turn it off and the TRNS and SPL record types come back as sheets of their own.
combining on by default
Check What Was Found
Every section the reader recognised is listed with its row count, next to the warnings and anything it could not place. That happens before a workbook is written, not after.
counts and warnings first
Review and Download
The workbook is written in the browser and saved straight to your downloads folder. It is the shortest way to open IIF in Excel: no import wizard, no column layout to pick, and no values quietly reinterpreted on the way in.
written in the browser
A Workbook You Rebuild, or One That Refreshes
A workbook you make once, against a workbook that is already current when you open it.
| Need | Free converter | Autymate |
|---|---|---|
| One IIF to read | Exactly what it is for | Not worth setting up |
| The same export every period | Run it again by hand each time | The run stays configured where you put it |
| The same cleanup after every conversion | Fix the same columns in the sheet each period | Approved transformations applied before the data lands |
| Several locations or company files | One file at a time, per entity | Standardized mappings and routing where supported |
| The workbook feeds a reporting tool or a warehouse | Upload or merge it yourself | Connect the available source to the destination when interfaces permit |
A Workbook Is a Snapshot
It is a copy of the books at one moment, and it is not a connection to them.
QuickBooks Does Not See Your Edits
The workbook is the company file as it stood when the IIF was exported. Sorting it, correcting it or deleting a row changes the spreadsheet and nothing else. Getting a change back into QuickBooks Desktop is a separate import with its own rules.
Totalling the Transactions Sheet Double Counts
Each line item repeats its parent transaction's fields alongside it, so a TRNS column summed down that sheet counts one transaction once per line it has. Total the SPL amount column instead, or turn the combining off and use the record tables as they came.
About 40 MB
That is the size the converter accepts, and it is far past the point where Excel is pleasant to use anyway. Split the export by period if you are over it. A file that size arriving every month is a sign the export itself belongs in an integration.
Unsupported Sections Are Named
A record type the reader does not recognise is listed in the warnings rather than left out in silence. You can see what did not come across before you rely on the workbook, which is the part that matters when the data is a client's books.
When Every Location Sends Its Own IIF
A single file is what this page solves. What follows is the same job at ten locations, which is a different problem wearing the same clothes.
- A separate export per location, each with its own sections and columns
- The same cleanup applied to every workbook, by hand, every period
- Separate QuickBooks company files, each needing the right file routed to it
- An export that arrives late, with nobody named to notice
- A new location set up from scratch the month it opens
Common Questions
What people ask before they trust a converter with their accounting system.
It reads a supported Intuit Interchange Format file, works out the tables inside it, and writes them into an Excel workbook with one worksheet per section. The result is easier to review, filter, analyze, migrate or share than the raw text file, and the amount columns arrive as numbers rather than as text that looks like numbers.
Yes, for the record sections the converter supports. A mixed file holding both lists and transactions produces several worksheets in one workbook rather than one merged table, and any section the reader does not recognise is named in the warnings instead of being quietly left out.
Yes. “Open IIF file in Excel” usually means the Text Import wizard, which Intuit documents, and it does work, because an IIF is tab-separated text. What it also does is guess: one column layout is applied to a file holding several tables, so header rows land in the data, account numbers lose their leading zeros, and long references turn into scientific notation. This converter reads the file's own structure first and types every cell before Excel opens it.
Yes, a genuine Office Open XML .xlsx workbook, the same format Excel itself saves. It opens in Excel 2007 and later, Google Sheets, LibreOffice and Numbers without a compatibility warning, and it is not a delimited text file given a spreadsheet extension.
That is the combined Transactions sheet. IIF keeps a transaction's header row (TRNS) and its line items (SPL) as separate record types with overlapping column names: both carry DATE, ACCNT and AMOUNT. The prefix says which side of the transaction a column came from. Turn the combining off in the output options and the two come back as sheets of their own.
Current Intuit guidance is that QuickBooks Desktop exports lists to IIF. General transactions can be imported by IIF but are not produced through the standard export workflow, which is why a transaction file of this kind usually comes from payroll or a third-party application rather than from QuickBooks itself.
Each section becomes its own worksheet in one workbook, named after the record type it came from, so nothing is merged on a guess and nothing has to be left behind. Row counts and warnings are listed before the workbook is written.
It is named in the warnings rather than dropped in silence. You see which section did not come across before you rely on the workbook, which is what matters most when the data belongs to a client rather than to you.
Up to about 40 MB, which is well past the point where Excel becomes unpleasant to work in. Above that, split the export by period and convert each period on its own; the sections and the column typing behave identically on a smaller file.
For the round trip, the Excel to IIF Converter reads an .xlsx workbook directly, including its date cells and its separate sheets, so there is no save-as-CSV step in the middle. It is not automatic: you confirm the column mapping, and each transaction total is recomputed so the file still balances.
No to both. The file is read inside your browser and the workbook is written there too, so nothing reaches a server and there is nothing for anyone to keep or delete. Reading an export is not a write to QuickBooks, so your company file is untouched either way.
No. Autymate builds and runs accounting integrations for franchises, software companies and bookkeeping firms, and this converter is one of the tools that came out of that work. It is not an Intuit product and it is not endorsed by Intuit. QuickBooks and IIF are trademarks of Intuit Inc., and Excel is a trademark of Microsoft Corporation.
Written and maintained by The Autymate integrations team. We build and run accounting integrations for multi-location franchises, ISVs and bookkeeping firms: QuickBooks Desktop and Online, POS, payroll and ERP. These converters exist because we kept writing the same ones for customers, and there was no reason to keep them to ourselves.
Last reviewed
Stop Cleaning Up the Same Workbook Every Month
One export, converted once, is what this page is for. When the same IIF lands every period and the same columns are tidied before it goes anywhere, tell us where the file starts, what reads the workbook next, and how many locations or company files are involved.
Exact source access, fields, permissions, QuickBooks behaviour and service scope are confirmed during discovery.