Quicken Error OL-221-A and OL-221-B: What It Means and How to Fix It

TL;DR: Quicken error OL-221-A and OL-221-B mean Quicken downloaded a file from your bank and could not parse it, because the bank generated the QFX incorrectly. A commonly reported trigger is a missing LEDGERBAL block, the field that carries the account balance. Nothing is wrong with your Quicken installation or your data file, which is why reinstalling and validating rarely help. Quicken's official guidance for Web Connect files is to contact your bank, because only the bank can fix the file it produces. The practical workaround is to generate a correctly formatted QFX yourself from the PDF statement and import that instead.

Last updated July 2026.

What does Quicken error OL-221 mean?

OL-221 belongs to the OL-220 through OL-226 family, all of which describe the same underlying situation: Quicken asked your financial institution for transactions, got a response, and could not read it. Quicken's own support documentation puts it plainly, saying that financial institutions create specifically formatted files for Quicken downloads and that sometimes those files are changed in a way that prevents them from downloading into Quicken.

The important consequence is that OL-221 is a message about the bank's file, not about your setup. That single fact rules out most of the advice you will find in general Quicken troubleshooting posts. Repairing your data file, reinstalling Quicken, clearing a cache, or creating a fresh file will not change what the bank sends you.

What is the difference between OL-221-A and OL-221-B?

Functionally, very little. Both codes report an invalid or unreadable response from the financial institution, and in practice they travel together: users regularly see OL-221-A in the main error dialog with OL-221-B shown in the corner of the same window. Treat them as one problem with one set of causes rather than two separate faults to diagnose. The letter suffix does not change what you should do next.

What causes the error?

Almost always a formatting fault in the QFX or OFX the bank generated. The specific fault that gets reported most often is a missing LEDGERBAL element. QFX is a structured format, and the ledger balance block is not optional in the way a bank's file generator sometimes treats it. When it is absent, or when a date, amount, or account block is written in a shape Quicken does not expect, the parser stops and returns OL-221.

Banks introduce these faults when they change their export systems, which is why the error tends to arrive in waves affecting many customers of one institution at once. Reports over the past few years have named Chase, Capital One, Huntington Bank, and Citizens Access among others. If you search the Quicken community and find a thread about your bank dated within the last few weeks, that is a strong signal the problem is on their side and not yours.

There is a second, smaller category worth knowing about: a genuinely truncated download. If a connection dropped partway through, the file on disk is incomplete and will fail to parse for exactly the same reason. Re-downloading catches this one, which is why it is the first thing to try.

How do I fix Quicken error OL-221?

Work through these in order. The first three are quick, reversible, and cover the cases that resolve on their own. Past that, you are dealing with a bank side fault and your options change.

Why does Quicken tell me to contact my bank?

Because for Web Connect files that is genuinely the only official remedy. Quicken's documentation splits the guidance by connection type: for Direct Connect and for Web Connect QFX downloads it directs you to contact your financial institution, and it notes that if the institution says it cannot assist, an escalation with the institution may be necessary. For Express Web Connect accounts it points you to Quicken Support instead, since Quicken's aggregation partner sits in the middle there.

That instruction is correct and, for most people, unhelpful. The person answering the phone at a retail bank branch has no route to the team that maintains the OFX export, and the timeline for a fix is measured in weeks. Meanwhile you still need this month's transactions in your register.

Should I edit the QFX file by hand?

Some people do, and it can work if the fault is a single missing element you can identify. A QFX is plain text underneath, so opening it in a text editor and adding a correctly formed LEDGERBAL block is technically possible. In practice it is a poor use of time for anyone who is not comfortable reading the OFX specification, and one wrong character produces the same error you started with. It also has to be repeated every single month until the bank fixes its exporter.

A more durable answer is to stop using the broken file. Your bank's PDF statements contain the same transactions and are not affected by whatever went wrong in the download system, and they usually stay available far longer than the download window does. Converting a statement produces a QFX written to spec, which imports cleanly the first time. Our PDF to QFX converter does exactly that, and the full import walkthrough sits on the convert bank statement to Quicken page. QuickBooks Desktop users run into the same class of problem with rejected QBO files, and the answer there is the same: generate a clean QBO from the statement rather than fighting the bank's export.

Which banks throw OL-221 most often?

It moves around, because it follows whichever institution most recently changed its export system. Chase has been a persistent source, and Quicken has confirmed an OL-221-A issue affecting Chase connections that centers on credit card accounts. Capital One, Huntington Bank, and Citizens Access have all generated their own community threads. If your bank is Chase specifically, the Chase not downloading to Quicken guide covers the OL-221 case alongside the reauthorization and permission problems that Chase's Express Web Connect Plus setup creates.

One pattern worth noting: it is common for a bank's checking accounts to download normally while its credit cards fail. Card and deposit accounts are frequently served by different systems inside the same institution, so a fault in one does not imply a fault in the other. If your checking account is fine and only the card errors, you have not misconfigured anything.

Will OL-221 create duplicate transactions once it is fixed?

No. A file that fails to parse never reaches your register, so nothing was imported and nothing needs undoing. The risk of duplicates comes later, when you import a converted statement covering a period the feed eventually delivers as well. Quicken compares incoming transactions against what is already in the register and flags likely matches for review, so a few days of overlap at the edges of a gap is safer than leaving a day uncovered. Review the matches before accepting them, then reconcile against the statement closing balance.

What if the transactions I need are older than the download window?

Then the download was never going to help you regardless of OL-221. Most banks offer somewhere between 90 days and 18 months of downloadable activity, while PDF statements commonly stay online for up to 7 years. Once a period ages out of the download window there is no file to fix, and the statement becomes the only remaining source of that data. This is the situation where converting is not a workaround at all but the only route, and it is covered in more depth in the Quicken not downloading transactions guide.

The short version

OL-221-A and OL-221-B tell you the bank sent Quicken a file it could not read. Re-download once, run Update Now on the account, and check whether other customers of the same bank are reporting it. If it persists, you are waiting on the bank, and the sensible move is to stop waiting: convert the PDF statement to a properly formed QFX, import that, and reconcile. The register stays current whether or not the bank ever fixes its exporter.