QFX File Format: What Is a QFX File, QFX vs OFX, and How to Open One

What is a QFX file?

A QFX file is a bank statement download formatted for Quicken. Intuit calls the feature Web Connect: you sign in to your bank, click a download link, and get a .qfx file you import into Quicken through the File menu. Underneath, the file is an OFX document. Open it in any text editor and you will see the same signon block, account block and transaction list that a plain OFX file carries.

What makes it a QFX rather than an OFX is a small set of Intuit specific elements added to the header, chiefly INTU.BID, a bank identifier, and INTU.USERID. Quicken reads those before it reads anything else. Financial institutions pay Intuit a licensing fee to participate, and in some cases pass quality checks, and only then will Quicken accept files identified as coming from them. The structure is open. The permission to import is not.

QFX vs OFX: what actually differs

This is the question that sends most people to this page, and the honest answer is that the difference is small in bytes and total in effect. A QFX file is an OFX file plus identifiers. Strip those identifiers out and Quicken stops accepting it.

The practical takeaway: if the destination is Quicken, you need QFX specifically. If the destination is almost anything else, plain OFX is the safer choice because it carries no identifiers that a parser might trip over.

What Quicken can and cannot import

Quicken's own import documentation is unusually blunt about this, and it contradicts what most people assume. Quicken for Windows can import the formats below, and it explicitly states that it cannot import Excel, QuickBooks, PDF or OFX files.

That single row about OFX explains a large share of the confusion around this format. People convert a statement to OFX because OFX is the format they have heard of, then find Quicken will not touch it, then assume the file is broken. It usually is not. It is the wrong flavor.

What does a QFX file look like?

Most QFX files in circulation use the OFX 1.x SGML syntax, which means colon delimited header lines, a blank line, then tags whose closing counterparts are optional. The Intuit elements sit in the header block near the top. A trimmed example looks like this:

OFXHEADER:100
DATA:OFXSGML
VERSION:102
SECURITY:NONE
ENCODING:USASCII
CHARSET:1252
COMPRESSION:NONE
OLDFILEUID:NONE
NEWFILEUID:NONE

<OFX>
  <SIGNONMSGSRSV1>
    <SONRS>
      <STATUS><CODE>0<SEVERITY>INFO</STATUS>
      <DTSERVER>20260731120000</DTSERVER>
      <LANGUAGE>ENG</LANGUAGE>
      <INTU.BID>1234</INTU.BID>
    </SONRS>
  </SIGNONMSGSRSV1>
  <BANKMSGSRSV1><STMTTRNRS><STMTRS>
    <CURDEF>USD</CURDEF>
    <BANKACCTFROM>
      <BANKID>121000248</BANKID>
      <ACCTID>000123456789</ACCTID>
      <ACCTTYPE>CHECKING</ACCTTYPE>
    </BANKACCTFROM>
    <BANKTRANLIST>
      <STMTTRN>
        <TRNTYPE>DEBIT</TRNTYPE>
        <DTPOSTED>20260715</DTPOSTED>
        <TRNAMT>-42.18</TRNAMT>
        <FITID>20260715000142180001</FITID>
        <NAME>SHELL OIL 5741</NAME>
      </STMTTRN>
    </BANKTRANLIST>
    <LEDGERBAL>
      <BALAMT>3184.92</BALAMT>
      <DTASOF>20260731</DTASOF>
    </LEDGERBAL>
  </STMTRS></STMTTRNRS></BANKMSGSRSV1>
</OFX>

The INTU.BID line is the whole difference. Remove it and you have an OFX file that Quicken will refuse. The BANKID value is the bank's routing number, ACCTID is the account number, and everything from BANKTRANLIST down is ordinary OFX that any parser can read.

Required fields inside a QFX transaction

Because the body is OFX, the transaction rules are the OFX rules. Four fields carry the weight, and a fifth block outside the transaction list causes more failures than any of them.

FITID deserves a note of its own, because it is the reason QFX beats CSV for statement history. Quicken uses it to recognize a transaction it has already seen. Import the same QFX twice and the second pass is matched and ignored. Import the same CSV twice and you get every row again.

How to import a QFX file into Quicken

Save the file somewhere you can find it, then in Quicken for Windows go to File, then File Import, then Web Connect File, and select the .qfx. Quicken will ask whether the transactions belong to an existing account or a new one. Choose the existing account if you have one, otherwise the register you already reconciled will end up split across two accounts.

On the bank's website the download link is usually labeled Download to Quicken, or marked with a Quicken logo, and often sits behind a menu named something like Download Transactions or Statements and Activity. Pick the Quicken option rather than the generic one. The generic option normally produces CSV, which imports without transaction IDs and without duplicate matching.

Why a QFX file will not import into Quicken

Work through these in order. The first two account for most cases.

• It is actually an OFX file. Open it in a text editor and search for INTU.BID. If it is missing, Quicken will not take the file, and renaming it will not change that.
• The institution does not participate. Quicken only accepts files identified as coming from a bank in the Intuit program. If yours is not, no download from them will import.
• The date range is empty. A file covering a period with no activity still imports, it just appears to do nothing.
• The account was matched to the wrong register. Check whether the transactions landed in a new account Quicken created during the import.
• LEDGERBAL is missing. Files assembled by third party tools sometimes omit the closing balance, which is a known cause of parse errors in the OL-220 to OL-226 range. Our guide to Quicken error OL-221 covers that family in detail.

If the file imports but the connection itself keeps breaking, that is a different problem with a different fix. See Quicken not downloading transactions for the connection side, and Quicken connection errors for the numbered codes.

QFX vs QIF vs QBO: which one does your software want?

All three descend from the same lineage and none of them are interchangeable. Picking the wrong one is the single most common reason an import fails on the first try.

QFX and QBO are close relatives, which is why people try to swap them, and why swapping them fails. Both are OFX with Intuit identifiers, but the identifiers differ and each product validates its own. If your destination is QuickBooks rather than Quicken, you want a QBO file, not a QFX.

How do I open a QFX file without Quicken?

Any text editor will open it. Notepad on Windows, TextEdit on Mac, or anything a developer would reach for. The file is plain text, so you can read the transactions directly, which is genuinely useful when you are trying to work out why an import failed.

Reading it and using it are different problems. If you need the transactions as rows you can sort, total and hand to someone else, converting is the practical answer. A QFX to Excel conversion gives you a worksheet, and a QFX to CSV conversion gives you something almost any accounting package will read. Renaming the file to .csv does not work, because the contents are tagged, not delimited.

How to create a QFX file when your bank will not give you one

This is the situation that sends most people looking for the format in the first place. The account is closed, or the download only reaches back 90 days, or the bank never joined the Intuit program, or you are rebuilding a client's books from a folder of PDFs. In every one of those cases the statement exists and the QFX does not.

Converting the statement solves it. Upload the PDF, check the extracted transactions against the printed page, and export QFX. The output carries the header elements Quicken checks, a unique FITID per row, dates as YYYYMMDD and the closing balance block, which are precisely the parts a hand assembled file gets wrong. If your destination is not Quicken, the same statement exports as plain OFX instead.

For the full technical reference on the format underneath all of this, see the OFX file format specification.