QBO vs QFX vs OFX: Which Bank File Format Do You Actually Need?

They are all the same family underneath

QBO, QFX, and OFX are not three unrelated formats. They are all built on OFX (Open Financial Exchange), an XML-style standard for moving bank transactions between institutions and accounting software. Open any of the three in a text editor and you will see the same skeleton: a <BANKMSGSRSV1> block, a list of <STMTTRN> transactions, dates, amounts, and a unique <FITID> on each line.

The differences are small but they matter at import time:

• OFX is the plain, vendor-neutral version. Generic financial apps read it happily.
• QFX is Intuit's flavor for Quicken. It adds an INTU.BID (Intuit Bank ID) field that tells Quicken which institution the data belongs to.
• QBO is Intuit's flavor for QuickBooks (Desktop and Online). It also carries an INTU.BID and is sometimes called "Web Connect."

So the question is never really "which format is better", it is "which app am I importing into, and what extension does it expect?"

Choose by your software, not your bank

Here is the decision in one table you can act on immediately:

• QuickBooks Online or QuickBooks Desktop → export .QBO. This is the native "Web Connect" upload that lands transactions straight in the bank feed for review.
• Quicken (Windows or Mac) → export .QFX. See our CSV to QFX guide for the full walkthrough.
• Xero, Wave, Sage, GnuCash, MoneyMoney, AccountEdge, and most everything else → export .OFX. Details in CSV to OFX.

The reason this is destination-driven is simple: QuickBooks Desktop historically refuses anything that is not .QBO, and Quicken expects its own .QFX. Handing QuickBooks an OFX file, or Quicken a QBO file, usually produces a flat "unsupported file" error even though the data inside is nearly identical.

Why your bank may only offer CSV or Excel

Many banks, especially smaller regional banks, credit unions, and most non-US institutions, only let you download CSV or Excel. The reason is the INTU.BID mentioned above: producing valid QBO or QFX files requires a paid Intuit registration (an Intuit Bank ID) that many institutions never bought. So they export a spreadsheet and leave the format conversion to you.

That is exactly the gap QBO Maker fills. Drop your bank's CSV or Excel export into the converter, map your date, description, and amount columns, and download a clean .QBO, .QFX, or .OFX file ready to import. Everything runs in your browser, your statement is never uploaded to a server. Note that we reads CSV, Excel and text-based PDFs (scanned PDFs need a CSV step first). statements; if your bank only gives you a PDF, export the transactions to CSV first.

What is actually different inside the files

If you are the kind of person who likes to peek under the hood, here is what changes between a QBO and a QFX file generated from the very same transactions:

• File header, both declare the OFX version, but Intuit formats include INTU.BID and (for QBO) INTU.USERID placeholders.
• Account type and routing, QBO is strict about <BANKID> and <ACCTTYPE> (CHECKING, SAVINGS, CREDITLINE). Get the account type wrong and QuickBooks may match it to the wrong account.
• FITID uniqueness, every transaction needs a stable, unique <FITID>. This is how the software avoids importing the same transaction twice. A good converter generates these deterministically so re-imports don't create duplicates.

Because the cores are so close, you will occasionally see people rename a .qfx to .qbo and try their luck. It sometimes works, but it is unreliable, the headers don't match what the target app expects, and a failed import can silently skip transactions. Generating the correct format from the start is safer.

Common errors and how to avoid them

Most format-related import failures come down to a handful of fixable issues:

1. Wrong extension for the app, OFX into QuickBooks Desktop, or QBO into Quicken. Re-export in the right format.
2. Date format mismatch, OFX wants YYYYMMDD internally. If your CSV has DD/MM/YYYY, the converter must interpret it correctly, or March 4 becomes April 3.
3. Sign convention, debits should be negative, credits positive. Some banks export both in one column, others split them. Map columns carefully.
4. Duplicate FITIDs, causes QuickBooks to skip rows as "already imported."

You can sanity-check any generated file before importing with our free OFX/QBO validator, which flags malformed headers, bad dates, and missing fields. Then head to the converter to produce your file.

Frequently asked questions

Related