Contact Info
Unit 9, 17 Power Ave
Alexandria, NSW 2015
info@hexflow.com.au
+61 (2) 8529 4085
Follow Us

XeroForce and JAX: What Xero’s AI Covers and What It Misses

XeroForce and JAX are Xero’s own AI, and they change what a practice should build. JAX is the finance partner you talk to — ask it about the numbers and it answers, and it can raise quotes and invoices for you. XeroForce, launched in May 2026, is a no-code builder that turns a plain-English description of a workflow into agents that run inside Xero. Both are real, both improve monthly, and both leave a gap a Sydney practice still has to fill.

The short version

  • JAX answers and acts on the numbers. XeroForce builds and runs workflows. Different jobs.
  • XeroForce logs every action and can run across a whole client list — that is a genuine change.
  • Xero has now started selling expertise alongside the tools, which tells you where the gap is.
  • Work that lives outside Xero, or needs your client-specific judgement, is still a build.

Two products on one foundation

JAX is a conversational finance partner. Ask what a client owes, why a number moved, or tell it to chase an overdue invoice, and it works from the organisation’s actual data rather than a report somebody remembered to run. It sits in beta, so check the current scope before betting a process on it.

XeroForce is the opposite shape: you describe a process — on the fifth of the month, find every uncoded transaction and ask the client — and it becomes a workflow with steps that runs in the background and records what ran, what data it touched and what is waiting on sign-off. Both sit on Xero OS.

What JAX does well, and what it will not answer

For a business owner or client manager, JAX is genuinely useful: outstanding invoices, a running balance, a quote drafted in seconds, an explanation of a figure the client is querying. The searches asking whether JAX can reconcile a bank account are the interesting ones — it can help you act on the items; the reconciliation is still signed by a person.

What it will not tell you is the professional answer. Whether an expense is deductible, how a mixed supply should be treated for GST, whether a payment is trust money, what the client actually agreed to on the phone. It answers from what is in Xero. Your obligations are not in Xero.

What XeroForce actually changes for a practice

Three things, and they are the right three. You describe your review steps and client sign-off limits in the instruction itself, so the workflow carries your control rather than bypassing it. Every action is logged and traceable — the difference between an automation your insurer can live with and one it cannot. And it runs across a client list, not one conversation at a time, which is the only version that matters at two hundred files.

Xero went further in November 2026, launching Xforce by Xero — partner consultants and forward-deployed engineers who build these workflows alongside a firm using XeroForce and Xero’s APIs. Read that for what it is: the vendor has concluded firms need help installing the work, not just the licence.

Where it stops for a firm like yours

XeroForce reaches Xero and the apps Xero connects to. It does not reach the parts of your practice outside that list.

Genuinely covered

  • Reading and acting on Xero data
  • Month-end steps, chase lists, filing dates
  • Repeating the same workflow for every client
  • A logged trail of what ran and what is awaiting approval

Still yours

  • The practice management file where the matter lives
  • The document store and the client portal
  • Anything with no usable API, or a desktop-only system
  • Your client’s specific treatment, learned from your own corrections
  • Any requirement that data never leaves your network

Who should use which

Three questions decide it. Is the work inside Xero and its connected apps? Can you describe the process, including the review step, in one paragraph? Is the same process run for many clients?

Three yeses means use XeroForce and do not pay us anything. If the process spans the practice management system, the file store and a portal — intake, matter opening, document assembly — it is outside the platform and a build is the only route. If you cannot state the review step in one sentence, the process is the problem; fix that first.

What each one costs you

Xero’s side is a plan and licensing question, and XeroForce has been in early access, so terms are moving. Ask Xero for the number in writing; we do not quote prices we cannot verify.

Our side is quoted per workflow, fixed before work starts. The comparison that matters is not licence against build, it is the cost of the work that stays outside the platform either way. A firm paying for XeroForce and still re-keying matter data into a practice system has automated the visible half.

What we build

We build the part Xero’s own agents do not cover: intake that lands in the practice management file, documents assembled and filed, records retrieved across your own store, and client-specific judgement learned from your team’s corrections. Where XeroForce does the job, we say so and you keep the licence.

Bring us the process, not the product

Describe one workflow your team runs weekly. We will tell you whether XeroForce covers it.

TALK TO US

Nirjhar works on the build side at Hex Flow in Alexandria, Sydney, where AI agents and automation are put together for accounting, legal, medical and NDIS practices.

Post a Comment