Xero bank feeds: what breaks and how to fix it

How the feed actually behaves

A bank feed is a pipe, nothing more. It moves transaction data from your bank into Xero on a schedule, usually once a business day. Most of the big Australian banks connect directly, which is the sturdiest option; some smaller institutions route through a third party data service instead, and a handful of accounts can't connect at all, so you're back to importing statements by hand. Which banks fall into which bucket changes over time, so treat Xero's own coverage list as the current word, not this article.

Here's the part people miss: a feed delivers data, it doesn't reconcile anything. Every line that lands still needs matching to an invoice or a bill, or coding to an account, by a person. The feed saves the typing. It doesn't do the thinking for you.

Getting the setup right from day one

Connect every account the business actually touches, not just the main transaction account. We still see files where the everyday account is connected and the business credit card isn't, so a chunk of spending sits outside the books until someone remembers it exists weeks later. Name each account in Xero the way your bank names it too, so nobody reconciles the wrong one by accident.

When a feed first connects, transactions usually start flowing from that point forward, not before. Older transactions need a separate statement import. Do that import before you start reconciling, otherwise you're left with a hole between your opening balance and the first transaction the feed actually delivered.

The gaps that never announce themselves

Feed problems don't send a warning. The books simply look normal while quietly leaving things out. These are the failures that turn up most often when we review a new file:

• A feed goes quiet for weeks after a bank security change, and nobody clocks it because other accounts are still ticking along fine
• Duplicate transactions creep in after a feed gets refreshed or repaired, overstating income or expenses if both copies end up reconciled
• A gap sits right at the switchover date, between the imported history and the first live transaction
• The bank issues a new card or account number and the old feed just keeps sitting there, dead, while nobody redirects it
• A feed gets connected to the wrong Xero account, so transactions pile up somewhere nobody is watching

Once you find a gap

Work out the date range first, using the balance check above. Download the statement for that period from your bank and import it manually. Xero will flag anything that looks like a duplicate of what's already there, but look at each suggestion rather than clicking through them; two identical direct debits on the same day happen all the time and are perfectly legitimate.

Duplicates run the fix in reverse: find out which copy is already reconciled, then remove the other one from the bank statement lines. Don't delete a reconciled transaction to tidy up a duplicate without checking what it was matched against first, or you'll orphan an invoice payment and end up with two problems instead of one.

Keeping a feed healthy

Feeds want light, regular attention rather than a big annual clean up. Reconcile weekly so a dropout surfaces within days, not at BAS time. Renew the connection whenever Xero asks, because most feeds carry an expiry date for security reasons. And when the bank sends a new card, add the feed to your changeover checklist rather than remembering it three months later.

Where NextEra fits in

Feed health is one of the first things we check on any new file, because everything downstream depends on it. We pair automated checks with a qualified person confirming statement balances every month, so a gap gets caught in days rather than at year end. If you want a second set of eyes on your own file, our Strategic Finance Review includes a full feed and reconciliation health check.