Consolidated Reporting Across Multiple Companies: A Practical Guide

A group with several companies usually has several systems, several charts of accounts, and one leadership team that wants one set of numbers. Too often that set of numbers is a spreadsheet someone rebuilds by hand at the end of every month.

The tool is rarely the obstacle. Consolidated reporting is mostly a data problem, and it is solvable in a fixed order.

Decide what the group needs to see

Start small. Leadership usually needs a handful of numbers across every company: revenue, margin, cash, headcount, orders, backlog, whatever you actually manage by. Resist the urge to consolidate everything. A short list that is right beats a long list that is approximately right.

Agree on common definitions

The same word means different things in different companies. One entity books revenue at shipment, another at invoice. One fiscal year ends in December, another in June. One reports in dollars, another in euros or in thousands. Before you build anything, write down one definition for each number in the group view, including the calendar, the currency and the unit.

If entities genuinely must differ, record the difference and decide how to bridge it. We wrote about running the conversation that gets finance and operations to agree.

Map every company's accounts to a group structure

Each company has its own chart of accounts, and the account numbers do not line up. Create a group structure and map each entity's accounts to it. This mapping is the core of consolidated finance reporting. It is slow, detailed work, it needs someone from finance to sign off, and it is the thing most worth getting right. Keep the mapping in a table, not in someone's head, so it can be reviewed and changed.

Bring the data into one reporting database

Source systems should not be the place you build group reports. Copy the data you need, read-only, into a single reporting database, and keep a company identifier on every row so you always know where a number came from. This is the same architecture we describe in why your ERP's reports are not enough, and it is what makes a group view possible without touching any entity's live system.

Handle intercompany activity

When one group company sells to another, that transaction appears as revenue in one and cost in the other. If you add the entities together without removing it, the group looks bigger than it is. Identify intercompany customers and suppliers, flag those transactions, and eliminate them in the group view. Reconciling the two sides of each transaction is often where hidden differences surface.

Be deliberate about currency

If entities report in different currencies, decide which rates you use and when. Common practice is to translate income statement items at an average rate for the period and balance sheet items at the period-end rate, but your accountants will tell you what applies to you. What matters for reporting is that the choice is made once, written down, and applied the same way every month.

Reconcile to the books

Each period, check the group view against what each entity reports in its own financial statements. Differences are expected at first. Each one you resolve makes the next period easier, and a reconciliation that ties out is what earns leadership's trust.

Decide who sees what

The group view is for leadership. Individual companies should see their own numbers, and often only their own. That means row-level access: leadership sees every company, a general manager sees theirs, and nobody sees another entity's detail unless you decide they should. Plan this early, because adding it afterwards is harder than building it in. Our guide to row-level security in BI covers the pitfalls.

Where Horizon fits

Horizon is our managed BI platform. For a group, we first bring the entities into one reporting database as part of our data architecture work, define the shared metrics once, and then build the group dashboards and each company's own dashboards on top. Each person sees only the data they are allowed to see, and leadership sees the whole group in one place.

If you run a group of companies and want to move off the monthly spreadsheet rebuild, reach out. We will start with the numbers leadership actually needs.