Does Chase Work With Quicken? How to Download Chase Transactions

TL;DR: Yes, Chase works with Quicken. Chase retired Direct Connect, so bill pay and account transfers from inside Quicken are gone, but transaction downloads continue through Express Web Connect Plus. You can also export activity yourself from chase.com in QFX form and import it manually. The export reaches back about 24 months, so anything older has to come from your PDF statements.

The confusion is understandable. Chase announced a connection change, forums filled up with people saying Chase had dropped Quicken, and a lot of users concluded their accounts were finished. That is not what happened. What Chase dropped was the two-way connection. The one-way flow of transactions into your register survived, and there is a manual path that works even when the automatic one does not.

Does Chase work with Quicken?

Chase accounts connect to Quicken using Express Web Connect Plus. You start the setup in Quicken, get handed to chase.com to sign in, and Chase passes a secure token back. Quicken stores the token rather than your credentials, and you can revoke access from your Chase profile whenever you want. Checking, savings, and credit card accounts all download this way.

What you gave up when Direct Connect went away is the two-way half: paying bills through Quicken Bill Pay and moving money between Chase accounts from the register. Those features required Chase to accept instructions from Quicken, and that channel is closed. Downloads were never part of that channel, which is why they kept working.

What changed with Express Web Connect Plus

Express Web Connect Plus sits between the two older methods. It is not the direct bank-to-Quicken pipe that Direct Connect was, and it is not the stored-password screen scraping that plain Express Web Connect uses. It is token based, which is more secure and also means the token expires and has to be renewed. Most of the Chase connection complaints you will read come down to that renewal step.

How do I download Chase transactions into Quicken?

Two routes, and it is worth knowing both. The automatic one runs on its own once set up. The manual one is what you fall back on when the automatic one stalls, and it is also how you grab a specific date range on demand.

For the automatic route, add the account in Quicken, sign in at the Chase screen when it appears, and make sure every account you want is checked on the permissions page. People routinely miss this and then wonder why one card never updates. After that, One Step Update collects new activity.

For the manual route, sign in at chase.com and open the account. Above the transaction list there is a download icon. Pick a date range, choose the file type, and download. The Quicken option produces a QFX file. Then in Quicken, use File, then File Import, then Web Connect File, and point it at the account that already exists in your register rather than letting Quicken create a new one.

How far back can I download Chase transactions?

About 24 months. The activity download covers roughly the last two years, and individual files are capped at around a thousand rows, so a busy checking account may need to be pulled in several date ranges rather than one go. Chase does not offer a structured export of older monthly statements at all. Those exist as PDFs in the Statements section, typically going back several years, but a PDF is not something Quicken can read.

Why is Chase not downloading to Quicken?

The usual cause is an expired token. Express Web Connect Plus asks you to reauthorize periodically, and if you dismiss the prompt or the browser handoff fails partway, the connection sits there looking fine while nothing arrives. Reauthorize from the account settings, and check every Chase account on the permissions screen while you are there.

The second cause is a Chase side change that breaks the aggregation layer, which surfaces as a CC error code. Those are not problems with your data file, so rebuilding the file is wasted effort. Give it a day, then deactivate the account for online services and set the connection up again, linking to your existing register. The broader troubleshooting order, including what to do when an update reports success but adds nothing, is on our guide to Quicken not downloading transactions.

One thing worth internalizing: once the connection is repaired, it does not go back and collect what it missed. Feeds deliver forward, not backward. If Chase was disconnected for six weeks, those six weeks stay empty until you import them from somewhere else.

Can I import a Chase PDF statement into Quicken?

Not as a PDF. Quicken reads QFX, OFX, QIF, and in some versions CSV, and it has no ability to interpret a statement document. Converting the PDF first gives Quicken a file it recognizes, with dates parsed, descriptions carried over, and debits signed negative so the balance ties out after the import.

This is the route for anything past the 24 month export window, and for rebuilding a gap left by a broken feed. Our PDF to QFX converter produces a Web Connect file from the statement, and the Chase bank statement converter page covers the quirks specific to Chase layouts, including how Zelle payments, QuickDeposit entries, and wire descriptions come through. If you are new to the format itself, what a QFX file actually contains explains why Quicken is picky about it.

Checking and credit card downloads behave differently

Worth knowing before you start reconciling. The checking export carries a running balance column; the credit card export does not, because a card statement tracks charges and payments rather than a balance you can tie to line by line. Card descriptions also arrive with merchant category information that checking activity has no equivalent for.

Practically, this means your reconciliation check differs by account type. On checking you can add the opening balance to the sum of every transaction and confirm it equals the closing balance. On a card you compare the total charges and total payments against the statement summary instead. Either way, do the check before you accept the import, not a month later when the register has moved on.

A workflow that stays current

Leave the automatic feed on and let it do the routine work. Once a month, when you reconcile, compare the register against the statement closing balance. If they disagree, pull a QFX for that month from chase.com and import it to fill whatever the feed dropped. If the gap is older than the export reaches, convert the statement PDF instead.

That routine takes a few minutes and it catches silent gaps early, which is the failure mode that actually costs people time. A connection that errors loudly gets fixed the same day. A connection that quietly skips eleven days gets discovered in April. If your books live in QuickBooks rather than Quicken, the same statement data can go in as a QuickBooks ready QBO file instead, and the reconciliation logic is identical.

Chase has not abandoned Quicken users. It has moved them onto a connection that trades convenience features for security, and left the manual export in place as the escape hatch. Knowing both routes, and knowing that feeds never backfill, is most of what it takes to keep a Chase account accurate in Quicken. For the full import walkthrough on any bank, see converting a bank statement to Quicken.