Multi-company consolidation in Business Central: when the standard features are enough

Once a business has more than one legal entity, month-end changes. It's no longer "close the books." It's close each company, match the intercompany balances, translate the foreign ones, eliminate what doesn't belong in the group numbers, and produce a consolidated picture someone will sign.

Business Central can do much of this out of the box. Where companies get into trouble is assuming either that it does everything, or that it does nothing and buying an add-on before understanding the problem. Here's a practical view of where the standard features hold up and where they stop.

What Business Central does as standard

Consolidation through business units. You set up a consolidation company and add each subsidiary as a business unit, with its ownership percentage, fiscal year and account mapping. Consolidation brings each unit's general ledger balances into the consolidation company for reporting. (Microsoft's documentation.)

Companies in other environments. If your subsidiaries sit in separate Business Central environments, say a different country or a company acquired with its own setup, consolidation can still pull from them using the API option rather than the same-database option. This matters for groups that grew by acquisition and never merged their systems.

Currency translation. For foreign subsidiaries, you can set translation methods per account. The options include average rate, closing rate, historical rate, composite rate and equity rate. That covers what most auditors expect for translating the income statement and balance sheet.

Intercompany transactions. Business Central's intercompany features let one company send a sales or purchase document, or a journal, to a partner company, where it appears as a matching transaction. With the auto-send and auto-accept settings, the partner company gets journal lines created for it automatically. They still need to be reviewed and posted.

Where the standard features stop

Eliminations are manual. Microsoft's documentation is direct about this: processing consolidation eliminations is a manual process. You enter general journal lines in the consolidation company, preview them with the eliminations report, then post. For a group with a handful of recurring intercompany flows, that's a short, predictable checklist. For a group with dozens of entities and constant intercompany trading, it becomes a real cost every month.

Intercompany matching isn't automatic. Business Central creates the matching transaction, but it won't tell you that Company A recorded a $48,000 management fee while Company B recorded $45,000. Reconciling intercompany balances before you consolidate is still a finance task, and unreconciled differences are the most common reason consolidated numbers don't tie out.

Minority interest and complex ownership structures need careful setup and often manual adjustments.

When an add-on earns its cost

Several solid third-party multi-entity and consolidation tools exist for Business Central. They're worth evaluating when:

  • you have more than roughly 10–15 entities, or the count keeps growing through acquisitions;
  • intercompany volume is high and recurring, such as shared services, inventory transfers or management fees every month;
  • you need automated eliminations and an audit trail that standard journal entries don't give you;
  • the close takes days longer than it should, and the delay is consistently in consolidation, not the entity closes.

They're usually not worth it when the real problem is upstream: inconsistent charts of accounts across entities, intercompany posted to the wrong accounts, or no agreed process for who books what. An add-on automates a process. It won't fix a broken one.

The setup decisions that matter most

In our experience, consolidation pain comes far more often from early design decisions than from missing features:

  1. One chart of accounts, or a clean mapping. Entities that share an account structure consolidate easily. Entities with their own charts need maintained mappings, and those drift.
  2. Dedicated intercompany accounts per partner, so balances can be reconciled at a glance.
  3. Dimensions designed for the group, not one entity at a time, so group reporting by department, region or product doesn't need spreadsheets.
  4. A written close calendar that covers intercompany cut-off and who resolves differences.
  5. One environment or several? Separate environments make sense for different regions, data residency or acquired businesses. They make consolidation and integrations a little more involved, so make the choice on purpose.

For more on these design choices, see Multi-company Business Central: intercompany and consolidation done right.

A seven-entity distribution group was about to buy a consolidation add-on because its close took 12 days. The review showed that the entity closes took two days each, and most of the rest went to chasing intercompany differences caused by two entities posting freight recharges to different accounts. After a chart-of-accounts cleanup and a one-page intercompany posting guide, the close dropped to six days using standard Business Central consolidation. The add-on wasn't needed, at least not yet.

Is your group close slower than it should be?

Or adding entities and want the structure right before it gets harder to change? Cateran works on exactly this: multi-company and multi-currency Business Central, intercompany design, and the integrations around it. See how Cateran handles complex projects.