QBO vs IIF: Which File Should You Import into QuickBooks Desktop?
QuickBooks Desktop has two common ways to bring transactions in from outside: QBO (Web Connect) files and IIF files. People often search for a “QBO to IIF converter” because they want transactions to land in the right accounts without clicking through the bank feed one by one. Before you switch to IIF, it is worth understanding what each format actually does.
The short version
| QBO (Web Connect) | IIF (Intuit Interchange Format) | |
|---|---|---|
| What it is | A bank statement in OFX format | A tab-separated list of QuickBooks transactions |
| Where it goes | Bank Feeds — you review, match and add | Straight into the registers as recorded transactions |
| Accounts / categories | You assign them during review (rules help) | Already in the file |
| Duplicate protection | Yes — each transaction has an ID (FITID) | No — importing twice creates duplicates |
| Validation | QuickBooks checks the bank and account | Very little; bad lines can corrupt data |
| Typical use | Regular bank and card imports | Bulk loads, migrations, one-off journal imports |
| Import menu | File → Utilities → Import → Web Connect Files | File → Utilities → Import → IIF Files |
QBO: the safe default for bank transactions
A .qbo file is the same thing your bank’s QuickBooks download gives you: a statement with dates, amounts, payees and a unique transaction ID. QuickBooks Desktop puts it into Bank Feeds, where every transaction must be matched to an existing entry or added with a payee and account. Bank rules (renaming and auto-categorisation) make this fast after the first month.
Because of the transaction IDs, re-importing the same period does not create duplicates, and QuickBooks keeps track of which bank account the file belongs to. For day-to-day bookkeeping this is the method Intuit supports and recommends.
No QBO download from your bank? Convert CSV to QBO, QFX to QBO or OFX to QBO.
IIF: powerful, but no safety net
An IIF file describes complete QuickBooks transactions — for example a check from Checking to Office Supplies for Staples — in a tab-separated text format with header lines such as !TRNS, !SPL and !ENDTRNS. When you import it, QuickBooks writes those transactions directly into your registers, with accounts, names and classes already set. There is no review step.
That is exactly why people want it, and exactly why it is risky:
- No undo and no duplicate check. Importing the same file twice doubles every transaction.
- Names must already exist or are created silently. A typo in an account or vendor name can create a new account instead of an error.
- Little validation. Unbalanced or malformed lines may be skipped or produce wrong entries.
If you use IIF, back up the company file first, import into a test copy, and review a few transactions in the register before importing into the real file.
When IIF makes sense
- Migrating a large history where reviewing thousands of bank feed items is not realistic.
- Importing transactions with known accounts from another system (for example, payroll or point-of-sale summaries).
- Bookkeepers with stable payee → account rules who process many clients every month.
For ordinary bank and credit card imports, QBO is usually the better choice: a few minutes of review in exchange for duplicate protection and a clean audit trail.
Converting bank files to IIF
An IIF file needs information a bank statement does not contain: the expense or income account for every transaction. A converter therefore needs mapping rules (for example “STAPLES → Office Supplies”, “GUSTO → Payroll Expenses”) on top of the statement data.
That is what we are building as QBO to IIF in ConvertQBO Pro: drop a QBO, QFX, OFX or CSV file, apply saved payee rules, and download an IIF file ready for QuickBooks Desktop. Join the waitlist to get early access.