Multi-Entity Xero Reporting: Comparing Organisations Without Consolidating Them

A franchisor runs twelve stores. Each franchisee is its own company with its own Xero organisation, its own bookkeeper and its own idea of what an account should be called. Once a month head office wants one page: every store's P&L, one column per store, so it can see who is ahead on labour costs and who is quietly losing money on delivery.

Head office isn't after a group total. Some of the stores may sit in a group and some may not, but either way this report is about comparing them, not adding them up. A combined revenue line wouldn't tell anyone which store needs attention.

This is multi-entity Xero reporting, and it isn't consolidation. It's comparison: the same layout and the same lines for every organisation, side by side. Xero doesn't do it, and most of the advice online answers the consolidation question instead.

Where native Xero stops for multi-entity reporting

Every report runs against one organisation. You pick an organisation, run its P&L, export, switch organisation, and do it again. Xero's own reports, including Xero Analytics, don't combine organisations. And even where you can consolidate, consolidation adds entities up, which isn't what this report needs.

Client insights is a summary, and it's for advisers. Xero Partner Hub has a Client insights screen that lists each client with revenue, expenses, net profit, cash, receivables, payables and current ratio. It's a genuinely useful health check across a client list but it doesn't show account lines, a standard layout, or the ratios you actually care about. It's also only there for advisers with access to clients on business plans, not a franchisor or a holding company.

Report templates travel. The mapping underneath doesn't. Practices can build report templates and apply them to clients. They work off report codes, a mapping each account carries, so they line up neatly when every client was set up from the same chart of accounts template. That said, existing clients rarely were. Xero's own community manager wrote in July 2025 that copying a custom report from one organisation to another "isn't planned in the near term". Even a perfect template still produces one report per organisation.

Tracking categories only work inside one organisation. If the twelve stores were one legal entity, each store could be a tracking option and Xero would put them in columns. Separate companies can't share tracking. We covered the other ceiling, two active categories, in the tracking category limit.

Ratios have to be worked out per entity. Even once you have twelve P&Ls in one workbook, labour as a percentage of sales is a calculation per column. Xero gives you no calculated rows across organisations, so every KPI is a formula someone maintains.

What hitting the wall looks like

The franchisor. Twelve exports, twelve differently named staff cost lines, and an afternoon spent deciding whether "Casual wages" belongs with "Kitchen labour". The comparison is finished three weeks after month end, when it's too late to act on. (The same store-level questions show up in F&B reporting from Xero.)

The portfolio owner. A holding company with stakes in five unrelated small businesses. Whether or not they count as a group for the statutory accounts, the monthly question isn't about a combined figure, and there's nothing to eliminate. What the owner wants is the same management accounts layout for each company, so a margin in one can be read against a margin in another.

The accounting firm with similar clients. Forty dental practices, or thirty cafés. The partner wants to show each client how it compares with its peers: wages as a share of revenue, rent per square metre, gross margin against the median. That's a strong advisory conversation and a reason clients stay. Client insights gets you to net profit, and the rest is a spreadsheet. We've written about where that kind of work fits in improving firm margins.

The group that consolidates quarterly but compares monthly. Some groups do need a proper consolidation for the board, with eliminations and FX translation, and that's covered in what native Xero can and can't do for consolidation. But the operating review each month is a side-by-side of the subsidiaries, and building it from the consolidation workbook means unpicking the eliminations every time.

The hard part is one account map

Pulling twelve P&Ls is tedious, but it isn't hard. The hard part is that twelve organisations have twelve charts of accounts, and a comparison only means something if every column puts the same costs on the same line.

Here's what three franchisees' staff costs might look like (invented, as always):

Store B's staff meals are a food cost in head office's view, so they move. Store C has no split between kitchen and front of house, so if the report wants that split, Store C shows one line and a note rather than an invented allocation. That's the kind of decision a mapping has to record once, so it isn't made differently next month.

A few rules keep the map honest:

• One mapping table, owned by one person. Each row is an organisation and account, pointing to a reporting line. Changes to the map go through that person, so two stores' identical accounts never end up on different lines.
• Choose codes or names knowingly. Codes are stable: a bookkeeper tidying "Wages - FOH" into "Front of house wages" doesn't break a map keyed on codes. Names catch something codes miss: a repurposed account, where an old code is renamed and reused for something else and a code-based map keeps sending it to the old line. Your bookkeeping SOP should discourage repurposing accounts, but it still happens. The cost of mapping on names is that every rename breaks the link, which makes the next rule essential.
• Surface orphaned accounts on every run. An exceptions tab lists every account that has activity but no mapping row, and every mapping row that no longer matches an account, with the amount involved. Nothing drops silently out of the comparison, and a new or renamed account gets mapped in the month it appears, not when someone notices a column looks light.
• Treat revenue the same way everywhere. If one store books delivery platform commission as a cost and another nets it off sales, their revenue isn't comparable. Decide which, and map both to it.
• Divide after mapping, not before. Ratios come from the mapped lines in each column, so a store with an odd chart still gets a fair labour percentage.
• Benchmarks instead of totals. For comparison work the useful extra columns are the median, the average and the best quartile. A total is often meaningless, and sometimes misleading.
• Decide on currencies and year-ends up front. A comparison across countries needs either local currency with ratios only, or every entity translated at one stated rate. Entities with different year-ends need calendar months, not "period 7".

We go deeper into the currency side in multi-currency reporting on Xero.

What good multi-entity Xero reporting actually looks like

1. One column per organisation, one shared layout. The same lines in the same order for every entity, whatever its chart looks like.
2. A single mapping table that maps every account in every organisation onto that layout, with unmapped accounts flagged rather than lost.
3. KPIs calculated per entity from the mapped lines: margins, labour percentage, rent to sales, whatever the business is run on.
4. Benchmark columns (median, average, best quartile) alongside or instead of a total.
5. A tie-out per column. Each organisation's mapped net profit agrees with its own Xero P&L for the period, so nobody can say the comparison moved their numbers.
6. New entities without rebuilds. A store that opens in March adds a column, shows blanks before it opened, and maps its accounts once.
7. Drill-down to the source. A surprising cell leads to that organisation's accounts and transactions, not to a different workbook.
8. Refreshed, not rebuilt. Next month regenerates from Xero. The mapping is the only thing that's maintained.

The workarounds, ranked

1. Export each organisation's P&L into Excel and map with lookups. Everyone starts here, and for three or four entities it's fine. It scales badly, because each export is a formatted report rather than a table, and new accounts slip through the lookups silently.
2. Client insights for the headline view. If you're an adviser and net profit and cash are enough, it's already there and costs nothing extra. It stops at headline figures.
3. Standardise charts with chart of accounts templates and report templates. The right long-term move for a firm setting up new clients. It doesn't fix the clients you already have, and it still produces one report per organisation.
4. A multi-entity reporting add-on. Joiin, Fathom and Spotlight Reporting all combine Xero organisations and can show entities side by side. We compared them in Joiin vs Fathom vs Spotlight. Test how each handles your mapping when charts differ, and whether you can get the benchmark and KPI columns you want rather than a consolidated total.
5. Build it on the Xero API. The most control and the most upkeep. Read what building on the Xero API involves before you commit.

Where Cheetah fits

Cheetah builds custom reports on Xero, and a lot of that work is this: a comparison across organisations that don't belong in a consolidation. We set up the shared layout and the mapping table with you, build the per-entity KPIs and benchmark columns, and add a tie-out tab so every column agrees with that organisation's own Xero P&L. The report arrives as a Google Sheet with an Excel download and refreshes on a schedule. A new entity is a mapping exercise, not a rebuild.

If you're spending the first week of every month lining up P&Ls from different organisations, Cheetah is worth a conversation.

The short version

Comparing Xero organisations is a different job from consolidating them. Xero reports one organisation at a time, Client insights stops at headline figures, and report templates only line up when every chart was built the same way.

The work that makes multi-entity reporting reliable is one account map across every organisation, KPIs calculated per entity, benchmarks in place of totals, and a check that every column ties back to Xero. For the ways to build it, see Xero Custom Reports: 4 Ways to Build Them in 2026.