Convert XLS to IIF

QuickBooks Desktop accepts IIF files for batch imports of lists and transactions, while older accounting exports often arrive as Excel .xls workbooks. The task is to turn spreadsheet values into the exact tab-delimited records required by the QuickBooks import type; changing the filename alone does not convert the data.

What XLS files contain

XLS is Microsoft Excel’s binary workbook format for Excel 97–2003. It is still produced by older business applications and used by Microsoft Excel, LibreOffice Calc, and other spreadsheet tools.

An XLS workbook may contain several worksheets, formulas, formatting, charts, merged cells, macros, comments, and hidden rows. IIF retains none of those workbook features: it imports only text values arranged as QuickBooks records.

What IIF files are

IIF means Intuit Interchange Format. It is a tab-delimited text format used primarily by QuickBooks Desktop to import certain lists and transactions, including accounts, customers, vendors, items, journal entries, invoices, bills, checks, and payments where supported by the installed QuickBooks edition.

IIF files use header rows beginning with ! to define fields and data rows identified by record types. A transaction file commonly contains !TRNS, !SPL, and !ENDTRNS headers, followed by matching TRNS, SPL, and ENDTRNS records.

IIF is useful for repeatable batch entry and can be edited in a text editor or spreadsheet software before import. It has less protection than entering transactions manually, so a structurally valid file can still post incorrect accounts, amounts, names, or tax treatment.

Preparing and converting the workbook

1. Identify the exact QuickBooks Desktop target: a list import, general journal entry, invoice, bill, check, or another supported transaction type. Each type requires different fields and record codes.
2. Create one correct sample record in the destination company file when possible, then export it as IIF. Use that export as the template for field names, date style, account names, transaction codes, and required columns. An XLS file does not need to have originated in QuickBooks.
3. Open the XLS file in Excel or LibreOffice Calc. Place one record type on one worksheet, remove blank rows, and replace formulas with calculated values if the resulting values are what QuickBooks should receive.
4. Map source columns to the IIF template. Account, customer, vendor, item, class, payment term, and sales-tax names must match names in the destination company exactly unless the import is deliberately creating those list entries.
5. Build the IIF headers and data rows using the exported template. For journal-style transactions, each transaction normally has one TRNS row, one or more SPL rows, and an ENDTRNS row. The signed AMOUNT values for the transaction must net to zero.
6. Save only the completed worksheet as tab-delimited text: File → Save As → Text (Tab delimited) (*.txt). Rename the output from .txt to .iif, such as journal-import.iif. Excel exports the active worksheet only.
7. Open the file in a plain-text editor. Confirm that fields are separated by actual tab characters, not commas, and that no spreadsheet column headings or blank lines were exported unintentionally.
8. Back up the QuickBooks company file, then use File → Utilities → Import → IIF Files. Test a small batch in a copy of the company file before importing the full file.

Tools for mapped imports

For small or one-time imports, Excel or LibreOffice Calc plus an IIF sample exported from the destination QuickBooks company gives the most direct control. For recurring imports, desktop products such as Transaction Pro Importer and Zed Axis can map XLS, XLSX, CSV, or text columns to supported QuickBooks Desktop objects without manually constructing every IIF row.

Generic online file converters should not be used for financial imports because they cannot determine the QuickBooks transaction type or validate company-specific account and list names. Cloud mapping services such as SaasAnt Transactions can be appropriate only after confirming support for the specific QuickBooks product, import object, and file format; review data-handling terms before uploading financial records.

Compatibility checks

• QuickBooks Desktop releases do not support identical IIF fields and record types. Build the template from the same QuickBooks version and company file that will receive the import.
• Use the date format shown in an IIF file exported by that company. Do not assume that a locale-specific date such as 31/01/2026 will be interpreted correctly.
• Remove embedded tabs and line breaks from names, addresses, and memo fields because they can shift fields or split a record.
• Use the encoding produced by the QuickBooks-exported template where possible. Non-ASCII characters can import incorrectly when a text editor saves the file in an unsupported encoding.
• IIF imports can create duplicates when rerun. Include a unique reference or document number where the transaction type supports it, retain the imported file, and verify imported counts and balances.
• QuickBooks Online has different import capabilities and should not be assumed to accept an IIF file prepared for QuickBooks Desktop.