When you’re comparing QBO vs IIF vs CSV for a bank import, the right choice depends on what you’re importing and which QuickBooks you run. In short: use a .QBO (Web Connect) file for bank transactions when your bank offers it, a CSV for bank transactions when it doesn’t, and an IIF only for special list/transaction imports in QuickBooks Desktop. These are the main QuickBooks import file formats, and mixing them up is the usual reason an upload fails.
QBO (Web Connect): the bank’s own format
A .QBO file is built on the OFX standard and carries each transaction’s date, amount, description, and a unique transaction ID. QuickBooks maps it automatically and uses those IDs to block duplicates. It’s the cleanest way to bring a statement period into the bank feed — when your bank actually offers a Web Connect download. Closed and non-connected accounts often don’t.
CSV: the flexible spreadsheet table
A CSV is just a plain table. The standard CSV format for QuickBooks bank uploads is three columns — Date, Description, Amount (negative for money out) — or a 4-column version splitting debits and credits. You map the columns yourself during Upload from file. CSV is the format to reach for when there’s no .QBO available or when you’ve converted a pdf or excel bank statement into a table. The trade-off: you map columns manually and there’s no built-in transaction ID, so you watch for duplicates.
IIF: lists and Desktop-only transactions
An IIF file (Intuit Interchange Format) is a tab-delimited text format used in QuickBooks Desktop to import or export lists (customers, vendors, chart of accounts) and certain transactions. It is not used in QuickBooks Online and is not the normal way to import a bank statement. Reach for IIF only when you’re moving list data or batch transactions in Desktop and you understand its strict column structure — it’s unforgiving and easy to corrupt.
So which one for a bank statement?
For day-to-day bank data: QBO if your bank offers it, CSV if it doesn’t. Skip IIF unless you have a specific Desktop list-import reason. But notice what all three share — every one of them imports transactions uncategorized. The format question gets your data in; it does nothing about coding it.
That coding step is what I built Bookmonstic to handle. (Disclosure: I’m a CPA and Bookmonstic is my own tool.) You feed it a pdf, csv, or excel bank or credit-card statement, it categorizes every transaction with AI, and it exports a ready-to-load QuickBooks “batch transactions import file” — so you skip both the format wrangling and the line-by-line coding. For the upload mechanics, see the three methods for importing bank statements into QuickBooks.
Frequently asked questions
QBO vs IIF vs CSV — which does QuickBooks Online use? QuickBooks Online accepts QBO and CSV for bank transactions. IIF is a QuickBooks Desktop format and isn’t used in QuickBooks Online.
What is the correct CSV format for QuickBooks? A 3-column file — Date, Description, Amount (negative for money out) — or a 4-column version with separate debit and credit columns. Keep one header row.
When should I use an IIF file? Only in QuickBooks Desktop, mainly for importing lists (vendors, customers, chart of accounts) or certain batch transactions. It’s not for normal bank-feed imports.
Do any of these formats categorize transactions for me? No. QBO, IIF, and CSV all import transactions uncategorized; you still code each one unless you use a tool that categorizes before export.
Written by the founder of Bookmonstic, a practicing CPA. Bookmonstic turns PDF/CSV/Excel bank statements into AI-categorized, import-ready files for QuickBooks and Xero — no rules to build, no API. Try it free →
Leave a Reply