Settings and activity
2 results found
-
27 votes
Hi everyone, thanks for sharing this idea and adding your feedback.
We understand why being able to connect Claude across multiple Xero organisations could be helpful, particularly for advisors and bookkeepers who work across several clients or entities. The idea is to allow a single Claude connection to access multiple organisations, removing the need to reconnect or switch between organisations when working across different datasets.
We've updated the status of this idea to Gaining Support. If this would be useful for your workflow, please add your vote and share more about how you'd use it.
An error occurred while saving the comment 
Luke Stevenson
supported this idea
·
-
774 votes
Hi community, thanks so much for all the interest we received. The teams interview spots filled up quickly and they are now fully booked.
Apologies if you didn't manage to sign up to one of the interviews — We really appreciate your enthusiasm and may reopen the link for future research rounds. We will make sure to update here if there's more opportunity.
We will be back to share outcomes from the teams exploration.
An error occurred while saving the comment Luke Stevenson
commented
Been the top request for a significant amount of time now. Clear that Xero doesn't listen to what its users actually want.
Sage, NetSuite, QuickBooks all offer this - even new systems like Rillet, Campfire & Digits have it! Clearly its a core feature that should be included in any accounting system.
An error occurred while saving the comment Luke Stevenson
commented
Scheduling of reports is a pretty standard functionality; surprised Xero doesn't have this. Makes automating some reporting process with AI tools challenging.
Luke Stevenson
supported this idea
·
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.