UK
Open a QFX file and a QBO file in a text editor and they look almost the same. So it feels like QuickBooks *should* just accept your QFX. It doesn't — and renaming the extension to .qbo doesn't fix it either.
The reason is small but strict, and once you see it the clean fix is obvious.
QFX and QBO are twins with different name tags
Both formats are built on OFX, the banking data standard. The difference is who they're made for.
- QFX (.qfx) is Quicken's Web Connect format. Inside, it's tagged for Quicken — including an Intuit branding ID that says "this file is for Quicken."
- QBO (.qbo) is QuickBooks' Web Connect format. Same OFX skeleton, but tagged for QuickBooks with its own INTU.BID and app identifiers.
QuickBooks checks those tags. When it sees a file targeted at Quicken, it refuses it — even though the actual transaction data would import perfectly. So "converting" QFX to QBO is really about rewriting those app tags correctly, not the transactions.
Why renaming or quick converters go wrong
- Wrong branding tags. Just changing .qfx to .qbo leaves the Quicken app tags in place, so QuickBooks still rejects it.
- Bank ID mismatch. QuickBooks matches the INTU.BID to a bank it recognises. A QFX carries Quicken's expectation of that value, which QuickBooks may not accept — hello, OL-301.
- Broken structure from sloppy edits. Hand-editing the tags often corrupts the OFX headers, and then neither app will open it.
- No reconciliation. Nothing checks that the totals still match your statement after the edit.
The clean way: generate a fresh QBO from your statement
If you have the original bank statement PDF, skip the QFX surgery. Build the QBO from the statement so it's tagged for QuickBooks from the start and balanced before you download.
- Open the bank statement to QBO converter and upload your statement PDF.
- Let it read every transaction and check the total against the statement's running balance.
- Select QBO as the output.
- Import the file into QuickBooks via File → Utilities → Import → Web Connect Files.
You get a file that's the right shape for QuickBooks, with dates, amounts and transaction IDs that reconcile — no tag-editing, no guesswork.
If QuickBooks still complains
QuickBooks can throw an OL-301 or OL-249 even on a valid QBO, because it's fussy about which banks it recognises for direct import. That's a QuickBooks limitation, not a data problem. When it happens, import the same statement as OFX or CSV — both come from the same converter and sidestep the bank-ID check.
Frequently asked questions
Can't I just rename QFX to QBO?keyboard_arrow_down
No. The transactions might be fine, but the file is still tagged for Quicken inside. QuickBooks reads those tags and rejects it. You need the QBO built with QuickBooks' own identifiers.
QFX and QBO look identical — why does QuickBooks care?keyboard_arrow_down
Both are OFX, so the transaction sections match. QuickBooks checks the app and bank identifiers in the header to decide whether to trust the file, and a QFX carries Quicken's — not QuickBooks'.
What's the safest format if QBO keeps failing?keyboard_arrow_down
OFX or CSV. OFX is the standard QBO is based on, and CSV maps to a simple column import — both are reliable when a specific bank won't import as QBO.
I don't have the original statement, only the QFX. Now what?keyboard_arrow_down
Re-download the statement PDF for the same dates from your online banking and convert that. A statement has everything a clean QBO needs; a QFX built for Quicken fights QuickBooks at every step.
Try it on your own statement
Clean Excel/CSV, with every transaction checked to balance.