OFX vs QFX vs QBO and Which Bank Statement Format to Use

TL;DR: OFX is the open interchange format that many personal finance and accounting tools read (the old MS Money, GnuCash, Xero and others, though not Quicken). QFX is Intuit's Quicken-specific Web Connect variant of OFX: it's the same underlying format with an added Intuit bank ID (INTU.BID). QBO is Intuit's QuickBooks Web Connect variant, built for QuickBooks. The short rule: choose QFX for Quicken, QBO for QuickBooks, and plain OFX for most other software.

If you download transactions from a bank or convert a PDF statement, you'll run into three similar file types that trip up a lot of bookkeepers. They look almost identical under the hood, but the extension you pick decides whether your accounting software accepts the file on the first try. Here's the honest breakdown, US context, no fluff.

OFX vs QFX vs QBO at a glance

All three descend from OFX (Open Financial Exchange), a specification originally created to move bank and investment transactions between financial institutions and software. QFX and QBO are Intuit's branded flavors of that same idea. The table below is the fastest way to see how they differ.

Notice how close QFX and QBO are: both are OFX with extra Intuit tagging. That's why a file often fails to import not because the data is wrong, but because the extension and internal identifiers don't match what the target program expects.

What is the difference between OFX and QFX?

OFX is the open, general purpose format that many programs can read. QFX is Intuit's Quicken version of OFX. Technically a QFX file is an OFX file with an added Intuit bank ID (INTU.BID) so Quicken's Web Connect recognizes it. Same core structure, one is branded for Quicken.

Why the extension matters more than the contents

Open a .qfx and a .ofx file in a text editor and they'll look nearly the same. The practical difference is that Quicken's Web Connect import path expects the .qfx extension and the Intuit identifier. Rename a valid OFX file to .qfx and it still fails because that bank ID is missing, and only your bank can issue it.

What is a QBO file?

A QBO file is QuickBooks' Web Connect version of the OFX format. It carries your bank transactions (dates, amounts, descriptions, check numbers) in OFX structure, tagged so QuickBooks Desktop or QuickBooks Online can import them. The .qbo extension tells QuickBooks to route the file through Web Connect rather than treating it as plain text.

Should I use OFX or QFX for Quicken?

For Quicken, QFX is the one that works, because it's Intuit's own Web Connect format and matches what Quicken's import expects. Quicken does not import plain OFX, and the Intuit bank ID that makes a QFX work can only be issued by your bank. When you have no QFX, Quicken's CSV import is the supported route.

Which format does QuickBooks use?

QuickBooks uses QBO (Web Connect) for direct transaction imports. QuickBooks Desktop imports .qbo files through the Web Connect feature, and QuickBooks Online can accept QBO alongside CSV. If your books live in QuickBooks Online, you can convert the statement straight to a .qbo file so the transactions land in the right accounts without retyping. For a full walkthrough, see our guide on how to convert bank statements to QuickBooks (QBO).

How to keep QFX and QBO straight

The names are easy to confuse because both are Intuit formats. Here's the memory trick: QFX ends the way Quicken does in spirit (both are for personal finance in Quicken), and QBO stands for QuickBooks Online in most people's minds. Point a QFX file at QuickBooks and it usually won't import cleanly; point a QBO file at Quicken and you'll hit the same wall. Match the format to the program.

Can I convert a PDF bank statement to OFX, QFX, or QBO?

OFX, yes. QFX and QBO, no. Banks rarely hand you an OFX, QFX, or QBO download for older statements, and you can convert the PDF yourself to OFX, CSV or Excel: a converter reads the transactions out of the PDF (including many scanned statements) and writes a clean file. QFX and QBO are different, because both carry a bank issued INTU.BID identifier that Intuit assigns only to participating institutions, so no converter can produce one that Quicken or QuickBooks Desktop will accept.

Which format should you export?

• Using Quicken? A genuine QFX can only come from your bank. Use the CSV route on the convert bank statement to Quicken page instead.
• Using QuickBooks Online? Export CSV or OFX; both import on the manual upload screen, up to about 1,000 lines per file. QuickBooks Desktop Web Connect reads only a bank issued QBO.
• Using something else, or not sure? Export OFX with our bank statement to OFX converter, since the widest range of tools reads it.
• Need a spreadsheet or a fallback? CSV works almost everywhere, though you'll usually map columns during import.

OFX vs QBO for accountants and bookkeepers

If you handle many clients, the decision often comes down to where the data ends up. Clients on QuickBooks want QBO. Clients on Quicken want a bank issued QFX, or CSV for converted statements. Firms running other ledgers or reconciliation tools usually accept OFX, and some prefer CSV so they can review rows before committing them. Standardizing on one export per client saves you from re-doing failed imports.

One caution: some newer versions of Intuit's software tighten which files they accept through Web Connect, so a QBO or QFX file needs valid identifiers, not just the right extension. That's the main reason a manually renamed file fails and a bank issued one doesn't.

A quick decision checklist

• Software is Quicken: use a bank issued QFX, or CSV for a converted statement.
• Software is QuickBooks (Desktop or Online): use QBO.
• Software reads OFX or you're unsure: use OFX.
• You only need the raw data in a spreadsheet: use CSV.

Common import errors and what they usually mean

When one of these files won't load, the culprit is almost always a mismatch between the format and the destination, not corrupted data. A few patterns show up again and again for US bookkeepers:

• Wrong extension for the program. A .ofx or .qfx file pointed at QuickBooks, or a .qbo pointed at Quicken, gets rejected before the data is even read. Re-export in the format that matches the target.
• Missing Intuit bank ID. QFX and QBO expect a valid INTU.BID value. A file that lacks it, or carries a placeholder, can fail Web Connect even though the transactions inside are perfectly fine.
• Duplicate transactions. Importing the same statement twice, or overlapping date ranges, can create duplicates. Most software flags these, but it's cleaner to import one statement period at a time.
• Date or amount formatting. When you fall back to CSV, columns sometimes map incorrectly (for example, a debit read as a credit). OFX-family formats avoid this because the structure is standardized, which is one reason bookkeepers prefer them over raw spreadsheets.

If you use a bank issued QFX or QBO for Web Connect, and a clean OFX or CSV from a converter for everything else, most of these problems disappear before they start. No converter can produce a file that is valid for Web Connect, because the identifiers come from the bank.

Do the three formats hold the same data?

For everyday bank statements, effectively yes. All three carry the transaction date, amount, description or payee, and often a check number or reference. The differences are in the wrapper: the extension and the Intuit tags that tell a specific program how to handle the file. So the choice between OFX, QFX, and QBO is really a choice about the destination software, not about how much detail you get to keep.

The bottom line

OFX, QFX, and QBO are three versions of the same family. OFX is the open format, QFX is Intuit's Quicken variant, and QBO is Intuit's QuickBooks variant. Once you know which program you're importing into, the right format is obvious: QFX for Quicken, QBO for QuickBooks, OFX for nearly everything else. When your statements only exist as PDFs, our bank statement converter turns them into OFX, or CSV for Quicken, so the import works the first time.