QIF to QFX Converter: Convert QIF to QFX and OFX Files

OFX (Open Financial Exchange) is the underlying standard for exchanging bank transactions. QFX and QBO are both OFX files with an extra Intuit header: QFX is branded for Quicken, QBO is branded for QuickBooks Web Connect. QIF is the older, unrelated plain-text format that predates OFX entirely. That branding is the whole reason you cannot simply rename one to the other and expect the import to work.

No. Renaming changes the extension, not the contents. A QFX file has to contain an OFX document with the correct header block, a signon response, an account block, and each transaction wrapped in its own STMTTRN element. A QIF file contains none of that, so Quicken opens the renamed file, finds no OFX header, and rejects it. The file has to be genuinely rebuilt, which is what this converter does.

Because current Quicken will not import a QIF into that kind of account. Quicken's QIF import is limited to asset, liability, and cash accounts, and it is explicitly not available for checking, savings, credit card, or brokerage accounts. Quicken moved bank transaction download to the OFX-based formats years ago, so a QIF exported from an old copy of Quicken, from Microsoft Money, or from a bank portal has nowhere to land. Converting it to QFX puts the same transactions into the format Quicken does still accept for those accounts.

Yes. QuickBooks Online accepts QFX alongside QBO, OFX, and CSV when you upload transactions manually, and QuickBooks Desktop reads QFX too. If QuickBooks is your destination, the .qbo Web Connect file is still the cleaner choice, because it is the format QuickBooks was built around and it lands directly in the banking review queue. The converter produces both, so you do not have to choose in advance.

INTU.BID is the Intuit bank identifier carried in the header of a QFX or QBO file, and it tells the Intuit product which financial institution the file came from. An import can fail or be attributed to the wrong account when that value is missing or nonsense. The converter writes a valid header block for you, so you do not have to hand-edit a bank ID into the file, which is the usual advice on Intuit's community forums and the usual source of a second failed import.

That direction is rarely what you actually want, because the tools that read QIF are the ones being retired, not the ones being adopted. If you are moving data into a current version of Quicken, QuickBooks, or almost any modern accounting tool, you want QFX, QBO, OFX, or CSV as the destination. If you need the transactions in a spreadsheet rather than in an accounting product, convert them to CSV or Excel instead.

Yes, and that is most of the value. QIF files carry no date-format declaration, so 03/04/2026 is ambiguous and Quicken-written files often use apostrophe years like D01/15'26. The converter inspects every date in the file to determine the real format, sums split lines into a single signed amount, strips currency symbols, and then reconciles the parsed total against the source before it writes the QFX. Nothing is exported until those totals agree.