QuickBooks Error OL-222: Bank Feed Download Fails on Invalid Response

Error OL-222 halts a QuickBooks bank feed download when the bank sends a response the software cannot read; our engineers explain the cause and the fix.

OL-222 is an online banking error in QuickBooks Desktop. It appears during a bank feed download, after the software has already reached your bank. The reply that comes back cannot be used, so the download stops and no transactions post. Our engineers rarely find anything wrong with the company file itself; the fault sits in the exchange between the software and the bank's server.

What does the OL-222 message say?

The message usually reads:

QuickBooks was not able to complete your request. Please contact your financial institution. (OL-222)

It appears when you send or receive bank feeds, often after the connection seems to have been established. Depending on the release, a second notice may follow stating that no new transactions were downloaded. The exact wording varies slightly between versions; the code at the end stays the same.

What does error OL-222 mean?

The OL-2xx family covers the conversation between the desktop software and a bank's servers. OL-222 is the member of that family you see when the server did answer, but the answer was invalid or unexpected. It may have arrived truncated, it may have been malformed, or it may have been a plain web page delivered where transaction data should have been. The software drops the download rather than import something it cannot verify. Nothing is written to your file. That is why we treat this as a connection fault rather than data damage.

What triggers OL-222?

Any of the following can produce the same code. Our engineers check them in roughly this order:

1. A temporary fault on the bank's side, including maintenance windows and unplanned server trouble.
2. A change the bank made to the format of its download, which an older release cannot parse.
3. A connection cut or altered in transit, by security software scanning encrypted traffic, a VPN, or a proxy.
4. A sign-in problem, where the bank returns a logon page or a verification prompt instead of data.
5. A desktop edition whose connected services have ended, since feeds are switched off in retired editions.

How do you fix OL-222?

Work through the scenarios in the order shown. Most cases clear at the first one.

A one-off bad response

1. Wait an hour or two and try again; transient server faults usually clear by themselves.
2. Sign in to the bank's website in a browser and confirm the account opens and statements display.
3. Read and dismiss any notice, alert, or updated terms waiting on the site. An unread notice can block downloads.
4. Retry the feed outside the bank's maintenance hours.

A stale or blocked sign-in

1. Take a backup of the company file before changing anything.
2. Open the Chart of Accounts from the Lists menu, edit the affected account, and review its bank feed settings.
3. Deactivate the connection, save, then run the bank feed setup again from the Banking menu and re-enter the credentials.
4. Complete any verification the bank sends during setup. That prompt is often what the first attempt was missing.

Something altered the reply in transit

1. Disconnect any VPN or proxy and retry on a direct connection.
2. Temporarily turn off HTTPS or SSL scanning in your security software and retry. If the feed succeeds, add an exception for QuickBooks.
3. In Windows Internet Options, on the Advanced tab, confirm that TLS 1.2 is enabled.
4. Restart the machine and try the download again.

An outdated release

1. Close the company file and install the latest release with the update tool under the Help menu.
2. Reopen the file and retry the feed.
3. If the edition is past its connected-services cutoff, online banking will not run in it. Intuit switches feeds off in retired editions, and no local setting overrides that.

How do you keep OL-222 from coming back?

Keep the desktop release and Windows both current, because banks retire old connection standards on their own schedule. Clear notices on the bank's website promptly, and set your security software to leave the traffic QuickBooks exchanges with banks alone. Note when your bank performs maintenance and schedule downloads around it. Back up before you deactivate or rebuild a feed connection. If the code persists for days across every account at one bank, the response format changed on their side, and it usually settles once their system does.