QBO vs OFX vs QFX vs QIF: What Each Bank File Format Actually Is

A bank's download menu often offers four similar-looking options — OFX, QFX, QBO and QIF — with no explanation of which one your accounting software will accept. The four are closely related, and picking the wrong one usually produces an import error. This page defines each format, names who controls it, and sets out which application accepts which, with a primary source linked inline.

What Is an OFX File?

An OFX file is a bank-statement file in Open Financial Exchange format, an open specification that any financial institution or software vendor may implement to move transaction data from a bank into money-management software. OFX is the parent standard against which QFX, QBO and QIF are measured.

Open Financial Exchange was created by Microsoft, Intuit and CheckFree, announced on 16 January 1997 with version 1.0 released that 14 February. Versions 1.0 to 1.6 are SGML-based; later versions are XML. The specification was governed by the OFX Consortium until 2019, when the work moved to the Financial Data Exchange, which maintains it today. The current banking release is OFX Banking 2.3, published in October 2020, and the specification remains a free public download.

What OFX Is Used For

OFX is used to carry a bank's transaction records — account identifiers, dates, amounts, descriptions, unique transaction IDs and balances — in a structured, tag-based file that accounting software reads without anyone retyping a line. OFX is also the specification underneath the online-banking connections that fetch those records automatically.

Both uses appear in Intuit's financial-data-partner documentation, which describes three connectivity types built on OFX: Direct Connect, the only two-way type; Web Connect, where the user downloads a file from the bank and opens it in their software; and Aggregation, also called Express Web Connect. Because the specification is open, applications outside the Intuit family implement it too — the GnuCash manual documents OFX import directly.

Which Apps Open an OFX File

An OFX file opens in GnuCash and in QuickBooks Online — but not in Quicken for Windows. Quicken's own support documentation states it plainly: "Quicken cannot import Excel (.xls), QuickBooks, PDF, or OFX files." That is counter-intuitive if you assumed the open standard would be the safe universal choice.

GnuCash's manual lists .ofx under File ▸ Import. Xero Central lists OFX among the bank-statement formats Xero accepts, and says that where a bank offers a choice, Xero recommends OFX over QIF, QFX, CSV or QuickBooks formats — that is Xero's own published guidance, not something tested here. Intuit's manual-upload help article for QuickBooks Online names .ofx in its step-by-step list. Microsoft Money also reads OFX, though Money was discontinued in 2009 and the free Money Plus Sunset build is offline-only and unsupported.

What Is a QFX File?

A QFX file is Intuit's licensed variant of the OFX format, used to import bank transactions into Quicken for Windows. The functional name for the download-and-import method that produces a QFX file is Web Connect. Wikipedia's QFX entry describes the format as "a standard OFX file with additional fields to support a licensing fee paid by institutions to Intuit."

Quicken documents the literal import path on its support site: File menu > File Import > Quicken Transfer Format (.QFX) File.

The expansion of "QFX" is genuinely unsettled, and two Quicken-owned properties disagree. Quicken's help site states that "QFX stands for Quicken File eXchange" (info.quicken.com), while the File menu quoted on Quicken's support page reads "Quicken Transfer Format (.QFX) File." Third-party sources add "Quicken Financial Exchange" and "Quicken Web Connect." Both Quicken pages were checked on 17 September 2026. Web Connect is the name the product itself uses.

How QFX Differs From OFX

QFX differs from OFX by carrying extra Intuit-specific tags inside the file's <FI> block — QFX files typically include INTU.BID and INTU.USERID — and by being tied to an Intuit contract. The transaction data itself is ordinary OFX; the additions identify the financial institution to Intuit's software.

No public specification for the QFX format exists, so this tag-level detail comes from practitioners who have inspected the files rather than from Intuit documentation. Those accounts place INTU.BID — the institution's Intuit Branding ID — immediately below the <LANGUAGE> line.

One point is widely got wrong: INTU.BID is not what separates QFX from QBO. The same tag appears in both. It separates the Intuit family from plain OFX, and it is the BID value, together with the file extension, that routes a file to Quicken rather than QuickBooks. The way those same accounts describe turning a QFX file into a QBO file is to edit that number and change the extension — a relabeling, not a translation.

Why Quicken Uses QFX and Not OFX

Quicken for Windows uses QFX rather than plain OFX because the Intuit variant carries a contracted institution identifier that Quicken validates on import. Intuit's financial-data-partner documentation states that "Web Connect and Direct Connect are directly associated with a contracted Intuit BID (Branding ID)" and that, for Web Connect, a "contract with Intuit or your OFX/Online Banking Provider is required."

Wikipedia's QFX article attributes that gate to a licensing fee paid by institutions to Intuit, and adds that "Quicken will only import QFX files where the providing institution has paid the fee and in some cases passed quality tests." Neither Intuit nor Quicken publishes the terms or the amount. The consequence is structural rather than technical. A bank that has not contracted with Intuit produces a file Quicken for Windows declines, even though the transaction records inside it are identical.

What Is a QBO File?

A QBO file is Intuit's Web Connect file for QuickBooks — an OFX-derived bank-transaction file with a .qbo extension that QuickBooks Desktop imports directly. A QBO file is not to be confused with QBO as shorthand for the QuickBooks Online product.

Intuit's own file-extension reference for QuickBooks Desktop is brief on the point: "When you download transactions from your bank, QuickBooks opens them from a file with a .qbo extension."

Practitioner accounts describe a QBO file as an OFX file with INTU.BID added and the extension changed, and are explicit that renaming alone fails. QuickBooks matches the BID against its list of Web Connect institutions and rejects files it cannot place. No public specification for the .qbo format has been published, so that mechanism is reverse-engineered rather than documented by Intuit.

What Is QuickBooks Web Connect?

QuickBooks Web Connect is Intuit's name for the connectivity method in which a user downloads a transaction file from their bank's website and imports it into QuickBooks or Quicken. Intuit's partner documentation defines Web Connect as the type "where end users download a .qbo (QuickBooks) or .qfx (Quicken) file and import that file into QuickBooks or Quicken."

Web Connect is one of Intuit's three connectivity types, alongside Direct Connect — the only two-way type — and Aggregation, also called Express Web Connect. The file originates at the bank, not at Intuit: a Web Connect user signs in to online banking, picks the QuickBooks or Quicken download option for the date range they need, and opens the resulting file in the application. The same Intuit page notes that a contract with Intuit or the bank's online-banking provider is required for Web Connect to be offered.

Which QuickBooks Versions Accept Which Files

QuickBooks Desktop and QuickBooks Online accept different file types, so naming the edition matters. QuickBooks Desktop's Web Connect import expects a .qbo file. QuickBooks Online accepts a wider set: across Intuit's manual-upload help article, the accepted types named are CSV, TXT, QBO, QFX and OFX.

That article lists the accepted formats twice, and the two lists disagree. Its Transaction list file guidelines section reads: "Your upload file must be in English and 350 KB or less. We suggest a QuickBooks Online data (QBO) file. You can also upload (Quicken) QFX, or Comma-separated values (CSV) files" — which omits OFX. Its Upload a list section reads: "Follow these steps if you'd like to upload your bank statement from these file types: .csv, .txt, .qbo, or .ofx" — which omits QFX. Neither list contains all five; the set above is the union of both, read live on 17 September 2026. The same page sets upload limits of 350 KB and 1,000 lines.

What Is a QIF File?

A QIF file is a Quicken Interchange Format file: a plain-text, ASCII record of financial transactions used to move data between programs. Quicken's own help describes QIF as "an open file format used to transfer financial data between software programs," stored in "plain-text, ASCII format." QIF predates OFX and was originated by Intuit.

QIF is open in the practical sense that anyone can read or write it, but it is not a governed standard. There is no standards body, no version numbering and no active maintainer — Intuit created the format and effectively left it. That is the substantive difference between QIF and OFX: OFX is an open specification with an organization behind it, while QIF is an open format with nobody behind it.

Why QIF Is Still Around

QIF is still around because it is plain text with no licensing gate: any program can read or write a QIF file without a contract or a vendor identifier. Several current applications still import it. What QIF cannot do is the reason the industry moved on: a QIF file carries no unique transaction identifiers.

Without an ID per transaction, a QIF import cannot be matched against records already in the destination file, so it cannot be reconciled or de-duplicated. That gap is widely described as one of the primary shortcomings of QIF, though it rests on reference and practitioner sources rather than a vendor specification. QIF also has no way to mark the currency a transaction was completed in, and its date handling is ambiguous. The OFX-derived formats carry a unique ID per transaction, which is why vendor guidance steers users away from QIF.

Does Quicken Still Import QIF Files?

Quicken's own documentation gives two incompatible answers on whether Quicken for Windows still imports QIF files into bank and brokerage accounts, and as of 17 September 2026 the contradiction is unresolved. All three pages quoted below are Quicken's own.

Quicken's support article How do I import data into Quicken for Windows? — article HOW23776, stamped Updated: June 05, 2026 — takes the restrictive position: "QIF import isn't available for checking, savings, or credit card accounts, or for 401(k) or any other brokerage accounts."

Quicken's Windows help site takes the opposite position, and states it more explicitly: "You can use QIF files to import data into any account type, including banking, investment, asset, liability, and cash accounts. This includes checking, savings, credit card, 401(k), brokerage, and others" (info.quicken.com). A second help-site page agrees: "Yes. While older versions of Quicken did not have this capability, you can now import any account type using QIF."

The tiebreakers point in opposite directions. The restrictive support article carries the newer stamp, June 2026, and uses the current product name Quicken Business & Personal. The most explicit permissive page uses the retired name Quicken Home & Business, suggesting older copy — yet it is the permissive one, the reverse of what you would expect if a restriction were being lifted over time. And the shorter permissive page — why-can-t-i-import-data-from-a-qif-file-into-a-ban — is the one Google's AI Overview currently cites for the query qif file, so the permissive version is the one propagating into AI answers.

The practical position for a Quicken for Windows user is to attempt the import and see which account types the dialog offers. If the account you need is not listed, the long-standing workaround is to import the QIF into a cash, asset or liability account, then select the transactions and move them to the real account — accepting that there is no reconciliation step.

Which Format Does Each App Need?

Which format you need depends entirely on the destination application: Quicken for Windows needs QFX, QuickBooks Desktop needs QBO, QuickBooks Online takes several, and Xero is the only application here whose own documentation lists all four. The matrix below sets application against format.

Quicken for Windows needs QFX, because Quicken's support page states it cannot import OFX or QuickBooks files. QuickBooks Desktop needs QBO, because Web Connect import expects a .qbo file. QuickBooks Online takes QBO as Intuit's suggested option, with QFX, OFX, CSV and TXT named across the same help article. Xero Central lists all four and recommends OFX over the rest — Xero's own published guidance, not an independently tested result. GnuCash's documented importers cover .ofx, .qfx and .qif; whether GnuCash reads a .qbo file is undocumented and untested here, so the matrix records it as not tested rather than guessing. Microsoft Money Plus Sunset reads all four, but Money was discontinued in 2009 and the Sunset build is offline-only and unsupported.

Frequently Asked Questions

What program opens a QFX file?

Quicken for Windows opens a QFX file natively, through File menu > File Import > Quicken Transfer Format (.QFX) File. Outside Quicken, QuickBooks Online names QFX in the guidelines section of Intuit's upload help, Xero Central lists QFX among the formats it accepts, and GnuCash imports .qfx with its .ofx importer.

Is a QBO file the same as QuickBooks Online?

No. "QBO" carries three separate meanings: the .qbo Web Connect file format that QuickBooks Desktop imports; the common abbreviation for the QuickBooks Online product; and Intuit's own phrasing in QuickBooks Online's upload help, which refers to "a QuickBooks Online data (QBO) file." The format and the product are not the same thing.

Can I open an OFX or QFX file in Excel?

An OFX or QFX file is tag-based text rather than a spreadsheet, so opening one shows markup tags wrapped around each value. For a spreadsheet you can work with directly, the reliable route is the export function in whichever application already holds the transactions.

What is the difference between an OFX file and a CSV file?

An OFX file is a structured, tag-based format defined by a published specification, so every value carries a declared meaning — account identifier, transaction ID, amount, balance. A CSV file is plain delimited text with no schema, so meaning depends on whoever produced it. QuickBooks Online, for instance, requires an uploaded CSV to have three columns (Date, Description, Amount) or four (Date, Description, Credit, Debit).

Which format keeps the most transaction detail?

The three OFX-derived formats — OFX, QFX and QBO — carry more than QIF does, because QIF has no unique transaction identifiers, no currency marking and ambiguous date handling. No vendor publishes a field-by-field comparison of the four, so this reflects QIF's documented gaps rather than a measured ranking.