When the bank feed stops, you do not have to wait for it. Upload the PDF statement your bank already gives you and download a clean CSV that imports straight into Quicken through its banking transactions import, dated, signed, and ready to reconcile.
Upload your bank statement
Drop file here or click to upload
PDF, JPG, PNG, BMP, HEIC, TIFF
Uploading...
Quicken stops downloading transactions for six common reasons: the bank connection needs reauthorizing, the account is on a connection method the bank no longer supports, the activity is already marked as downloaded, the bank changed its online banking platform, the account was deactivated for online services, or the bank feed itself is down. Work through them in that order. If none apply, download the statement from the bank, convert it to CSV and import it, which puts the missing transactions in the register today instead of waiting for the feed to come back.
A feed that quietly stops is worse than one that fails loudly. Quicken reports a successful update, the register looks normal, and the gap only shows up weeks later when nothing reconciles.
One Step Update finishes with no error while a week of activity never arrives, so the balance drifts and you find out at month end.
The bank asks you to reauthorize, you sign in, and the same prompt comes back on the next update without any new transactions.
These point at the connection layer between Quicken and the bank rather than at your data file, so nothing you change locally helps.
Institutions retire Direct Connect or move to a new platform, and accounts that worked for years stop updating with no warning.
Even when the feed comes back, most connections only reach back a limited window, so the missing weeks never fill in on their own.
You cannot close the month, categorize for taxes, or trust a report while part of the account activity is simply absent.
Every bank still publishes statements. Turn one into a QFX file and Quicken imports it the same way it imports a download.
A genuine Web Connect QFX can only come from your bank, so the export here is a clean CSV, the file Quicken imports for bank and credit card accounts through File, File Import, Banking Transactions, From (.CSV) File.
Convert as far back as your statements go, which is how you recover the months a restored feed will never re-download.
Debits import negative and credits positive, so the account balance after the import ties to the statement instead of doubling.
Older statements saved as scans are read with OCR, so paper era activity converts the same way a downloaded PDF does.
Upload consecutive statements and convert them together when a feed has been dead long enough to leave a real hole.
Need the same activity in a spreadsheet or in software that reads plain OFX? Both come from the same extraction.
No waiting on the bank, no retyping.
Sign in to the bank and save the PDF statements covering the period Quicken skipped.
Tip: Note the first missing date so you know where the gap starts.
Upload the statements, check the transaction table, and export CSV for Quicken or OFX for software that reads it.
Tip: Pick OFX instead if you are on MS Money or another program.
Use File, then File Import, then Banking Transactions, From (.CSV) File, choose the right account, and import only dates Quicken does not already have, since a CSV import does not match existing transactions.
Tip: Note the last date Quicken already has and start the CSV the day after.
Anyone whose books depend on Quicken staying current with the bank.
Files with a decade of history where one account quietly stops updating and the rest keep working normally.
Business checking on a connection the bank has changed, with a quarter to close and no time to wait for a fix.
Working in a client Quicken file where the feed broke months ago and the gap has to be rebuilt from statements.
Brokerage and retirement accounts where the connection is the least reliable and the activity matters most at tax time.
Start at the top. The first three account for most cases and take a minute each, and they are all reversible, so nothing here risks your data file.
| Cause | What you see | What to do |
|---|---|---|
| Connection needs reauthorizing | A sign in prompt on every update, or an update that completes with nothing new | Reauthorize from the account settings and grant access to every account the bank lists |
| Update ran but added nothing | One Step Update reports success, register unchanged | Use Update Now on the individual account from the register gear icon rather than the global update |
| Transactions already marked downloaded | Recent days appear, older gap never fills | The connection will not re-fetch what it has already sent, so the gap has to be imported from a statement |
| Bank changed its online platform | Errors such as CC-501 or CC-502 appearing suddenly for one institution | Deactivate the account for online services, then reconnect and link to the existing account rather than adding a new one |
| Account deactivated for online services | The account is skipped entirely by One Step Update | Open Account Details, then Online Services, and set up the download again |
| Connection type retired by the bank | Direct Connect stops being offered, or the institution disappears from the list | Move to whatever the bank still supports, and use a manual QFX import for anything the new method will not backfill |
Quicken talks to banks in three different ways, and the failure you are looking at depends on which one your account is on. Knowing the method tells you whether the fix is yours to make or the bank's.
| Method | How it works | Typical failure |
|---|---|---|
| Direct Connect | Quicken connects to the bank directly, often on a paid or enrolled service | Credentials or enrollment lapse, or the bank retires the service |
| Express Web Connect and Express Web Connect Plus | An aggregation service in the middle collects the data on a schedule | Reauthorization prompts, delays of a day or more, and connection errors after a bank platform change |
| Web Connect | You download a QFX from the bank and import it yourself | The bank stops offering the download, or only offers a short date range |
Web Connect is the one worth understanding, because it is the fallback that always works. A genuine QFX file has to come from the bank, since Quicken checks for a bank-issued institution tag no converter can produce, so a statement stands in through the CSV import instead. The full walkthrough sits on the convert bank statement to Quicken page.
If Quicken is showing you a specific code rather than silence, start there instead: the Quicken connection errors reference decodes every OL and CC code and points to the fix that matches the family it belongs to.
Chase accounts are on an aggregated connection, so a break usually shows up as a reauthorization prompt or a CC error rather than a login failure. Reauthorize from the account settings first and make sure every Chase account you hold is checked in the permission screen, because leaving one unchecked drops it from the feed. Chase is also the bank with the fewest fallbacks, having retired Direct Connect for all accounts back in October 2022, and it is a frequent source of the OL-221 error where the QFX Chase generates is itself malformed. The dedicated Chase not downloading to Quicken guide covers both cases in order. Older periods can be rebuilt from the PDF statements on the Chase bank statement converter page.
Bank of America connections tend to fail after a security or platform change on the bank side, and the symptom is an update that completes with no new activity. Deactivating the account for online services and reconnecting, then carefully linking to the existing register instead of creating a second account, clears most of these. Anything that fell in the gap while the connection was broken will not backfill, so convert those statements and import them. The dedicated Bank of America not downloading to Quicken guide walks through the Express Web Connect Plus migration step by step.
Both are large enough that an outage on their side affects many users at once, which is worth ruling out before you change anything in your own file. If other accounts in Quicken update normally on the same day, the problem is that institution, not your setup or your data file. Waiting is reasonable for a day or two. Beyond that, importing statements keeps the register current while the connection gets sorted out. Wells Fargo has its own wrinkle, because it is migrating accounts to Express Web Connect Plus while keeping Direct Connect alive, and its download window only reaches back so far. The Wells Fargo not downloading to Quicken guide covers that migration and the 90 day limit in detail. Capital One fails differently: it runs on an aggregated sign in with no Direct Connect to fall back on, and its recurring problem is a reauthorization prompt that loops instead of completing, which the Capital One not downloading to Quicken guide walks through fix by fix. American Express is the case where the usual advice actively backfires: it has moved entirely onto Express Web Connect Plus with a reauthorization roughly every 90 days, and Quicken states plainly that you should not deactivate and reactivate those accounts while completing the reauthorization, so American Express not downloading to Quicken sets out the correct order to work in. Fidelity is the outlier of the group, because its HSA accounts are not a connection problem at all: Quicken support has explained that Fidelity sends HSA data without the transaction description Quicken requires, so no amount of reconnecting will ever populate them, and its NetBenefits 401(k) side is a separate institution entry that fails on its own terms. The Fidelity not downloading to Quicken guide separates the four Fidelity account types and says which fixes apply to each.
Investment connections are the least forgiving because the download carries positions and cost basis as well as cash activity, so a partial failure often looks like missing transactions rather than an error. Check whether the account is still linked for downloads at all, then reauthorize. For statements a broker publishes as PDF only, the investment statement to OFX converter pulls the dated cash activity out so the account can be brought current.
Convert the statements that cover the gap, then import the CSV with File, File Import, Banking Transactions, From (.CSV) File. Point it at the account that already exists rather than letting Quicken create a new one. A CSV import does not match against what is already in the register, so trim the file to the missing dates, starting the day after the last transaction Quicken has. Review the accepted list before you finish, and reconcile against the statement closing balance to prove nothing is missing.
Usually not. Once a connection has reported a date range, it does not send that range again, and most connections only reach back a limited window in the first place. That is the practical reason to import statements rather than wait: the missing weeks are not queued up somewhere waiting to arrive. Fix the connection so future activity flows, and rebuild the gap from statements in the same sitting.
In most cases the bank connection needs reauthorizing, the account is on a connection method the bank changed, or the activity was already marked as downloaded so it will not be sent again. Check those three first, then whether the account is still activated for online services. If the update reports success but nothing arrives, the connection is working and the data range is the problem.
A sudden stop for one institution while other accounts keep updating almost always means the bank changed something: a platform migration, a new security requirement, or a retired connection type. Deactivate that account for online services and reconnect it, linking to the existing register rather than creating a new account.
Use Update Now on the individual account from the gear icon in the register instead of running One Step Update across everything. That targets one connection and surfaces the specific error rather than rolling it into a general update. If it still returns nothing, the transactions have already been sent once and will not be re-downloaded.
Almost never. Connections only reach back a limited window and will not resend a date range they have already delivered, so reconnecting restores future downloads but leaves the gap. The reliable way to fill it is to convert the statements covering those weeks and import them as a CSV file.
Both point at the connection layer between Quicken and the bank rather than at your data file, which is why deleting and rebuilding the file does not help. They commonly appear after a bank changes its online banking platform. Retry the next day, and if the error persists, deactivate the account for online services and set the connection up again.
Not directly. Quicken imports QFX, QIF, and CSV depending on the version, but it has no way to read a PDF. Converting the statement to CSV first gives Quicken a file its banking transactions import accepts, with dates, descriptions and signed amounts in their own columns.
It depends on the bank and the connection type, and roughly 90 days is a common limit, with some institutions offering less. That window is why a feed that has been broken for a couple of months cannot be recovered by fixing the connection alone. Statements go back years, which makes them the dependable source for older activity.
It can. A QFX downloaded from your bank carries transaction IDs that Quicken matches against the register, but a CSV import does not match existing transactions, so any overlap comes in twice. Import only the dates the feed missed, then reconcile to the statement closing balance afterward.
PDF statements into Quicken for Mac through its CSV import.
The Bank of America Express Web Connect Plus feed, fixed.
The Chase feed, the OL-221 error, and no Direct Connect.
The Capital One reauthorization loop, and picking the right entry.
Amex, the 90 day reauthorization, and why not to deactivate.
Why Fidelity HSA and NetBenefits accounts never update.
Decode any OL or CC error code and its matching fix.
The full walkthrough for importing a statement into Quicken.
Get a PDF statement into Quicken the way that works.
Brokerage and retirement statements into importable activity.
Get started converting bank statements to OFX.
USD
per month
per month
$294 charged today
Choose speed vs accuracy when extracting
| Base AI Faster | 2,500 pages |
| Pro AI Best accuracy | 500 pages |
Scale statement conversion with bulk upload, custom templates and reports.
USD
per month
per month
$894 charged today
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
per month
$ charged today
Choose speed vs accuracy when extracting
| Base AI Faster | pages |
| Pro AI Best accuracy | pages |
