Power BI Multi Entity Consolidation Dashboard for Groups on Mixed ERPs

What does a consolidation dashboard actually do?

It turns several separate ledgers into one set of group financials that refreshes on its own. It maps each entity’s accounts to a shared group structure, removes intercompany activity so the group is not counting money it moved to itself, translates foreign entities into one reporting currency, and totals the result — while keeping every number traceable to its source.

The point is not prettier charts. It is that the consolidated P&L stops being a manual artifact rebuilt after each close and becomes a model your controller, FP&A team and leadership all read from. When an entity reposts a journal, the next refresh carries it through to the group view. When an auditor or board member asks where a number came from, the drill path answers it. Every rule — the account mapping, the eliminations, the rate types — is written down and agreed with you before it is built, because consolidation rules are accounting policy, and accounting policy is yours to set.

How do you consolidate entities on different ERPs?

Each ledger is extracted on its own route, then everything meets at a common grain: entity, group account, period, currency and amount. The source system matters for extraction and stops mattering after mapping. That is why one model can hold a Sage Intacct parent, Xero subsidiaries and a NetSuite or Business Central acquisition together.

The table below shows how each common system typically feeds the model. The right route for your group depends on edition, licensing and data volume, and we confirm it in the scope estimate before any hours are used.

If your whole group lives on a single platform, the platform-specific build is usually the better starting point: see our Sage Intacct Power BI dashboards for groups consolidating inside Intacct, or our Xero Power BI dashboards for groups made up of several Xero organisations. This page is for groups whose entities do not share a ledger. The same pattern applies to our QuickBooks, NetSuite and Business Central builds when one of those is the source for part of the group.

How are intercompany eliminations handled?

Intercompany accounts and counterparties are tagged during mapping, and elimination entries are generated from rules you approve: intercompany sales against purchases, receivables against payables, management fees against fee expense, and loans against borrowings. The group view shows figures before and after eliminations, so the effect of every rule is visible.

The harder problem is that the two sides rarely agree. One entity books the invoice in March and the other in April, or one records it in a different currency. Rather than forcing the totals to net to zero and hiding the gap, the model surfaces an intercompany exceptions page listing each entity pair, both balances and the difference. Your team fixes the mismatch in the source ledger, and the next refresh clears it. Ownership adjustments such as non-controlling interests follow the treatment your accounting policy sets — we implement it as defined, and we do not replace your auditors’ judgment.

How does FX translation work in a consolidation model?

Each foreign entity is reported in its own functional currency and translated into the group’s reporting currency at rates your finance team supplies. Under the common current-rate approach, balance sheet lines use the period-end rate and income statement lines use an average rate, with the translation difference held in its own line rather than buried in profit.

Rates are loaded into a rate table by currency, period and rate type — closing, average or historical — from wherever you source them today. Because the model keeps local-currency amounts alongside translated ones, the dashboard can show how much of a movement came from trading and how much came from the exchange rate, and can restate prior periods at constant currency for a like-for-like comparison. Which rate applies to which line is your accounting policy; we build the rate logic to match it and document it in plain language.

How do you model consolidation so it reconciles?

We build a star schema: entity, group account, calendar, currency and dimension tables around a single fact table of trial balance or journal amounts. Every entity loads at the same grain, so the mapping, elimination and translation logic is written once in DAX and reused by every page instead of copied into separate reports.

We follow Microsoft’s star schema guidance for Power BI (opens in new tab), and for groups with long journal histories we use incremental refresh (opens in new tab) so only recent periods reload. The model reconciles each entity back to its own trial balance before eliminations, so the first question at launch is never whether the source numbers are right. Entity managers can be limited to their own company with row-level security while group finance sees everything — our row-level security setup guide explains how. For the modeling detail, see our data modeling and DAX service.

Who is a multi-entity build for?

It fits groups with two or more legal entities whose consolidated results are still assembled by hand: owner-led groups that grew by acquisition, holding companies with subsidiaries on inherited systems, private equity portfolio companies after an add-on, and nonprofits or franchisors reporting across separately booked organisations.

Portfolio-level KPI rollups across separately owned companies are a different question, covered on our private equity portfolio dashboards page. Fractional CFOs who build a pack for several unrelated clients will find that workflow on our fractional CFO page. Once the group P&L exists, adding a budget layer is a natural next step — our budget vs actual report guide walks through it, and our finance and accounting dashboards cover the wider FP&A picture.

What does consolidation reporting cost?

Work is drawn from prepaid Flex Support hours that never expire. A Starter block is $2,500, Growth is $4,600 and Power is $8,000, and senior hourly work starts from $100. You get a written scope and hours estimate before any work begins, and hours are deducted only for work you approve.

The number of ledgers, currencies and intercompany relationships drives the effort more than the number of entities. Two entities on one system with no currency translation is a modest build; five entities on three systems in two currencies needs more mapping and testing. Most tasks ship 3 to 5 business days after you approve the estimate, and banked hours stay available for the next acquisition, a new entity or a changed elimination rule.

Pricing is our Flex Support labor, not Microsoft licensing. You hold your own Power BI licenses; we work inside your tenant, so you own the workspace, semantic model and credentials.