Xero has announced XeroForce, a no-code agent builder that lets accountants, bookkeepers and small business owners describe a workflow in plain English and have it run automatically across Xero and the apps connected to it. Early access is open now. Broader availability is coming in the months ahead.
The announcement leans heavily on a phrase Xero is now using everywhere: a move "from a system of record to a system of action." That language is doing a lot of work, and it is worth examining what it actually means for the firms being asked to adopt this.
What was actually announced
A practitioner describes a task in natural language. XeroForce builds and runs the agent. No code. The example Xero offers: "on the 5th of every month, get clarification on uncoded transactions." The agent runs on schedule, watches for triggers, drafts client messages, and waits for sign-off where the workflow requires one.
Xero is leading with five claims. The agents are always-on, running in the background over days or weeks. Every action is logged for audit. Workflows can run across an entire client base, not one client at a time. The logic is purpose-built for financial workflows. And the whole thing sits on Xero OS, the same AI-native layer that powers JAX.
Stripped of the marketing, that is the announcement. An agent builder, with logging, scoped to financial workflows, running on Xero's platform.
What is genuinely interesting
The purpose-built argument has weight. Generic AI platforms treat the ledger as raw input. They pull data out, run it through a model, and push something back. They do not understand what a BAS is, what a payrun is, or what a sign-off should look like. Xero does, because Xero has spent two decades building that context.
For a workflow like uncoded transactions chasing, that context is the difference between an agent that works and an agent that needs constant correction. Firms that have tried building this kind of automation on top of generic platforms know how brittle the result tends to be.
The bulk-action point is also real. The bottleneck in most practices is not knowing what to do. It is doing the same thing consistently across two hundred client files every month. If XeroForce delivers on practice-wide execution, that is meaningful leverage.
What should give firms pause
Audit trails are being positioned as a differentiator. They are not. They are table stakes. Any AI product touching client data without a logged audit trail should not be in a regulated firm in the first place. Xero gets credit for shipping it. Xero does not get credit for inventing it.
Always-on agents that run in the background over days or weeks are a more complicated proposition than the announcement suggests. The honest version of that feature is that something will be running, touching client data, sending messages, and updating records while no one is watching. The audit trail will tell you what happened after the fact. It will not stop a wrong thing from happening in the first place. Firms need to think hard about which workflows they actually want running unsupervised, and which they do not.
The natural language interface is also less novel than it sounds. Every AI agent platform shipping in 2026 lets you describe workflows in English. That is the baseline. The question is not whether the prompt works in the demo. It is whether the agent does the right thing on the messy, edge-case-ridden 47th client file of the day. That is not something a launch post can answer.
The platform question
The bigger story, and the one Xero is not framing this way, is platform control.
XeroForce sits on Xero OS. JAX sits on Xero OS. Whatever Xero ships next will sit on Xero OS. Xero is building an operating layer underneath its accounting product and asking firms to build their automations on top of it.
That has obvious upside. Tighter integration. Better context. Workflows that understand the ledger they are operating on.
It also has a cost worth naming. Every workflow a firm builds inside XeroForce is a workflow that runs on Xero's terms, on Xero's pricing, with Xero's roadmap deciding what is possible. Firms that build deep automation inside XeroForce are also building deep dependency on Xero. That is a reasonable trade for some firms. It is a real risk for others, particularly those who have lived through previous platform shifts and watched pricing or capability change without notice.
The right question to ask is not "does XeroForce work." It is "what is the cost of building my practice's automation layer inside Xero specifically."
What firms should actually do
For most firms, the sensible move is to wait. Early access is for firms that have the capacity to test something carefully on non-critical workflows, with someone senior watching what the agent actually does. That is a small number of firms.
For everyone else, the right posture is sceptical interest. Read the case studies when they arrive. Ask other firms what broke. Pay attention to what Xero quietly changes in the first six months, which will tell you more about the maturity of the product than any launch post will.
XeroForce might be the most significant thing Xero has shipped in years. It might also be a competent first version of a product that needs another two cycles before it is ready for production use across a real client base. Both are possible. Both have happened before in this category.
The waitlist is open. Worth knowing about. Worth waiting to see.
