What is QFX Format?

When Intuit co-developed the OFX standard in 1997 alongside Microsoft and CheckFree, the goal was an open format that any financial software could use. But Intuit quickly recognized a commercial opportunity: by adding a proprietary header requirement, they could build a licensing program around bank connectivity.

The result was Quicken Web Connect, branded as QFX. Banks that want to offer one-click transaction downloads into Quicken must license Intuit's Web Connect service and register for an INTU.BID code. This creates a revenue stream for Intuit and a controlled ecosystem where every participating bank is vetted and mapped to a unique identifier.

From a technical standpoint, Intuit's justification was threefold. First, the INTU.BID enables automatic account matching — Quicken can map the downloaded file to the correct account without user intervention. Second, the controlled registration process ensures that FITIDs (Financial Institution Transaction IDs) are properly generated, preventing the duplicate transaction imports that plagued the older QIF format. Third, the licensing program creates a quality control layer where Intuit can test and certify bank integrations.

The practical consequence for users is significant: if your bank provides an OFX download but you use Quicken, the file will be rejected. This remains the single most common source of frustration in the Quicken user community and drives substantial demand for OFX-to-QFX conversion tools.

A QFX file is structurally identical to an OFX 1.x (SGML) file. It begins with the standard OFXHEADER block, followed by SGML markup containing sign-on information, bank account details, and transaction records. The only structural addition is the INTU.BID tag within the <FI> section of the sign-on response.

The <INTU.BID> tag is the only element that distinguishes a QFX file from a standard OFX file. It appears inside the <FI> (Financial Institution) block alongside the <ORG> and <FID> tags. The INTU.BID value is typically the same as the FID, but not always — some institutions have different identifiers in the Intuit directory.

When Quicken opens a QFX file, it reads the INTU.BID to look up the institution in its internal database. This determines which account the transactions will be imported into, what transaction categorization rules to apply, and whether the file should be processed as a bank statement, credit card statement, or investment report.

QFX was designed exclusively for Quicken, and Quicken is the only software that requires QFX specifically. All other financial software treats QFX files as standard OFX, silently ignoring the INTU.BID header. This creates an asymmetric compatibility landscape.

QFX files are plain text with SGML structure — you can open them in any text editor to inspect the transaction data. The content is nearly identical to an OFX file, with the addition of the INTU.BID header in the FI section.

To analyze QFX data in a spreadsheet, convert it to a tabular format. FinanceConvert's QFX to CSV converter extracts transactions into clean columns. For Excel with native date and currency cells, use the QFX to Excel converter.

To strip the Intuit-specific headers and produce a standard OFX file compatible with GnuCash, Moneydance, or other open-source finance tools, use the QFX to OFX converter. For printable records, the QFX to PDF converter generates formatted transaction statements.

"Invalid file format" in Quicken. This is the most frequent QFX-related error. It occurs when users download a standard OFX file from their bank and try to open it in Quicken. Because the file lacks the INTU.BID header, Quicken refuses it. The fix is to convert OFX to QFX using a tool that adds the correct INTU.BID for your institution.

Wrong INTU.BID code. Each financial institution has a specific INTU.BID in Intuit's directory. Using the wrong code can cause Quicken to map transactions to the wrong account, apply incorrect categorization rules, or reject the file outright. If Quicken imports the file but associates it with the wrong account, the INTU.BID is likely incorrect.

Bank compatibility changes. Banks periodically update their online banking platforms, which can change the format of their OFX/QFX downloads. After a bank platform upgrade, previously working QFX imports may fail. Common causes include changed FID values, updated ORG names, or modifications to the SGML structure.

FITID uniqueness violations. The OFX specification requires that each FITID be unique within a statement period. Some banks generate non-unique FITIDs (e.g., using sequential numbers that reset monthly). This causes Quicken to skip legitimate transactions it believes are duplicates. Regenerating FITIDs during conversion can resolve this.

Credit card statements. QFX files for credit cards use CREDITCARDMSGSRSV1 instead of BANKMSGSRSV1. Some converters only handle bank statements, producing files that Quicken cannot import for credit card accounts. Ensure your converter supports the correct message set for your account type.