QuickBooks Error OL-205: Bank Feed Download Fails or Times Out

QuickBooks Desktop error OL-205 stops your bank feed when the bank's server returns an invalid or delayed response; here is how to restore the download.

QuickBooks Desktop throws error OL-205 when an online banking download ends without the answer QuickBooks expects. The request leaves your computer, but the bank's server either replies with something unreadable or stays silent until the connection times out. The message looks alarming, yet the cause usually sits outside the company file. This page covers the wording, the triggers, and the fixes that work.

What does the error message say?

Most releases present the code in a small dialog during or right after a download. The usual wording reads:

There was an error connecting to your financial institution. (OL-205)

Some versions shorten it to a single line, such as "QuickBooks was unable to complete your request," with OL-205 shown underneath. The sentence varies between releases and editions; the code does not. If OL-205 appears while you download transactions or refresh a bank feed, the failing step is the exchange between QuickBooks and the bank's server, not your data entry.

The code behind OL-205

The OL prefix belongs to the online banking family of codes. OL and OLSU numbers both describe the handoff between QuickBooks and an outside server: OLSU codes usually point at setup and sign-in, while plain OL codes point at the download exchange itself. The 205 portion means the response failed validation. QuickBooks sent a well-formed request and got back a malformed reply, an empty reply, or nothing before the timeout expired. A slow server and a broken server look identical at that moment, which is why the message cannot tell you which side failed.

Why does the bank feed download fail?

The download depends on a chain: your computer and its network, the routing service in the middle, and the bank's own server. Trouble anywhere along it surfaces as OL-205. The triggers we encounter most often are:

  • The bank's server is busy or down for maintenance. The commonest cause by a wide margin. Banks run maintenance windows, often overnight, and month-end traffic can push response times past the timeout QuickBooks allows.
  • The bank changed its connection. A new portal, a retired server address, or an added authentication step can make the reply unreadable.
  • Something local interferes. Security software that inspects encrypted traffic, a strict firewall, or a filtering proxy can strip or delay the response.
  • The saved feed went stale. An expired session or outdated credential inside the company file makes every attempt fail the same way.
  • An outdated QuickBooks release. Maintenance releases refresh the connection components, and an old build may no longer speak the current protocol.

One test narrows the field before you change anything: if every account at every bank fails, look locally; if only one bank fails, the trouble sits at that institution.

How do you fix OL-205?

Work through the scenarios in order. The first resolves most cases without touching the company file.

Scenario 1: the bank's server is slow or offline.

  1. Open a normal browser and log in to the bank's own website. If their online banking is slow or unavailable, the fault sits with the bank, and nothing on your computer will change it.
  2. Wait thirty to sixty minutes and retry. A busy server usually recovers on its own.
  3. If the error appears at the same hour every day, move the download clear of the bank's overnight maintenance window.

Scenario 2: the saved connection has gone stale.

  1. Back up the company file first. Deactivating a feed changes the account's online services settings, and a fresh backup makes the step trivially reversible.
  2. Open the Chart of Accounts, right-click the affected account, choose Edit, and open the Bank Feed settings.
  3. Choose Deactivate All Online Services, save, then close and reopen the file.
  4. Return to the same settings, switch the feed back on, and sign in with your bank credentials. When QuickBooks asks which account to connect, choose the existing register rather than a new account, or you will duplicate the history.

Scenario 3: local security software or the network is in the way.

  1. Pause security software that scans encrypted traffic and retry. If the download then works, add QuickBooks to that software's allow list instead of leaving protection off.
  2. Connect the computer to a different network, a phone hotspot for instance, and retry. Success on the second network points at a firewall, proxy, or filter on the first.
  3. Check the Windows clock. A wrong date breaks secure handshakes and produces exactly this class of failure.

Scenario 4: the bank has changed what it supports.

  1. Ask the bank whether it still supports direct downloads into desktop accounting software, and whether it has moved to a new connection method.
  2. If it has, deactivate and reactivate the feed as in scenario 2 so the account picks up the new details.
  3. Install the latest maintenance release for your QuickBooks version from the Help menu, then retry.

How do you stop OL-205 from returning?

  • Download often. A weekly pull meets a busy server far less often than a monthly one, and there is less to clean up when a download does fail.
  • Avoid the bank's maintenance window. Early evening on a normal business day is usually quieter than midnight or month end.
  • Keep QuickBooks current. Install maintenance releases promptly; they refresh the components that handle the exchange.
  • Keep security software configured. Add QuickBooks to the allow list before a scan blocks it.
  • Back up before changing online services settings. The deactivate-and-reactivate routine is safe, and a current backup makes it safer.

None of this needs a specialist. It is habit, and the habit covers most of the OL-205 cases our engineers see.

Keep going

Your Desktop doesn’t have to end when Intuit says so.

Start with the master survival guide, or jump straight to the fix you need.