Convert IIF to CSV

A reporting tool, spreadsheet, or database may require CSV when the source data is available only as a QuickBooks IIF export. Converting the file makes tab-delimited records easier to inspect and exchange, but it does not automatically create a normalized accounting table.

What the IIF format is

IIF means Intuit Interchange Format, a plain-text exchange format used mainly by QuickBooks Desktop to import and export lists and transactions. QuickBooks Desktop and older accounting integrations use IIF for accounts, customers, vendors, invoices, bills, payments, journal entries, and other records.

An IIF file normally uses tab characters between fields. Lines beginning with markers such as !TRNS, !SPL, !ACCNT, and !ENDTRNS identify layouts or transaction sections; following lines contain the corresponding records. One file can therefore contain several record types with different column structures.

What the CSV format is

CSV represents tabular data as rows and columns, usually separated by commas. Fields containing commas, line breaks, or quotation marks are enclosed in quotation marks, with embedded quotation marks escaped according to the CSV dialect. Excel, LibreOffice Calc, Google Sheets, databases, reporting systems, and programming libraries support CSV.

CSV is suitable when every output row follows one consistent column layout. It does not preserve QuickBooks transaction relationships, posting rules, IIF section markers, or import metadata.

How to convert an IIF file

Using LibreOffice Calc

1. Make a backup of the original .iif file.
2. Open LibreOffice Calc and choose File → Open. Select the file, or set the file picker to show all files if the .iif extension is hidden.
3. In the Text Import dialog, select Separated by, enable Tab, and disable comma, semicolon, and space separators.
4. Set identifiers, account numbers, ZIP codes, and any other values whose leading zeroes must remain intact to Text. Check dates and amounts rather than allowing automatic type detection to change them.
5. Confirm that fields appear in the intended columns, then choose File → Save As.
6. Select Text CSV (.csv). Choose UTF-8 encoding when the destination supports it, and confirm the CSV format when Calc asks.

Excel uses the same general workflow: open the file through its text-import process, select tab as the delimiter, review column types, and choose File → Save As → CSV UTF-8. Do not rename file.iif to file.csv; changing the extension does not change tab delimiters or the record structure.

Using a local script

For a simple IIF file with one consistent layout, Python's standard library can copy tab-separated fields into a CSV file without uploading financial data:

import csv

with open('input.iif', newline='', encoding='utf-8-sig') as source, open('output.csv', 'w', newline='', encoding='utf-8-sig') as target:
    rows = csv.reader(source, delimiter='\t')
    csv.writer(target).writerows(rows)

This performs delimiter conversion only. It does not interpret !TRNS and !SPL relationships, combine transaction headers with split lines, or remove QuickBooks-specific fields. A custom script must select the required record type, define its columns, and map related lines into the desired report structure.

Exporting from QuickBooks Desktop

If the data is still available in QuickBooks Desktop, direct export is usually preferable to converting IIF. Open the required report and use Reports → report name → Export → Export to Excel, or export a list from its QuickBooks list window. Save the resulting spreadsheet as CSV. This produces a report-oriented table instead of exposing the mixed sections and markers in an IIF file.

Using an online converter

Services such as CloudConvert and Convertio are established online conversion providers, but their supported input formats and IIF handling can change. Use one only when its current format list explicitly accepts IIF or generic text input and offers CSV output; configure the source delimiter as a tab rather than assuming the service will understand QuickBooks sections.

Upload the file, select CSV as the output, check the delimiter and encoding options, run the conversion, and inspect the downloaded file in a text editor or spreadsheet. Do not upload files containing payroll, banking, customer, vendor, or other confidential financial data unless the organization permits that transfer. A local Calc workflow or script keeps the source on the computer.

Quality and compatibility limitations

• Mixed sections: A single CSV cannot cleanly represent IIF sections with different columns. Use separate CSV files, add a record-type column, or accept blank fields in a combined table.
• Transaction structure: A !TRNS line and its !SPL lines are related records, not independent rows. A visually correct CSV may still be unsuitable for import into QuickBooks or another accounting system.
• Automatic conversion: Spreadsheets can change dates, currency values, negative amounts, long numbers, and identifiers with leading zeroes. Import sensitive columns as text and compare row counts and totals with the original.
• Encoding: Use UTF-8 for accented and non-Latin characters. Older Windows-based workflows may expect Windows-1252; test the target application if characters become corrupted.
• CSV dialect: Some programs expect semicolons instead of commas, a particular line ending, or a UTF-8 byte-order mark. Match the destination application's requirements rather than relying only on the .csv extension.
• Import safety: CSV is plain text and does not retain QuickBooks validation or accounting controls. Treat converted data as an export for inspection, reporting, or exchange unless the receiving system documents a compatible import layout.