QBO bank feeds break. Not always; not even often, but reliably enough that every bookkeeper has a story. The connection that worked fine for two years suddenly stops syncing. New transactions don't appear. Or worse: they appear duplicated. Or they appear three days late.
When this happens, the instinct is to blame QuickBooks. Sometimes that's right. More often, the root cause is on the bank side — an authentication change, a security policy update, or a Plaid/Yodlee aggregator issue between QBO and the bank.
This is the order to diagnose, from working bookkeepers who's worked through this on most major US banks.
The short version: Most bank feed failures are auth-related — either an expired connection, a new bank security policy, or MFA changes. Try the disconnect-and-reconnect first, then check the bank's online portal for any "account security update required" messages. If those don't fix it, you may be looking at a multi-week wait while QBO and the bank sort out an integration issue.
Step 1: Confirm the symptom
"Bank feed not working" can mean different things. Identify which:
- No transactions are appearing at all. The connection is fully broken.
- Some transactions are appearing but they're days late. Sync is running but slow.
- Transactions are appearing twice. Duplicate sync (often after a reconnection).
- Old transactions disappear or change retroactively. Rare but possible — usually a Plaid resync issue.
- You get an error message in QBO. "Bank update needed" or similar — QBO is telling you it failed.
The fix differs depending on which one you're seeing.
Step 2: Check the bank's online portal first
Before touching QBO, log into the bank's online portal as the client. Look for:
- A "you need to update your password" prompt
- A "new device verification" requirement
- A notice about updated terms of service or security policies
- Multi-factor authentication that's been enabled or changed
Any of these will break the QBO connection silently. The bank doesn't tell QBO that auth changed; QBO just stops getting data.
If you find one of these, complete whatever the bank is asking for (update the password, complete MFA, accept new terms). Then go to QBO and disconnect/reconnect the bank account — this triggers QBO to re-authenticate.
Step 3: The disconnect-and-reconnect
If the bank's portal looks normal but the feed is still broken, the standard fix is to disconnect and reconnect:
- In QBO, go to Bookkeeping → Transactions → Bank transactions
- Click the pencil/edit icon next to the broken bank account
- Choose Edit account info
- Check "Disconnect this account on save"
- Save
- Then click Link account and reconnect, entering credentials fresh
This forces QBO to re-establish the connection through its aggregator (Plaid for most banks, Yodlee for some). New auth tokens, fresh sync.
Heads up: Disconnect-and-reconnect sometimes causes a "re-download" of the last 30-90 days of transactions, which can create duplicates if those transactions were already in QBO. Match the new sync against existing transactions before accepting them.
Step 4: If reconnect doesn't fix it
If you disconnected and reconnected and the sync still isn't working, the issue is one level deeper. Possibilities:
A. The bank's aggregator integration is broken
QBO uses Plaid (or Yodlee for some banks) to pull data from financial institutions. When a bank changes their backend, the aggregator needs to update its integration. This can take days or weeks.
To check: go to status.plaid.com and search for your client's bank. If there's an active incident, you're waiting for Plaid to fix it.
B. The account has too much history
QBO sometimes refuses to reconnect accounts with very large transaction volumes (10,000+ transactions). The error message is rarely clear about this. The workaround is to set the reconnection start date to "30 days ago" instead of the default longer window.
C. Wrong bank product type selected
Banks sometimes have multiple "QuickBooks" entries in QBO's bank search. Chase shows up as "Chase Bank," "Chase Business Banking," "JPMorgan Chase," etc. Selecting the wrong one can lead to a connection that "succeeds" but doesn't actually pull data.
The fix: disconnect, re-search the bank by name, and read the descriptions carefully. Pick the one labeled for your client's specific account type (business vs personal).
Step 5: When to fall back to PDF imports
If the bank feed isn't fixable in a reasonable timeframe, switching to PDF imports is the pragmatic move. The workflow:
- Pull the monthly statement PDF from the bank's online portal
- Convert it to a CSV using a bank statement converter
- Upload the CSV via QBO's Upload from file workflow
This is more manual than a live feed, but it's reliable. If a bank feed has been broken for two weeks, you're better off doing one PDF import per month than waiting indefinitely.
For PDF imports when the feed is broken: YourStatementConverter converts PDFs to QBO-ready Excel with auto-reconciliation. 25 pages free, no credit card — useful as a fallback when bank feeds fail. See our full PDF-to-QBO walkthrough for the step-by-step.
Common causes by bank
Chase
The most common cause is Chase's periodic security policy updates, which silently invalidate the QBO connection. The fix is almost always to log into Chase's portal, complete any pending security verification, then reconnect in QBO.
Wells Fargo
Wells Fargo business accounts sometimes require their "Treasury Management" portal authentication, which QBO's Plaid integration doesn't always handle cleanly. If you're seeing repeated failures on a Wells Fargo business account, check whether the client has Treasury Management enabled.
Bank of America
BoA's SafePass MFA can break QBO connections when the client changes their phone number or the SafePass device. If the connection broke around the same time as a phone change, that's almost certainly the cause.
Smaller banks and credit unions
Many smaller institutions have unreliable QBO integrations because they're served by aggregators that don't prioritize them. If you're processing for a client at a small credit union, expect periodic outages and have a PDF-import workflow ready.
When the bank just doesn't connect at all
If you've never been able to connect a particular bank to QBO, the bank may not be supported. Check QBO's bank search results carefully — if your client's bank isn't there, the only path is PDF imports.
For ongoing PDF-only workflows, see our guide to importing PDF bank statements into QBO.
The hard truth about bank feeds
Bank feeds are convenient when they work and a tax on your time when they don't. For mission-critical client accounts, having a tested PDF-import fallback is worth more than relying on the feed alone. The bookkeepers who get burned are the ones who assume the feed will keep working forever.
For deeper context on PDF workflows, see our catch-up bookkeeping playbook.