Why QuickBooks rejects bank .QBO / .QFX imports with Error OL-222 (and how to convert CSV, QFX, or IIF in the browser)
If you have ever helped a small business owner or bookkeeper import bank statements into QuickBooks, you have probably run into a surprisingly stubborn wall: QuickBooks Online and Desktop frequently reject .QBO or .QFX files with Error OL-222 or "Unable to verify the Financial Institution" . Native 3-column CSV imports strip out Check Numbers ( CHECKNUM ) , break on multi-line bank summary…
QuickBooks frequently rejects .QBO or .QFX files with Error OL-222 when attempting to import bank statements. This error occurs due to three syntax issues: unescaped ampersands in merchant names, missing INTU.BID, and field length truncation. To fix these issues, replace unescaped ampersands with escaped ones, include the INTU.BID tag, and ensure 32-character vendor names and 255-character descriptions remain intact.
When using QuickBooks' built-in 3-column CSV upload, check numbers are dropped from the transaction. To preserve them, convert the CSV into a structured .QBO STMTTRN block, placing check serials in the CHECKNUM field and maintaining full descriptions in the MEMO field. If importing credit card charges as positive numbers, flip the sign polarity before importing to prevent QuickBooks from importing purchases as payments.
For QuickBooks Desktop editions (2018-2023), Web Connect (.QBO) imports are blocked, forcing bookkeepers to use legacy .IIF files or pay for converter tools. To bypass QuickBooks' 3-year sunset policy on .QBO Web Connect imports, use an .IIF file instead. However, .IIF files require strict double-entry balance on every transaction, so using a browser-based CSV & .QBO to .IIF converter can ensure proper formatting and prevent balance errors.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.