IIF vs QBO for QuickBooks Desktop
IIF is QuickBooks Desktop's batch-import format (splits, journal entries, CoA). QBO is the Web Connect bank-feed format (transactions only, dedupe on FITID).
IIF and QBO both import into QuickBooks Desktop, but they solve different problems. IIF is a batch format for splits, journal entries, and list imports (CoA, customers, vendors). QBO is a bank-feed format for straight transaction imports with FITID-based dedupe. Neither works in QuickBooks Online (IIF at all; QBO does).
Candidates
Batch imports with splits, journal entries, list updates
- Full journal entries with splits
- List imports (CoA, customers, vendors)
- Tab-delimited, editable in Excel
- QuickBooks Desktop only — not Online
- Strict header validation — easy to break
- No dedupe (no FITID equivalent)
Recurring bank-feed transaction imports
- Dedupe on FITID — safe re-imports
- Works in QuickBooks Online AND Desktop
- One-click import via Banking → Upload from File
- Transactions only (no splits or JEs)
- Needs bank ID header
Decision matrix
| Use case | Pick | Why |
|---|---|---|
| Import a batch of journal entries | IIF | Only IIF supports multi-line JEs. |
| Import monthly bank statements | QBO | FITID dedupe is essential for monthly imports. |
| Import chart of accounts | IIF | QBO can't carry CoA. |
| Import to QuickBooks Online | QBO | QuickBooks Online doesn't accept IIF. |
FAQs
No — IIF is Desktop-only. Convert to QBO for bank transactions, or use QBO's batch transaction tools for JEs.
Partially — QBO carries per-transaction category memos, not full splits. IIF is the right format for splits.
No — re-importing the same IIF creates duplicate transactions. That's why bank feeds use QBO.