Xero AI Agents in 2026: Shipped, Beta or Just Announced

It is Monday. You open Xero to reconcile the bank, the way you do every Monday, and there is a panel there that was not there last month. It says JAX.

Under that panel sits a question the marketing does not answer. Has it already done something? Are those forty lines waiting for you, or did something clear nineteen of them at two in the morning?

Xero announced a lot this year. JAX, JAX Assure, XeroForce, a month-end agent, live Xero data inside Microsoft 365 and Claude and ChatGPT. Read it in order and you still cannot tell which part you can use this afternoon.

So I sorted it. I did not log into a Xero account; I read Xero's help centre, newsroom and blog on 20 September 2026 and put every agentic announcement into three piles: shipped, beta, or slide.

What is a Xero AI agent?

A Xero AI agent is software that does the accounting work itself inside your Xero account. Today that means JAX, which Xero runs in beta: a chat assistant you prompt, and an automatic bank reconciliation that acts on its own when it is confident. XeroForce, a builder for your own agents, is invite-only.

Two words there carry the weight. Beta means Xero can change it, and Xero says so. Invite-only means you cannot switch it on by deciding to. The version of the definition with no Xero in it is what is an AI agent.

What is actually switched on today

I count nine agent-framed items across Xero's 2026 announcements. Four are in some form of beta, one is invite-only, and four are announcements with no availability attached.

Statuses there come from Xero's own help centre, blog and press releases, plus trade coverage of Xerocon Denver, all read from outside a Xero account on 20 September 2026. Beta and rollout states move, so check any row you plan around.

Why there is no Xero price table here

Xero's US plans are called Early, Growing and Established. I am not going to print what they cost.

The reason is specific. Xero's pricing page did not give up its prices when I read it on 20 September 2026, which is consistent with a page that assembles them in the browser. The figures circulating on comparison sites are not from Xero, and I could not check them against Xero's own page. Read the rates on Xero's own page, and check which promotion is running.

One naming trap, before it costs you an hour. Xero's help article on auto bank reconciliation describes availability in terms of Grow and above, with Ignite and Simple able to add it for a fixed monthly price. Those are the UK, Australia and New Zealand tier names. They do not exist on a US account, and I did not find the same line against a US plan.

The one feature that already acts on its own

Auto bank reconciliation powered by JAX is the most concrete agentic thing Xero has shipped, and it is in open beta. It reconciles statement lines where its confidence is high. Where confidence is low, Xero surfaces a suggestion for you to confirm or edit.

Xero names four methods behind it: Rule, Match, Memory and Prediction. Rule and Match read like the mechanisms Xero has documented for years. Memory and Prediction are the new half. Xero's description of them is thin, so I will not invent definitions, but neither depends on a rule anybody wrote down.

• There is a Reconciled page. It shows what JAX reconciled, and any transaction on it can be reviewed or adjusted. That page answers the Monday question.
• Correcting it teaches it. Xero says that when you fix a reconciliation, JAX learns and is less likely to repeat that mistake.
• Xero admits it gets things wrong. The help centre acknowledges that JAX can reconcile a transaction incorrectly and documents the fix path, which is more useful than an accuracy claim.

One number gets quoted about this feature and it is worth getting right. Xero's stated goal is for JAX to auto-reconcile more than 80% of bank statement lines in real time. A goal. Nobody has published what it hits, and reading it as a result means planning your month around a press release.

Open the Reconciled page before you touch anything else on the first Monday it appears.

What Xero could already do before any of this

Bank rules are not new and they are not AI. You write the conditions, and on import Xero checks each statement line against them and suggests a spend, receive or transfer money transaction. Require that all conditions match and the rule turns restrictive: Xero suggests it only when every one is met.

Reconciliation suggestions have long drawn on three things. Your bank rules, similar transactions you previously reconciled, and the details on the statement line itself. That is smart matching, and it is deterministic. Same input, same suggestion, every time. The invoice-side version of the job is in Xero invoice reconciliation with an agent.

Here is the part that matters for reading the announcements. Those rules produce suggestions you accept. They do not fire on their own, which you can confirm from Xero's own product ideas site, where a request to have rules applied automatically sits open.

So the delta from JAX is narrower than the launch language implies, and still worth having. It is the click. It is also Memory and Prediction reaching lines no rule of yours describes. If you reconcile four hundred lines a month, the click is the job.

What Xero says JAX will not do

The most useful page Xero has published about JAX is the one listing what it does not do. I would read it before any of the launch posts.

• No financial advice. Xero states that JAX is unable to give financial advice or recommendations, and points you at a qualified professional before you make business decisions. Worth reading twice if your plan was to ask it whether you can afford the hire.
• No data flow if you stay out. JAX processes your data when you send it a message, and Xero states that if you do not join the beta, neither JAX nor the models behind it interact with your data.
• Third-party models, fenced. JAX runs on third-party large language models, and JAX Assure is the layer Xero built to restrict what those models receive to the data a task needs. Xero says it verifies outputs and produces fewer hallucinations than tools relying on a model alone. No error rate, no test set, no third-party evaluation, so that is a vendor claim.

One brand name, two products, two opposite sentences

Xero's help article on JAX says it will not act on your behalf, that it needs your prompts to perform, and that you keep complete control over what it does. Xero's help article on auto bank reconciliation powered by JAX says it reconciles lines when confidence is high, and nothing there requires a prompt from you.

Both are accurate. They describe different products.

JAX chat is the thing you talk to, and it does wait. Auto bank reconciliation runs on JAX and does not. One brand name across both makes two true sentences read like a contradiction.

That is a naming problem rather than a dishonesty problem, and it has one consequence for you. If the only Xero page you have read is the one about JAX chat, you believe nothing in your ledger moves unless you move it.

What it still will not do

Everything above happens inside Xero. Most of the work that ends in Xero does not start there.

• The document that arrives by email. A supplier PDF in an inbox, a receipt in a chat thread, an approval waiting on somebody who is in a meeting until four. None of it is a Xero object until a person or another piece of software makes it one.
• The chase. Nothing I read describes JAX contacting your customers on a schedule and working the replies. JAX cashflow, announced at Xerocon Denver, spots gaps across invoices, bills and payroll and fine-tunes payment timing. Spotting a gap and chasing four people are different jobs.
• The close. The month-end agent is the clearest announced-and-not-shipped item on this page.
• Advice. Ruled out in writing.

The objection from people who do this all day

Accountants posting on AccountingWEB's Any Answers forum, in a thread arguing that Xero is no longer fit for accountants, make three complaints worth hearing. They say JAX largely replicates manual tasks more slowly, and with errors or error messages. They object to paying for AI upgrades nobody asked for, when most clients want invoicing, bank reconciliation and a VAT return. And they warn that an agent learning how a business runs from a badly set up ledger will do more harm than good.

That is a forum thread, and the people posting are not a neutral sample. The third complaint is still the one I would act on. Anything that learns from your coding history learns your mistakes with it, which makes tidying the coding a prerequisite. The bookkeeper's version of that argument and the practice view go further than I can here.

Where Gravity fits next to Xero

Gravity does not keep your books, and I would not ask it to. An agent inside the ledger with your whole transaction history will beat an outsider at categorisation. That argument is over and Xero won it.

What is left is the work around the ledger, which is most of the hours. Reading the invoice that arrived by email and checking it against another system. Chasing the customer who is nineteen days late, then the one who replies asking for a copy. Collating the month into whatever your accountant actually wants. Invoice chasing and receivables follow-up come up most, and the finance hub maps the rest.

Gravity is in private alpha, so the honest framing is what you get once you are let in. Your first agent is free and there is no card. After that Pro is $5 a month during the alpha, and Max is $20 a month for more agents and usage. Buy more usage from your account if you run out. A run that fails on a platform error, with no usable output, is refunded under the refund policy.

The division is clean. Xero's agents own the work inside the ledger. A cross-tool agent owns the work that has to reach it.

FAQ

Sources