Consolidated Reporting for Family Offices: One Statement Across Multiple Entities, Currencies, and Asset Classes
A single-account investment statement has one owner, one currency, and one custodian's data feed behind it. A family office consolidated statement has none of those simplifications. The same family's wealth typically sits across several legal entities — a trust here, an LLC there, a holding company somewhere else — each with its own custodian relationship, its own asset mix, and in many cases its own currency, because family wealth doesn't confine itself to one jurisdiction just because the reporting template would prefer it to.
Building a report for this isn't a bigger version of a single-account statement. It's a structurally different document, because the thing being reported on — "the family's wealth" — isn't a single position with a single value. It's a roll-up of several genuinely distinct entities, each of which needs to be represented correctly on its own terms before any consolidation happens at all.
Why Family Office Reporting Is Structurally Harder
The complexity isn't a matter of more line items. It's a matter of more dimensions that all need to be represented simultaneously and correctly.
Multiple legal entities. A trust, an LLC holding real estate, a holding company for operating business interests, a direct investment account — each is a separate legal structure with its own custodian relationship, its own transaction history, and often its own accounting basis. Treating them as one undifferentiated pool loses exactly the structure that matters for the family's own governance, tax, and estate planning purposes.
Multiple custodians. Each entity's holdings frequently live with a different custodian or platform, meaning the underlying data doesn't arrive as one clean feed — it arrives as several, each in that provider's own format and cadence, that need to be brought together for the consolidated view.
Multiple currencies. A family with property in one country, an operating business in another, and liquid investments held in a third does not have one natural reporting currency at the entity level. Each entity's figures are meaningful in their own currency; only the family-level roll-up needs a single reference currency to actually be comparable.
Multiple asset classes. Public securities, private holdings, real estate, direct business interests — often within the same entity, let alone across the family's full structure — each with different presentation conventions.
None of these dimensions is unusual on its own. What makes family office reporting genuinely hard is that all of them apply simultaneously, on one document, for one family.
The Entity-to-Consolidated-View Problem
The core design tension is this: each entity's holdings need to be reported on that entity's own terms — its own currency, its own asset mix, its own level of detail — and then rolled up into a single family-level summary, without the roll-up process erasing the entity-level detail that the family, their tax advisors, and their attorneys actually need.
Collapsing everything into one flat, entity-agnostic table to make the roll-up simpler solves the wrong problem. It produces a summary that's easy to read and useless for anyone who needs to know which entity actually owns which asset — which is, for a family office, most of the audience the statement is for. The correct structure preserves each entity as its own section, reported correctly and completely, with the family-level summary sitting alongside — not replacing — that entity-level detail.
How Subreports Map to This Structure
This is the same architectural pattern that applies to any document assembled from independently scoped sections: each entity becomes its own independently maintained report unit — with its own data source, its own currency formatting, its own asset class breakdown — embedded into a parent document that handles the overall structure and the consolidated roll-up.
The advantage of treating each entity this way rather than building one large template that tries to account for every entity's peculiarities inline is that a change to how one entity's real estate holdings are presented doesn't require touching the trust's securities section or the operating company's balance sheet section. Each entity's reporting logic lives and evolves independently. Adding a new entity to the family's structure — a newly formed LLC, an additional trust — doesn't require rebuilding the statement. It requires adding one more entity to the list the parent document iterates over, using the same entity-level template that's already proven correct for every other entity.
This also means the number of entities a family has doesn't determine how many templates need to be maintained. One entity-level template, reused once per entity in the family's structure, produces a consolidated statement for a family with three entities or thirty, without the template count growing alongside the family's structure.
The Multi-Currency Requirement
Multi-currency handling in a family office statement has two distinct layers, and conflating them is where this usually goes wrong.
Entity-level display. Each entity's own section should show that entity's figures in that entity's native currency. A trust holding euro-denominated securities should show euro figures in its section — converting them to the family's reference currency at the entity level obscures what the entity's own records actually say, and creates a reconciliation headache when the entity's figures are compared against its own custodian statement.
Family-level roll-up. The consolidated summary, by contrast, needs everything expressed in one reference currency to actually be comparable and summable across entities. This roll-up figure is a conversion and aggregation calculation — take each entity's native-currency total, convert it to the family's chosen base currency at the applicable rate, and sum across entities.
The important distinction is that this conversion and aggregation is a data calculation your accounting or portfolio aggregation system performs upstream, not something a reporting template does on the fly. The reporting layer's job is to display each entity's figures correctly in their native currency, and separately display the already-converted, already-summed roll-up figures in the family-level section — each formatted with the correct currency format for its own section. This is a formatting and structural concern, not a computation the template needs to own, and it's exactly why one template can serve entities in different currencies without needing a template variant per currency.
Where This Differs from a Standard Investor Statement
A standard investor statement answers "what does this client own and how has it performed." A family office consolidated statement answers a related but broader question: "what does this family's structure hold, entity by entity, and how does it add up." The audience is different too — often the family principals themselves, alongside the family office's own operations, tax, and estate planning functions, rather than an external investor relationship the statement exists to maintain.
That broader question is why entity-level ownership detail isn't optional context to a family office statement — it's frequently the primary reason the document exists. A single-account template, however well designed, was never built to answer "which entity owns this," because a single-account client only has one answer to that question. A family office statement has to answer it correctly for every entity in the structure, every time.
How This Maps to CxReports
Each entity as its own subreport. An entity-level report — its own data source, its own currency, its own asset-class breakdown — is built once as a subreport, with an entity identifier as its scoping parameter. The parent statement's entity list drives data-driven repetition, embedding one subreport instance per entity in the family's current structure. Adding an entity to the family's structure means adding a row to that list, not rebuilding the template.
Native currency per entity section. Each entity's subreport formats its figures using the currency format appropriate to that entity — currency;EUR;2 for a euro-denominated trust, currency;GBP;2 for a UK real estate holding LLC — independently of what currency any other entity in the same statement uses.
Family-level roll-up as its own section. The consolidated summary is a Data Table or Key Value Grid bound to a roll-up data source that already contains the converted, summed figures in the family's base currency — supplied by your accounting or aggregation system, not calculated within the template. This section uses the base currency's format code, consistent regardless of how many entities or currencies feed into it.
Asset class breakdown within each entity. Where an entity holds a mix of asset classes, that entity's subreport uses the same Data Table grouping and aggregation used for any asset allocation breakdown — configured once per entity type, not once per entity.
What stays outside CxReports: currency conversion rates and the resulting converted figures, the aggregation logic that sums across entities into the family-level roll-up, and the determination of which entities belong in a given family's structure are all your accounting, custodial data aggregation, or family office management system's responsibility. CxReports assembles the entity sections correctly, formats each section's figures in the right currency, and presents the roll-up you provide — it does not perform the conversion or the consolidation math itself.
Getting Started with CxReports
| Family office reporting requirement | CxReports mechanism | What stays with your systems |
|---|---|---|
| One section per legal entity, correctly scoped | Subreports with entity identifier as scoping parameter | Entity data source and current entity list |
| Adding entities without rebuilding the template | Data-driven repetition of the entity subreport | Maintaining the entity list your aggregation system provides |
| Native currency display per entity | Currency format codes configured per entity section | Each entity's native-currency figures |
| Family-level roll-up in one reference currency | Data Table / Key Value Grid bound to a roll-up data source | Currency conversion and cross-entity summation, calculated upstream |
| Asset class breakdown within an entity | Data Table grouping and aggregation | Asset classification data per entity |
| Entity ownership detail preserved alongside the summary | Entity sections retained as independent subreports, not flattened | Entity structure and ownership records |
For documentation on subreports, data-driven repetition, and text formats, see the CxReports documentation. To discuss consolidated reporting across your family office's entity structure, request a demo.