What it actually costs to run twenty companies on Xero
7 September 2026
You multiply. Xero charges per organisation, there is no volume pricing however many you run, and in Australia the multi-organisation discount was removed from 1 July 2026 — so twenty companies is twenty subscriptions at list price.
For a realistic mixed group that lands somewhere around A$16,000 a year before a single add-on. The number itself is rarely the surprise. What catches groups out is that it rose twice this year, and that the subscription turns out not to be the expensive part.
Prices below are Australian, GST inclusive, as published from July 2026. Xero changes them — check the current plan page before budgeting on these.
Is there a discount for running multiple Xero organisations?
Not any more, in Australia. Xero previously applied an automatic discount when several Business Edition organisations sat under the same subscriber email and country edition. That discount was cut to 15% and then removed for Australian subscribers from 1 July 2026.
Two details matter if you are working out why the bill moved. Existing promotional codes are honoured until they expire, so some groups are still on old economics and will feel this later rather than now. And the change landed in the same month as a price rise, which means multi-entity groups took two increases at once — new plan prices, then the loss of the discount on top.
For a group of any size the second is usually the larger of the two. A few dollars a month per plan multiplied across twenty organisations is real but modest; losing a percentage off the whole bill is not.
Worth noting the date differs by region — the equivalent change for US subscribers runs from 1 October 2026 — so advice written for another market may give you the wrong month.
What does twenty entities actually cost?
Between roughly A$8,900 and A$25,700 a year, depending entirely on plan mix. The plans, monthly: Ignite A$37, Grow A$78, Comprehensive A$107, Ultimate A$143, with a larger Ultra tier from around A$500.
Twenty of everything, annually:
| Plan | Monthly each | 20 organisations |
|---|---|---|
| Ignite | $37 | $8,880 |
| Grow | $78 | $18,720 |
| Comprehensive | $107 | $25,680 |
Real groups are mixed. A common shape is a handful of dormant or holding companies on the cheapest plan, most trading entities on the middle one, and one or two carrying payroll and projects higher up. Six on Ignite, twelve on Grow, two on Comprehensive comes to $1,372 a month, or $16,464 a year.
Against that same group, July’s price rise alone added about $62 a month — roughly $744 a year — before the discount removal is counted.
Can a dormant or holding company sit on the cheapest plan?
Usually yes, and it is the single easiest saving available — but check what the entity actually needs to do rather than what it looks like it does.
The trap is that plan tiers gate specific features rather than volume alone. Multi-currency and Projects appear from the middle tier; Expenses and Analytics Plus sit at the top. A holding company that does nothing but receive dividends and pay an accountant genuinely needs very little. A “dormant” entity that turns out to hold a foreign-currency loan does not, and discovering that at year end is worse than the money saved.
Payroll capacity is the other tier-driven variable, and it is per organisation rather than pooled across the group. Employees in one entity do not use up allowance in another, and they do not share it either — five entities with two employees each are five separate payroll subscriptions, not one for ten people.
What costs are easy to miss?
The app layer, because it usually prices per organisation too — which means the multiplication that hurts is not Xero’s alone.
Most of the tools a multi-entity group ends up needing exist precisely because Xero is single-entity: an approval layer, a document capture tool, a consolidation tool, an intercompany reconciler. Each is reasonable at one entity. Priced per connected organisation across twenty, any one of them can rival the Xero bill itself. When comparing options, the question that matters is whether a tool prices per organisation or per group, and it is worth asking explicitly because pricing pages rarely lead with it.
Two smaller ones. Add-ons that are bundled at higher tiers are chargeable extras lower down, so a cheap plan plus two add-ons sometimes costs more than the next plan up. And every organisation carries its own setup: chart of accounts, bank feeds, users, tracking categories. That is not billed, but it is not free either.
Is the subscription the expensive part?
No. At twenty entities the licence cost is the visible number and the smaller one — the expense is the work the per-organisation design creates.
Consider what is genuinely per-entity rather than per-group: a bank reconciliation, a month-end close, a BAS, a set of approvals, a login to switch into. Xero deliberately keeps one organisation open at a time — a position it has stated it has no plans to change, because data entered against the wrong organisation would create a permanent audit trail in the wrong ledger — so that switching is not incidental friction, it is the design.
Put a number on it locally. If closing one entity takes half a day and you have twenty, month-end is two person-weeks. At any sensible loaded cost that dwarfs $16,000 a year, and unlike the subscription it grows with transaction volume as well as entity count.
This is why “can we cut the Xero bill” is usually the wrong question. Moving six entities down a plan tier saves a few thousand a year. Removing a day a month of switching and re-keying saves more, and does not require anyone to accept fewer features.
Can you reduce the number of entities instead?
Sometimes, and it is worth asking once a year — but the answer is usually structural rather than financial, so accounting cost should not drive it.
Entities exist for reasons: liability separation, different ownership, licensing, a joint venture, a historical acquisition nobody has wound up. The last category is the one worth examining. Groups accumulate dormant companies that still cost a subscription, a tax return and a slice of attention every month, long after the reason for them has gone. Winding one up has a one-off cost and removes a recurring one.
What almost never works is merging entities that have genuinely different ownership or risk profiles to save software licensing. If the structure is right, the tooling should adapt to it.
Where else does Xero’s per-organisation design cost you?
In the places where the shape of the work does not match the shape of the software — and once you notice the pattern, most complaints about Xero in a group turn out to be the same complaint.
A few that come up repeatedly:
- Custom fields. You cannot add custom fields to contacts or invoices. The request has been open on Xero’s own product ideas forum since 2012, and it is standard in comparable systems. Groups that need a supplier’s insurance expiry, or an entity code, or a contract reference, end up keeping it in a spreadsheet beside Xero.
- Multi-step approvals. Bill approval is a single status change. There is no routing by amount, no sequential chain, no delegation when the approver is on leave — so any policy more nuanced than “these people can approve” lives outside the system.
- Two tracking categories. Xero allows two active tracking categories, around a hundred options each. For a group wanting entity, division, project and cost centre, that is two dimensions short, and the usual workaround is encoding two things into one category name.
- No consolidation, no intercompany. Each ledger is sealed, so a group P&L and any recharge between entities need something above Xero.
Each of these is individually survivable, and plenty of groups survive all of them at once with a spreadsheet and a good bookkeeper. The reason to name them together is that they share a cause: Xero is built for one company, and does that well. The cost of running twenty is not really the twenty subscriptions — it is everything you build around the edges to make twenty behave like one.
We will take the approval and custom-field gaps apart properly in a following guide, since those two are where most of the manual work in a multi-entity finance team actually accumulates.
Related guides
- How to approve bills across multiple Xero organisations
Xero keeps one organisation open at a time by design, so group approvals need a layer above it. What native approval does, and what the options cost.
- How to handle intercompany recharges in a Xero group
Recharge shared costs with an invoice, not a journal, on a documented allocation basis — and reconcile the mirrored balances monthly, not at year end.