How do you build a group foundation without erasing the reality of subsidiaries?

A multi-entity platform must distinguish the scope, data, and rules of each entity while keeping a coherent group foundation.

The real issue is avoiding group consolidation based on manual rework or on different interpretations of the same object depending on country, brand, or business unit.

Which permissions and reference data should be governed at group level?

Permissions must be defined by entity, role, region, language, or responsibility level according to the group structure.

That framework must remain understandable for both central and local teams. Without it, a group platform quickly becomes a product nobody truly dares to evolve anymore.

What should be shared without making local entities rigid?

Some building blocks should remain shared: reference data, reporting, identity, documents, or approval rules.

The right level of shared capability is the one that allows consolidation, comparison, and governance without forcing every entity into a uniform logic that no longer matches operational reality.

How do you welcome new entities without rewriting the platform?

The platform must accept new entities, local rules, and countries without distorting the product core.

A healthy group foundation is recognized by its ability to absorb a new entity without reopening a full architecture initiative or multiplying exceptions that become impossible to maintain.