Intercompany in Business Central: scope early, or you pay later

Intercompany in Business Central is decided at the start, not afterwards. What has to be settled first: same environment or cross environment, how group consolidation is meant to run, and who owns the shared master data. If that is only clarified once the companies are set up, every later correction becomes expensive. If all companies sit in the same BC environment, intercompany postings and shared master data run more directly. If they are separated for legal, regional or operator reasons, the flow needs a deliberately built synchronisation. This fundamental decision shapes everything that follows and can hardly be reversed later without a break. It is not only technical: in a shared environment, companies also share permission logic and number series. That takes coordination during setup but saves it in daily operation. The question therefore belongs before the first setup, not in the rollout phase of the second company.

How the group view of the figures builds on this is covered in How do I consolidate multiple Business Central companies?

Same environment or cross environment: what do you decide first?

If all entities sit in the same BC environment, intercompany postings and shared master data run more directly. If they sit in separate environments, often for legal, regional or operator reasons, the intercompany flow needs a deliberately built synchronisation.

Source: Microsoft Learn: Manage intercompany transactions

This fundamental decision shapes everything that follows and can hardly be reversed later without a break. It is not only technical: in a shared environment, entities also share permission logic and number series, which requires coordination but saves coordination effort in operation.

The question therefore belongs before the first setup and not in the rollout phase of the second entity. Whoever raises it there for the first time has effectively already given the answer, namely through the structure that is already running productively.

Why think about consolidation and master-data ownership from the start?

How do several companies roll up into one consolidated view? Business Central supports intercompany postings and consolidation, but only if the chart of accounts, dimensions and mapping are set up consistently from the start. Retrofitting is considerably more expensive than setting it up correctly.

Source: Microsoft Learn: Consolidate financial data from multiple companies

Set up consistently means concretely: the same chart-of-accounts structure, the same dimension logic and a documented mapping of which accounts feed into the consolidation. Two points belong clarified early here.

• Name master-data authority clearly: who is the data owner for shared customers, vendors, items? Without named authority the companies drift apart and consolidation becomes manual work. A data owner per master-data domain is governance, not a detail.
• Separate mandatory deviations: national law, tax and local processes belong cleanly delimited from the shared intercompany core.

Why scope before creating the companies?

These questions belong answered before the first company is created, not afterwards. Whoever defers them builds a structure that can later only be changed with a break, and in our experience that break falls due exactly when the business has the least time for it.

The effort for the clarification is manageable: there are few decisions, but they need the right people at the table, namely finance, IT and at least one operating country entity. Without that third perspective you get requirements that do not work locally and are then quietly worked around, which afterwards costs the consolidation unnecessary manual work month after month.

Control over structure and master-data ownership stays on your side, with Business Central as home. Before you create the companies: let us scope your intercompany structure and master-data ownership together.