Xero is the default SMB ledger across Australia, New Zealand, and the UK. The accountant or bookkeeper sits inside Xero all day, and increasingly an AI agent is sitting next to them, suggesting codings, matching bank lines, drafting end-of-month entries. The question for 2026 is not whether agents touch the ledger. They already do. The question is where their reasoning lives, and who gets credit for what.
The split: Xero is the ledger, Dock is the agent's workspace
Xero stays source of truth for the chart of accounts, contacts, invoices, and posted journal entries. Dock holds the agent's OUTPUT: the coding recommendation, the bank-feed match suggestion, the variance flag, the question the agent wants the bookkeeper to answer. Each Dock row carries an xero_invoice_id or xero_account_id pointer back to the canonical record. Agents read fresh from the Xero API on every pass, so they never reason against a stale mirror. And Dock's consent gate fires the journal entry, invoice, or bill back to Xero only after a human bookkeeper approves it. Posting is the dangerous op; everything before it is draft work that an agent can do at full speed.
Worked workflow: bank feed reconciliation
A bank feed drops 142 new transactions into Xero overnight. A reconciliation agent picks them up, pulls each one through the Xero API, and writes a row per transaction into a Dock surface called bank-reconciliation-may. For each row it proposes an account code, a contact match, and a confidence score. High-confidence rows (vendor seen 30+ times, exact amount, recurring) get tagged "auto-suggest." Low-confidence rows (new payee, unusual amount, possible duplicate) get tagged "needs human." The bookkeeper opens the workspace at 9am, sees 142 rows already triaged, approves the 118 confident matches in a batch, and spends real attention on the 24 that actually need a judgment call. Every approval clicks through Dock's consent gate and posts the reconciliation back to Xero. The agent's reasoning, including the rejected suggestions, stays attributed in the workspace, so the next month's reconciliation starts smarter.
Five-step data flow
- Pull. Agent reads transactions, contacts, and chart of accounts from the Xero API.
- Reason in Dock. Agent writes a coding suggestion, contact match, and confidence note into a Dock row with an
xero_transaction_idpointer. - Triage. High-confidence rows batched for fast approval; low-confidence rows flagged for the bookkeeper.
- Consent gate. Bookkeeper approves. Dock blocks any write to Xero without a human signoff on the row.
- Post. Dock fires the reconciliation, journal, or bill to Xero. The agent's reasoning stays in the workspace, attributed and auditable.
Why Xero specifically
Xero's strength is its advisor workflow. AU, NZ, and UK accountants run multi-client practices through Xero's partner program, and any agent layer has to respect that the bookkeeper, not the business owner, is often the operator. Xero's multi-currency support matters for the cross-border SMBs (e-commerce, agencies, SaaS) that make up a growing share of its base. And the Xero App Marketplace, with 1,000+ connected apps, means agents often need to reason across Xero plus a payroll tool plus an inventory tool plus a payments processor. Dock is the surface where that cross-app reasoning lands before any of it touches the ledger. For practices already standardizing on agent-supported month-end close, or comparing Xero against QuickBooks or NetSuite, the pattern is the same: ledger stays canonical, workspace holds the work.
If you run SMB books in Xero and your agents are already doing the easy 80%, give them a workspace where the other 20% lives in the open. Start with the accounting use case.
FAQ
Does this fit the Xero advisor workflow? Yes. Dock surfaces can be scoped per client, so a bookkeeper running ten Xero files sees ten workspaces, each with its own agent activity and approval log.
Multi-currency? The agent reads currency and FX rates directly from Xero on each pass, so reconciliation suggestions respect the transaction currency and the org's base currency without a mirrored conversion table.
Marketplace apps? Agents can read from any app that exposes an API (Stripe, Shopify, Gusto, Hubdoc) and write the combined reasoning into Dock. Xero stays the posting target.
GST and VAT lodgement? Lodgement itself remains a Xero-side action, gated by your jurisdiction's rules. Dock holds the agent's review of the BAS or VAT return as a draft for the advisor, never as an auto-filed return.
Sources: Xero Developer documentation, Xero Small Business Insights.