Stop waiting for a bank side fix. Upload the PDF statements covering the period Quicken missed and download a clean QFX that imports the same way a bank download does, with dates, descriptions and signed amounts already in place.
Upload your bank statement
Drop file here or click to upload
PDF, JPG, PNG, BMP, HEIC, TIFF
Uploading...
Quicken error codes split into two families, and the prefix tells you where the fault sits. OL codes come from a direct link to the bank: OL-220 through OL-226 mean the bank sent a file Quicken could not parse, while OL-292 through OL-297 mean Quicken could not reach the server at all. CC codes come from Express Web Connect, the aggregation service Quicken runs on your behalf, so CC-501 to CC-503 point at credentials or a dropped session rather than at your data file. Almost none of these are fixable from inside Quicken, which is why the transactions you need are faster to get from the PDF statement you already have: convert it to a QFX file and import that.
The advice that circulates for Quicken error codes is mostly generic, and the official remedy often ends at contact your bank. Here is what is actually going wrong.
For the OL-220 to OL-226 family the bank generated a malformed file. No amount of reinstalling Quicken, validating the data file or resetting the account changes a file the bank wrote incorrectly.
Quicken states plainly that financial institutions create these files and that for Web Connect the remedy is to contact your bank. That is accurate, and it is useless when you need the quarter closed today.
OL-301-A and OL-393-A each get reported for several unrelated reasons, from a stale Bill Pay setting to an account the bank no longer serves, so a single published fix rarely matches your case.
CC-501 to CC-503 commonly persist because an old, closed or hidden account still sits activated under the same bank logon, and the connection keeps failing on the account you forgot about.
Once a connection is repaired it resumes from the current date. The weeks it skipped are not resent, so a gap remains in the register even after the error is gone.
Downloads reach back a limited period. If the error persisted for months, the earliest missing transactions can no longer be downloaded at all, at any connection type.
Your statements are already sitting in online banking as PDFs, and they cover every transaction the feed dropped. Turning one into a QFX gives Quicken a file it accepts, generated correctly rather than by the system that is failing.
The export carries the balance and transaction blocks Quicken expects, including the LEDGERBAL field whose absence is a frequently reported trigger for OL-221.
When the bank is the one producing a faulty download, generating a fresh file from the statement removes the faulty file from the process entirely.
Convert statements from months or years back, which is the only practical way to recover history that has aged out of the download window.
Debits import negative and credits positive, so the register balance ties to the printed statement instead of drifting.
The workflow is identical whether your error is OL-221-A at a big national bank or CC-503 at a small credit union.
The same extraction exports plain OFX for MS Money and other finance software, or CSV for a spreadsheet.
No waiting on a support ticket, no retyping a statement by hand.
Sign in to online banking and save the PDF statements covering the period Quicken failed to download, one file per statement.
Tip: Statements live under a documents or statements section, separate from the transaction download tool.
Upload the statements, check the extracted transaction table against the printed one, and export a QFX built for Quicken.
Tip: Choose OFX instead if you are importing into MS Money or another program.
Use File, then File Import, then Web Connect File, pick the existing account, and review the matches before accepting.
Tip: Quicken flags likely duplicates, so a small overlap at the edges of the gap is safer than leaving a day uncovered.
Anyone whose books depend on Quicken staying current with a bank account.
Files with years of history where one account started erroring and the register quietly stopped updating.
Business checking on an aggregated connection, with a quarter to close and a CC code that returns every morning.
Working in a client file where the feed broke months ago and the gap now sits outside the download window.
Credit card accounts throwing OL-221 on every download while the checking account at the same bank updates normally.
Read the prefix first. OL means Quicken talked to the bank directly, through Direct Connect or a Web Connect QFX download. CC means the request went through Express Web Connect, the aggregation layer Quicken operates. That single distinction rules out most of the wrong fixes.
| Code | What it means | Where the fault sits | First thing to try |
|---|---|---|---|
| OL-220 to OL-226 | Quicken received a file from the bank and could not parse it | The bank, which generated the file | Retry the next business day, then convert the statement to QFX |
| OL-221-A and OL-221-B | The same parse failure, commonly a missing LEDGERBAL balance field | The bank | Treat as one fault, not two. Generate a clean QFX from the statement |
| OL-292 to OL-297 | Quicken could not establish a connection to the bank server | Network, security settings, or the bank server | Enable TLS 1.2, check the system clock, allow qw.exe through the firewall |
| OL-301-A | A Direct Connect update failed. Widely reported causes include a server side problem, rejected credentials, and a transaction dated outside the range the bank accepts | Usually the bank or the account setup | Re-enter credentials, then look for an out of range transaction date in the register |
| OL-393-A | Account information does not match what the bank expects. Often an account activated for a service the bank has not enrolled, or one the bank no longer serves | The account settings in Quicken | Check whether Bill Pay is switched on in Quicken without matching enrollment at the bank |
| CC-501 | Express Web Connect could not complete the connection to the bank | The aggregation service or the bank | Wait it out, then deactivate every account under that bank logon and reconnect |
| CC-502 | The connection started and then dropped, commonly a timeout | The bank server or the session | Retry later, update Quicken, then deactivate and reconnect if it repeats |
| CC-503 | The stored sign in details being sent to the bank are blank, stale or wrong | Saved credentials in Quicken | Update the saved credentials after any bank password change |
One caveat worth stating: Quicken advises against following community posts that tell you to reset CC credentials through undocumented steps, and points people to Support instead. The table above sticks to the changes that are reversible and safe.
It means Quicken could not complete an exchange with your financial institution, and the code identifies which part of that exchange failed. A code in the OL family points at a direct exchange with the bank, either a file that arrived malformed or a server Quicken could not reach. A code in the CC family points at Express Web Connect, the service that signs in on your behalf. In neither case is your Quicken data file damaged, which is why validating or reinstalling rarely helps.
The prefix identifies the connection method. OL errors come from Direct Connect or from a Web Connect QFX file, so Quicken is dealing with the bank directly and the bank controls both the server and the file format. CC errors come from Express Web Connect, where Quicken signs in to the bank on your behalf and normalizes the results, so problems usually involve stored credentials, an expired authorization, or a dropped session. Fixes for one family generally do nothing for the other.
OL-221 means Quicken received a file from the bank but could not read it, because the bank wrote the QFX incorrectly. A frequently reported trigger is a missing LEDGERBAL block, the field carrying the account balance. OL-221-A and OL-221-B are the same underlying problem and often appear together in one dialog, so there is no point chasing them separately. Because the fault is in the file itself, producing a correctly formatted QFX from the statement resolves it immediately. There is a full walkthrough in the Quicken error OL-221 guide.
OL-297-A means Quicken could not establish an internet connection to the financial institution, even though your computer is online and you can sign in to the bank website in a browser. Quicken groups it with OL-295 and OL-296 and attributes it to a server outage, a bank security change, or local network settings. Its published steps are to enable TLS 1.2, confirm the system date and time, restart, allow qw.exe through the firewall, and then contact the bank. The OL-297-A guide covers each step and what to do when they all fail.
OL-301-A appears when a Direct Connect update fails. Reported causes vary: a problem on the bank server, credentials the bank rejected, and, in a pattern several users have documented, a single transaction in the register dated outside the range the bank will accept. Start by re-entering your credentials in the account setup. If the error survives that, scan the register for a transaction with an obviously wrong date, such as one sitting years in the past or future, and correct it before updating again.
OL-393-A signals a mismatch between how the account is configured in Quicken and what the bank has on file. Three situations account for most reports: the account is activated for online bill payment in Quicken without the matching enrollment at the bank, the bank no longer offers the account for download, or the account is hidden in Quicken but still activated. Checking the Bill Pay setting first resolves a good share of cases, since a reconnection can switch it on by default.
Start by giving it time, because CC-501 frequently reflects a temporary problem between the aggregation service and the bank that clears without any action. If it persists past a day or two, deactivate online services for every account that shares the same bank logon, including closed, hidden and long forgotten accounts, then reconnect and link each result to the account that already exists in your file. That last detail matters: letting Quicken add new accounts is what splits history in two.
Because most US banks now use methods that require periodic reauthorization rather than a permanent link. Express Web Connect and Express Web Connect Plus sign in on your behalf, so a bank password change, a new security prompt, or an expired authorization silently ends the session. Banks also change their systems on their own schedule, which is why an account that worked for years can start failing overnight without anything changing on your machine.
No, and this is the part most guides leave out. The error blocks one delivery route, not the data. Every transaction the feed missed is printed on the statement your bank has already published, so converting that statement to a QFX file and importing it puts the transactions in your register regardless of whether the connection is ever repaired. Fixing the feed is still worth doing for future downloads, but it is not a prerequisite for closing the books.
Once you have the file, import it against the account that already exists. The PDF to QFX converter produces exactly the Web Connect file Quicken expects, and the convert bank statement to Quicken page walks through the import screen by screen. If the trouble is limited to one bank, the Quicken not downloading transactions pillar covers the per bank picture, with dedicated pages for Chase not downloading to Quicken, Bank of America not downloading to Quicken and Wells Fargo not downloading to Quicken. For background on the connection types themselves, see Express Web Connect versus Direct Connect.
Import into the existing account rather than a new one, and let Quicken run its matching pass. It compares incoming transactions against what is already in the register and flags likely duplicates for review, so overlapping a few days at either edge of the gap is safer than leaving a day uncovered. Review the flagged list before accepting, then reconcile against the statement closing balance. If the balance ties, nothing is missing and nothing is doubled.
It means Quicken could not complete an exchange with your bank, and the code says which part failed. OL codes involve a direct exchange with the bank, either a malformed file or an unreachable server. CC codes involve Express Web Connect, the service that signs in on your behalf, so they usually point at credentials or a dropped session. Your Quicken data file is not damaged in either case.
OL errors come from Direct Connect or a Web Connect QFX download, where Quicken deals with the bank directly and the bank controls the file and the server. CC errors come from Express Web Connect, where Quicken signs in for you and normalizes the data. Because the two use different plumbing, a fix published for one family will usually do nothing for the other.
It means Quicken received the file but could not parse it, because the bank generated it incorrectly. A commonly reported trigger is a missing LEDGERBAL field, which carries the account balance. OL-221-A and OL-221-B are the same problem and often appear together. Since the fault is in the file, converting the PDF statement to a clean QFX resolves it without waiting on the bank.
It means Quicken could not establish a connection to the bank, even while your browser reaches the bank website normally. Quicken lists it alongside OL-295 and OL-296 and points to server outages, bank security changes, or local network settings. The published steps are TLS 1.2, system date and time, restart, firewall access for qw.exe, then contacting the bank.
Wait first, because CC-501 often reflects a temporary problem between the aggregation service and the bank that clears on its own. If it lasts more than a day or two, deactivate online services for every account sharing that bank logon, including hidden and closed ones, then reconnect and link each account to the one already in your file rather than creating new ones.
Almost never. A repaired connection resumes from the current date and does not resend a range it already attempted, so the gap stays in your register. To fill it, convert the statements covering those dates to a QFX file and import them against the existing account.
Not directly. Quicken imports QFX, OFX, QIF and CSV depending on the version and platform, but it cannot read a PDF. Converting the statement to QFX first gives Quicken a file it accepts, with dates, descriptions and signed amounts already structured the way the importer expects.
Usually not. OL and CC codes describe a failed exchange with the bank, not damage to your file. Validate and Repair File is worth running when a single account misbehaves while others at the same bank work, but it will not clear a malformed download or an expired authorization.
The per bank view of the same problem, fixed in order.
Chase, the bank that retired Direct Connect entirely.
Turn a PDF statement into the QFX file Quicken imports.
The full import walkthrough for Quicken users.
Get started converting bank statements to OFX.
USD
per month
billed as
$288 yearly
Choose speed vs accuracy when extracting
| Base AI Faster | 2,500 pages |
| Pro AI Best accuracy | 500 pages |
Scale statement conversion across your team with automation.
USD
per month
billed as
$888 yearly
Choose speed vs accuracy when extracting
| Base AI Faster | 10,000 pages |
| Pro AI Best accuracy | 2,000 pages |
Enterprise-grade bank statement conversion and controls.
USD
per month
billed as
$ yearly
Choose speed vs accuracy when extracting
| Base AI Faster | pages |
| Pro AI Best accuracy | pages |
