neatstatement

What is a QFX file?

Sharp angular folds of white paper forming nested chevron shapes

You clicked “download for Quicken” on your bank’s website and got a file ending in .qfx. Double clicking it either opens Quicken or opens nothing at all.

A QFX file is not a document. It is a data feed in a file, meant for software to swallow rather than for you to read.

What is inside one

QFX stands for Quicken Financial Exchange. Underneath it is OFX, the Open Financial Exchange specification that banks and finance software have used since 1997, with a few extra tags that identify the file to Quicken.

Rename the file to .txt, open it, and you get something like this:

<STMTTRN>
  <TRNTYPE>DEBIT
  <DTPOSTED>20260314120000
  <TRNAMT>-62.41
  <FITID>2026031400418822
  <NAME>HANOVER GROCERY 4471
</STMTTRN>

One of those blocks per transaction, wrapped in a header that names the bank, the account and the period.

Two things stand out to anyone who has seen XML. There are no closing tags on the value lines, and the file is not XML at all: OFX 1.x is SGML, an older standard where a tag closes implicitly at the next tag. Software written to parse XML chokes on it, which is a common source of “the file is corrupt” errors that have nothing to do with the file.

The other thing is FITID. It is the bank’s unique identifier for that transaction, and it is the reason importing the same file twice does not usually create duplicates: the software recognises the ID and skips it.

The tags that become spreadsheet columns

OFX tags mapped to spreadsheet columns The DTPOSTED tag becomes the date column, NAME and MEMO become the description, TRNAMT becomes the amount, TRNTYPE becomes the type, and FITID has no column because it is an internal identifier. IN THE QFX FILE IN A SPREADSHEET DTPOSTED20260314120000 Date14/03/2026 NAMEHANOVER GROCERY 4471 DescriptionHanover Grocery TRNAMT-62.41 Amount−62.41 TRNTYPEDEBIT TypeDebit FITID2026031400418822 no column: it is the bank's own id
A QFX carries more than a CSV: the type and the transaction id survive, which is what stops duplicate imports.

That extra structure is the whole argument for the format. A CSV of the same transactions loses the type and the identifier, so the receiving software has to guess at both, and guessing at identity is how you end up with the same month imported twice.

QFX, QBO and OFX

Three extensions, one format underneath, and they are not interchangeable.

Extension Made for What makes it different Will it import elsewhere?
.ofx The open spec, any compliant software Nothing added Widely accepted, rejected by Quicken and QuickBooks
.qfx Quicken Carries INTU.BID, an Intuit bank id Quicken only, in practice
.qbo QuickBooks Desktop Carries INTU.BID and a matching FI id QuickBooks only

Renaming a .ofx to .qfx does not work. Quicken looks for the Intuit branding tags, and an unbranded file is refused with a message about the financial institution not being supported.

That branding is a licence. Banks pay Intuit to issue QFX and QBO files, which is why some banks put “Quicken” and “QuickBooks” downloads behind a fee or a business account, while the plain CSV is free. It also explains the more useful piece of advice on this page: if your bank charges for QFX, you do not have to pay it.

How to open a QFX file

To import it, which is what it is for: in Quicken, File then Import then Bank or Brokerage File, and pick the account. Quicken matches on FITID and will tell you how many transactions it accepted and how many it skipped as already present.

To read it, rename the extension to .txt and open it in any text editor. Everything is legible, just verbose.

To get it into a spreadsheet, convert it. Excel will not open a QFX usefully: it is not delimited, so the import wizard produces one long column of tags.

To use it in QuickBooks, which will not take a QFX, convert it to a QBO. The transactions are identical and only the branding tag has to change.

When you have a PDF and need a QFX

This is the common case, and it is worth saying plainly: if your bank will not give you a QFX, or charges for it, you can make one from the PDF statement.

Our converter reads a PDF statement in your browser and writes .qbo for QuickBooks Desktop or .qfx for Quicken, with the transaction type inferred from the sign and a stable identifier generated per row so a second import does not duplicate. Nothing is uploaded, which for a year of transactions is the part that matters.

Two things to get right when you do it:

Set the account type. Checking, savings and credit card produce different account blocks in the file, and importing a credit card statement as a checking account inverts every sign.

Import into the right account. Both QFX and QBO carry a financial institution id, and Quicken and QuickBooks check it against the account you are importing into. If you get a message about the wrong financial institution, that is what happened. Set the account up fresh and let the software bind it on the first import.

Common questions

What is a QFX file?

A Quicken Financial Exchange file: a plain text file, produced by your bank, listing transactions in the OFX format with Quicken-specific tags added. It exists to be imported into Quicken rather than read.

How do I open a QFX file?

In Quicken, use File then Import. To read it rather than import it, rename the extension to .txt and open it in any text editor, or convert it to CSV or Excel and open it in a spreadsheet.

What is the difference between QFX and OFX?

OFX is the open specification. QFX is the same format with extra tags identifying the bank to Quicken. Quicken accepts QFX and generally rejects a plain OFX file, which is why renaming one to the other does not work.

Can I convert a QFX file to Excel?

Yes. A QFX file is text, so the transactions can be pulled out and written to a spreadsheet. If you are starting from a PDF statement rather than a QFX, you can skip a step and convert the PDF straight to Excel.