You open QuickBooks to do the month and the last transaction is from eleven days ago. The feed has not thrown an error, the account still shows as connected, and nothing obvious has changed at the bank. This is the most common way a bank feed fails — quietly.
A QuickBooks bank feed usually stops for one of five reasons: the bank connection needs re-authorisation, the bank has changed its login or security process, there is a temporary outage at the bank or aggregator, the account was disconnected and reconnected creating a gap, or the transactions arrived but sit unmatched rather than missing. Identify which before you disconnect anything.
Feed stopped and month-end is due? WhatsApp us and we will work out which of the five it is.
Quick Summary — Five Causes
| Symptom | Likely cause | First step |
| Feed stops, no error | Authorisation expired | Update sign-in from Banking screen |
| Error on refresh | Bank changed login or security | Reconnect and re-authenticate |
| Some accounts work, one does not | Account-level issue at the bank | Check that account separately |
| Gap in dates after reconnecting | Feed only pulls a limited history | Upload the gap manually |
| Feed works, transactions not visible | Already matched or excluded | Check For Review and Excluded tabs |
💡 TaxKitab Tip :
Before you disconnect the account, check the last successful update date and write it down. The single most common way a small problem becomes a large one is disconnecting and reconnecting without noting where the feed stopped — the new connection pulls only a limited history, and the gap between the old last date and the new first date is invisible until reconciliation fails weeks later. Ninety seconds of noting the date saves a day of manual entry.
Check This Before Anything Else
Open the Banking or Transactions screen and look at the last update date for each account, not just the one you noticed.
Then open the For Review tab and the Excluded tab. Transactions that were downloaded and then excluded, or that auto-matched to existing entries, are not missing — they are just not where you were looking. This accounts for a surprising share of reported feed failures.
If the dates are current and the transactions are in Excluded, the feed is fine and the problem is a rule or a matching setting.
Authorisation That Has Quietly Expired
Banks require periodic re-authorisation of third-party access, and the expiry rarely announces itself. The connection still appears active, it simply stops returning data.
The fix is to update the sign-in from the Banking screen rather than removing and re-adding the account. Updating preserves the connection history; removing it does not.
Where the bank has introduced a new security step since you connected — an additional verification, an app-based approval — the re-authorisation will walk you through it. Have access to whatever the bank now requires before you start, because the flow times out.
The Bank Changed Something
Banks migrate systems, rename their online banking, and change the login page. Any of these breaks an existing connection, and the aggregator behind the feed has to catch up.
The signal here is an explicit error rather than silence. Search the exact error text rather than guessing — QuickBooks error codes on banking are specific and the fix differs between them.
If your bank recently changed its online banking, expect the feed to need reconnecting even if nothing looks different to you.
Temporary Outages
Not everything is your problem. Aggregator and bank-side outages happen, typically resolve within a day or two, and produce no error beyond the feed not updating.
The way to tell: if multiple accounts at the same bank stopped on the same date, it is not your configuration. Give it twenty-four hours before intervening. Reconnecting during an outage often makes things worse by creating a history gap.
The Gap Nobody Notices
This is the expensive one.
When you disconnect and reconnect an account, the new connection pulls only a limited window of history — typically a few weeks, sometimes less. If the feed had been down for longer than that window, the intervening transactions never arrive.
Nothing flags this. The feed looks healthy, the recent transactions are there, and the gap sits in the middle of your ledger until the bank reconciliation refuses to balance.
The fix is to identify the gap by comparing your last fed transaction against your bank statement, then import that period manually using a CSV from the bank.
When to Stop and Import Manually
If the feed has been down more than a few weeks, or the bank connection is unreliable, manual import is the faster route.
Download a CSV or QBO file from your bank for the missing period and upload it through the Banking screen. Check the date range against what is already in QuickBooks first, because duplicate imports are harder to clean than missing transactions.
Some accounts — particularly business credit cards at smaller banks — are genuinely better handled by monthly manual import than by an unreliable feed. There is no prize for keeping a feed that breaks every month.
After It Is Working Again
Reconcile the affected period before moving on. A feed that has been down and restored is exactly the situation that produces both gaps and duplicates, and the reconciliation is what surfaces either.
Then check that your bank rules still apply correctly to the restored transactions, because a reconnected account sometimes loses rule associations.
Frequently Asked Questions
Why did my feed stop without showing an error?
Most often expired authorisation. Banks require periodic re-approval of third-party access and the connection stays visible after it lapses.
Should I disconnect and reconnect the account?
Try updating the sign-in first. Disconnecting limits how much history comes back and can create a gap in your ledger.
Transactions are missing from the middle of a month. Why?
Usually a reconnection gap. The new connection pulled only recent history and the earlier period never arrived. Import it from a bank CSV.
Multiple accounts stopped on the same day. Is that me?
Probably not. Accounts at the same bank failing together points to a bank or aggregator outage. Wait a day before changing anything.
The feed works but I cannot see the transactions?
Check the Excluded tab and whether they auto-matched to existing entries. Downloaded and excluded is not the same as missing.
Is a manual CSV import acceptable long term?
Yes. For accounts with unreliable feeds, a monthly import is often more dependable than a connection that breaks repeatedly.
How long does QuickBooks bank feed take to update?
Most banks update transactions with QuickBooks about every 24 hours, although timing can vary by bank and connection. If a transaction has not appeared, you can manually select Update from the Bank transactions screen. QuickBooks notes that transactions may sometimes take up to 48 hours to appear. Pending transactions are not downloaded until they are posted by the bank
How do I manually upload missing bank transactions into QuickBooks?
If transactions are missing from the bank feed, download the relevant period from your bank in a supported file format such as CSV or QBO, then upload it through the Banking or Transactions area in QuickBooks. Before importing, compare the date range with transactions already in QuickBooks to avoid duplicates. After the import, review, match and reconcile the transactions.
Will disconnecting and reconnecting QuickBooks bank feed delete transactions?
Disconnecting a bank feed does not normally mean that transactions already recorded in QuickBooks are automatically deleted. The bigger risk is losing the connection to the previous feed history and creating a gap when the account is reconnected. Before disconnecting, note the last successful feed date and check which transactions have already been downloaded, matched or excluded.
References
- QuickBooks Online documentation on bank connections, updating sign-in details and manual upload
- Open banking re-authorisation requirements applied by banks to third-party access
⚠️ Bank connection behaviour, error codes and history limits differ by bank and by region, and change with platform releases. Check current guidance for your own bank and plan.
Related Reading:
Xero Bank Reconciliation Not Matching: The Usual Causes · Undeposited Funds in QuickBooks: What It Is and How to Clear It · Month-End Close Checklist for a Small Business
Call or WhatsApp: +91 7448200422 Email: info@taxkitab.com See our Accounting & Bookkeeping service, or explore Global Desk if your business sits outside India.
