OL-222 QuickBooks Desktop Error: Fix the QBO Import

OL-222 in QuickBooks Desktop means the .qbo file you are importing contains something QuickBooks cannot parse. Most often it is a character the Web Connect format does not allow, such as an ampersand, an accented letter or a curly apostrophe in a payee name. Remove or replace that character, save the file as plain text, and import it again. If the file came from a hand-built spreadsheet or a converter that writes broken files, rebuilding it is faster than repairing it.

The message itself is no help. It reads like a connection failure, and a lot of the advice written about it sends people off to reinstall QuickBooks or rebuild the company file. Neither touches the actual problem, which sits inside a text file you can open in Notepad. The fixes below are ordered by how often they clear the error on a US Desktop install.

What OL-222 is telling you on a QBO import

A .qbo file is Intuit's version of OFX, a plain text format with tags such as NAME, MEMO and TRNAMT around each transaction. When QuickBooks Desktop reads a Web Connect file and hits something that does not fit the format, it stops and reports OL-222. Nothing is posted, so a failed import does not leave half a statement in your register.

That also tells you what is not the cause. OL-222 on a file import is not about your bank login, your internet connection or your company file. Those produce different codes. The fastest route is to look at the file.

How do I fix error OL-222 in QuickBooks?

Make a copy of the .qbo file first, then work through these in order. The first one resolves the large majority of cases reported in the QuickBooks Community.

1. Remove the characters the format rejects

Right-click the .qbo file, choose Open with, and pick Notepad on Windows or TextEdit on a Mac. Use Find to search for the ampersand. Look only at lines that start with NAME or MEMO, and replace each ampersand with the word "and". Then scan the same lines for accented letters, curly apostrophes and long dashes, which usually come from payee names pasted out of a PDF or an email. Replace them with plain letters and straight punctuation.

Save the file as plain text and keep the .qbo extension. On a Mac, TextEdit has to be in plain text mode (Format, then Make Plain Text) or it will save rich text that QuickBooks cannot read at all. Then import again with File, Utilities, Import, Web Connect Files.

2. Switch Bank Feeds to Classic Mode and retry

Intuit's own support replies suggest this when a clean file still fails. Go to Banking, then Bank Feeds, then Change Bank Feeds Mode, choose Classic Mode (Register Mode), and import the file again. You can switch back to Express Mode afterward. It changes how the transactions are staged for review, not how the file is read, so treat it as a second attempt rather than a cure.

3. Update QuickBooks Desktop

Go to Help, then Update QuickBooks Desktop, download the latest release for your version and restart. Back up the company file before you do. If your Desktop version is past Intuit's support date, updating will not bring Web Connect import back, and the file needs to go in as IIF instead. The PDF to IIF route for older Desktop versions covers that case.

4. Get a clean file from the source

If the file came straight from your bank and a fresh download fails the same way, try a shorter date range, one statement period at a time. A single bad transaction description can break a whole year's download, and a month-sized file isolates it. If every range fails, the bank's export is broken and only the bank can fix it.

When to stop editing and rebuild the QBO file

Hand-editing is fine for one file with one bad payee. It stops being fine quickly. A typical business checking statement has 80 to 150 transactions, and searching each NAME and MEMO line by eye takes around 15 to 20 minutes per statement once you include the retry. On a catch-up job of twelve months, that is most of a working day spent repairing files rather than reconciling.

Files that were built in a spreadsheet, typed by hand or produced by a free script usually have more than one problem. Fix the ampersands and the import gets further, then fails on a date format or a missing header field. The most common header problem is a missing bank identifier, which QuickBooks Desktop checks before it reads a single transaction and reports as "QuickBooks is unable to verify the Financial Institution information" rather than OL-222.

If the transactions came from a PDF statement in the first place, the quicker path is to go back to the PDF. A converter that writes plain ASCII payee names, escapes reserved characters and fills in the bank identifier produces a file that imports on the first attempt. With PDFQBO you upload the statement, check the rows against the closing balance on screen and download the .qbo, and the PDF statement to QuickBooks Desktop converter covers both the Web Connect and IIF outputs. The Starter plan is $49 a month for 50 documents, which is less than the hour it replaces on most bookkeeping rates.

Some OL-222 files are not bank statements at all but old personal finance data being moved into a business file. If what you actually have is a Quicken export, converting the QIF file to QBO gets you a valid Web Connect file without any hand-editing.

Is OL-222 the same as OL-301 or QBWC1039?

No, and mixing them up leads to the wrong fix. They point at different parts of the process.

Other questions about OL-222

Does OL-222 happen on QuickBooks Desktop for Mac?

Yes. Mac users report the same code when importing .qbo files, including on QuickBooks Desktop 2023 for Mac Plus. The causes and fixes are the same. The one Mac-specific trap is TextEdit saving rich text by default, so switch it to plain text before you save the edited file.

Can I edit a QBO file in Notepad?

Yes. A .qbo file is plain text, so Notepad or TextEdit opens it safely. Work on a copy, change only the text inside NAME and MEMO lines, and leave the tags, dates, amounts and FITID values alone. Changing a FITID can cause QuickBooks to import a transaction twice.

Why does the same QBO file import in QuickBooks Online but not Desktop?

QuickBooks Online and Desktop read Web Connect files with different importers, and Desktop is stricter about the header and the character set. A file that QuickBooks Online accepts can still fail in Desktop with OL-222 or the financial institution error, which is why fixing the file for Desktop is worth doing even if Online took it.

Will a converted PDF statement avoid OL-222?

It should, if the converter writes a valid file. Check that the payee names come out as plain text, that the header includes a bank identifier, and that the file imports into a backed up company file before you convert a full year. The Web Connect file guide shows what a well-formed .qbo contains.

Where to start

Open a copy of the failing file and search for the ampersand. If replacing it clears the error, you are done. If the file fails again on something else, or you have more than a couple of statements to get through, rebuild the files from the PDF statements and spend the time on the reconciliation instead. If you are still deciding how to turn PDFs into QBO files at all, why Adobe Acrobat cannot do it is a short read before you try.