Xero bank feed status: down, late, or never there in the first place
Xero publishes feed status in three separate places and they answer three different questions. The Xero status page tells you whether Xero itself is up, the bank feed disruptions page tells you whether your bank is in a known outage, and View Status Updates on the bank account tells you what Xero thinks about your feed in particular. This page isn't a live status board and can't be, so if you're checking right now, open the two Xero pages linked below first.
Three places to check, in this order
Whether the platform itself is having an incident, and where Xero posts them while they're open. If Xero is degraded, feeds are usually among the first things to show it. It won't name individual banks, which is what the next one is for.
The significant feed outages Xero currently knows about, by region. Xero's status page points here for feed problems specifically, so a quiet status page alongside a listed disruption is the normal combination rather than a contradiction.
The per-account view, and the only one of the three that knows anything about your connection rather than everyone's. In Xero, open the Accounting menu, select Bank accounts, click the menu icon next to the account, then choose View Status Updates.
People usually check one of these, get an all-clear, and conclude the problem must be at their end. The three cover different ground, and a green light on one says nothing about the other two. Two minutes spent going through all three tells you whether this is yours to fix or somebody else's to wait out.
If your bank is listed on the disruptions page, reconnecting won't help and can make things worse, because you'll be reauthorising into an outage and losing a working connection in the process.
Late is not the same as down
A good share of what gets reported as a broken feed is a feed working exactly as documented. Xero's own bank feeds page says transactions appear in the account roughly every twelve hours, and that you can refresh a feed by hand to pull the latest lines in rather than waiting for the next cycle. An account that looks a day behind first thing in the morning is often just an account that hasn't had its second update yet.
Before you decide a feed has stopped, note the date of the last statement line that did arrive. A feed that delivered yesterday and nothing today is late. A feed whose last line is from three weeks ago has stopped, and those two need completely different responses.
- About bank feedsXero on how often feed transactions arrive and how to refresh a feed without waiting for the cycle.
Everything is green and the feed still isn't delivering
This is the common case, and it's the one the status pages are worst at, because most feeds don't stop for a reason Xero would ever publish. UK open banking consent expires every ninety days and has to be reauthorised, which is a regulatory requirement rather than a fault, so nothing anywhere will call it an incident. A pending set of terms or an unread security alert at the bank will hold a feed silently until somebody logs into the bank directly and clicks through it. And an account that was never eligible for a feed has no status to report, because there's nothing there to be up or down.
The order to work through those in, and what actually fixes each, is the whole subject of our guide to a Xero bank feed that has stopped working. The short version is that reconnecting is the reflex and it only addresses one of the four causes.
What none of the three status pages tell you
An outage gets marked resolved when the connection starts working again, and that is not the same thing as your ledger being complete. A restored feed runs forward from the moment it's restored. The stretch between the day it stopped and the day somebody noticed doesn't come back on its own, and no status page will ever mention it, because from Xero's side nothing is wrong any more.
That gap is why an account still won't reconcile after a resolved incident and a successful reconnect. The transactions exist, they're on the statement the bank will happily give you, and they're simply not in Xero. Xero's documented answer is the manual import, which is a per-file job with no running-balance check and nothing confirming the export covered the whole period.
Accounts that will never have a status, because they never had a feed
Worth ruling out early, because it saves a lot of checking: plenty of accounts can't hold a Xero feed at all. Personal accounts doing business duty, accounts at banks with no agreement in your region, foreign currency accounts held abroad, and most of the platforms that hold money without being a bank. Searching a status page for those is time spent confirming an absence.
For those, the question isn't whether the feed is down. It's what to do about an account whose transactions will only ever exist on a statement, permanently, every month.
Closing the gap the status page leaves behind
However a feed stopped, the residue is the same shape: the bank has the transactions, the statement has the transactions, and Xero doesn't. StatementClear posts those statements into Xero through the Bank Feeds API, so the lines land the way feed lines land rather than as another imported file. Duplicates are skipped on upload, which is what makes it safe to post over a period the native feed partly covered, and the running balance is recomputed and checked before anything reaches the ledger.
That matters most in exactly the situation this page describes, because a gap caused by an outage almost always overlaps at the edges with what the feed did deliver, and posting the overlap twice is the thing you're trying to avoid.
- Import a CSV bank statementXero's documented manual fallback, its accepted formats, and how it treats lines it has seen before.
- Bank Feeds API overviewThe interface a posted feed line arrives through, and why that isn't the same as an imported one.
A restored feed won't post the weeks it missed. You still can.
StatementClear posts the statements you already export into Xero as live bank feed lines, deduped and balance-checked before anything reaches the ledger.