Skip to main content
Skip to content
FREE TOOL — BROWSER-BASED

Convert QBO Files to
Standard OFX

Strip QuickBooks-specific INTU.BID headers and convert QBO files to universal OFX format. Works with Quicken, GnuCash, YNAB, and more.

100% PrivateInstantUniversal OFX

FAQ

QBO to
OFX
Questions

Can't find what you're looking for? Reach out to our support team.

Contact Support

It takes QuickBooks Web Connect (.qbo) files and converts them into standard OFX (Open Financial Exchange) format. The key difference is the removal of the INTU.BID tag and other QuickBooks-specific headers. All transaction data, dates, amounts, and account information are preserved during conversion, producing a universally compatible OFX file.

Why Convert QBO Files to Standard OFX Format

QBO (QuickBooks Web Connect) is Intuit's proprietary extension of the OFX format, designed specifically for importing financial data into QuickBooks. While QBO files work perfectly within the QuickBooks ecosystem, they contain the INTU.BID tag and other Intuit-specific headers that can cause compatibility issues when trying to import financial data into other software. If you're migrating away from QuickBooks, switching to a different accounting platform, or simply need to share financial data with someone who doesn't use QuickBooks, converting QBO to standard OFX is the solution. OFX (Open Financial Exchange) is the universal standard format supported by virtually all financial software, making it the most portable choice for your transaction data.

Common QBO File Compatibility Issues

When attempting to import a QBO file into non-QuickBooks software, users commonly encounter these problems:

  • “Unrecognized file format” — Many financial applications reject QBO files because they don't recognize the INTU.BID tag or other Intuit-specific extensions. Standard OFX parsers expect a clean OFX structure without proprietary additions.
  • “Invalid OFX header” — Some QBO files include Intuit-specific signon response fields (likeINTU.USERID) that cause strict OFX parsers to fail. The converter generates a clean signon block that conforms to the OFX specification.
  • Software lock-in — QBO files downloaded from banks through QuickBooks' Direct Connect feature are optimized for QuickBooks and may not import cleanly into Quicken, GnuCash, YNAB, or other software without first removing the QuickBooks-specific metadata.
  • Archival and portability — Standard OFX is a better choice for long-term data archival because it doesn't depend on any single vendor's proprietary extensions. Years from now, standard OFX files will still be readable by any compliant financial software.

How the QBO to OFX Converter Works

The converter transforms QBO files into standard OFX through a clean three-step process:

  1. Parse the QBO file — The converter reads your QBO file and extracts all transaction data including dates (DTPOSTED), amounts (TRNAMT), transaction types (TRNTYPE), payee names (NAME), memos (MEMO), check numbers (CHECKNUM), and financial institution transaction IDs (FITID). Account-level data like account ID (ACCTID), bank ID (BANKID), and account type (ACCTTYPE) are also extracted.
  2. Strip QuickBooks-specific metadata — The critical step is removing the INTU.BID tag, INTU.USERID, and any other Intuit-proprietary elements from the signon response block. The converter generates a fresh OFX document from scratch, so no QuickBooks-specific data leaks into the output file.
  3. Generate standard OFX output — The final OFX file is assembled with proper SGML structure following the OFX 1.x specification, including the standard OFX header block, a clean signon response (without INTU.BID), and the bank or credit card message set with all transactions properly formatted.

Understanding the QBO (Web Connect) Format

QBO is Intuit's proprietary extension of the OFX format, specifically designed for QuickBooks Web Connect imports. The file extension is .qbo, and the internal structure closely mirrors standard OFX with one critical addition: the INTU.BID(Intuit Bank ID) tag within the SONRS (Signon Response) block. This tag serves as a financial institution identifier that tells QuickBooks which bank profile to use when processing the import. Without this tag, QuickBooks would not know which account template to apply. The value is typically a numeric code (e.g., 3000) that maps to Intuit's internal database of financial institutions. Beyond INTU.BID, QBO files may also include INTU.USERID and other proprietary tags that are meaningful only to QuickBooks and should be removed for standard OFX compatibility.

Understanding the OFX Format

OFX (Open Financial Exchange) is an open standard financial data format originally developed by Microsoft, Intuit, and CheckFree in 1997. It uses SGML (Standard Generalized Markup Language) syntax — similar to XML but with some key differences like optional closing tags. An OFX file consists of a header block specifying the encoding and version, followed by the data body wrapped in <OFX> tags. Within the body, transactions are contained in <STMTTRN> blocks inside a<BANKTRANLIST> element. Each transaction includes a type (DEBIT, CREDIT, CHECK, DEP, etc.), posting date, amount, and various optional fields like payee name and memo. The format supports both bank accounts (via BANKMSGSRSV1) and credit card accounts (via CREDITCARDMSGSRSV1), each with their own message set structure. OFX is supported by hundreds of financial applications worldwide, making it the de facto standard for financial data interchange.

Financial Software That Supports OFX Import

After converting your QBO file to standard OFX, you can import it into a wide variety of financial software applications. Here are the most popular options:

  • Quicken — All versions of Quicken (Classic, Deluxe, Premier, Home & Business) support OFX import natively. Use File → Import → Bank/Brokerage to load your OFX file.
  • GnuCash — The popular free and open-source accounting software supports OFX import via File → Import → Import OFX/QFX.
  • YNAB (You Need A Budget) — YNAB supports OFX file upload for manual transaction import, complementing its direct bank connection feature.
  • Moneydance — Supports OFX import through File → Import → Downloaded Transactions. Moneydance handles both OFX 1.x (SGML) and OFX 2.x (XML).
  • Banktivity (Mac) — Previously known as iBank, Banktivity supports OFX import for Mac users looking for a QuickBooks alternative.
  • Microsoft Money — Although discontinued, Microsoft Money Sunset Edition still supports OFX import for users maintaining legacy installations.

Importing OFX Files into Quicken

After converting your QBO file to OFX format, follow these steps to import into Quicken:

  1. Open Quicken and go to FileImportBank/Brokerage File (OFX, QFX).
  2. Browse to and select your converted OFX file.
  3. Quicken will display a preview of the imported transactions — verify that dates, descriptions, and amounts are correct.
  4. Choose the Quicken account to import into, or create a new account if this is your first import.
  5. Click Import to complete the process. Transactions will appear in the selected register for review.

Tip: Quicken uses FITID values from the OFX file to prevent duplicate imports, so you can safely re-import updated files without creating duplicate entries.

Importing OFX Files into GnuCash

GnuCash is a popular free, open-source alternative to QuickBooks. To import your converted OFX file:

  1. Open GnuCash and go to FileImportImport OFX/QFX.
  2. Select your converted OFX file from the file browser.
  3. GnuCash will parse the file and display a matching dialog where you can map imported transactions to existing accounts.
  4. Review the matches and click OK to complete the import.

GnuCash's OFX importer handles both SGML-based (v1.x) and XML-based (v2.x) OFX files, so the output from this converter works without any additional configuration.

Related Free Accounting Tools

The QBO to OFX Converter is part of PrimeConnect's complete suite of free QuickBooks conversion and utility tools: