Contact Info
Unit 9, 17 Power Ave
Alexandria, NSW 2015
info@hexflow.com.au
+61 (2) 8529 4085
Follow Us

Xero Multi-Entity Accounting: Where It Breaks Down

Xero multi-entity accounting is not one ledger with four columns. Every company, trust or entity is a separate organisation with its own chart, its own bank feeds, its own rules — and the work of a group is the work of four files that never speak to each other. Xero’s separation is right for compliance and expensive for administration; the gap between those two is where the hours go.

The short version

  • Each entity is a separate ledger. Nothing is shared, including the setup work.
  • Group consolidation is not in the standard product — it is a separate tool or a spreadsheet.
  • Intercompany pairs are the item that breaks, because elimination only works when both sides agree.
  • Below about three active entities, a person is still cheaper than a build.

What Xero’s model gets right

Separation is the feature. One login reaches every organisation, permissions are set per organisation so a bookkeeper can be kept to one entity, each entity reconciles on its own bank feed, and no transaction can leak across a legal boundary by accident — which, for a group with a trust, a trading company and a holding company, is the control you want.

The cost is that the model has no idea the entities belong together. It will not tell you that a payment from one entity appears as a receipt in another, and it will not warn you when the same supplier invoice is coded twice in two files.

What doubles when you add an entity

The admin does not scale by four neatly, and the parts that scale exactly are the ones people forget to cost.

Task One entity Four entities
Chart of accounts to maintain One, stable Four sets that drift apart within a year
Bank rules to build and review Built once, edited when suppliers change Rebuilt per organisation from scratch
Contacts One clean list Duplicated, with different spellings and payment terms
Coding the same supplier invoice Once Once per entity, by hand, context lost each time

Consolidation is not in the box

Xero reports per organisation. It does not produce a group profit and loss as a native report, which is why “xero multi entity consolidation” is one of the more honest searches on the topic. Firms solve it three ways: a third-party consolidator, a spreadsheet that maps four trial balances, or a person who assembles it every month.

The manual version is where month-end time hides: export four trial balances, map to a group chart, eliminate intercompany balances, reconcile the eliminations to zero. That last step consumes the day, because zero only works if every pair matches.

Intercompany, the part nobody budgets for

Groups generate intercompany entries constantly: a management fee, a loan from the holding company, shared rent allocated across three entities, a service charge with GST. Each has two sides in different files, entered by different people, sometimes in different months.

When the two sides disagree the consolidation does not balance, and someone spends an afternoon finding an amount keyed in one direction only. An agent can match the pairs and report the mismatch with both sides shown. It cannot decide which side is right — that is a judgement about which entry is wrong, and it belongs to the person who signs.

The pricing question, answered honestly

“Can Xero have multiple companies, and what does it cost?” is two questions. Whether one login can reach several organisations: yes. What it costs, and whether a discount applies, depends on your plan, region and partner agreement.

We do not quote software prices we cannot verify. Ask Xero or your partner, and get it in writing. What we can tell you is that the subscription is rarely the larger number — the labour across four files usually is.

What an agent does differently across entities

The design mistake is shared learning. An agent that learns “this supplier is always materials” from one client and applies it to another is not intelligent, it is contaminated, and it quietly codes a second file wrong.

What a well-built one does instead:

  • Learns per organisation and refuses to carry a coding habit across a legal boundary.
  • Reads the document, not just the narration, so it can tell a materials invoice from an office supplies invoice from the same supplier.
  • Produces a group-level exception list: these fourteen lines are uncoded, and these three are intercompany pairs that do not match.
  • Does the genuine bulk in parallel: bank feeds, filing, statements — without inventing judgement it does not have.

Where it does not pay

Under about three active entities, or entities touched quarterly, there is no volume to recover. If one bookkeeper already knows all four files and the chart is consistent, the advantage shrinks to review time. Fixed assets or payroll across entities is its own project — do not let it into the first one.

What we build

We build agents that work inside a group’s separate ledgers without merging them: entity-scoped learning, document reading, intercompany matching with both sides shown, and a review queue a bookkeeper can clear rather than rebuild each month. Every action is logged against the entity it touched.

Tell us how many entities

Send the entity count, what each one runs, and where consolidation happens now.

TALK TO US

Nirjhar works on the build side at Hex Flow in Alexandria, Sydney, where AI agents and automation are put together for accounting, legal, medical and NDIS practices.

Post a Comment