QBO to IIF: When You Need Accounting Entries Instead of a Bank Feed

Convert a bank QBO statement into balanced IIF transactions for a controlled QuickBooks Desktop import. 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

Read the bank transactions, review their signs, then choose the destination bank and offset account names. The names are case-sensitive to your bookkeeping workflow and should match the 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 QBO 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 qbo 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 iif output.
5. Compare the downloaded file with the original before importing it into your destination software.

What changes in this format

The original bank feed is converted into accounting entries. Each main transaction receives one offset line. This is useful for a deliberately prepared import, but the bank file does not contain the bookkeeping categories required for automatic categorization.

Worked example: verify the meaning, not just the extension

Two bank transactions create two TRNS blocks and two SPL blocks. This is four accounting lines but only two bank transactions. When verifying a 1,250.00 deposit and a -42.50 withdrawal, the TRNS net is 1,207.50 and all TRNS plus SPL lines sum to zero. Those two checks answer different questions and should both pass.

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

Desktop can also import QBO through Web Connect. Prefer that route when you want bank-feed review and matching. IIF is a different workflow, and repeatedly importing it can create duplicate entries.

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