Chase keeps PDF statements online for up to 7 years, far longer than any download window. Upload those statements and download a clean QFX that imports straight into Quicken, dated, signed, and ready to reconcile.
Upload your bank statement
Drop file here or click to upload
PDF, JPG, PNG, BMP, HEIC, TIFF
Uploading...
Chase runs Quicken on Express Web Connect Plus, a bank hosted sign in that has to be reauthorized periodically, so a stalled feed usually means the reauthorization lapsed or an account was left unchecked on the Chase permission screen. Chase is also the bank that went furthest: it retired Direct Connect for all accounts on October 6, 2022, so there is no two way connection to fall back on and no Quicken bill pay. The other common Chase failure is OL-221, which is not your setup at all but a malformed QFX coming from Chase. In both cases the fix that always works is converting the Chase PDF statement to a clean QFX and importing that.
Chase left Direct Connect behind years before the other big banks, so its failure modes are different. Most people hit one of these.
Express Web Connect Plus sends you to a Chase hosted sign in on a rolling basis, and a prompt that is dismissed or half completed quietly stops the downloads without a visible error.
The Chase permission screen lists every account you hold and defaults are not guaranteed. Any account left unticked is dropped from the feed even though the connection itself reports success.
Quicken rejects the file Chase generated because it is malformed, often a missing LEDGERBAL field. Quicken has confirmed this as a known issue that hits Chase credit card accounts in particular.
Chase discontinued Direct Connect for all accounts on October 6, 2022, so the usual advice to switch connection types does not apply here, and Quicken bill pay through Chase is gone for good.
Even a healthy connection reaches back a limited period, and Chase credit card and investment accounts are tighter than checking, so an older gap cannot be re-downloaded at all.
Once the connection works again it resumes from the current date rather than resending the weeks it skipped, leaving a hole that only a statement import closes.
Chase keeps up to 7 years of statements online as PDFs. Turn any of them into a QFX file and Quicken imports it the same way it imports a bank download, with none of the formatting faults that trigger OL-221.
The export is a Web Connect QFX written to spec, with the balance and transaction blocks Quicken expects, so the import runs instead of erroring out.
When the problem is the file Chase produced, generating a fresh QFX from the statement removes the faulty file from the equation entirely.
Convert statements from years back, which is the only way to get Chase history that sits outside the download window into Quicken.
Debits import negative and credits positive, so the balance after the import ties to the Chase statement instead of doubling.
Chase checking, savings, and Chase credit card statements all convert, including the card accounts that OL-221 tends to hit hardest.
Need the same Chase activity in a spreadsheet or in software that reads plain OFX? Both come from the same extraction.
No waiting on a reauthorization prompt, no retyping.
Sign in to chase.com and save the PDF statements covering the period Quicken skipped, one file per statement.
Tip: Statements sit under Statements and Documents, separate from Download Account Activity.
Upload the statements, check the transaction table, and export a QFX file built for Quicken.
Tip: Pick OFX instead if you are on MS Money or another program.
Use File then File Import then Web Connect File, choose the Chase account, and review the matches before accepting.
Tip: Quicken flags likely duplicates, so overlap at the edges is safe.
Anyone whose books depend on Quicken staying current with a Chase account.
Files with years of history where the Chase account quietly stopped updating after a reauthorization prompt went unanswered.
Chase business checking on an aggregated connection, with a quarter to close and no Direct Connect option to fall back on.
Working in a client Quicken file where the Chase feed broke months ago and the gap sits outside the download window.
Chase credit card accounts throwing OL-221-A on every QFX download while the checking account updates normally.
Work from the top. The first three account for most Chase cases, take a minute each, and are reversible, so nothing here risks your data file.
| Fix | What you see | What to do |
|---|---|---|
| Complete the reauthorization | A Chase hosted sign in prompt keeps appearing, or updates finish with nothing new | Run the prompt through to the end and tick every Chase account on the permission screen, not just the one you were looking at |
| Update the one account | One Step Update reports success, the Chase register is unchanged | Use Update Now on the account from the register gear icon rather than the global update, which surfaces the real error |
| Deactivate and relink | The account was skipped entirely, or errors persist after reauthorizing | Deactivate online services, reconnect, and link to the existing account rather than letting Quicken add a new one |
| Retry an OL-221 the next day | OL-221-A or OL-221-B on a Chase download, often on a credit card | The fault is in the file Chase generated, so Update Now or a retry the following business day sometimes catches a corrected file |
| Validate the data file | Only one account misbehaves while other Chase accounts update fine | File then Validate and Repair File, which clears register level damage that blocks a download from posting |
| Convert the statement | The gap is older than the download window, or Chase keeps serving a file Quicken rejects | Convert the PDF statements covering the gap to QFX and import them, which bypasses both the window and the malformed file |
Yes, but through one connection method only. Chase supports Express Web Connect Plus for automatic downloads and still offers a manual QFX through Download Account Activity on chase.com. What Chase no longer supports is Direct Connect, which it retired for all accounts on October 6, 2022 after announcing the change that July with a September 26 cutover. That makes Chase the most restricted of the big US banks for Quicken users, and it is the reason so much Chase advice written before 2023 no longer applies.
| Method | Status at Chase | What it means for you |
|---|---|---|
| Direct Connect | Discontinued October 6, 2022 | Not available on any Chase account. Quicken bill pay through Chase went with it and has not returned |
| Express Web Connect | Replaced by Express Web Connect Plus | Accounts still sitting on the old method were moved during the same changeover, which is when many registers stopped updating |
| Express Web Connect Plus | The current Chase method | Bank hosted sign in with periodic reauthorization, download only, no bill pay and no transfers from inside Quicken |
| Web Connect (manual QFX) | Still offered | Download Account Activity gives you a QFX for Quicken, but only within the recent activity window, and this is the download that throws OL-221 |
OL-221 means Quicken received a file from the bank and could not parse it, because the bank wrote the QFX incorrectly. A frequently reported trigger is a missing LEDGERBAL block, the field that carries the account balance. Quicken has acknowledged an OL-221-A issue affecting Chase connections, primarily on credit card accounts, and its official guidance for Web Connect files is to contact your bank, since only the bank can correct the file it generates.
That advice is technically right and practically useless when you need the transactions today. Because the fault lives in the file rather than in Quicken or your data file, producing a different, correctly formatted QFX solves it immediately. Converting the Chase PDF statement gives you exactly that. There is a fuller walkthrough of the error in the Quicken error OL-221 guide.
Less far than most people expect, and it varies by account type. Chase checking and savings offer the longest downloadable window, while Chase credit card and JPMorgan Chase investment accounts are noticeably tighter, with investment activity often limited to a very short recent period. Statements are the exception: Chase keeps up to 7 years of PDF statements online depending on the account and how long you have held it. That gap between what you can download and what you can read is why a converter matters, because Quicken cannot open a PDF.
A successful update with nothing new usually means the connection is healthy but the account was not included in the Chase permission grant, or the aggregation behind Express Web Connect Plus has not picked up the latest activity. Check the permission screen first, since a single unticked account produces exactly this symptom. If every account is granted and other institutions are current, the missing range was already delivered once and will not be resent.
Open the account register, go to Account Details, then Online Services, and deactivate online services for the account. Return to the same screen, choose Set up Now, search for Chase, and sign in through the bank hosted prompt. When Chase lists the accounts it will share, tick all of them, then link each result to the account that already exists in your file rather than letting Quicken add a new one, which is what creates duplicate accounts and split history.
Once downloads resume, fill the gap the outage left. A converted statement produces the same Web Connect QFX Quicken accepts from the bank, so it slots straight into the importer. The PDF to QFX converter makes exactly that file, the Chase bank statement converter page covers Chase layouts specifically, and the wider walkthrough sits on the convert bank statement to Quicken page. If other banks are affected too, the Quicken not downloading transactions guide covers the rest, Bank of America not downloading to Quicken covers a bank that retired Direct Connect later, and Wells Fargo not downloading to Quicken covers the one that kept it. For background on the connection itself, see does Chase work with Quicken.
Convert the Chase statements that cover the gap, then import the QFX with File, File Import, and Web Connect File. Point it at the Chase account that already exists rather than letting Quicken create a new one. Quicken compares incoming transactions against the register and flags likely matches, so a small overlap at either edge of the gap is safer than leaving a day uncovered. Review the accepted list, then reconcile against the statement closing balance to prove nothing is missing.
Most often the Express Web Connect Plus reauthorization lapsed, or an account was left unticked on the Chase permission screen so it was dropped from the feed while the connection still reported success. Run the bank hosted sign in through to the end and grant access to every Chase account listed. If the update reports success but nothing arrives, the connection is working and the missing range has to come from a statement.
No. Chase retired Direct Connect for all accounts on October 6, 2022, after announcing the change in July 2022 with a September 26 switchover deadline. Express Web Connect Plus is the only automatic method Chase offers now, alongside the manual QFX download. Any guide telling you to switch a Chase account to Direct Connect predates that change.
It means Quicken received the QFX file but could not read it, because Chase generated it with a formatting fault, commonly a missing LEDGERBAL field. Quicken has acknowledged this as a known issue affecting Chase, especially credit card accounts, and its official fix for Web Connect files is to contact the bank. Converting the PDF statement to a clean QFX sidesteps the broken file entirely.
No. Quicken bill pay through Chase depended on Direct Connect, which Chase discontinued in October 2022, and Express Web Connect Plus is a one way download only. You can still schedule payments in the Chase online bill pay service directly, but they will not be initiated from inside Quicken.
The downloadable window depends on the account, with checking offering more than credit cards and JPMorgan Chase investment accounts offering the least. PDF statements go back much further, up to 7 years depending on the account, which is why converting a statement is the practical way to load older Chase history into Quicken.
Almost never. Reconnecting restores future downloads but the connection resumes from the current date and will not resend a range it already delivered. Convert the statements covering those weeks and import them as a QFX file to close the gap.
Chase generates the download files for card accounts through a different path than deposit accounts, and the acknowledged OL-221-A issue has centered on credit cards. It is also common for a card added after the original connection to be missing from the Chase permission grant. Check the permission screen first, then convert the card statement if the download keeps erroring.
Not directly. Quicken imports QFX, OFX, QIF, and CSV depending on the version, but it cannot read a PDF. Converting the Chase statement to QFX first gives Quicken a file it accepts, with dates, descriptions, and signed amounts already structured the way the importer expects.
The same fix across every bank Quicken connects to.
The bank that retired Direct Connect later, fixed.
The bank that kept Direct Connect, and its short window.
Turn a PDF statement into the QFX file Quicken imports.
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 |
