How to Fix Quicken Error OL-220

Quicken Error OL-220 is an online banking connectivity error that occurs when Quicken cannot process the response from your financial institution's server during a One Step Update. The error belongs to the OL-220 through OL-226 family, all of which point to communication failures between Quicken and your bank's Direct Connect or Express Web Connect servers. This guide covers all fixes verified on Quicken Classic for Windows 2024 and 2025 running on Windows 10 and Windows 11.

What Is Quicken Error OL-220?

Quicken Error OL-220 is part of a group of OL-series errors that appear during Online Center updates or One Step Update sessions when Quicken receives an OFX (Open Financial Exchange) response from your financial institution's server that it cannot process. The OFX protocol is how your bank transmits transaction data to Quicken, and when that response contains unrecognized or malformed information, Quicken returns an OL error code.

The OL-220 family spans codes OL-220 through OL-226. Each code signals a slightly different failure point within the same communication exchange, but they all share the same root causes and the same fix steps. You will typically see one of these messages on screen:

"OL-220: The financial institution's server returned an error. Quicken is unable to complete the requested action."

The error surfaces during One Step Update or when manually updating a specific account in the Online Center. It does not corrupt your local Quicken data file; it simply means the update session failed for the affected account.

Symptoms

You may be experiencing Error OL-220 if you notice:

• An OL-220, OL-221, OL-222, OL-223, OL-224, OL-225, or OL-226 error code appears in the One Step Update Summary
• One or more bank accounts stop downloading new transactions while others continue to update normally
• The error appears every time you run One Step Update for a specific account
• Quicken prompts you to re-enter your bank login credentials repeatedly
• An account that previously connected without problems suddenly begins returning this error
• The error appears after a recent password change at your bank or after your bank migrated to a new online banking platform

Root Causes

1. Unrecognized Account or User Information at the Bank's Server

This is the most common cause. Your financial institution's server rejected the credentials or account identifiers that Quicken sent. This can happen after a password change, a username change, or a bank-side account migration where the account number format changed.

2. Temporary Server Outage at the Financial Institution

Banks occasionally perform maintenance on their Direct Connect or Express Web Connect servers. During these windows, any Quicken update attempt returns an OL-series error. The outage is usually resolved within one business day without any action on your part.

3. Outdated or Stale Vault Password in Quicken

Quicken stores your bank credentials in an encrypted Vault. If you recently changed your bank password but did not update it in Quicken's Vault, the credentials mismatch causes OL-220.

4. Deactivated Account Connection

If a bank account's Online Services connection was deactivated, either by the bank or through a previous Quicken troubleshooting session, Quicken cannot communicate with the server and returns an OL error.

5. Corrupted Cloud Sync or Account Settings

Occasionally, corrupted local account settings cause Quicken to send malformed requests to the bank server, which responds with an OL-series error code.

Before You Begin

• Confirm which account is triggering the error by reviewing the One Step Update Summary (open via Tools > One Step Update Summary)
• Note the exact OL error code shown (OL-220 through OL-226) to confirm you are on the right guide
• Confirm your bank's website is accessible and that you can log in normally in a browser using your current credentials
• Have your bank account number, routing number, and online banking username and password ready
• Do not call your bank's general customer service line; you will need their Online Banking Support team specifically for OFX and Direct Connect issues

Step-by-Step Fix

Work through these methods in order. Most cases are resolved by Method 1 or Method 2.

Method 1: Update Your Account Credentials in Quicken

The first step is to ensure the credentials stored in Quicken match what you currently use to log into your bank's website.

1. Open Quicken and go to Tools > One Step Update Summary
2. Identify the financial institution and account returning the OL-220 error
3. Close the Summary window
4. In the account list on the left, click the affected account to open it
5. Click the gear icon (Account Actions) in the upper-right corner of the account register
6. Select Edit Account Details
7. Click the Online Services tab
8. Click Update Now
9. When prompted, enter your current bank username and password
10. Click Connect and wait for the update to complete

If the update succeeds and no OL error appears, you are done. If the error persists, continue to Method 2.

Method 2: Deactivate and Reactivate Online Services

Resetting the account connection clears corrupted settings and forces Quicken to re-establish a clean connection to your bank.

Step 1 - Deactivate the account:

1. Open the affected account register
2. Click the gear icon (Account Actions) at the upper right
3. Select Edit Account Details
4. Click the Online Services tab
5. Click Deactivate (or Remove from One Step Update)
6. Confirm when prompted
7. Click OK to close Account Details

Step 2 - Reactivate the account:

1. With the account register still open, click the gear icon again
2. Select Edit Account Details
3. Click the Online Services tab
4. Click Set Up Now
5. Search for your financial institution by name
6. Select the correct institution from the list and choose your connection method (Direct Connect or Express Web Connect)
7. Enter your bank username and password when prompted
8. Click Connect
9. Quicken will display your accounts at that institution. Match the Quicken account to your existing account by selecting Link to existing Quicken account
10. Do not create a new account if the account already exists in Quicken
11. Click Next and complete the setup

After reactivation, run One Step Update to confirm the error is resolved.

Method 3: Update the Vault Password

If you recently changed your bank password, update it in Quicken's password Vault so Quicken can authenticate correctly.

1. Go to Tools > Quicken ID and Password Vault
2. Enter your Quicken ID password to unlock the Vault
3. Review the stored passwords for the affected financial institution
4. Click the entry and update it with your current bank password
5. Save and close the Vault
6. Run One Step Update again

Method 4: Wait One Business Day and Retry

If your bank's server is undergoing maintenance or experiencing a temporary outage, the OL-220 error will resolve on its own once the server is restored.

1. Go to Tools > One Step Update Summary and note the time the error first appeared
2. Visit your bank's website or status page to check for any posted outage notices
3. Wait until the next business day and run One Step Update again
4. If the error clears, no further action is required

This is particularly relevant if the error appeared suddenly on an account that was working fine before, without any recent password or settings changes.

Method 5: Contact Your Financial Institution

If none of the above steps resolve the error, the issue lies on the bank's side. Only your financial institution can investigate their server logs and determine why your account data is being rejected.

1. Call or chat with your bank's Online Banking Support team (not general customer service)
2. Tell them you are receiving OFX error OL-220 (or the specific OL code you see) in Quicken
3. Request that they check whether Direct Connect or Express Web Connect is properly enabled for your account
4. Ask them to verify that your account number and routing number are being transmitted correctly in OFX format
5. If your bank recently migrated platforms, ask them to confirm the new OFX endpoint is correctly configured

Quicken Support does not have access to your bank's servers and cannot force the bank to resolve a server-side OFX issue.

OL-Series Error Comparison

All OL-220 through OL-226 errors share the same root cause category but differ in the specific failure point within the OFX exchange. Use this table to confirm you have the right error and understand what it means.

The fix steps for all codes in this range overlap significantly. Start with Method 1 and Method 2 regardless of which specific OL code you see.

When to Call Support

Contact Quicken support phone number if:

• The OL-220 error persists after completing all five methods above
• Multiple accounts at different financial institutions are all returning OL errors simultaneously, which may indicate a Quicken application issue rather than a bank-side issue
• The error appeared immediately after a Quicken software update, suggesting the update may have introduced a connectivity regression
• You cannot locate the Deactivate option in Online Services, which may indicate the account type does not support standard reconnection steps

You can also visit the Quicken Community to check whether other users at your bank are reporting the same OL error, which would confirm a bank-side outage.

Prevention Tips

• Update your Quicken Vault immediately after changing your bank password. Do not wait until the next One Step Update fails. Go to Tools > Quicken ID and Password Vault and update the password right away.
• Keep Quicken updated. Go to Help > Check for Updates monthly to ensure you have the latest build, which includes updated OFX connection settings for participating banks.
• Run One Step Update at least weekly. Frequent updates catch credential issues early, before a large transaction gap builds up.
• Monitor your bank's status page. Many banks publish system status pages. Bookmark yours so you can quickly confirm whether an OL error is bank-side before spending time troubleshooting Quicken settings.
• Avoid canceling mid-update. Canceling One Step Update partway through can leave account connections in an inconsistent state that produces OL errors. Always let updates complete or time out naturally.