Karbon is practice management: clients, work items, templates, email, time. Xero is the ledger and, for the practice itself, the invoicing. The official integration between them is good at what it claims and silent about the rest. If you are deciding whether the pairing will remove the admin from your week, the distinction matters.
What the integration actually does
From Karbon's own description of the Xero integration:
- Contacts are matched both ways and created automatically where missing; partial matches are flagged for a person to resolve.
- Invoices raised in Karbon sync to Xero, with Karbon's service types mapped to Xero account codes.
- Payments recorded in either system update the invoice in both.
- Practice metrics (WIP, receivables, realisation) draw on the combined data.
Alongside that, Karbon's own features cover a lot of the practice's internal workflow: work templates that generate the recurring jobs, email triage that turns messages into tasks or attaches them to work, Karbon AI summaries and draft replies, and on the Business plan and above, automatic client reminders for outstanding requests.
For a practice migrating from Xero Practice Manager, note what the XPM link is: a two-way contact sync, with the rest of the migration done by CSV export and import. Jobs and time do not flow across automatically, and the XPM API is scheduled for retirement at the end of April 2027, so the migration is a project with a deadline, not a toggle.
What it leaves where it was
The integration is about the practice's own billing and client list. It does not touch the work the practice does on clients' books, which is where most of the hours are:
- Query clearing across every client's Xero organisation: unexplained bank lines out, answers back, postings proposed.
- Receipt and document chasing that stops when the document arrives rather than when someone remembers to cancel the reminder. Karbon's client reminders cover requests raised inside Karbon; they do not know what has landed in Dext or in the client's Xero.
- Monthly packs pulled from each client's Xero into a document with narrative.
- Meeting follow-up: the summary, actions and opportunities from each client call, filed against the client and turned into work items.
- Cross-system visibility: one view of which clients are waiting on the practice, which are waiting on the client, and where the deadlines are, across Karbon, Xero and the inbox.
How the Karbon API closes the gap
Karbon has a proper public API: contacts, organisations and client groups, work items (including creation from templates), invoices and payments, custom fields, file uploads, time and budgets, and webhooks, at 120 requests a minute. That is enough to make Karbon the system of record for work a separate automation does.
The pattern that works: the automation reads each client's Xero through the Xero API, does the job (drafts the query list, matches the receipts, builds the pack, summarises the meeting), and writes the result back into Karbon as a work item, a note or a task on the right client, from the right template, assigned to the right person. The team sees it in the place they already look. Nothing new to log into.
Two Xero details shape that build. First, access: a practice working across many client organisations uses a partner app with each client's OAuth consent, not Xero's custom connections, which are single-organisation and cannot reach Xero HQ. Second, limits: the Xero API allows 60 calls a minute per organisation and a daily cap per organisation, so a build that sweeps fifty clients every morning has to be paced, which is a design detail rather than a problem.
Where Xero's own AI fits
Xero's JAX assistant and the features announced around it (document capture, automatic bank reconciliation, document chasing and payment follow-ups described as coming) help one organisation's bookkeeping. They are worth switching on per client. They do not aggregate across a practice's client base or write anything into Karbon, so the practice-side automation above is still the layer that gives a team its hours back.
Deciding what to build first
If you are on Karbon and Xero today: switch on the official integration and the client reminders, use the work templates properly, and then look at where the remaining hours go. For most practices it is query clearing or document chasing across clients, and both are two-to-four-week builds on the two APIs. The Xero workflow automation guide ranks the candidates, and the accountancy practices page has the pricing and the compliance detail.
Founder, Anco AI. Builds the systems this site talks about, and runs his own business on them.
