“Quicken cannot process the data from your bank”
OL-220-A means Quicken received a response it could not process. Unlike a connection failure, the data arrived — it simply contained something the parser refuses, and the message gives no hint which part.
Symptoms
One Step Update or a manual import stops with error code OL-220-A The account connected without trouble last month and nothing changed on your side Other accounts at the same bank update normally
What actually causes it
Invalid characters in a transaction description
A raw ampersand, an angle bracket or a control character in a payee name breaks parsing at that exact byte. New merchants introduce these regularly, which is why an account that worked for years suddenly stops.
A malformed value in a required field
Dates outside the YYYYMMDD shape and amounts carrying currency symbols or thousands separators both produce a response Quicken cannot read, even though the rest of the file is perfect.
A truncated or oversized response
Very large date ranges can return a response that is cut short server-side. The structure is valid up to the cut and unparseable after it.
How to fix it
- Download the file manually rather than using One Step Update, so you have something to inspect.
- Drop it into the fixer below — invalid characters, malformed dates and amounts and truncation are all reported and repaired in place.
- Import the repaired file through File → File Import → Web Connect (.QFX) File.
- If the download itself will not complete, narrow the date range; a shorter request often avoids the server-side truncation entirely.
Related import problems
Skip the manual edit — fix it automatically
The fixer names the exact character or value Quicken choked on, which is the one thing the error code does not tell you. Free, no signup, no upload.
Open the fixer