QBO Format

OFX to QBO ConverterThe single tag QuickBooks Desktop is missing

QBO is OFX with one extra tag inside the SONRS block. Intuit charges banks an annual fee to include that tag — INTU.BID — declaring the institution to QuickBooks's import system. If your bank doesn't pay, you get OFX, and QuickBooks Desktop refuses to open it. Drop your OFX file here. We add the missing tag locally in your browser, save the result with a .qbo extension, and QuickBooks Desktop accepts it through the Web Connect import path like nothing happened.

Why Use Our OFX to QBO Converter Tool?

No AI call — pure text edit

The conversion happens entirely in your browser — no AI inference, no transaction data uploaded. Just the INTU.BID and INTU.USERID tags QuickBooks needs, added locally. Your statement content stays on your machine.

OFX 1.x SGML and OFX 2.x XML, both handled

Older banks ship OFX 1.x with unclosed SGML tags. Newer ones ship XML with proper closing tags. The injector detects which yours is and adds the new tag in the right syntax for each.

Bank picker for the QuickBooks import dialog

INTU.BID drives the bank label QuickBooks shows during the Web Connect import. Pick from the dropdown so it shows your actual bank, or use Generic — the destination account is yours to choose at import time.

Add one tag, change the extension

1

Export OFX from your bank

Look for an OFX or "Quicken / Money 2003" download option in your online banking. The file extension is .ofx and the content is structured XML or SGML.

2

Upload the PDF

Drop the .ofx file above. OFX 1.x SGML and OFX 2.x XML both accepted.

3

Pick the import-dialog bank label, save as QBO

Pick a bank from the dropdown (or Generic / Other) so QuickBooks shows the right label during import. Click Download. In QuickBooks Desktop: File → Utilities → Import → Web Connect Files.

Why QuickBooks rejects OFX files

QBO and OFX are technically the same format

Both are OFX-spec files. QBO just has one extra tag — INTU.BID — to declare which bank issued the file under Intuit's licensing system.

INTU.BID is gated by Intuit's annual licensing fee

Banks pay Intuit a per-institution license to be eligible to export QBO. Banks without that license can only ship OFX, leaving their QuickBooks Desktop customers stranded every reconciliation cycle.

Renaming .ofx → .qbo doesn't work

A common forum suggestion. Doesn't hold up: QuickBooks reads the file content, finds no INTU.BID, and rejects with "Unable to verify financial institution." The tag must physically be there.

Online OFX-to-QBO converters charge or upload your data

Commercial tools cost $30–80 and typically upload statements to their servers. This page is free and runs entirely in your browser.

When OFX to QBO is the right fix

Banks Without an Intuit License

Smaller banks and credit unions that don't pay Intuit's licensing fee can only export OFX. Their customers running QuickBooks Desktop hit a wall every month. This bridges it.

International Banks Shipping OFX-Only

EU, AU, and emerging-market banks frequently support OFX but skip QBO. Same INTU.BID injection works for any country's OFX file.

Old OFX Files Sitting In an Archive

Years of OFX downloads from a bank that recently switched to QBO. Convert the back-catalog so QuickBooks Desktop can finally pick them up.

Bookkeepers With Mixed Bank Files

Some clients' banks ship QBO, others ship OFX. Add the tag to the OFX side and standardize the import workflow across every client.

Backfilling Months of History

A year of OFX statements sitting in a folder. Convert each to QBO, import in sequence. QuickBooks dedupes by FITID so re-imports are safe.

When QuickBooks Online Isn't the Right Tool

QBO Online accepts OFX directly — but plenty of accountants prefer QuickBooks Desktop for control. Stay on Desktop without losing your bank's OFX export option.

Frequently Asked Questions — OFX to QBO Converter

QWill the resulting file actually import into QuickBooks Desktop?

Yes. The INTU.BID and INTU.USERID tags are placed inside the SONRS block where QuickBooks looks for them. The rest of the file — your bank's OFX content — is preserved unchanged. QuickBooks reads the result as a valid Web Connect file.

QWhy do I have to pick a bank from the dropdown?

INTU.BID drives the bank label QuickBooks shows during import — "Wells Fargo" vs "Chase" etc. The destination account in your QuickBooks file is something you pick at import time, so even a wrong dropdown choice imports the transactions correctly. The label is cosmetic.

QIs the conversion really client-side?

Yes — your file content is. The .ofx is read and edited entirely in your browser, then saved as .qbo. The only network call is a small request to deduct your conversion credit; no transaction data ever leaves your machine.

QMy OFX is from a non-US bank. Does it work?

Yes. INTU.BID is what QuickBooks Desktop checks; it doesn't care which country the underlying OFX came from. Pick Generic / Other from the dropdown if your bank isn't in our list. Transactions import the same way.

QHow does this differ from your QFX to QBO converter?

OFX has no INTU.BID tag at all — we inject one. QFX has one with Quicken's licensed value — we replace it with a QuickBooks one. Same destination format, different starting point.

QCan I use the output for QuickBooks Online?

You don't need to. QuickBooks Online accepts plain OFX directly. Use this tool only when you specifically need a QBO file (i.e., for QuickBooks Desktop or another QBO-only application).

QWill I get duplicate transactions if I run the same OFX twice?

No. Each OFX transaction has a FITID (a unique identifier from your bank). We preserve those exactly. QuickBooks Desktop uses FITID for deduplication on import — re-importing the same file is a no-op.

Other Conversion Formats

Save the .qbo, import to QuickBooks

OFX from your bank, QBO into QuickBooks Desktop. Free, instant, no signup needed to start. The fix is one tag — we add it in your browser.