OL 203 QuickBooks Error, Fix Bank Feeds or Import QBO

OL-203 in QuickBooks Desktop means Bank Feeds could not complete the connection to your bank, and Intuit files it with the codes whose usual causes are a notice waiting on the bank's website, the bank changing how it connects to QuickBooks (Direct Connect or Web Connect), or an inactive account in your company file that still has online banking turned on. Clear the notice, turn off online banking on stale accounts, and reset the connection. If the bank has moved your account to Web Connect, or the fix takes days, a .qbo file made from the PDF statements imports today with no connection at all.

The code looks generic, and the error-code sites treat it that way, with the same ten steps they publish for every OL number. The useful part is narrower. Intuit's help article on fixing OL and OLSU Bank Feeds errors in QuickBooks Desktop lists OL-203 and OL-205 together and gives three specific causes. Two of them live in your company file and take five minutes. The third lives at the bank and can take weeks, and that one decides whether you wait or import a file.

What causes QuickBooks error OL-203?

Work down this table in order. Each row tells you where the problem sits and how to recognize it before you spend an afternoon on the wrong fix.

Cause	Where it lives	How you spot it	Fix time
An alert or notice waiting on the bank's website	The bank	Signing in on the bank site shows new terms, a security prompt or a message to acknowledge	Minutes
An inactive account in QuickBooks still set up for online banking	Your company file	Chart of Accounts shows a closed or hidden account with the online banking icon	Minutes
The bank changed its service to Web Connect or Direct Connect	The bank	The error started after a bank merger, a platform upgrade or a letter about "new ways to connect"	Days to weeks
A problem at the bank's server	The bank	The test company check below fails too, and other users of the same bank report it	Unknown
A damaged company file or an unsupported QuickBooks version	Your install	The test company works, your real file does not, or your version is past its support date	An hour, or an upgrade

How do I fix error OL-203 in QuickBooks Desktop?

Start with the two causes that are yours. They are the fastest and they account for a good share of the cases people post about.

1. Clear anything waiting on the bank's website

Sign in to the bank's own website in a browser, with the same credentials QuickBooks uses. Accept any new terms, answer any security step, and read any banner about connecting to accounting software. Banks hold Direct Connect requests until those prompts are cleared, and QuickBooks only sees the refusal, not the reason.

2. Turn off online banking on inactive accounts

Open the Chart of Accounts, show inactive accounts, and look for any closed or merged bank account that still carries the online banking icon. Edit each one, go to Bank Feed Settings, and deactivate all online services. A dead account that still tries to connect during a download can make the whole session fail. Then go back to the account that errored and refresh its connection.

3. Run the test company check

This tells you whether the problem is your file or the bank. Go to File, New Company, click Express Start or Start Setup and skip the details, then add the same bank account and try to download. If the download fails in the empty test file too, the problem is at the bank or in how it now connects, and nothing you do to your real file will change it. If the test file downloads fine, your company file is the problem. Run Verify and Rebuild Data, and check that your QuickBooks version is still supported.

4. Download a .qbo file from the bank

Intuit's own article suggests signing in to the bank website outside QuickBooks and downloading transactions as a .qbo file. If that file imports, you have your answer and your transactions. It also tells you something important: if the bank now offers only a "QuickBooks Web Connect" download and no Direct Connect enrollment, the bank has changed its service offering, and error OL-203 will come back every time Bank Feeds tries the old method. You switch the account to Web Connect and import files from now on.

When the bank moved you to Web Connect

This is the case the error-code sites miss, and it is common after a bank merger or a move to a new online banking platform. Direct Connect was the automatic download. Web Connect is a file you download and import by hand. When a bank drops Direct Connect for a type of account, Bank Feeds keeps trying the old route and returns an error until you deactivate it and set the account up again.

Web Connect has two limits that matter at month-end. First, the bank's download window is short. Wells Fargo, for example, keeps card activity for download for 90 days and checking activity for 18 months, while its statements go back further. Second, someone has to sign in to download, which is a problem when you are the bookkeeper and the client holds the login. Both limits disappear if you build the Web Connect file from the statement PDF instead of downloading it. Our PDF bank statement to QuickBooks Desktop converter reads the statement and writes the same .qbo format Desktop imports through File, Utilities, Import, Web Connect Files.

Import the statements while the connection is broken

If the test company check pointed at the bank, you have no fix to apply, only a wait. Month-end does not wait. Here is the route that gets the transactions in the same day:

Save the statement PDFs for the months you need from the bank's website, or use the ones the client already emailed.
Drop them into the converter and compare the extracted total with the opening and closing balance on each statement.
Download a .qbo file for QuickBooks Desktop versions that still support Web Connect, or an IIF file for versions that do not. The PDF to IIF converter covers the older files.
Import each file into the account that shows OL-203, oldest statement first, and match the closing balance before moving to the next.

A .qbo import does not touch Bank Feeds settings, so it will not fight with the broken connection. When the bank side is fixed, set the connection up again and let the first download start the day after the last statement you imported. If you import from files for good because the bank has gone Web Connect only, our guide on uploading bank statements to QuickBooks Desktop covers the routine.

OL-203 compared with the other OL codes

The OL numbers look alike but point at different places. Knowing which one you have saves you from applying the wrong fix.

Code	What it points at	First thing to try
OL-203	Connection not completed: bank notice, changed service, inactive account	Clear the bank notice, deactivate stale accounts
OL-301	The bank returned a general error for the request	Test company check, then wait on the bank
OL-332	The bank refused the sign-in details	Password or Direct Connect PIN
OL-222	A .qbo file QuickBooks could not read	Use a correctly built Web Connect file

What waiting costs a firm

An OL-203 that turns out to be a changed bank service is not a one-day outage. It lasts until someone notices the bank has moved the account and sets it up again, and in the meantime transactions pile up unrecorded. Typing a month of a busy checking account into the register takes an hour or more and leaves typos to find at reconciliation. Converting the statement and importing it takes a few minutes plus a balance check.

On the Starter plan here, $49 a month covers 50 statements. For a firm with several clients at a bank that just changed platforms, that is cheaper than one afternoon of data entry. If the same account also pays vendor bills, the payments your accounts payable software scheduled still need to match against something, and a register that stops three weeks ago cannot give them that. When several banks fail at once, the bank feed not working page covers closing the whole month from statements.

Frequently asked questions

What does error OL-203 mean in QuickBooks?

OL-203 means QuickBooks Desktop could not complete the Bank Feeds connection to your bank. Intuit groups it with codes caused by a notice waiting on the bank's website, a bank that changed its service to Web Connect or Direct Connect, or an inactive QuickBooks account that still has online banking on. Clear those, then reset the connection.

Is OL-203 a QuickBooks Online error?

No. OL-203 is a QuickBooks Desktop Bank Feeds code, including Enterprise. QuickBooks Online shows its own numbered connection errors. The Online equivalent of the workaround is Transactions, Bank transactions, Link account, Upload from file, which accepts a .qbo file.

Can I still import transactions while I have error OL-203?

Yes. A Web Connect .qbo file imports through File, Utilities, Import, Web Connect Files without using the broken connection. Download one from the bank for recent dates, or convert the PDF statements to .qbo for older months or when you do not hold the login.

How do I know if my bank switched from Direct Connect to Web Connect?

Sign in on the bank's website and look at the download or accounting software options. If it offers a QuickBooks Web Connect download but no Direct Connect enrollment for that account, the bank has changed its service. Deactivate online services on the account in QuickBooks and set it up again as Web Connect.

Will reinstalling QuickBooks fix OL-203?

Rarely. Most OL-203 cases sit at the bank or in account settings, so reinstalling changes nothing. Run the test company check first. Reinstall or upgrade only if the test file downloads and your real file does not, or if your QuickBooks version is past its support date.