Quicken OL-220 through OL-226: Fixing These Online Services Errors
One Step Update fails with OL-220, OL-221, OL-222, OL-223, OL-224, OL-225, or OL-226.
Why: This whole family appears when your bank sends Quicken a transaction-download file in a format Quicken can’t process — typically because the bank changed something on its servers or is in maintenance. It’s almost always on the institution’s side, so the fixes are: pin down which bank failed, try a refresh, then wait or escalate to the right party based on how that account connects.
Fix 1: Find out which bank actually errored
One Step Update bundles every account, so one bank can mask the rest.
- Tools → One Step Update Summary.
- Read which financial institution reported the OL-22x error and note the exact code.
Fix 2: Refresh that account’s connection
Force a fresh update on just the affected account.
- Open the affected account’s register.
- Click the Account Actions gear (top right of the register).
- Choose Update Now and let it run.
Fix 3: Wait a business day
Because these are usually temporary bank-server or maintenance conditions, Quicken’s own guidance is to try updating the next business day.
- Also disable any VPN before retrying — a VPN can trigger OL-22x errors.
- Check the Quicken Community for alerts about a known, widespread issue at your bank.
Fix 4: Escalate to the right party for your connection type
If it persists, who you contact depends on how the account connects.
- Tools → Account List and look at the Transaction Download (or method) column for that account:
- Direct Connect → contact your financial institution (it’s their direct feed).
- Express Web Connect → contact Quicken Support.
- Web Connect (you import .QFX files) → contact your bank.
If you’re adding this account for the very first time, the bank may require you to authorize Quicken’s access through its website before any download will succeed.
FAQ
Is my data file damaged? No. OL-220 through OL-226 are connection/file-format errors between Quicken and the bank, not signs of local data corruption.
Why did this start when I didn’t change anything? The bank changed how it generates its download file or is doing server maintenance. The format no longer matches what Quicken expects, so it’s resolved on their schedule.
It’s been several days and only one bank fails. Use Fix 4 to identify the connection type and contact the correct party — a single bank failing for days is server-side, not something rebuilding will fix.