Multi-entity reporting in Xero: scope, mappings and review controls

Integration update, 20 October 2026: Clarity Ledger now connects Xero, QuickBooks Online and FreeAgent. GBP Xero examples below remain valid. Check current provider and currency eligibility; planning, KPI and pack-preparation tasks described as manual remain separate workflows.

A portfolio of property SPVs needs more than a collection of reports with matching headings. Before combining figures, agree which entities, periods, accounts and adjustments belong in the result.

This guide distinguishes reporting within a Xero organisation from the separate controls required for a portfolio roll-up. It does not assume that every reporting tool provides eliminations, ownership adjustments, transaction drill-through or statutory consolidation.

1) Start with the scope of the Xero report

Organisation-level financial reports

Xero documents financial reports including profit and loss, balance sheet and cash flow, with options to customise layouts and compare information. Check the selected organisation, period and report settings before using its figures as portfolio inputs. Xero's financial reporting documentation.

A report for one organisation and a report combining several legal entities answer different questions. Keep an entity register and reconciliation evidence rather than assuming that a matching report name establishes the required group scope.

Tracking categories describe dimensions within an organisation

Xero's tracking categories can label areas such as departments, locations or cost centres. Xero documents a maximum of four categories in total, with only two active at once. Xero Central: tracking categories and options.

A category such as region or property manager can help organise a single organisation's data. It does not, by itself, define which separate SPVs belong in a portfolio or how intercompany balances should be adjusted.

Check current practice tools rather than relying on old product names

The former Xero HQ URL now directs to Xero Partner Hub. Xero describes Partner Hub as a place for practices to access client information, tools and reporting templates. Assess those documented functions against your needs; practice oversight and a particular portfolio-consolidation method are separate requirements. Xero Partner Hub.

2) Define the portfolio requirements explicitly

A shared reporting structure

Agree the reporting lines used across SPVs, including rent, recoveries, property operating costs, capex, financing and relevant balance sheet categories. Define terms such as NOI so that a difference in account coding does not become a difference in reported performance.

This reporting structure can sit above local bookkeeping charts. It does not require every source ledger to use identical account codes.

A reviewed mapping table

For each source account, record its entity, code, name and intended reporting line. Review new accounts and conflicting mappings before using the roll-up.

Keep a dated copy of the mapping used for each published pack and explain any changes that affect comparative figures. These are workflow requirements; confirm whether a chosen tool implements them or whether your team must retain the record separately.

Documented ownership and adjustments

State whether the management view includes 100% of each entity or a defined ownership share. Keep intercompany balances, eliminations and other group adjustments in an approved schedule that reconciles before and after adjustment.

If currencies differ, specify the required translation policy and use a tool or model that actually supports it. A simple sum of source balances is not evidence that translation, eliminations or statutory consolidation have been completed.

Traceable supporting evidence

Reviewers should be able to trace a reported portfolio figure to the contributing SPVs and source accounts. Review transactions in the source ledger or a separately verified tool when the explanation requires them.

Avoid describing transaction drill-through as available until it has been demonstrated in the actual reporting workflow.

3) Evaluate tools against a reconciled example

Xero's UK App Store lists reporting products with differing consolidation, forecasting and related functions. These are capabilities of individual listed products, subject to their own scope and setup; they are not interchangeable with native Xero reports or Clarity Ledger. Xero App Store: reporting and forecasting.

Use a closed period and a small, representative set of SPVs to evaluate any workflow:

1. Confirm the included entities and source periods.
2. Check mapping coverage and reporting definitions.
3. Reconcile pre-adjustment totals to the source reports.
4. Review ownership, intercompany and currency adjustments separately.
5. Trace a material movement to source evidence.
6. Record who reviewed the result and which source versions were used.

Choose the process for the complexity of the reporting requirement, rather than an arbitrary entity-count threshold. A controlled spreadsheet may be suitable for some management reports; other requirements may need a separately selected consolidation system.

Worked example: map and reconcile two property SPVs

The figures below are invented for a training example. They are not customer data or evidence of a customer's results. Both SPVs have a GBP base currency, use September 2026 as the reporting period, and contribute 100% of the three accounts shown. There are no intercompany transactions, ownership adjustments or currency translations in this example.

Start with each company's Source report. Keep the original account code and name so a reviewer can find the figure in Xero. In this example, income is positive and costs are negative; confirm the sign convention in the reports you actually use.

1. Retain the source accounts and propose the Standard mapping

Company	Source account	Proposed Standard account	September amount
SPV A	400 — Rent Received	4000 — Rental income	£12,000
SPV A	610 — Repairs	6100 — Routine repairs	−£1,500
SPV A	620 — Property Management	6200 — Property management fees	−£600
SPV B	500 — Rental Income - Flats	4000 — Rental income	£8,000
SPV B	732 — Contractors - Routine Repairs	6100 — Routine repairs	−£1,000
SPV B	740 — Managing Agent Fees	6200 — Property management fees	−£400

The source codes stay different. The shared Standard codes make the reporting lines comparable. Before applying a mapping, the reviewer checks what the account contains: the word “Contractors” alone would not establish that every transaction is a routine repair. A mixed account containing capital improvements needs separate review and an appropriate accounting treatment.

Download the example account-mapping CSV. It contains these six fictional rows, their period, currency and signed amounts. Every row starts with review_required; that status is a prompt for your own review, not an approval or a product validation result. This is a static template for external review and manual mapping. Clarity Ledger does not provide a bulk CSV mapping import through this download.

2. Compare the mapped lines with the Source totals

Once the reviewer has confirmed the proposed mappings, the three-line Standard view would be:

Standard reporting line	SPV A	SPV B	Combined
Rental income	£12,000	£8,000	£20,000
Routine repairs	−£1,500	−£1,000	−£2,500
Property management fees	−£600	−£400	−£1,000
Three-line reporting subtotal	£9,900	£6,600	£16,500

Check the arithmetic in each company before relying on the combined column:

• SPV A: £12,000 − £1,500 − £600 = £9,900.
• SPV B: £8,000 − £1,000 − £400 = £6,600.
• Company check: £9,900 + £6,600 = £16,500.
• Reporting-line check: £20,000 − £2,500 − £1,000 = £16,500.

Mapping changes where an amount is presented; it should not change the amount included. The Source subtotal and Standard subtotal therefore match for each company and for the combined selection, leaving a reconciliation difference of £0. A zero difference would not prove the classification was correct, which is why account review comes first.

3. Keep the limit of the example visible

The £16,500 is a subtotal for the three selected reporting lines. It is not NOI, a complete profit and loss result, distributable cash or a statutory consolidated profit. The example omits other possible income, operating costs, interest, depreciation and tax. A real report needs the full account population and agreed reporting definitions.

Retain the source reports, selected companies, period, proposed mapping, reviewer decision and reconciliation outside the example. If real entities trade with one another, have different ownership shares or use different currencies, complete those additional controls in a separately supported workflow; this simple aggregation does not perform them.

For the property use case, see Xero reporting for property portfolios and SPVs. For the wider reporting workflow, see Source and Standard reporting across selected Xero companies.

Where Clarity Ledger fits today

Clarity Ledger supports selected GBP-base Xero companies. After a successful sync, it provides saved historical P&L, balance sheet and trial balance reports, Source and Standard views, mappings that the user reviews and applies, and Reload/Print actions.

Automatic eliminations, statutory consolidation, transaction drill-through, budgets, forecasts, scenarios, AI commentary, automatic property KPI calculations and investor-pack generation are not enabled. Keep those requirements in a separate reviewed workflow. Explore multi-company Xero reporting.

The practical first step is to prove one historical reporting period reconciles, then decide which additional controls and tools the portfolio needs.

External product references checked on 12 October 2026. Confirm current scope and configuration when choosing a workflow.