CSV to IIF: Account Names, Balanced Entries and a Safe Import

Convert bank CSV transactions into balanced IIF entries for QuickBooks Desktop, with account names you choose. 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

Map signed amounts or separate Debit and Credit columns, then enter your bank, income and expense account names exactly as they appear in the destination chart of accounts.

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 CSV to IIF Converter. Use Download sample file or the sample button first if you want to inspect the workflow with fictional data.
2. Choose the original csv file. The converter reads it locally. Keep an untouched copy for comparing counts and values later.
3. Confirm the date, description and amount mappings. Use either a signed Amount column or separate Debit and Credit columns. Set the date order explicitly.
4. Inspect the preview and resolve any errors. Read and acknowledge format limitations when they appear, then download the iif output.
5. Compare the downloaded file with the original before importing it into your destination software.

What changes in this format

Each transaction becomes a TRNS line and an equal, opposite SPL line followed by ENDTRNS. A receipt is treated as a deposit and a payment as a check. The tool does not infer tax codes, customer records or expense categories.

Worked example: verify the meaning, not just the extension

For a -42.50 supplies payment, the main Checking entry is -42.50 and its offset Expense entry is +42.50. The pair totals zero. For a 1,250.00 receipt, the main Checking entry is +1250.00 and the Income offset is -1250.00. If the receipt is a loan rather than revenue, change the offset account to the appropriate liability account before importing.

Set up the destination

For IIF output, confirm all three account names before downloading. A bank account, an income offset and an expense offset are required. These names select the accounts used in the generated entries; they are not labels for the output file. The tool produces balanced pairs but cannot know whether a transfer, refund or loan belongs in a particular account. See Intuit’s IIF import guidance for the destination workflow.

Common mistakes to avoid

An IIF import changes accounting entries rather than simply presenting a bank feed. Back up the company file and test a small import. Do not import a loan receipt as income or a transfer as an expense without correcting the account allocation.

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 CSV to IIF Converter or explore the other converters. For a related workflow, inspect IIF entries as CSV.