Connecting Claude to Xero, QuickBooks or Sage without losing control of your books

Connecting Claude to Xero, QuickBooks or Sage is mostly a question of access and approval, not technology. The connectors available today let Claude read your accounting data and answer questions about it in plain English. According to the vendors' own descriptions, they do not let Claude post to your ledger. For most firms, that is the right default.

This guide explains what each of the three packages exposes and how to read invoices with Claude. It also covers how to draft payment reminders, which permissions to grant and what your bookkeeper still signs off. It includes one worked example in Xero, a table of who does what, and a section on what this means for a UK business.

One principle runs through all of it. The model reads and drafts. A named person approves, posts and sends. If you already use Claude in other business tools, the same pattern applies. Our post on putting Claude to work inside the tools you already use covers that wider setup.

The facts below come from the vendors' own pages where these exist, and from practitioners who have tested the connections. Where the sources disagree, the guide says so. Check the permission screen you see on the day you connect, because these products are changing quickly.

A few words come up again and again. Here is what each one means in this guide.

• API (application programming interface): the programmatic door into a system. Other software sends requests to it and gets data back.
• MCP (Model Context Protocol): a standard way for AI tools such as Claude to reach outside data. CData describes it as the protocol that gives AI tools "secure and governed access to live data".
• Connector: a packaged MCP connection you add from Claude's connectors directory. You sign in and approve access, and no code is needed. Carly reports that the directory had passed 400 connectors by mid-2026.
• MCP server: the software on the other end of a connection. Xero separates its read-only connector from the Xero MCP server, which it calls "a developer tool for custom workflows and automations".
• Ledger: the record of posted transactions in your books. Posting to it is the step that changes your accounts.
• Read-only: the connection can fetch data but cannot create, edit or delete anything.
• OAuth: the sign-in and consent method most connectors use. You log in to the accounting package and approve what the other tool may do, without handing over your password.

Keep the difference between a connector and an MCP server in mind. A connector is the ready-made, limited route. An MCP server or direct API gives a developer more freedom, and with it more responsibility for permissions.

The three packages have reached Claude by different routes. The table summarises what the sources describe.

For QuickBooks, Tax Care reports that Intuit and Anthropic announced a multi-year agreement on 24 February 2026, and that QuickBooks in Claude began rolling out on 23 April 2026. Intuit Enterprise Suite users can also build custom agents with the Claude Agent SDK.

The sources are not unanimous on write access. Carly's guide describes the Xero connector as read/write, while Xero's own page says it is read-only at launch. A LinkedIn post lists transaction categorisation for QuickBooks, which Tax Care says Claude cannot do. Treat any write feature as unconfirmed until you see it on the consent screen.

Reading is where these connections are useful today. Xero says Claude answers plain-English questions about profit, cash, invoices and customers using live Xero data. It also returns links to the report, invoice or contact it used, so you can check before you act. Tugger lists questions such as which invoices are overdue and expenses by category for a quarter as ones Xero's connector handles well.

There are limits, and practitioners have found them quickly.

• Arithmetic at volume. A Xero integration developer on Reddit warns that when you ask for a total of overdue invoices, "the AI is doing the addition itself". It works for ten invoices. At a hundred, you may get wrong answers without knowing it.
• Date ranges. One tester asked for March revenue and Claude pulled 2 to 31 March. Because he invoices on the 1st, the answer was wrong.
• Depth of data. The same tester reports account-level figures only, the top five revenue and expense accounts, and unpaid invoices only.
• Scope. Xero's connector only sees data held within Xero.

The sources talk about invoices and expenses rather than supplier bills in any detail. If bills matter to you, test those questions before you rely on them.

The practical rule is to use Claude to find and explain, and to use the package's own reports for any figure you file, pay or present. Ask for a list with links rather than a single total, then open the links.

Here is a setup you can follow, using the steps and settings Xero and Carly describe.

1. Connect. In the Claude app or on claude.ai, go to Customize, then Connectors. Find Xero and click Connect.
2. Sign in and choose. Sign in with your usual Xero login and choose the organisation you want. If you run more than one, pick the one this user should see and no other.
3. Approve permissions. Read the consent screen line by line before you approve. It tells you what access is actually being granted.
4. Ask a narrow question. For example: "List every invoice more than 30 days overdue, with customer, amount and due date, and link each one."
5. Check the sources. Open two or three of the links Claude returns and compare them with Xero's aged receivables report.
6. Draft, do not send. Ask Claude to write a polite reminder for each customer. Where Gmail is connected, Carly reports that Claude's email capability is draft-only, so the reminders land as drafts.
7. Review and send. Your credit controller reads each draft, corrects anything wrong and sends it from their own mailbox.

At no point does Claude change anything in Xero. The payment still arrives through your normal bank feed, and the bookkeeper reconciles it in Xero as before. Xero states that the connection is session-only. Anything Claude retrieves still stays in your Claude chat history, so set how long you keep those chats and delete them when you no longer need them.

Two checks make this safe. Ask for a list rather than a total, as the Reddit warning suggests. Then compare the list against the report before any reminder goes out.

Once the one-off version works, the next step is running it regularly. The limits here are about timing, not permissions.

Carly notes that connectors have no event triggers. They run when you ask, or on a schedule you set. Claude Cowork's scheduled tasks can run a receivables sweep unattended, but "on a fixed clock", so Claude never notices a transaction as it lands. A weekly timer on an overdue-date condition will always be between one and seven days late. If you want to set this up, our guide to using Claude Cowork for your business walks through scheduled work.

Pick the rhythm that matches your credit terms. A daily sweep suits short terms. A weekly sweep is fine if reminders go out at 30 and 60 days and a few days either way make no difference.

A direct API route can go further, but at a cost. One tester connected an agent tool straight to the Xero API and pushed updates over iMessage. He found it "extremely powerful", but it cost about 100 US dollars a day in tokens. For most small firms, a scheduled read-only sweep that produces drafts is the better trade. It costs less and keeps a person on the send button.

Claude takes on none of the accounting responsibilities. Xero says plainly that its connector is not a source of tax, compliance or financial advice. Xero also says it does not replace your accountant, your bookkeeper or JAX, Xero's own assistant. The table sets out a sensible split.

A LinkedIn tester summed up the current state well. Daily accounting work still happens in the Xero interface, and Claude serves as "a very basic BI layer on top". That is useful, but it is a reporting aid rather than a bookkeeper.

If a later version adds write access, keep this table. Write access would change what Claude is able to do. It would not change who is accountable for the books.

Permissions are where most of the risk sits, and the accounting packages do not always make it easy. The Reddit developer points out that Xero lacks granular read-only permissions. In his words, "a read-only license gives access to everything", including bank balances. He also notes that Xero offers neither single sign-on nor SCIM, the automated creation and removal of user accounts.

That means you control exposure mainly through who connects and which organisation they choose. At Svennis, we connect accounting data under a dedicated user who can see only the organisation in question, and we keep every step that changes the books with a named person. A checklist:

• Use a dedicated login for the connection, not the finance director's own account.
• Connect one organisation. If you manage several, CData notes you can specify a Tenant ID so the connection points at one instance only.
• Choose the right sign-in method. For CData's Xero connection, CData recommends PKCE for individual users, OAuth for interactive authorisation and OAuthClient for automated service-level access.
• Log activity. CData recommends audit logs for prompts, tool calls and Claude's responses.
• Know your plan. Carly reports that first-party directory connectors work on lower tiers, while custom connectors need a paid Claude plan.
• Review quarterly. Remove connections for people who have left, because there is no SCIM to do it for you.

The same approach applies to any business system. Our guide to connecting Claude with MCP, step by step shows it applied to Zoho CRM.

For a UK company, the cost of trying this is low. Xero UK says the connector is free to add, with an active Xero subscription and a free or paid Claude account. Carly lists Claude Pro at 20 US dollars and Max at 100 to 200 US dollars, if you outgrow the free tier.

QuickBooks users should watch their subscription as well as Claude, because some users report price rises this year. Check the current price for your plan on Intuit's UK pricing page. Tax Care offers a simple way to judge the value. If Claude saves two hours a month at £50 an hour, that is £1,200 a year. Use your own hourly cost and your own measured time saving.

Data protection is the other UK question. Xero says your Xero data is not used to train AI models. Tax Care reports that Intuit and Anthropic say the same for QuickBooks data shared through the integration. Check both companies' own terms before you rely on it. Data Claude retrieves also sits in your Claude account, so check your Claude plan's privacy and training settings as well.

Those statements do not replace your own checks on where data goes, who can see it and how long it is kept. Our UK GDPR checklist for Claude covers those checks, including whether sending data to Claude counts as a restricted transfer outside the UK.

Sage 50 users have the least direct route in these sources. Tugger connects Sage 50, Xero, QuickBooks and FreeAgent into one warehouse, which also suits accountants querying several clients at once. Tugger says your accounting subscription stays exactly as it is.

Start small, read-only, and with one question you already answer by hand every week.

1. Pick one job. Overdue invoices are a good first choice, because the answer is easy to check against a standard report.
2. Create a dedicated user in your accounting package, with access to one organisation only.
3. Check the contract, then connect. Before you connect, check that your Claude plan comes with a data processing agreement that covers the customer and supplier details in your books, and how data leaving the UK is covered. Our UK GDPR checklist for Claude walks through both. Then connect through Claude's connectors directory and read the consent screen before approving.
4. Run the worked example for two or three weeks alongside your existing process. Compare every list with the package's report.
5. Write down the split of who reads, who drafts, who approves and who posts, using the table above. Share it with your bookkeeper and accountant.
6. Add a schedule only once the lists match, and keep reminders as drafts.
7. Decide on anything beyond read-only as a separate project, with logging and a named approver for each write action.

If your team will share prompts and instructions for this work, our guide to Claude Projects and Skills for a small team shows how to keep them consistent. When you are ready to connect Claude to the rest of your business systems, the MCP setup guide mentioned in the permissions section is the next page to read.