If you run more than one Xero organisation, you know the drill. Log into Entity A. Pull the report. Export to Excel. Switch to Entity B. Repeat. Any cross-entity work happens in a spreadsheet, not in Xero.
This is the reality for property managers running SPV entities, investment firms managing fund-level books, group companies with subsidiaries and accounting practices serving multiple clients. Xero is designed for single-entity accounting. Multi-entity work is a workaround, not a feature.
Why Xero doesn't solve this natively
Xero's architecture is one organisation, one login session. You can switch between organisations through the org picker, but each switch is a separate context. There's no way to:
- Query data across multiple organisations in one view
- Reconcile intercompany transactions without exporting to a spreadsheet
- Post journals that reference data from another entity
- Run a consolidated P&L or cash flow across the group
Xero HQ exists for multi-entity visibility, but it's limited to high-level dashboards. It doesn't support write operations, detailed reconciliation or workflow automation across entities.
For businesses with two or three entities, the manual approach is manageable. For those with five, ten or twenty, it becomes the single biggest time sink in the finance function.
Three approaches to multi-entity Xero
1. Manual (the current state for most)
Open each entity separately. Export reports to Excel. Build reconciliation spreadsheets. Copy invoices between entities by hand. This works, but it doesn't scale.
A finance team managing ten entities spends hours each week on work that's purely mechanical: switching contexts, exporting data, re-keying numbers. The time isn't spent on analysis or decisions. It's spent on data transfer.
2. Xero HQ
Xero HQ gives you a single dashboard across multiple organisations. You can see combined cash positions, review invoices and monitor bank balances. It's useful for oversight.
But HQ is read-only at the consolidated level. You can't post journals, create invoices or run reconciliation workflows across entities from HQ. It's a window into your data, not a tool for working with it.
3. AI-powered multi-entity management
This is where MCP (Model Context Protocol) changes the picture. An MCP server connects an AI assistant like Claude directly to Xero's API. With multi-entity MCP, all your organisations are accessible from a single session.
Instead of switching between entities manually, you describe what you need:
"Show me all outstanding invoices over 30 days across all entities."
Claude queries every connected entity and returns a single consolidated view. No switching. No exports.
What multi-entity AI accounting looks like in practice
Cross-entity cost apportionment
A 10-entity investment firm needs to apportion shared costs (office rent, IT, compliance) across entities based on a defined allocation matrix. Without AI, someone opens each entity, calculates the allocation, posts the journal manually in each org.
With multi-entity MCP, the allocation matrix is defined once. Claude calculates the splits, drafts the journals for each entity and posts them. The finance team reviews and approves. What took hours of manual posting happens in one interaction.
Intercompany reconciliation
Entity A invoices Entity B for management fees. Entity B pays. Both sides need to match. Across ten entities with multiple intercompany transactions each month, this reconciliation is a significant manual effort.
With multi-entity access, Claude pulls all intercompany transactions across connected entities, matches payments to invoices and flags discrepancies. The reconciliation that used to fill a spreadsheet becomes a conversation.
Consolidated cash flow
A property management company with 12 SPV entities needs a real-time cash flow view across the portfolio. Each SPV has its own Xero org with its own invoicing schedule and bank account.
With multi-entity MCP, Claude pulls the current cash position, outstanding invoices and scheduled payments from every entity and builds a consolidated view. The model is always current because it's pulling from Xero, not from a spreadsheet that was last updated three days ago.
Accounts payable automation
An invoice arrives for a cost that needs to be split across three entities. Without AI, someone creates three separate bills in three separate Xero orgs, splitting the amounts manually.
With multi-entity MCP, you describe the split ("$3,000 from Supplier X, split 50/30/20 across entities A, B and C") and Claude creates the draft bills in each entity. The bookkeeper reviews and approves rather than re-keying the same data three times.
What this means for finance teams
The shift isn't about replacing people. It's about where they spend their time.
Finance teams running multiple entities currently spend a significant portion of their week on data transfer: switching between orgs, exporting, re-keying, reconciling in spreadsheets. That work is necessary but purely mechanical.
Multi-entity AI management handles the mechanical work. The finance team's time shifts to the decisions that require human judgement: reviewing reconciliation results, approving journal entries, analysing cash flow trends, advising on cost allocation changes.
One investment firm we worked with ran ten Xero entities. Their finance lead spent roughly two days each month on intercompany reconciliation alone. With multi-entity MCP, that reconciliation runs in a single Claude session. The finance lead now reviews the results and handles exceptions rather than building the reconciliation from scratch.
Getting started
If you're running multiple Xero organisations and want to explore multi-entity AI management, ELab's Xero MCP is built specifically for this. It connects all your Xero orgs to Claude from a single session and includes pre-built workflows for reconciliation, cost apportionment and AP automation.
For a technical walkthrough of how Xero connects to Claude, read how to connect Xero to Claude AI.
