Check Xero status, then refresh or reconnect the affected bank connection: those two steps resolve most feed interruptions. Re-authentication problems and platform disruptions account for the bulk of reported cases. After reading this, you will know how to check status, reconnect safely, handle feed-specific quirks, import a backup statement without creating duplicates, and know exactly when to call in outside help.
TL;DR:
- Most feed issues are caused by expired bank authorizations or platform outages, which can often be resolved by re-authorizing or checking Xero status pages.
- Direct bank feeds typically delay transactions by one or two days during API outages, while third-party connectors like Yodlee or Plaid require manual refreshes or re-linking.
- Browser, cookie, MFA, or permission issues on the local device can block reconnects, so clearing caches or testing in incognito mode is recommended before contacting support.
- Manual CSV or OFX imports can temporarily keep books current but require careful exclusion of duplicates to prevent reconciliation problems.
- Running weekly feed status checks and reauthorizing connections before troubleshooting helps maintain accurate, current books, reducing month-end stress.
Table of Contents
- How to check Xero and bank status before troubleshooting
- Step-by-step: refresh, reconnect, and re-authorize the bank connection
- Feed-type troubleshooting: direct feeds vs third-party connectors
- Local-device causes: browsers, cookies, MFA, and permissions
- Manual import: safe CSV or OFX import and avoiding duplicates
- When to escalate: what to gather and who to contact
- Tolliver Team checklist and best practices for bookkeeping workflows
- Why timely bank feeds matter for small-business bookkeeping
- How Tolliver Team can help with Xero setup and feed cleanup
- FAQ
- Sources
How to check Xero and bank status before troubleshooting
Before you touch any settings, rule out a platform-wide or bank-side outage. Xero publishes known issues on its Disruptions to bank feeds and status page, and the separate Xero Status site tracks the health of core products and regional services.
- Open Xero Status first to confirm the core platform is running normally.
- From within Xero, go to Accounting, then Bank accounts, then View Status Updates to see feed-specific notices.
- A feed marked “late” usually means the import is delayed, not broken, so give it a few hours before assuming a fault.
If the status pages show no issues and your feed is still stuck, the problem is almost always on the connection side, which is where the next step comes in.
Step-by-step: refresh, reconnect, and re-authorize the bank connection
Most feed failures trace back to an expired consent, not a broken integration. Open banking rules require banks to re-confirm your authorization periodically, and Xero’s guide to renewing your bank connection walks through the exact screens.
- Go to Accounting, then Bank accounts, and find the affected account.
- Click the Manage Account dropdown next to that feed.
- Select Refresh Connection first. If the feed still shows an error, select Reconnect or Renew Connection instead.
- Log in with your bank credentials when prompted and approve the new consent request.
- Wait for Xero to confirm the connection, then check whether missing transactions reappear over the next import cycle.
Xero typically requires periodic re-authorization for open banking connections, and most banks send a reminder email or in-app notice before the consent lapses. If you reconnect and nothing changes within a day, the account link itself may need to be rebuilt rather than just refreshed.
Pro Tip: Reconnect first, then wait a full import cycle before trying anything else. Stacking fixes on top of each other makes it hard to tell which one actually worked.
Feed-type troubleshooting: direct feeds vs third-party connectors
Not every bank connection behaves the same way, and the fix depends on which type you have. Xero connects directly with many US banks and uses third-party connectors like Yodlee when a direct feed isn’t available.
- Direct feeds: delays are usually caused by a bank-side API outage, and transactions often post a day or two behind your actual bank statement, which is normal timing rather than a fault.
- Yodlee and other third-party feeds: these often need a manual refresh inside the Manage Account menu, and you may see errors that reference the connector by name rather than your bank.
- Plaid-based feeds: expect a re-linking flow that asks you to log in again and may trigger a fresh multi-factor prompt, especially after a password change on the bank’s side.
Knowing which type you’re dealing with saves time, since a direct feed outage needs patience while a third-party connector error usually needs a manual refresh.
Local-device causes: browsers, cookies, MFA, and permissions
Sometimes the block isn’t the feed at all, it’s the device you’re using. Clear your browser’s cookies and cache, or try a private or incognito window in a different browser, to see if the reconnect screen behaves differently.
- Clear cookies and cache, or open an alternate browser, to rule out a stuck login session.
- Check whether multi-factor authentication, such as Xero Verify, an authenticator app, or a backup code, is blocking the reconnect step, since an expired code will silently fail the login.
- Confirm your Xero user role has permission to manage bank connections, since a standard user role can sometimes be restricted from reconnecting feeds.
Pro Tip: If reconnecting fails only in one browser, it’s a device issue, not a Xero or bank issue, so test in a second browser before contacting support.
Manual import: safe CSV or OFX import and avoiding duplicates
When a feed can’t be fixed quickly, a manual import keeps your books current without waiting on the connection; consider using a bank statement loan calculator to explore cash flow options during feed interruptions. Xero’s CSV import guide supports CSV, OFX, and QIF files and attempts to flag duplicates automatically during the process.
- Download a statement covering only the missing date range directly from your bank’s website.
- In Xero, go to the bank account and choose Import a Statement, then upload the CSV or OFX file.
- Review the import preview carefully and exclude any lines that overlap with transactions already in Xero.
- Complete the import, then check the account balance against your actual bank statement to confirm it matches.
If duplicates slip through anyway, open the Bank statements tab and look for lines marked “User,” since those are the manually imported ones you can safely delete without disturbing the original feed data. Avoiding overlapping date ranges in the first place is far easier than cleaning up duplicates afterward.
When to escalate: what to gather and who to contact
If status checks, reconnecting, and device checks all fail, it’s time to loop in support or your bank. Collect your organization name, the exact bank account name, the last successful import date, and screenshots of any error message before you reach out, since that information speeds up every support conversation.
- Contact your bank when you see bank-side API errors or repeated multi-factor rejections during reconnect.
- Contact Xero support when the issue matches a known disruption or looks like a platform-side rate limit rather than a bank problem.
- Bring in an experienced bookkeeper or Xero advisor when reconciliations have piled up or duplicate entries have already affected your account balances.
Tolliver Team checklist and best practices for bookkeeping workflows
A safe troubleshooting order protects your audit trail: check status first, then change one variable at a time, reconnecting before touching browser or MFA settings, and treat manual import as the last resort rather than the first move. Skipping steps or changing several things at once makes it harder to know what actually fixed the problem, and harder to explain later if a reviewer asks.
Weekly feed checks catch a lagging connection before it turns into a month-end scramble, and reconciling frequently rather than waiting until period end keeps small errors from compounding into a bigger cleanup. We generally step in to remove duplicate statement lines and track down phantom discrepancies once a feed outage has already created a backlog, since untangling weeks of unreconciled transactions takes a different kind of patience than a quick reconnect.
Pro Tip: Run a feed status check every Monday morning. It takes thirty seconds and almost always beats discovering a three-week gap on the 28th of the month.
Why timely bank feeds matter for small-business bookkeeping
A bank feed that runs on time is what makes frequent reconciliation possible in the first place. Reconcile weekly instead of monthly and small coding errors get caught while they’re still small, not buried under a quarter’s worth of transactions. That habit also makes tax season less stressful, since clean, current books mean fewer surprises when it’s time to file.
— Tolliver Team
How Tolliver Team can help with Xero setup and feed cleanup
We work exclusively in Xero, so feed and reconnection issues are something we handle routinely rather than as a one-off fix. We offer no-cost Xero migration, monthly bookkeeping with ongoing reconciliation, and cleanup work for accounts where duplicate imports or a stalled feed have left gaps.
If your feed problems have already caused a backlog, our catch-up bookkeeping service is built for exactly that kind of gap.
- Tell us your organization size and number of connected bank accounts so we can scope the work accurately.
- Share the date of your last successful reconciliation so we know how far back cleanup needs to go.
- Reach out through our site for a fast estimate on setup, migration, or cleanup.
FAQ
Is Xero having problems with bank feeds?
Bank feed disruptions happen periodically and are posted on Xero’s disruptions and status page as they occur. Checking that page, along with Xero Status, is the fastest way to confirm whether a current issue is platform-wide rather than specific to your account.
Is Xero having an issue today?
The quickest way to find out is to check Xero Status directly, since it reflects the current operational state of core products and regional services. If status shows all clear, a feed problem you’re seeing is more likely tied to your specific bank connection.
Why do accountants not like Xero?
Opinions on accounting platforms vary widely among bookkeepers and accountants, and dissatisfaction usually centers on feed reliability, migration friction, or feature gaps compared to other platforms rather than a single universal complaint. As a Xero Silver Partner, we work exclusively in Xero and find that most feed frustrations trace back to expired bank consent rather than the platform itself.
Why is my Tide Xero bank feed not working?
Third-party and direct bank feeds can fail for the same core reasons: an expired authorization, a bank-side outage, or a local browser or device issue. Start by checking Xero Status, then refresh or reconnect the account through the Manage Account dropdown, following the same renewal steps Xero outlines for any open banking connection.
What should I do if my Xero bank feed keeps creating duplicates?
Open the Bank statements tab and look for lines marked “User,” which indicate a manually imported transaction rather than one pulled from the live feed. Delete those duplicate lines rather than reconciling them, and double-check your CSV import preview next time to exclude any overlapping date range before confirming the import.