Convert an OFX File to QBO for QuickBooks

Why QuickBooks rejects a plain OFX file

You download an OFX file from your bank, try to import it into QuickBooks, and it will not take it. QuickBooks Desktop reads bank activity only from a QBO Web Connect file, and a plain .ofx is not one. The reason is a single missing piece: QuickBooks looks for an Intuit bank identifier called the INTU.BID inside the file and checks it against its internal list of Web Connect-enabled institutions. A plain OFX has no INTU.BID, so even though the transactions inside are perfectly good, the import fails with a generic error. Converting the OFX to a QBO adds the identifier QuickBooks is looking for, so the same transactions import cleanly.

OFX, QFX, and QBO are the same file in different clothes

All three formats share the same underlying structure and differ only in their headers and extension. OFX is the open, unbranded Open Financial Exchange standard. QFX is the Quicken version, with an Intuit identifier that ties it to Quicken. QBO is the QuickBooks version, an OFX carrying the Intuit-specific headers, primarily the INTU.BID, that QuickBooks requires before it accepts any transaction data. So an OFX and a QBO hold identical transactions; the QBO just wears the label QuickBooks checks for. Converting between them is about the wrapper, not the data.

Why renaming .ofx to .qbo fails

The obvious shortcut, changing the file extension from .ofx to .qbo, usually does not work. QuickBooks does not decide by extension alone; it reads inside the file for a valid INTU.BID, and a renamed OFX still has none. The result is the same generic import error, which is confusing because the transactions look fine. A real conversion adds a valid bank identifier and writes the Intuit headers the QBO format expects, then saves with the right extension. That is the difference between a file QuickBooks rejects and one it imports without complaint.

Converting and importing into QuickBooks

Upload the OFX file, and the converter re-packages the transactions into a QBO with the QuickBooks identifier in place; every transaction stays reviewable before export. In QuickBooks Desktop, import the result through the Banking menu, then Bank Feeds, then Import Web Connect Files, choose the QBO, and pick the account it belongs to. QuickBooks routes the transactions into the Bank Feeds Center, where you match and add them. If the target account has an active direct-connect feed, deactivate its online services first so the Web Connect import does not conflict with the live download.

Accuracy and privacy

Because the conversion re-wraps rather than re-derives the data, the amounts and dates that import match what your bank recorded in the OFX, and every transaction is shown for review so nothing questionable slips through. The OFX file holds real account activity, so it is processed to build the QBO and then deleted automatically, with nothing retained on a server afterward. For anyone converting files on behalf of a client, that automatic deletion keeps account data from lingering in a third-party tool once the QBO is in QuickBooks.

Frequently Asked Questions