Enter your idea

This would be really useful as we have 2 companies in Xero and I need to be able to produce consolidated dashboards and reports. If this can be prioritized it would be very helpful.

One reason we need this is we are at a disadvantage to our own clients who can quickly access their data via their AI tool while we are not able to do the same.

This is absolutely needed - most business and family groups do not operate in isolation and analysing a single entity at a time is inefficient

We need this badly. I run a unlisted property trust fund called Natgen. We have over 30 entities. We need this asap!

I concur with Duyen.

We operate 6 trading entities. We can analyse data at a single entity level no problem. What would bring real value would be the ability to aggregate and analyse data across the Group without a lot of manual data extraction.

I'm thinking analysing payables, receivables, trends, cash-flow forecasting, and aggregation of expenditure line items (eg: software subs, travel, training).

Honestly, getting Claude to analyse one org is maybe cute, but really doesn't add a lot of additional functionality. I'm not here for cute.

Luke has described the two real gaps precisely. Worth adding for anyone hitting them today: both are solvable outside the official connector. Xero's public API does expose transaction-level detail (bank transactions, invoices, journals), and the open source Xero MCP server can be adapted to hold connections to several organisations at once. Our practice runs exactly this setup for scheduled multi-entity work, including reconciliation-grade transaction pulls, on both Mac and Windows. These limits sit in the official connector's design rather than the platform, so native support for both would make the integration what it should be. Happy to compare notes on the setup, I am easy to find on LinkedIn (same name as this comment).

Duyen, well said. Holding companies, family groups and related trading entities under one login is exactly the scenario where the single-org connector falls short, and intercompany journals and consolidated views are where multi-org access pays off most. As mentioned in my earlier comment, we adapted the open source MCP setup to handle this for our own practice, so it is workable today. Happy to compare notes if useful, feel free to reach out to me on LinkedIn (same name as this comment). Fully agree native support is the right long-term answer.

Strong support for this idea. Worth noting for others hitting the same wall: this is solvable today. Xero's API supports custom connections, and the open source Xero MCP server can be adapted so Claude holds connections to multiple organisations in one session. We run this daily in our practice across several client orgs, on both Mac and Windows, so the single-org limit is a connector design choice rather than a platform constraint. Native support in the official connector would still be the right outcome for most users. Happy to share what we learned building ours if useful.

The ability to connect Claude with multiple organisations sounds like a useful step toward making AI more flexible for teams that work across different environments. Managing separate workflows, knowledge sources, and collaboration spaces can be challenging, so having smoother connections could save time and improve productivity. I think the future of AI will depend a lot on how easily it fits into the tools and platforms people already use, much like PhotocallTV focuses on making access to entertainment simple and straightforward. Do you think multi-organisation AI connections will become a standard feature for most businesses in the future? https://photocalltv.es/

Two significant limitations with the Xero-Claude connector that make it difficult to use in practice:

Single entity authentication only. Multi-entity businesses need to aggregate data across legal entities, but currently you have to stop the Claude session and reauthenticate for each entity. This rules out any scheduled or automated processes, which largely negates the value of the integration - at that point it's quicker to download a Xero extract or use another tool like XO.

No transaction-level data. Pulling GL balances is useful, but most reconciliations and business reports require underlying transaction detail. Since Claude can't pull this, you're already logging into Xero to download transaction extracts manually - at which point there's little reason to bring Claude into the process at all. If transaction-level access were available, this integration would become genuinely powerful. Hoping that comes soon.

I would like to submit my idea to reconfirm the issue other users have brought up.

The Problem
Currently, the Claude connector only supports a single Xero organisation. To switch between entities, users must disconnect and reconnect the integration each time — selecting a different organisation during setup. For businesses managing multiple related entities, this is a significant friction point that undermines the value of the integration entirely.

Who This Affects
This is not an edge case. Inter-company structures are extremely common across Australian businesses — including holding companies, investment entities, family groups, and businesses with subsidiaries or related trading entities. Any Xero subscriber who manages more than one organisation faces this same limitation the moment they try to use Claude for accounting tasks.

The Business Impact
For multi-entity users, the current single-organisation restriction means:

Switching between entities mid-workflow requires a full disconnect/reconnect cycle, breaking continuity
Claude cannot assist with cross-entity tasks such as intercompany journals, consolidated reporting, or bill processing across related entities
The integration becomes impractical as a day-to-day tool, defeating the purpose of connecting it in the first place

This is particularly relevant for bookkeepers and accountants managing multiple client files or related business entities under a single Xero login — a very common scenario in practice.

The Requested Enhancement
Allow Claude to connect to all organisations accessible under a user's Xero account, with the ability to select or switch between organisations within a session — similar to how Xero's own interface handles multi-organisation access. Ideally, the connector would allow the user to specify which organisation context to work in for any given task, without requiring a full reconnection.

The Benefit
Multi-organisation support would make the Claude integration genuinely useful for the businesses that need AI assistance most — those managing complex, multi-entity structures where accurate, efficient bookkeeping across all entities is critical. It would also align the Claude connector's capability with Xero's own multi-organisation functionality, which already accommodates this common business reality.

I agree with Peejay: Accountants, Bookkeepers, and many business owners don't work with only one organisation, so having to connect and disconnect to get an answer from one company makes it easier to add a new custom report and jump between entities in Xero.