IIF to CSV: Keep TRNS and SPL Separate in Your Spreadsheet

Inspect supported IIF transaction entries in CSV, retaining both TRNS and SPL records. This guide follows the actual controls and output of CSV2QBO, so you can distinguish a completed file conversion from a verified import.

Prepare the right source

Choose a tab-delimited transaction IIF with headers and ENDTRNS markers. Lists-only exports such as customers or inventory are outside this tool, as are unsupported invoice and payroll transaction types.

Work with a copy covering one account and a known date range. An export from a bank or finance application is preferable to a manually reconstructed table because it gives you an original to compare. Never rename a PDF or a company backup to a different extension and expect its contents to become transaction data.

Convert and review

1. Open the IIF to CSV Converter. Use Download sample file or the sample button first if you want to inspect the workflow with fictional data.
2. Choose the original iif file. The converter reads it locally. Keep an untouched copy for comparing counts and values later.
3. Review the parsed transactions. For QIF or IIF, set the source date order explicitly; OFX-family files already contain structured dates.
4. Inspect the preview and resolve any errors. Read and acknowledge format limitations when they appear, then download the csv output.
5. Compare the downloaded file with the original before importing it into your destination software.

What changes in this format

Unlike a bank CSV, this output contains both sides of the accounting entry. The Record column identifies TRNS and SPL. All encountered columns are retained, and each transaction must balance before export.

Worked example: verify the meaning, not just the extension

For a check with a TRNS amount of -100.00 and SPL amounts of +60.00 and +40.00, the CSV contains three rows. Filter Record to TRNS to see the bank payment. Inspect SPL to review the allocation. Summing every amount produces zero. Removing the Record column would make this table easy to misinterpret.

Set up the destination

For CSV output, open the result as a table and keep all columns together when sorting. Spreadsheet programs may reinterpret identifiers or dates, so import those columns as text when exact values matter. Text that could be interpreted as a formula receives an apostrophe prefix; this is a deliberate spreadsheet safety measure, not a financial adjustment.

Common mistakes to avoid

Filter Record to TRNS for main transaction totals. Adding TRNS and SPL amounts together should produce zero for balanced entries; that total is not your sales revenue or bank movement. Never count a split as another bank transaction.

An invalid date or amount blocks export rather than quietly removing a transaction. If an error names a record or source row, correct that record in a copy of the source and load it again. A date that is valid in two different orders still needs your explicit choice. Check a date whose day is greater than twelve to confirm the source convention when such a row is available.

A final comparison before import

Compare the first and last transaction dates, the number of main transactions, the total money in and the total money out. Inspect at least one refund or reversal when the source has one. A matching net total alone is insufficient: two errors with opposite signs can cancel each other. Keep the source and output together until the destination has been checked.

The local file limit is 5 MB, and supported financial inputs are bounded to 50,000 records. The destination software may allow less. Files remain in your browser; no account is needed, and no conversion file is stored on CSV2QBO servers.

Use IIF to CSV Converter or explore the other converters. For a related workflow, review a QBO as a spreadsheet.