QuickBooks Error OL-206: Bank Feed Download Rejected by Your Bank

Error OL-206 appears when your bank's server rejects a QuickBooks Desktop feed download. Learn what breaks the connection and what restores it.

When QuickBooks Desktop reaches for your bank feed and the bank's server refuses the session, the download stops and the program reports OL-206. Nothing imports that day. Our engineers meet this code often, and it almost never points at damage inside the company file. It points at the connection, and connections can be rebuilt.

What does the message say?

OL-206 shows up in the Bank Feeds window, right after a connection update fails. The wording varies a little between releases, but the notice reads close to this:

QuickBooks was unable to complete your online banking request. Your financial institution's server rejected the connection. (OL-206)

Some builds shorten it to a line about the last online connection not completing. The sentence matters less than the number at the end. That number identifies the failure, so record it exactly as shown.

The meaning of the code

Bank feed errors come in families, and the letters tell you the family. Codes in the OL-1xx and OL-2xx range describe the conversation between your machine and your bank's server. OL-206 sits in that group. The session opened, the server saw the request, and it declined to hand over statement data.

That refusal is a connection problem, not corruption. Your existing downloaded transactions are not at risk.

What triggers OL-206?

In rough order of how often our engineers meet each cause:

• The bank, or the processor that runs its feeds, has taken the service down for maintenance. The server refuses every session until the window closes, then recovers on its own.
• The stored connection profile in QuickBooks has gone stale. The saved server details no longer match where the bank routes its feeds now, often after a merger or a rebrand.
• The bank moved its desktop feed channel, and the old link in your file points at a retired endpoint.
• Your release of QuickBooks is out of date, or past the point where Intuit still carries its connected services. It then calls the server in a way the bank no longer accepts.
• Something local is in the way: a firewall, a security suite, or a Windows encryption setting that blocks the secure session.

How do you fix it?

Work through the scenarios in order, and stop as soon as a download succeeds.

The server refused the session during maintenance

1. Close the Bank Feeds window and wait a few hours before trying again.
2. Sign in to the bank's own website in a browser. If the site shows a maintenance notice, the feed will fail no matter what QuickBooks does.
3. Open the Banking menu, choose Bank Feeds, and run the download again. Most OL-206 stops our engineers see end at this point.

The stored connection has gone stale

1. Back up first. Use File, then Back Up, and keep the copy somewhere safe. Never change online services without a fresh backup.
2. Open the Chart of Accounts, edit the affected account, and find its Bank Feed settings. Older releases label this tab Online Banking.
3. Deactivate online services for the account, then save and close.
4. Run the connection setup again, match the bank to the existing account, and complete one download. QuickBooks rebuilds the link against the bank's current server details.

The bank changed its feed channel

1. Ask the bank whether desktop feeds are still offered on your account, and whether a merger or rebrand requires re-enrolment.
2. When you set the account up again, search the bank's current name rather than reusing the old saved entry. The fresh listing points at the live server.
3. If the bank has retired its direct connection entirely, ask which channel it supports now, then rebuild the account on that channel.

Your QuickBooks release is behind or retired

1. Press F2 with a company file open. The Product Information window shows the version and release at the top.
2. If the version is still supported, choose Help, then Update QuickBooks Desktop, install everything offered, and restart.
3. If the version sits past its discontinuation point, its feeds are switched off at the vendor's end. Upgrading the file to a release still in service is the only lasting fix.

Something local is blocking the session

1. Open Internet Options in Windows, choose the Advanced tab, tick Use TLS 1.2, and restart the machine.
2. Let QuickBooks through your firewall and security suite, or pause the suite briefly as a test.
3. Try the download on another network, such as a phone hotspot. If it succeeds there, the block lives in your network, not in the file.

Keeping the connection healthy

Install QuickBooks updates when they arrive rather than months later, since feed fixes often ship inside maintenance releases. Plan an upgrade before your version reaches the end of its connected services, because feeds stop working at that point no matter how healthy the file is.

Keep a fresh backup before touching online settings. Download statements on a steady rhythm instead of letting the link sit idle for months. When your bank announces a merger or new sign-in rules, rebuild the connection promptly rather than waiting for the first failure. A few minutes of housekeeping prevents most repeats of OL-206.