QBO vs QFX — the difference explained
QBO is for QuickBooks; QFX is for Quicken. Both are OFX 2.x variants with different FI signatures. Here's when to use each and how to convert.
QBO and QFX are OFX-family siblings, both built on OFX 2.x. The only meaningful difference is the FI signature block — QBO has <INTU.BID>, QFX has a Quicken-specific FID. That one difference is why QuickBooks rejects a QFX with 'invalid file' and vice versa. Every real-world 'QBO vs QFX' question is really 'which app am I importing to'.
Candidates
QuickBooks Online / Desktop bank imports
- Native to QuickBooks — one-click import
- Dedupe on FITID
- Rejected by Quicken
- Needs bank ID header
Quicken Web Connect imports
- Native to Quicken
- Same FITID dedupe as QBO
- Rejected by QuickBooks
- Bank subscription may be required (Intuit branding fee)
Decision matrix
| Use case | Pick | Why |
|---|---|---|
| Import to QuickBooks Online | QBO | QuickBooks native. |
| Import to Quicken | QFX | Quicken native. |
| Bank offers only QFX and you use QuickBooks | QFX → QBO conversion | Rewrite the FI block; keep FITIDs. |
| Bank offers only OFX | OFX → QBO (or QFX) conversion | OFX needs FI block injection for either QuickBooks or Quicken. |
FAQs
No — QuickBooks reads the file signature, not the extension.
Yes — same transaction fields, same FITID scheme. Only the FI signature differs.
Both dedupe on FITID identically. The difference is only which app accepts the file.