QuickBooks bank feeds not working: causes & fixes.
“Bank feeds not working” covers a cluster of symptoms — transactions that stop importing, a bank connection that shows disconnected, duplicate or missing downloaded transactions, or a bank that suddenly needs to be reconnected. Most cases trace to a handful of causes, and the self-fix steps below work in order of likelihood. Below that: when a recurring disconnect or months of unreconciled transactions means it’s a ProAdvisor call. Independent firm, not affiliated with Intuit Inc.
“QuickBooks bank feeds not working” means new transactions aren’t flowing from your bank into QuickBooks the way they should — the feed has stopped updating, the connection shows as disconnected, transactions are arriving duplicated or not at all, or the bank is asking you to re-authenticate. The most common single cause is a bank connection that needs to be re-authenticated (often after a bank-side login or security change), and many cases clear by manually updating the feed and reconnecting the account. Bank feeds exist in both QuickBooks Online and QuickBooks Desktop; the fixes differ slightly but follow the same order of likelihood.
Reference maintained by the Certified QuickBooks ProAdvisor team at TechBrot Inc., an independent firm — not Intuit, and not Intuit’s official software support. Not affiliated with Intuit Inc.
Bank feeds not working, in five questions.
What does “QuickBooks bank feeds not working” mean?
New transactions aren’t flowing from your bank into QuickBooks the way they should — the feed has stopped updating, the account shows as disconnected or asks you to sign in again, transactions are downloading twice or appear missing, or the bank is forcing a re-authentication. It happens in both QuickBooks Online and QuickBooks Desktop.
Why did my QuickBooks bank feed stop working?
Most often the bank connection needs to be re-authenticated — usually after the bank changed its login, security, or feed provider. Other common causes: a temporary outage on the bank or aggregator side; duplicate or excluded transactions clogging the feed; a browser cache or extension issue for QuickBooks Online; or an account-mapping mismatch so downloads land in the wrong register.
How do I fix bank feeds in QuickBooks myself?
In order of likelihood: re-authenticate / reconnect the bank connection; run a manual update or refresh of the feed; check for a bank-side notice or outage; clear the browser cache (or try a private window) for QuickBooks Online; review the excluded and duplicate lists; and if it still won’t hold, disconnect and re-link the account. Re-authenticating and manually updating clears a large share of cases.
When do bank-feed problems need a ProAdvisor?
When the feed keeps disconnecting after you reconnect it; when months of transactions are unreconciled, duplicated, or missing; when the feed broke during a migration between QuickBooks versions or platforms; or when reconciliation no longer ties to the bank statement. That’s bookkeeping damage a reconnect can’t fix — it’s a file review and a focused diagnostic or cleanup.
Is a broken bank feed a QuickBooks problem or a bank problem?
It can be either, and the fix differs. A connection that needs re-authentication, an outage, or a bank login change is on the bank or aggregator side — sometimes only the bank or Intuit can resolve it. Duplicates, missing dates, miscategorized downloads, and a reconciliation that won’t tie are inside your books — that’s the operational work an independent ProAdvisor firm does.
“Bank feeds not working,” plainly.
A bank feed is the live connection between your bank or credit-card account and QuickBooks that downloads transactions automatically so you don’t key them in by hand. When people say the feed “isn’t working,” they usually mean one of a few things: new transactions have stopped importing or updating; the account shows as disconnected or asks you to sign in again; transactions are downloading twice (duplicates) or appear to be missing for a date range; or the bank is forcing a re-authentication after changing its own login or security.
The good news is that most of these trace to a short list of causes, and the self-fix steps below address them in order of likelihood — re-authenticating the connection and manually updating the feed clears a large share of cases. What the steps can’t fix is the bookkeeping damage a broken feed leaves behind: weeks or months of missing, duplicated, or miscategorized transactions, and a reconciliation that no longer ties. That part is a ProAdvisor job, not a reconnect. And if the underlying issue is your Intuit account, login, or an Intuit-side outage, that’s Intuit’s to resolve — not something we can reach.
Common causes, in order of likelihood.
The self-fix steps address these in the same order — so working through them in sequence resolves most broken feeds efficiently.
Cause 01 · The connection needs re-authentication
The single most common cause. Banks periodically require you to sign in and re-authorize the QuickBooks connection — often after a password change, a new multi-factor step, or a security update on the bank’s side. Until you re-authenticate, the feed shows connected-but-stalled or asks you to sign in again, and no new transactions arrive.
Cause 02 · The bank changed its login or feed provider
Banks update their online-banking login, security questions, or the data provider behind the feed. When that happens the old connection breaks and has to be re-established — sometimes by reconnecting, sometimes by choosing the bank’s new connection option in the list.
Cause 03 · A temporary outage on the bank or aggregator side
Feeds depend on the bank’s systems and the aggregator that brokers the data. A maintenance window or outage on either side stops new transactions until it clears. This one usually resolves on its own — check for a notice before deeper troubleshooting.
Cause 04 · Duplicate or excluded transactions
Transactions that were downloaded twice, manually entered and then re-imported, or moved to the excluded list can make the feed look broken — entries appear missing, doubled, or stuck in review. The data is arriving; it’s the duplicate and excluded handling that needs cleaning up.
Cause 05 · A browser, cache, or extension issue (QuickBooks Online)
For QuickBooks Online, a stale browser cache, a blocking extension, or a sign-in conflict can stop the feed from updating in the interface even though the connection is fine. Clearing the cache or trying a private window often confirms and clears this quickly.
Less common · Less common: account-mapping mismatch or migration damage
Downloaded transactions mapped to the wrong account in QuickBooks, or a feed that broke during a migration between QuickBooks versions or platforms, can leave the register out of sync with the bank. These are where surface steps stop working and a file review is warranted.
How to fix bank feeds yourself.
Six steps, in order. Most feeds come back within the first two or three — if all six don’t resolve it, or the books are already behind, stop and get the file reviewed.
Re-authenticate the bank connection
Open the banking / bank feeds area, find the affected account, and choose the option to update sign-in info or reconnect. Re-enter your online-banking credentials and complete any multi-factor prompt the bank requires. This alone restores the feed in a large share of cases.
Run a manual update
Use the Update / Refresh option on the banking screen to pull transactions on demand rather than waiting for the automatic sync. If new transactions appear after a manual update, the connection is healthy and the automatic refresh just needed a nudge.
Check for a bank-side notice or outage
Before troubleshooting further, check whether the feed is paused for bank or aggregator maintenance — QuickBooks usually surfaces a notice on the account. If it’s an outage, the fix is to wait for it to clear; nothing on your end is broken.
Clear the browser cache (QuickBooks Online)
For QuickBooks Online, clear your browser cache and cookies for the QuickBooks site, or open it in a private / incognito window. If the feed updates there, a blocking extension or stale cache was the cause — disable extensions one at a time to find it.
Review excluded and duplicate transactions
Open the excluded list and the For Review tab and look for duplicates or entries that were wrongly excluded. Restore anything excluded by mistake and remove genuine duplicates — carefully, so you don’t delete real transactions — so the feed reflects reality again.
If it still won’t hold, disconnect and re-link the account
As a last self-fix step, disconnect the account from the feed and re-link it fresh, taking care with the “from” date so you don’t re-import transactions you already have. If the feed still won’t hold — or you’re now facing duplicates or unreconciled months — stop and get the file reviewed before the gap grows.
Feed keeps breaking, or months are unreconciled?
A Certified ProAdvisor reviews the file free, then fixes the feed and the books behind it — a focused diagnostic is typically a $1,200–$3,000 fixed-fee scope; cleanup runs $1,500–$15,000+ if the books are behind. Independent firm.
Three signals it’s a ProAdvisor call.
It keeps disconnecting
You reconnect the feed and it breaks again within days or weeks. A recurring disconnect points to an underlying connection or account-mapping issue that a one-time reconnect masks rather than resolves — and each break leaves another gap in the books.
Months are unreconciled or duplicated
The feed broke a while ago and now you’re looking at weeks or months of missing, doubled, or miscategorized transactions, with a reconciliation that no longer ties. That’s bookkeeping damage — cleanup work, not a reconnect.
It broke during a migration
The feed stopped working during a move between QuickBooks versions or platforms, or alongside other errors. That signals the register and the bank are out of sync at a deeper level — the moment to have the file assessed before the discrepancy compounds.
A Certified ProAdvisor fixes the feed and the books behind it.
Reconnecting a feed is the easy part. The work that actually restores trust in the numbers is everything the broken feed left behind: removing duplicate downloads without deleting real transactions, recovering the gap of missing dates, re-categorizing what came in wrong, and re-running reconciliation until each month ties to the bank statement again. A Certified QuickBooks ProAdvisor with active Online and Desktop certifications does that against a written scope and verifies the feed is stable before closing. Independent firm — not Intuit, and not Intuit’s software support; an Intuit account, login, or billing matter stays with Intuit.
Free
file review first — we look before we scope
$1,200–$3,000
typical fixed-fee diagnostic for a focused feed + reconciliation fix
Independent
Certified ProAdvisor firm — not Intuit, not Intuit’s software support
What people ask about broken bank feeds.
Is this Intuit’s official QuickBooks support?
Why are my QuickBooks bank feeds not working?
How do I reconnect a bank account in QuickBooks?
Why are bank transactions downloading twice (or missing)?
Is a broken bank feed a QuickBooks problem or a bank problem?
Does this affect QuickBooks Online and QuickBooks Desktop?
When should I stop self-fixing and call a ProAdvisor?
Can you reset my bank login or fix my Intuit account?
Feed keeps breaking, or the books no longer tie?
Self-fix didn’t hold? Get the file reviewed.
If the feed keeps disconnecting, you’re staring at months of duplicate or unreconciled transactions, or reconciliation no longer ties, the problem is in the books — not just the connection. Start with a free file review; from there a focused diagnostic is typically a $1,200–$3,000 fixed-fee scope, and a full cleanup runs $1,500–$15,000+ when the books are behind. Independent ProAdvisor firm, written scope before any work begins.