UK
Of all the "convert X to QBO" jobs, OFX is the closest to working — because QBO *is* OFX, just wearing a QuickBooks badge. That's why it's so frustrating when QuickBooks still won't take your OFX file.
Here's the one gap between the two, and how to close it cleanly.
QBO is OFX with QuickBooks' name on it
- OFX (.ofx) is the open banking-data standard. Lots of tools and banks export it, and it holds your transactions in a well-defined structure.
- QBO (.qbo) is the same OFX structure with QuickBooks-specific identifiers added — chiefly the INTU.BID that tells QuickBooks which bank the file is from, plus the Web Connect app tags.
So an OFX file has all the *data* QuickBooks wants but not the *labels* it insists on. QuickBooks won't import a plain OFX through Web Connect because it can't confirm the bank, even though the transactions inside are perfectly readable.
Why a plain OFX import fails
- No QuickBooks bank ID. Without a recognised INTU.BID, QuickBooks won't accept the file for direct import (OL-301 territory).
- Missing Web Connect tags. QBO expects specific app identifiers that a generic OFX export leaves out.
- Header quirks. OFX files come in two dialects (older SGML headers and newer XML). Get the header wrong and QuickBooks silently refuses the file.
- Nothing verifies the totals. A converter that only relabels tags won't tell you if a transaction was dropped along the way.
The dependable fix: build the QBO from your statement
Rather than relabel an OFX and hope QuickBooks accepts the bank, generate the QBO from the original bank statement PDF so it carries the right identifiers and a balance that checks out.
- Open the bank statement to QBO converter and upload your statement PDF — scanned statements included.
- Let it extract the transactions and reconcile them against the statement balance.
- Pick QBO as the export format.
- Import into QuickBooks under File → Utilities → Import → Web Connect Files.
The result is a QBO shaped for QuickBooks from the ground up, so you skip the bank-ID roulette that trips up a relabelled OFX.
When QBO still won't import
Even a valid QBO can hit an OL-301 or OL-249 because QuickBooks only trusts certain banks for direct Web Connect import — a QuickBooks limitation, not a flaw in your file. If that happens, keep the plain OFX (many accounting apps, including QuickBooks Online's bank feed, take OFX happily) or fall back to CSV. Both come from the same converter.
Frequently asked questions
Is OFX the same as QBO?keyboard_arrow_down
Almost. QBO is OFX plus QuickBooks' own bank and app identifiers. The transaction data is the same; QBO just adds the labels QuickBooks checks before it will import.
Why won't QuickBooks import my OFX file directly?keyboard_arrow_down
QuickBooks Desktop's Web Connect import wants a recognised bank ID, which a generic OFX doesn't carry. QuickBooks Online's bank-feed import is more forgiving of OFX — but for Desktop, a proper QBO is the reliable path.
Which should I use if the QBO import keeps failing?keyboard_arrow_down
Try OFX first — especially for QuickBooks Online — then CSV. Both avoid the strict bank-ID check that QBO relies on.
Can I convert OFX to QBO without the original statement?keyboard_arrow_down
You can relabel it, but it's hit-and-miss because of the bank-ID check. If you can, re-download the statement PDF and build the QBO from that instead — it's the version QuickBooks is most likely to accept.
Try it on your own statement
Clean Excel/CSV, with every transaction checked to balance.