OFX to QBO Converter and QBO Fixer

Why QuickBooks rejects files that look fine

An OFX file can open perfectly in a text editor and still fail in QuickBooks. The usual causes are structural: the file is OFX 2.x XML while QuickBooks Web Connect expects OFX 1.02, dates are written as short 8-digit values instead of full timestamps, or transaction IDs (FITIDs) are missing or repeated — and a repeated FITID makes QuickBooks silently skip a real transaction as if it were a duplicate. This fixer rebuilds the file as a clean OFX 1.02 QBO and reports every change it made, with counts, before you download.

The INTU.BID promise

Some fixers stamp a made-up bank ID into your file. That can point QuickBooks at the wrong bank, so this tool never does it: it preserves your file's INTU.BID exactly as it is, and never guesses a bank's ID. If your file has no INTU.BID at all, the field is left unset — and if QuickBooks tells you your bank is not supported, you can type one in above, copied from a working QBO file downloaded from your own bank.

What this tool handles

• Header normalization — OFX 2.x XML and other versions are rebuilt as OFX 1.02, the Web Connect format.
• Date repair — short DTPOSTED values become full 14-digit timestamps.
• FITID repair — missing IDs are generated and repeated IDs are regenerated, deterministically, so a re-import cannot duplicate your books.
• A before-and-after report — the problems found in your original file and the fixes applied, side by side.

Not sure what is wrong with your file? The QBO File Checker reports its problems without changing anything, and the QBO import-error decoder explains the exact message QuickBooks showed you. To go the other way — from a QBO into a spreadsheet — use the QBO to CSV converter.