Free IIF to CSV Converter for QuickBooks Desktop
Turn a supported QuickBooks IIF file into structured CSV data you can review, filter, clean, analyze, or prepare for another workflow.
If your team repeatedly receives an IIF, converts it to CSV, 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.
Why Renaming It to .csv Does Not Work
A QuickBooks IIF to CSV conversion has to answer a question that renaming the file cannot. An IIF is not one table. It is several, stacked in one document, each introduced by a header line beginning with an exclamation mark and each carrying its own columns. A CSV holds one table, so something has to decide which table you get and what becomes of the rest.
The answer is one row per line item, carrying its transaction's date, payee and reference in the same row. Two stacked blocks whose only connection is the order the lines happen to sit in become a single table where every row reads on its own, and that table sorts, filters and pivots like any other spreadsheet.
Rename the file instead and a spreadsheet gets three record shapes in one document with the header rows mixed into the data. That is why it shows one column of text, or splits it into columns that do not line up between record types. The record types that are not transactions are not lost either; they come out as tables of their own.
| From the .IIF — three record shapes, stacked | |||||
|---|---|---|---|---|---|
| TRNS | BILL | A/P | ACME | -450.00 | The transaction |
| SPL | BILL | Supplies | East | 300.00 | A line item |
| SPL | BILL | Rent | West | 150.00 | A line item |
| ENDTRNS | Closes it | ||||
| Into one table — one row per line item | |||||
| Txn | TRNS.DATE | TRNS.NAME | SPL.ACCNT | SPL.AMOUNT | |
| 1 | 3/4/2026 | ACME | Supplies | 300.00 | Parent repeated |
| 1 | 3/4/2026 | ACME | Rent | 150.00 | Parent repeated |
The relationship an IIF implies by line order becomes columns you can sort, filter and pivot. The repeated fields are why each row reads on its own.
Written to Survive the Round Trip
Four things decide whether the file still means the same thing once it reaches a spreadsheet.
Blank Fields Keep Their Place
Three tabs in a row means two empty columns, and both are written out. Parsers that treat a run of whitespace as one separator shift every column after the gap, and they do it quietly. You find out when the amounts turn up in the memo column.
Commas and Quotes Are Re-escaped
A value is quoted on the way out whenever it holds the separator, a quote mark or a line break, and any quotes inside it are doubled. A memo reading Storage, unit 4 comes back as one field rather than two.
Multi-line Memos Stay in One Cell
An address or a memo that wraps onto a second line is written inside quotes, so it arrives in its own cell instead of breaking the row in half and pushing everything after it up a line.
A Missing ENDTRNS Is Tolerated
Some third-party exporters leave the ENDTRNS marker off. A new TRNS line closes the transaction before it rather than that transaction being dropped, so the number of transactions you get back is the number the file describes.
What an IIF File Is
Where a QuickBooks Desktop IIF export comes from, and what is inside one when it arrives.
Lists Are the Native Export
IIF stands for Intuit Interchange Format, and the file is plain tab-separated text. Current Intuit guidance is that QuickBooks Desktop exports lists this way, so the chart of accounts, customers, vendors, items and classes each become a section of the file.
Transactions Travel the Other Way
General transactions can be imported by IIF but are not exported through the standard IIF export workflow. A file full of TRNS and SPL lines has usually come from payroll, a third-party application, or another system built to feed QuickBooks Desktop.
One File, Several Schemas
A single file can carry accounts, customers, vendors, items, classes and transactions at once, each under its own header line and each with a different set of columns. Files in the wild also arrive comma or semicolon separated, so the separator is worked out from the header lines rather than assumed.
How to Convert IIF to CSV
Four steps, and the separator you pick decides whether you get a .csv or a .tsv.
Drop Your .IIF
An .iif or .txt export from QuickBooks Desktop, or whatever produced the file you were sent. It is read inside your browser, so nothing is uploaded and there is no sign-up.
.iif · .txt
Choose How Transactions Come Out
Combined into one readable table is the default. The raw TRNS and SPL tables are one checkbox away, either instead of the combined table or alongside it.
one table, or every table
Check the Preview
The table count, the row count and the transaction count are shown with the first table's columns and rows. Any record type the file gave no header line for is named in the warnings here, before you download anything.
warnings before download
Pick a Separator and Download
Comma is the default, semicolon suits European Excel and tab writes a .tsv. That is all it takes to open IIF as CSV, and the same panel offers an .xlsx download if a workbook turns out to be what you wanted.
comma · semicolon · tab
Every Section, or Just the Transactions
You choose the shape, and both come out of the same read of the same file.
The Combined Table
One row per line item, each carrying its transaction's date, payee and reference. This is what most people want out of the conversion, so it is what happens unless you say otherwise. Turn it off and the raw TRNS and SPL tables come out as they sit in the file, or keep both and the combined table arrives with the raw tables beside it.
Every Table on Its Own
The chart of accounts, customers, vendors, items and classes are each their own section of the file and each becomes its own table. One table downloads as one file. More than one and you get all of them together as a .zip, plus a separate download for each, named after the section it came out of.
One Export to Read, or a Standing Report
Reading one export is this page. Reading the same one monthly is a different problem.
| Need | Free converter | Autymate |
|---|---|---|
| A file you have to read once | This page, and there is nothing to set up | More than the job asks for |
| The same export every period | The same options chosen again each time | The choices are made once and then they hold |
| Cleanup after every conversion | The same columns reshaped in a spreadsheet each period | Approved transformations run before the data lands |
| Several company files | Convert each file on its own | Standardized mappings and routing where the environment supports it |
| A destination that is not a spreadsheet | Upload or merge the CSV by hand | Connect the available source to the destination where interfaces permit |
What a CSV Cannot Carry Back
A CSV is a readable copy, not a return ticket. Four things follow from that.
It Is Not an IIF Any More
Converting to CSV does not mean the file can later be imported back into QuickBooks with the same meaning. QuickBooks Desktop reads CSV and Excel for some data, but a flat table carries no record types and no header lines, and those are what an IIF import reads the file by.
Totalling a Parent Column Double Counts
The transaction's own fields repeat onto every line item, which is what makes each row readable on its own. It also means a TRNS.AMOUNT column summed down the page counts one transaction once for every line it has. Total the SPL columns instead, or filter to one row per transaction first.
Skipped Records Are Named
A record type with no header line above it cannot be identified, so its rows are skipped and the record type is named in the warnings along with the reason. What the converter could not read is reported rather than quietly left out of the count.
It Is a Copy
Editing the CSV changes nothing in QuickBooks. The company file does not know this file exists, and nothing you do to the columns travels back on its own. Getting any of it into QuickBooks is a separate import with its own consequences.
Across Locations and Company Files
This page handles one file at a time. The list below is what begins to cost real time once every location sends its own IIF, every period, into its own company file.
- A different set of record types in every file, depending on what produced it
- The same columns renamed and reshaped after every conversion
- Separate QuickBooks company files, each with its own chart of accounts
- A file that arrives late, or arrives twice, with nobody named to notice
- A new location added, and the whole routine built again from scratch
- A catch-up across earlier periods, with period boundaries and duplicates to keep straight
Common Questions
What people ask before they trust a converter with their accounting system.
It reads a supported Intuit Interchange Format file and writes the data out as comma-separated tables you can review in a spreadsheet, a database, a migration or an analytics tool. The useful part is that it separates the record types and joins each line item to its transaction, which a plain rename cannot do.
Yes, for the record sections the converter recognises. A QuickBooks IIF file to CSV conversion produces one table per section, and transactions come out combined into a single readable table by default. Anything the file gave no header line for is named in the warnings rather than converted on a guess.
Current Intuit guidance is that QuickBooks Desktop exports lists to IIF. General transactions can be imported by IIF but are not exported through the standard IIF export workflow, so a transaction file has usually been produced by payroll, a third-party application, or another system built to feed QuickBooks.
You can, and Intuit documents doing it through the text import workflow. It is worth knowing what you take on: the header rows sit inside the data, the record types do not share columns, and the line items are not joined to their transactions. A converter is the shorter route when you want that joining done and a repeatable output.
Yes, through a grouping column. The combined table numbers each transaction and repeats its fields onto every line item, so the relationship an IIF implies by line order becomes columns you can sort and filter on. Turn the combining off and you get the raw TRNS and SPL tables as they sit in the file.
They are not wrong. An IIF transaction balances to zero, so the header line and its line items carry opposite signs. A bill's header sits at -450.00 against line items of +300.00 and +150.00, and the two cancel. If you only want one side of it, filter on the SPL columns.
Check that it still carries its header lines, the ones beginning with an exclamation mark. Some editors and email gateways strip or mangle them, and without them nothing in the file can be identified. The converter names the record types it had to skip and why, which usually points straight at the missing header.
Not as a general replacement. QuickBooks Desktop accepts CSV and Excel for some kinds of data, but a flat table does not carry every IIF structure or transaction type, and the record types an IIF import reads the file by are gone once it is flat. Treat the CSV as a copy to read, not a route home.
No. The converter reads the file you hand it and writes a new one beside it. It never opens, writes to, or connects to a QuickBooks company file, and QuickBooks does not need to be running for any of it.
There is no upload. The file is parsed inside your own browser and the CSV is written there too, so it never reaches a server and there is nothing for anyone to keep, log or delete. If you are handling a client's books, that is usually the deciding detail.
Where the original source and destination expose the data and an integration method, Autymate can scope the wider workflow rather than the middle step. The best design often removes the file entirely, because nobody wanted the IIF or the CSV in the first place. They wanted what the CSV was going to feed.
No. QuickBooks and IIF are trademarks of Intuit Inc. Autymate is not affiliated with or endorsed by Intuit, and this converter is not an Intuit product. It is a free tool built by the team that writes accounting integrations for a living.
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
When the Export Itself Is the Problem
The converter is the right tool when one file has to be read. If someone produces an IIF every period so it can become a spreadsheet somewhere else, tell us where it starts, what reads the CSV next, and how many company files are involved.
Exact source access, fields, permissions, QuickBooks behaviour and service scope are confirmed during discovery.