← All white papersGuide · October 2026

Claude and Grok Bot for accountants and bookkeepers in Australia

Every Xero client on one key, each staff member’s Bot limited to their own clients, and the client permission the TPB now expects.

8 min read·Published by AI Pathway

The short answer: Claude and Grok Bot can both work for an accounting or bookkeeping practice, but connecting them client by client does not scale. Xero’s own tools reach one organisation at a time. A practice key reaches every client you connect, or only the ones you tick, and every change it makes lands on one named client. Before any client’s data goes in, get their permission: the Tax Practitioners Board said so in July 2026.

In short

The problem
A connection per client, a Bot per client, or one partner's Xero login shared across staff. None of it scales, and the login breaks Xero's terms.
One practice key
Clients join by your Xero sign-in or their own invite link. One key reaches every client, or only the ones ticked. The Bot lists clients by name, reads across the practice, and writes to one named client at a time.
Xero's own tools
The free Claude connector reads one client at a time. The open-source MCP server can write, but it is a developer tool tied to one organisation per custom connection.
Compliance
TPB(GS) 55/2026: client permission before client data goes into an AI tool. Privacy Act: you answer for an overseas provider.
Cost
Connect, $19 a month per organisation for reading and notes, billed to the practice or the client. Draft invoices and calls only with Get Paid, $199 a month.

Take the spec to Claude, ChatGPT or Copilot. The sentence to paste is one click away.

Want the whole thing by email?

This paper, plus the rest of the library. One click to stop them.

1. “We have forty clients. Do we set Claude up forty times?”

Most guides to Claude or Grok Bot with Xero are written for one business with one file. A practice hits three walls straight away:

  • A connection per client. Grok Bot’s Xero plugin needs a custom connection made on Xero’s developer site for each organisation, each with a monthly Xero fee. Forty clients, forty connections.
  • A question per client. Xero’s free Claude connector switches between clients but does not combine them, so “which clients have the most overdue?” becomes forty separate questions.
  • A shared login.The shortcut is to sign the Bot into Xero as a partner. Then every staff member’s Bot can open every client, every change shows under the partner’s name, and Xero’s terms ask you not to let anyone else use your login.

What a practice needs is the opposite: one setup, every client by name, and each staff member seeing only their own book of clients. Our guide to whether Grok Bot is safe covers the login problem in more depth.

2. How one key covers every Xero client in your practice

Think of it as the practice’s key cabinet. Each client’s Xero sits behind its own hook, and you cut keys that open the hooks you choose. An Office Voice key works this way, in Claude, Grok Bot or any AI tool that takes a custom MCP server. Office Voice is our product.

  1. Add each client.Sign in with Xero and pick the client’s organisation, or send the client your practice’s invite link so they connect their own Xero. The client never needs an Office Voice login.
  2. Cut a key per person. Under Keys, a key reaches every client by default, or only the clients you tick. A junior’s Bot sees their five clients; yours sees all forty. Tick what the key may do: Read the book, Write drafts and notes, and, on Get Paid only, Queue calls.
  3. Add it to the Bot. In Grok Bot, ask it to add a custom MCP server and enter the key in the secure secret card, never in the chat. In Claude, add a custom connector and put the key in the request header. The exact message and steps are in connecting Grok Bot to Xero for a practice and adding the key to Claude.

Once it is in, the Bot can list your clients by name, read across the whole practice in one question, and write only to one named client at a time. A draft or a note meant for Smith Plumbing cannot land in another client’s book. The key writes draft invoices, quotes and promise-to-pay notes for a person to check, and it can never approve, send or pay anything.

One thing to know for Claude: on a Claude Team or Enterprise plan, Anthropic’s help says every member using a custom connector shares the credential it was added with, so add it with a key limited to what those members should reach. Per-person keys fit individual Claude accounts and Grok Bot.

3. Claude for accountants: what to ask across your clients

Start by checking what the key reaches:

Using Office Voice, list the client organisations you can reach, by name. Read only: do not change anything in Xero and do not contact anyone.

Overdue totals by client. One read across the practice, ready for the Monday catch-up:

Using Office Voice, read only. For every client you can reach, total the sent invoices past their due date. Give me one table: client, overdue total, number of invoices, oldest days overdue. Largest total first. Do not change anything in Xero and do not contact anyone.

Check two clients against Xero’s Aged Receivables report as at today before you trust the table. The full weekly version, with the calls handed over, is the Xero debtor call list.

Supplier bills awaiting approval. A sweep before the client’s pay run:

Using Office Voice, read only. Go through my clients one at a time. For each, list the supplier bills awaiting approval with the supplier, the total and the due date. Flag any bill that appears twice for the same supplier and total. Do not approve, pay or edit anything.

Add each client’s agreed rates and it becomes the supplier bill check.

A promise-to-pay note. A write, so it names one client:

Using Office Voice, for Smith Plumbing only: add a promise-to-pay note to invoice INV-0412 saying the customer promised payment of the full amount by Friday 7 November. Show me the note before you save it. Do not touch any other client.

For trade clients on ServiceM8, the same key runs unbilled jobs and quote follow-up. To put any of these on a weekly schedule, see how to use Grok Bot.

4. The Claude Xero connector and the Xero MCP server, versus a practice key

Xero publishes two ways for Claude to reach your files, and they are often mixed up.

  • Xero’s Claude connector is free to add, needs a Xero subscription and a free or paid Claude account, and needs no developer setup. It is read-only and follows the Xero permissions of the person who connects it. Accountants and bookkeepers switch between clients; Xero says data is not combined across organisations.
  • Xero’s MCP server is open source, and Xero describes it as the developer tool. It can create and update records, including invoices, quotes and payments. You run it yourself, and connect it with a custom connection, which Xero ties to one organisation, or with a sign-in flow you build.
Xero’s Claude connectorXero MCP serverPractice key (Office Voice)
SetupAdd in Claude, sign in with XeroRun the server, make a custom connection or build a sign-in flowSign in with Xero per client, or send an invite link; one key
ClientsOne at a time, switchingOne organisation per custom connectionEvery client connected, or only the ones ticked
WritesNoneInvoices, quotes, payments and moreDraft invoices, quotes and promise-to-pay notes; never approves, sends or pays
Works inClaudeAny MCP tool you set it up inClaude, Grok Bot, any tool that takes a custom MCP server
CostFree to addFree software; check Xero’s current terms for custom connections$19 a month per organisation; calls only with Get Paid, $199

If a partner wants to ask questions about one client’s file, Xero’s free connector is the right start and worth recommending to clients too. If the practice wants one question across many clients, or wants the Bot to leave drafts and notes for staff to check, that is what the practice key is for. More on the free connector is in our guide to Claude with Xero, and how the two Bots differ is in Grok Bot vs Claude.

5. “Are we allowed to put client files into AI?”

Yes, with permission. The Tax Practitioners Board’s TPB(GS) 55/2026, issued 22 July 2026, applies the Code’s confidentiality rule to AI. Registered tax and BAS agents must get each client’s permission before divulging client information to a third party, and the TPB says that can include entering it into AI models and tools, depending on how they are configured and used.

  1. Tell the client. The TPB recommends saying to whom and where the information goes, where it is stored, and whether AI tools may be used.
  2. Get it in writing. A signed engagement letter, signed consent, or a fact find with consent are all named as ways to give permission. The invite link is a natural moment: the client connecting their own Xero is a good time to have signed the updated letter.
  3. Check the tools. The TPB puts the due diligence on the practitioner: review that each AI tool keeps information secure and meets the Privacy Act. Where tax file numbers are involved, the TFN Rule may also apply.

The Privacy Act adds the overseas question. Under APP 8, before personal information goes to a provider overseas you take reasonable steps to make sure they handle it properly, and you stay accountable for what they do with it. Grok Bot’s cloud computer runs in the United States. One exception applies where the client is expressly told the protection will not apply and consents; the OAIC’s guidelines set out what that telling involves.

A scoped key helps you show what you did: which tool, which clients, and what it may do are all written down on the key. It does not replace the permission. Our page on whether Grok Bot is safe covers the security side.

6. What a practice key costs, and who pays

$19 a month per organisation for reading and notes, billed per organisation, to the practice or the client. Connect makes no calls. Draft invoices, quotes and phone calls come only with Get Paid, which includes it.

Claude and Grok Bot are billed separately by Anthropic and xAI; check their current prices. Give each staff member their own key, limited to the clients they look after.

7. How to start with three clients

  1. Pick three. Clients with live debtor books, who will say yes to an updated engagement letter that names the AI tools and where the data is stored.
  2. Connect them. Sign in with Xero for each, or send each one your invite link.
  3. Cut one read-only key. Tick Read the book only, and only those three clients.
  4. Test it.Ask for the client list, then overdue totals by client. Each total should match Xero’s Aged Receivables to the cent.
  5. Run it for four Mondays. Then add Write drafts and notes, more clients, and a key for each staff member.

Steps as Claude, Grok Bot and Xero set them out on 30 October 2026. Grok Bot ships a new version most weeks, so expect the odd label to move. New to it? Start with what Grok Bot is.

8. Questions

Can accountants use Claude with Xero?

Yes. Xero's own connector for Claude is free to add, works on a free or paid Claude account, and reads one client organisation at a time, switching between clients. It is read-only. To have Claude write drafts and notes across many clients from one setup, add a practice key from a service such as Office Voice as a custom connector. Check the Tax Practitioners Board's AI guidance first, because client data going into an AI tool can count as a disclosure needing the client's permission.

Is Claude good for bookkeepers?

For reading and checking, yes: overdue totals, bills awaiting approval, contacts and recent invoices, answered in plain English from live Xero data. It does not replace the bookkeeper's judgement, and no connector reconciles the bank, because Xero does not give ordinary apps the unreconciled bank feed lines. Treat Claude's answers as a first draft you check against Xero.

What is the Xero MCP server?

It is Xero's open-source server that lets an AI tool such as Claude work with Xero through the Model Context Protocol. Unlike Xero's free Claude connector, which only reads, the MCP server can create and update records, including invoices, quotes and payments. It is a developer tool: you run it yourself and connect it with a custom connection, which Xero ties to one organisation, or with your own sign-in flow.

Is there a Claude Xero connector for practices with many clients?

Xero's connector lets accountants and bookkeepers switch between clients, one at a time, and does not combine data across organisations. If you want one question answered across every client, such as overdue totals by client, you need a connection built for a practice. With an Office Voice key, the practice connects each client once and the key reaches all of them, or only the ones you tick.

Can Grok Bot be used for accounting?

Yes, with care. Grok Bot can read and draft in Xero through Xero's plugin, which needs a custom connection and a monthly Xero fee per organisation, or through an Office Voice key added as a custom MCP server. Never give it your Xero login. Its cloud computer runs in the United States, so for a practice the Privacy Act's overseas disclosure rules and the TPB's client permission guidance both apply.

Do I need my clients' permission to use AI on their Xero files?

Often, yes. The Tax Practitioners Board's guidance TPB(GS) 55/2026, issued 22 July 2026, says practitioners must get each client's permission before divulging client information to a third party, which can include entering it into AI tools depending on how they are set up. It recommends telling the client to whom and where, where the data is stored and whether AI may be used. An updated engagement letter is one accepted way.

Want one key for your clients?

Connect each client’s Xero to Office Voice once and give Claude, Grok Bot or any other AI a key limited to the clients you choose. $19 a month per organisation, billed to the practice or the client; calls come with Get Paid at $199 a month.

Published by AI Pathway · https://aipathway.com.au

Read the full interactive version at https://aipathway.com.au/explore-ai/claude-and-grok-bot-for-accountants