When one company becomes three sets of books

The first entity has a dashboard. The second gets a second tab in the same spreadsheet. By the third, someone has built a summary tab with formulas pointing at the other two, and that tab is now load-bearing infrastructure that exactly one person understands.

This is the point where reporting stops being a report and becomes a monthly ritual.

The two questions that conflict

Multi-entity reporting is awkward because two legitimate questions pull in opposite directions.

• How is each entity doing? Each set of books has its own obligations, its own tax position, and often its own lender. It has to stand alone.
• How are we doing? The group has one payroll cycle to survive and one set of owners. Someone needs the combined picture.

Tools that answer only the first make you build the second by hand every month. Tools that answer only the second quietly hide the entity that is running out of road.

Three things that go wrong first

Intercompany transfers get double-counted. Money moved from the holding company to an operating entity is not income. It shows up as a receipt in one set of books and a payment in another, and unless someone marks it, the group looks more liquid than it is.

Shared costs land in one entity. The software subscription, the office, the bookkeeper — usually paid from whichever account was easiest. The entity that pays looks expensive and the others look lean, and any per-entity margin figure is fiction until it is allocated.

The calendars drift apart. One entity pays rent on the first, another on the tenth; one runs payroll fortnightly, another monthly. Consolidating monthly totals hides the fact that the group's thinnest day is a specific Tuesday.

What to fix before it gets worse

Symptom	Fix
The summary tab only one person can maintain	Move consolidation out of the spreadsheet and into something that recalculates on its own
Intercompany transfers inflating the group total	Tag them at the source so both sides net to zero
One entity carrying every shared cost	Agree an allocation rule once, and apply it the same way every month
Month-end totals hiding a mid-month crunch	Project daily, per entity, then combine — not the other way round

Consolidate daily figures, not monthly ones

This is the part most people get backwards. If you total each entity's month and then add the months together, every within-month timing problem disappears from the result. Projecting each entity day by day and summing the daily figures keeps the shape — and the shape is where the risk is.

It also means the group view and the entity view never disagree, which removes a whole genre of argument from the monthly meeting.