The Rollout

This is how we got Claude to do some of our actual work in Xero.

Not answering questions about the numbers. Doing the job, drafting bills, reconciling bank lines, checking expense claims.

For an accountant it’s the simplest productivity win I’ve found this year, and the setup is easier than it sounds. One of the three ways is a single click.

Watch it work first. Then I’ll show you all three.

THE VIDEO
Claude just matched 2 bills to a $4,500 payment

Claude on the left working through Xero on the right, matching two SMART Agency bills to a $4,500 bank line until Xero shows Totals match

Claude on the left, Xero on the right. Real footage on Xero’s demo company. I didn’t touch it.

A $4,500 payment to SMART Agency sitting on the reconcile screen, with two open bills for $2,000 and $2,500. Claude found both, ticked them, and Xero came back with "Totals match".

In the video I set all three up and run them on real tasks. A GST review, a page of bank reconciliation, a batch of staff expenses. Watch it, then keep this email as your cheat sheet. The setup guide is further down and every prompt is in one doc.

THE THREE WAYS
One reads, one drafts, one does the work

Claude connector vs Xero MCP vs built-in browser

Tested on Xero’s demo company, September 2026.

Don’t pick by features. Pick by the job.

1. The Claude connector. Settings, Connectors, search Xero, connect. One click, free. It reads your numbers and can build you a report or answer "who owes us money". It can’t change a thing.

Use it when the job is answering questions. A client rings and asks where they’re at. This is the one.

2. The Xero MCP. Xero’s own official connection. More setup, and AU$10 a month per organisation. But it’s fast, it can draft bills, invoices and journals, and you set its permissions inside Xero. It can’t reconcile.

Use it when the job is a review. Month-end journals, a GST check before the BAS, a batch of bills to draft for someone to approve.

3. The built-in browser in Claude Cowork. Claude opens Xero and uses it the way you do, through the screen. Slower. But it’s the only one that can reconcile and check expenses.

Use it when the job is the clicking. The screens the other two can’t reach.

Takeaway: none of them does everything. Ask questions with the connector, draft and review with the MCP, and use the browser for the screens the other two can’t reach.

THE BROWSER IN ACTION
Claude on the left, Xero on the right

This is the one that does the actual bookkeeping. Open Claude Cowork, click the browser button and sign in to Xero yourself. Claude works on the left. Xero changes on the right.

Claude reconciling bank lines in Xero, side by side

The log. Every bank line, what Claude did, and how confident it was. The unclear ones are left for a person.

A page of bank lines took about six minutes. It matched what it could and left the unclear ones for me, with a note on each. That log is the bit I’d show a client, not the speed, the fact that there’s a written reason next to every line.

Claude checking staff expense claims in Xero, side by side

Checking staff expenses, then on to payroll. Claude flags what’s wrong, you approve, and the approved claims go to the next pay run.

Then it saved the approved claims to a spreadsheet, ready for the next pay run.

Both prompts, word for word, are in one doc. Copy them into Cowork and change the rules to suit how you work, because the prompt is the workflow. Write down how you check things today, turn it into rules, and save it to a Cowork project per client so it builds up over time.

THE SETUP GUIDE
Xero MCP in about 30 minutes

This is the fiddly one, so here’s every step. Do it on the demo company first. It’s free there.

  1. Go to developer.xero.com, My Apps, New app. Pick Custom connection.

  2. Company URL can be your own website. When it asks if you’ll use Xero data to train an AI model, the answer is no. You’re only reading it.

  3. Scopes: tick only the ones ending in .read to start. Bank transactions, contacts, invoices, manual journals, payments, settings and the reports.

  4. Authorise it and pick Demo Company (AU). For a real business, that org needs a custom connection subscription, AU$10 a month.

  5. On the app’s Configuration page, copy the Client ID and click Generate a secret. Copy the secret straight away. Xero only shows it once.

  6. Open Terminal, paste this and press Enter. It asks for the ID and secret and hides the secret as you paste. Never paste your secret into a chat.

read "XID?Xero Client ID: "; read -s "XSEC?Xero Client Secret: "; echo; claude mcp add xero --scope user -e XERO_CLIENT_ID="$XID" -e XERO_CLIENT_SECRET="$XSEC" -e XERO_SCOPES="accounting.banktransactions.read accounting.contacts.read accounting.invoices.read accounting.manualjournals.read accounting.payments.read accounting.settings.read accounting.reports.aged.read accounting.reports.balancesheet.read accounting.reports.banksummary.read accounting.reports.profitandloss.read accounting.reports.trialbalance.read" -- npx -y @xeroapi/xero-mcp-server@latest; unset XID XSEC
  1. Open a new Claude Code session and ask it to review the last 90 days for GST problems.

Xero MCP GST and coding review results

24 read-only calls, 29 seconds, nothing changed.

Mine read 88 bank transactions and 92 bills and invoices in 29 seconds. First thing it flagged was a $4,500 bank wire coded to Legal expenses with $409 of GST claimed on it. A wire from a lender has no GST.

START WITH ONE
What I’d do on Monday

Don’t connect anything to a real client yet. Open the demo company and pick one job.

  1. Write down how you check it today. The actual rules, the ones you hold in your head.

  2. Pick the connection that reaches it. Questions, the connector. Drafting and review, the MCP. The clicking, the browser.

  3. Run it on the demo company until it’s boring.

  4. Then point it at one real client, read-only, with you pressing the final button.

One job, one client, one month. The practices I watch get stuck are the ones trying to roll out "AI" instead of automating a single check they already do by hand.

KEEPING IT SAFE
What I’d tell a client

The permissions live in Xero, not in the AI’s good behaviour. With read-only scopes, Xero refuses any change, whatever Claude tries.

  • Give Claude its own Xero user with a limited role. Not your admin login.

  • You sign in. Claude never sees the password, and it isn’t allowed to type one.

  • Don’t import your browser logins into Cowork. Then Xero is the only thing it can see.

  • Keep the hard rules and keep the logs. Anything it’s unsure about comes back to a person.

  • Sign out when you’re done. Cowork remembers logins between sessions.

  • Use a business Claude plan, or switch model training off. And get your client’s OK in writing first.

Sources: Xero MCP server · Xero's AI tools · Xero custom connections · Claude Cowork's built-in browser. Demo data only. Not tax advice; check GST treatment with your accountant.

Refer The Rollout, unlock the AI stack

  • Every share gets you closer to the tools I actually use to run this thing. Hit the share button below and you're in.

    • 1 referral → 3 months free of Notion Plus, the workspace I run everything in

    • 5 referrals → 75% off Xero for 6 months, cloud accounting that handles the boring stuff

    • 10 referrals → 3 months free of Wispr Flow, AI dictation that's 3x faster than typing

    Your unique share link is right below 👇

Until next week,
Daniel

PS. Want this set up for your practice or business? Reply "Xero" and I'll tell you how we do it at Phlo.

Recommended for you

View all
caret-right