QBO vs QFX vs OFX: Which File Format Does QuickBooks Need

If you have ever downloaded a bank statement and stared at the file extension, wondering whether to pick QBO, QFX, or OFX, you are not alone. The names look interchangeable, but QuickBooks treats them very differently. Choosing the wrong one is the most common reason a bank import fails on the first try. This guide explains what each format is, which software accepts which, and how to decide in about thirty seconds.

Quick comparison: QBO vs QFX vs OFX vs QIF vs CSV

Here is the short version before the details. The table below maps each format to the software that actually accepts it.

Format Full name Base standard Best for Accepted by
QBO QuickBooks Web Connect OFX 1.x (SGML) with Intuit extensions QuickBooks Desktop and Online QuickBooks only
QFX Quicken Web Connect OFX 1.x (SGML) with Intuit extensions Quicken (personal finance) Quicken only
OFX Open Financial Exchange OFX 1.x or 2.x Generic OFX clients, some banks Varies by bank and tool
QIF Quicken Interchange Format Plain text, legacy Very old Quicken and Money Legacy import only
CSV Comma Separated Values Plain text Any spreadsheet or accounting tool Almost everything

The key insight is that QBO, QFX, and OFX share a common ancestor. OFX is the open standard. QBO and QFX are Intuit’s branded flavors of OFX, each carrying extra fields that tell QuickBooks or Quicken who the bank is. That one extra field is the whole reason the formats are not interchangeable.

What each format actually is

OFX: the base standard

OFX stands for Open Financial Exchange. It is an open specification maintained by the OFX Consortium. An OFX file is a structured text file that carries account information, transactions, balances, and payee details. Early OFX (1.x) is written in SGML, a markup style similar to HTML. Later OFX (2.x) switched to XML. Banks often offer OFX downloads labeled simply as “OFX” or “Web Connect” without a brand.

QBO: QuickBooks Web Connect

QBO is OFX plus Intuit-specific extensions. The most important extension is the INTU.BID field, which holds the bank’s unique identifier in Intuit’s directory. QuickBooks uses INTU.BID to recognize the financial institution and match the import to the right bank feed. Without it, QuickBooks cannot complete a Web Connect import. A QBO file is usually SGML-based OFX 1.x with these extra Intuit tags.

QFX: Quicken Web Connect

QFX is the same idea as QBO but for Quicken. It carries its own Intuit-style bank identifier and is branded for Quicken Web Connect. Quicken will not import a QBO file, and QuickBooks will not import a QFX file. The two look almost identical inside, which is why people confuse them.

QIF: the legacy format

QIF is an older, simpler text format from the Quicken era. It has no bank identifier and no standard transaction schema. QuickBooks can import QIF in some legacy paths, but results are often messy. Modern workflows should avoid QIF unless a bank only offers QIF.

CSV: the universal fallback

CSV is just rows and columns. Every tool reads it. The trade-off is that CSV carries no bank identity and no structured balance information, so QuickBooks cannot auto-match it to a bank feed. You map columns manually during import.

From Bank Statement to QuickBooks-Ready File

That manual cleanup you just read about? This tool skips it. Turn your PDF into QBO for QuickBooks without storing your data anywhere.

Start Converting

QuickBooks Desktop vs QuickBooks Online acceptance matrix

Acceptance depends on both the product and the import path. The matrix below covers the common cases.

Software QBO QFX OFX QIF CSV
QuickBooks Desktop (bank feed / Web Connect) Yes No Sometimes Legacy only Yes, manual mapping
QuickBooks Online (bank upload) Yes No Sometimes No Yes, manual mapping
Quicken No Yes Sometimes Legacy Yes
Other accounting tools Rarely Rarely Often Rarely Yes

“Sometimes” for OFX means it depends on whether the file carries the fields QuickBooks expects and whether the bank is recognized. In practice, a plain OFX download from a bank often imports into QuickBooks only if an INTU.BID or equivalent bank id is present. Many users find that a generic OFX file imports but cannot be matched to the right account, or fails outright.

Decision tree for choosing the right file format
Decision tree for choosing the right file format

The INTU.BID field and why it matters

INTU.BID is a tag inside the OFX header that stores the bank’s Intuit directory ID. When QuickBooks opens a QBO file, it reads INTU.BID first. It uses that ID to look up the bank in its directory, confirm the account type, and connect the import to the correct bank feed. If INTU.BID is missing or wrong, QuickBooks stops and shows an error such as “unable to verify financial institution” or “file not supported.”

This is why a file can look perfectly valid as OFX yet fail in QuickBooks. The transaction data is fine. The bank identity is missing. QuickBooks refuses to guess which bank sent the file, because guessing would create duplicate accounts and corrupted feeds.

For a QBO file to work, INTU.BID must be present, it must match a real entry in Intuit’s bank directory, and it should match the account you selected during import. EasyStatementSheet generates QBO files with the correct INTU.BID already filled in, which removes the most common failure point.

Why renaming .ofx to .qbo does not work

Renaming a file changes the label, not the contents. A file named statement.qbo that actually contains plain OFX without Intuit extensions will still fail in QuickBooks, because QuickBooks reads the tags inside, not the extension. The extension is a hint; the INTU.BID and Intuit header tags are the requirement.

Some users try renaming because the bank only offers OFX and they need QBO. The rename produces a file QuickBooks will attempt to open, then reject. The error message often confuses people into thinking the file is corrupt, when really it is just missing the Intuit layer. The fix is conversion, not renaming.

Conversion between formats: when possible, when not

Conversion is possible when you have the source data and a tool that can rewrite the OFX header with the right extensions. It is not possible when the source lacks the bank identifier or transaction detail.

  • OFX to QBO: possible if you add the correct INTU.BID and Intuit header tags. This is what a proper converter does.
  • QBO to OFX: possible by stripping the Intuit extensions. The result is standard OFX, usually importable by other tools.
  • QFX to QBO: not directly. The bank IDs differ. You would need to rewrite the header for the target software.
  • CSV to QBO: possible only if you also supply the bank ID and account details. A converter maps columns and writes the OFX structure.
  • QIF to anything modern: rarely worth it. Re-export from the source if possible.

What conversion cannot fix is missing data. If the source file lacks closing balances, payee names, or transaction dates, no format change will add them. Always check the source before converting.

Decision tree: which format to download or use

Use this quick decision path.

  1. Are you importing into QuickBooks Desktop or QuickBooks Online? If yes, download or convert to QBO.
  2. Are you importing into Quicken? If yes, use QFX.
  3. Are you using another accounting tool or a spreadsheet? If yes, try OFX first; fall back to CSV if OFX is rejected.
  4. Does your bank only offer PDF or paper statements? Convert the statement to QBO for QuickBooks or CSV for anything else. Use convert bank statement to QuickBooks for the QBO path.
  5. Are you unsure which software you will use later? Keep a CSV copy. CSV is the safest archive format.

When in doubt, download every format your bank offers. Banks often provide QBO, OFX, and CSV from the same download page. Having all three costs nothing and saves a round trip later.

Common failure modes when you choose wrong

Wrong format imported

You upload a QFX into QuickBooks and see “file not supported” or “invalid file format.” The fix is to re-download as QBO or convert. Do not rename the extension.

Duplicate transactions

You import the same statement twice, or import a QBO and then a CSV of the same period. QuickBooks may create duplicates if the transaction IDs differ between formats. Always import one format per period, and check for duplicates before reconciling.

Missing INTU.BID

A generic OFX file lacks INTU.BID, so QuickBooks cannot identify the bank. Symptoms include “unable to verify financial institution” and an import that stops at the bank selection screen. The fix is a QBO file with the correct INTU.BID.

Account mismatch

The INTU.BID identifies a bank, but the account type in the file does not match the account you selected in QuickBooks. Choose the matching account during import, or fix the account type in the file.

Encoding or SGML errors

Some banks export OFX with characters that break SGML parsing. If QuickBooks reports a parse error, re-export from the bank or run the file through a converter that normalizes the markup.

When to use CSV instead of QBO

CSV is the right choice when you need flexibility more than automation. Use CSV when:

  • You are importing into a tool that does not accept QBO or OFX.
  • You need to edit transactions before import, such as splitting a combined deposit or fixing payee names.
  • You are archiving or analyzing data in Excel or Google Sheets.
  • The bank’s QBO download is broken or missing INTU.BID and you cannot convert it.

The trade-off is manual column mapping and no automatic bank feed matching. For a deeper comparison, see CSV vs QBO for QuickBooks. If you are starting from a PDF or paper statement, convert a bank statement to CSV first, then decide whether to convert onward to QBO.

How EasyStatementSheet fits in

EasyStatementSheet converts bank statements into QBO files with the correct INTU.BID filled in automatically. That removes the failure mode that blocks most first-time imports. If you are moving from a PDF or scanned statement into QuickBooks, the bank statement conversion path produces a QBO ready for Web Connect. If an import still fails after that, the troubleshooting guide covers the remaining edge cases.

For the technical details of the QBO format itself, including the OFX tags and Intuit extensions, see the QBO format reference.

Turn any PDF statement into a clean sheet

Skip the typos and the hours of copying. Our converter handles any bank statement format and outputs Excel, CSV, or QBO for QuickBooks. No file retention, free to try.

Convert your statement
ESS Editor
ESS Editor

Samandya writes practical guides on converting bank statements into usable financial data, including PDF-to-Excel, CSV, and QBO files for QuickBooks. His articles help individuals, businesses, and bookkeepers review transactions, compare formats, and prepare financial documents for bookkeeping and reconciliation.