QuickBooks error OL-222, OL-301 and the other OL codes
Bank Feeds fails with a code like OL-301 or OL-222 and the message tells you nothing about which of two completely different problems you have. One is QuickBooks failing to talk to your bank. The other is QuickBooks failing to read a file. The fixes have nothing in common, so the first job is working out which one you are looking at.
🔒 If it turns out to be the file, you do not have to wait on your bank: build your own QBO from a CSV or PDF statement — free, runs in your browser, nothing uploaded.
Which family is your code in?
Intuit has one troubleshooting article covering the OL and OLSU codes. These are the codes it names:
"OLSU-1011, OLSU-1013, OLSU-1014, or OLSU-1016" … "OL-202, OL-203, OL-205, OL-206 or OL-209" … "OL-221, OL-231, OL-232, or OL-249" … "OL-301, OL-332, OL-334, OL-392, or OL-393"
— Fix OL and OLSU Bank Feeds errors in QuickBooks Desktop, QuickBooks Support
Every one of those is a connection problem — QuickBooks, your bank's server and your company file failing to complete a conversation. If your code is in that list, skip to the next section.
OL-222 is not in that list, and that is the useful part. It is absent because it is not a connection error at all: the threads where people hit it are about importing a .QBO file they already downloaded. Nothing in the connection checklist will fix it, which is why people go round in circles deactivating accounts that were never the problem.
If it is a connection code (OL-301, OL-332, OL-393, OL-202, OLSU-1011…)
Intuit's article gives its steps in a deliberate order, and the order is worth keeping:
- Download Bank Feed transactions in a test company file. This tells you whether the bank's servers are the problem or your company file is.
- Check whether the file from your bank works with QuickBooks — download transactions straight from the bank's website in
.qboformat and import that. - Turn off online banking on inactive bank accounts, then reestablish the connection on the affected account.
- Create a copy of the account, then merge it with the old one, which flushes out company file corruption.
- Turn off, then set up online banking for each account to isolate the one connection that is broken.
Step 2 is the fork in the road. If a .qbo downloaded by hand from the bank's website imports cleanly, then the file format is fine and your problem is purely the automated connection — stop editing files and work on the connection. If that manual file also fails, you are no longer dealing with a connection error at all, whatever the code said.
If it is OL-222: the file could not be parsed
OL-222 shows up when QuickBooks cannot make sense of the OFX inside a Web Connect file. In the clearest Intuit community thread on it, the file was a .qbo downloaded from Synchrony Bank, which only offered manual downloads, and it failed on import into QuickBooks Pro Desktop.
Two causes come out of that thread, and both are the file's fault rather than yours:
- A field that is too long once encoded. QuickBooks checks a field against its length limit before it decodes the escaped characters. So a file containing
éfor an "é" — perfectly legal OFX — gets measured as six characters where one was intended, blows the limit, and is rejected. - Structurally invalid OFX. Running the same file through an OFX analyzer produced "XCSTMTTRN element not allowed at this point in BANKTRANLIST element" — the bank had simply written the statement wrong.
Practical options, in the order worth trying:
- Open the
.qboin a text editor and look at the payee lines. Shorten or strip the escaped characters (é,&and friends) in the<NAME>and<MEMO>fields. It is crude, and it works. - Update the financial institutions directory (the FIDIR / FIDER file), which the same thread recommends.
- Stop using the bank's file. If their QBO is malformed you are waiting on them, and that can take months. Download a CSV export instead and build the QBO yourself, which puts the file under your control.
🔒 Convert a CSV or PDF statement to QBO — free, in your browser, nothing uploaded.
Converters cause OL-222 too — including ours, until we fixed it
This is worth saying plainly, because it is the same bug on the other side of the fence. The OFX <NAME> field holds 32 characters. An ampersand has to be written as &, which is 5 characters instead of 1. So if a converter cuts the payee to 32 characters and then escapes it, an ampersand pushes the finished field past the limit — and QuickBooks, measuring the encoded text, refuses the file.
Ampersands in payee names are not an edge case: AT&T, H&M, SMITH & SONS, BARNES & NOBLE. We found this in our own converter on 30 October 2026 while researching this page: SMITH & JONES & CO LTD PAYMENT R is 32 characters that ship as 40. It now escapes first and cuts afterwards, and never mid-escape, because a half-written &am is invalid on its own and breaks the parse just as thoroughly.
So if you converted a statement yourself and got OL-222 on a file whose payees contain ampersands or accents, you have found your tool's bug rather than your bank's.
Is it Bank Feeds you actually need?
If you are chasing connection codes because Bank Feeds stopped working altogether, check first whether the feed is coming back at all — Intuit has been retiring older Desktop versions' bank feeds, and no amount of troubleshooting fixes a service that has been switched off. See QuickBooks Desktop bank feeds discontinued.
And if a file import is rejected with a message rather than an OL code, the other causes are covered in Web Connect import errors and QuickBooks cannot verify the financial institution, which is the FID and INTU.BID one.
Build a QBO from your statement — free
Or see it work on a sample statement — no file of your own needed.
Sources
- Fix OL and OLSU Bank Feeds errors in QuickBooks Desktop — QuickBooks Support, source for the OL and OLSU code list and the five troubleshooting steps in order.
- OL-222 error — Intuit community thread, source for the Synchrony Bank
.qboimport, the encoded-length cause and the OFX analyzer'sBANKTRANLISTfinding.