QuickBooks Desktop file choice

QuickBooks Desktop CSV vs QBO vs IIF: choose the workflow before the file.

These file types have different jobs. A CSV is a table, a QBO is a Web Connect bank statement, and IIF is a separate QuickBooks interchange format. An extension alone does not establish compatibility.

Updated July 25, 2026 · Examples use fictional data.

Use the next step nowIf the target is a Web Connect import, inspect the statement and test boundary before opening Desktop.

Validate a QBO first

The short comparison

Format	Typical role	BankFileKit boundary
CSV	A flexible delimited table used for spreadsheet review or CSV-specific import workflows.	Can format CSV/TXT/XLSX locally into a 3-column or 4-column bank CSV layout. It does not claim one universal Desktop CSV import path.
QBO	A QuickBooks Web Connect bank statement in the OFX family.	Can inspect a QBO locally as an audit CSV; CSV/XLSX-to-QBO output is an unverified beta candidate.
IIF	A QuickBooks interchange format used in separate Desktop data/list workflows.	Does not read, generate, repair, or validate IIF files.

CSV: a table that needs a target-specific mapping

CSV has columns rather than a universal bank-statement schema. Before using it, confirm the target's required headers, date convention, sign direction, and whether it expects one signed Amount column or separate Credit and Debit columns. BankFileKit's CSV formatter is for that local table-preparation step.

QBO: a Web Connect statement, not a company backup

Intuit identifies .qbo as a QuickBooks Bank Statement file. It may carry account metadata, a statement period, transactions, and identifiers such as FITID. It is not a .qbw company file, a .qbx accountant transfer, or a complete ledger export.

IIF: separate scope and separate risk

Intuit lists IIF among QuickBooks Desktop file types, but that does not make IIF an interchangeable replacement for a QBO bank statement or a formatted bank CSV. IIF content and import behavior need their own documented data model and a separately tested tool; BankFileKit deliberately does not advertise that capability.

Decision guide

Choose a formatted CSV when the intended target explicitly accepts a bank CSV and you can map the columns correctly.
Choose a bank-provided QBO when the intended workflow is QuickBooks Web Connect; inspect it and test in a blank company first.
Use an IIF workflow only when you already have an IIF-specific import requirement and a compatible, independently validated tool.
Do not choose a format merely because a filename can be renamed.

A fictional example

CSV review row: 07/25/2026,Fictional Workshop,-48.20
QBO tag: <FITID>FICTIONAL-0007
IIF: not supported by BankFileKit

Compatibility is not a marketing label

A local parse or download proves only what the browser code produced. It does not prove that a particular QuickBooks Desktop release, company file, account connection, or IIF workflow will accept the result. Keep backups and use controlled tests.

Sources checked July 25, 2026: Intuit: QuickBooks Desktop file types; Intuit: Import and export data in QuickBooks Desktop; Open Financial Exchange specifications.