QuickBooks Error OL-202: Bank Feeds Activation Rejected During Setup

QuickBooks error OL-202 blocks bank feeds activation when the bank server rejects a download; learn what causes it and how to clear it.

OL-202 is an online banking error in QuickBooks Desktop. It appears while you are activating an account for Bank Feeds, usually right after you enter your sign-in details. The bank server refuses the download or returns a response the software cannot interpret, and the activation stops before any account is linked. Our engineers treat it as a connection fault first and a file fault second, and that order shapes the fixes below.

What does the OL-202 message say?

The dialog appears during Bank Feeds setup rather than during a routine download. Most builds state that QuickBooks was unable to complete your request, with the code in brackets at the end, for example [OL-202]. The exact wording varies by release and edition, and some builds add a line about verifying your financial institution. What stays constant is the timing: the failure lands during activation, and no account gets connected.

What does OL-202 mean?

The OL prefix marks the online banking family of errors. Codes in the 200 range mean the exchange with your bank began and then broke down: the server rejected the request or sent data QuickBooks could not parse. This separates OL-202 from pure connection failures, where the session never starts at all. In practice the fault usually sits on the bank side or in the connection path, not in your bookkeeping.

What triggers OL-202?

Several conditions produce the same code, and the list below covers the ones our engineers see most often:

• The bank server is down for maintenance or is refusing sessions, which happens most often overnight and on weekends.
• QuickBooks is not on the current maintenance release, so it uses an outdated connection standard.
• The bank profile stored in your company file is stale after the bank changed its platform.
• The wrong bank listing was chosen, which is common when a card is issued by a different bank than the brand on it.
• Your sign-in fails on the bank's own site, or a security prompt is waiting for you there.
• A firewall, proxy, or wrong system date breaks the session before the server answers.

How do you fix OL-202?

Work through the scenarios in order, because they run from most common to least. The numbering is continuous so you can pick up where you left off.

The bank server rejected the session

1. Sign in to your bank's website with the same credentials you used in QuickBooks.
2. Open the statements or account activity area and confirm it loads normally.
3. If the site is slow or shows a maintenance notice, wait and retry activation later in the day.
4. Clear any unread alerts or messages at the bank first, because some banks block outside access until you acknowledge them.

QuickBooks needs the latest release

5. Close your company file, then choose Help and Update QuickBooks Desktop.
6. Select Update Now, mark every available item, and let the download finish.
7. Restart when prompted and let the new release install.
8. Open your file and run the Bank Feeds activation again.

The bank profile needs a refresh

9. Choose Banking, then Bank Feeds, then Participating Financial Institutions.
10. Refresh the list so QuickBooks picks up the bank's current connection details, then close the window.
11. Start setup again and select your bank from the refreshed list.

The wrong bank listing was selected

12. Search the participating institutions list for every name your bank trades under.
13. Compare the sign-in page shown during setup with the page you use on the bank's site.
14. For a card account, search for the issuing bank named on the card rather than the brand on the front.

The account's online services need a clean restart

15. Open the Chart of Accounts and edit the affected account.
16. On the Bank Settings tab, choose Deactivate All Online Services and save. Older releases call this the Online Banking tab.
17. Close the company file, reopen it, and run the setup again.

Security software or the system clock

18. Confirm the Windows date and time are correct, then retest.
19. Set your firewall or antivirus to trust QuickBooks, or pause it briefly for the attempt.
20. Bypass any proxy or VPN for the test, since both can alter the response the bank returns.

The company file itself

21. Create a new, empty test company and try activating the same bank in it.
22. If the test file connects, the online banking data in your working file is damaged.
23. Run Verify and Rebuild from the File menu under Utilities, then retest.
24. If the code survives both, the file needs hands-on repair of its online banking structures, which our engineers perform on a copy.

How can you stop OL-202 from coming back?

Install maintenance releases as they arrive, because banks retire old connection standards with little notice. Confirm your login works on the bank's own site before any activation attempt, and finish any pending security steps there. When your bank announces a merger or platform change, deactivate feeds on the affected accounts first and set them up again afterward.

Take a backup before you change any online services, so a failed activation never leaves half-linked accounts behind. If two attempts fail, stop and check the bank's site instead of forcing rapid retries, since some banks lock the session after repeated failures.