Multi-company is one of Business Central’s most powerful features and one of its most misconfigured. We have seen companies pay six-figure consulting bills to reorganize a setup they could have done right the first time with three days of thinking.
This article walks through the multi-company setup we use as a starting baseline. It is opinionated. It will not fit every situation. But it will keep you out of the most common traps and give you a clean foundation to evolve from.
Decide your structure before you create your first company
The most expensive multi-company mistakes happen before the first transaction is posted. Three decisions matter most.
Decision one: legal entities vs operating units. BC’s « company » concept is a legal entity. If you have one legal entity with multiple operating units (warehouses, business lines), do not use multiple BC companies. Use dimensions instead. They give you the analytical depth without the operational overhead.
Decision two: shared vs separate master data. If your companies sell to the same customers and buy from the same vendors, you want shared master data via Master Data Management or a custom synchronization. If they are truly distinct businesses, separate master data is fine.
Decision three: shared vs separate chart of accounts. Shared chart of accounts massively simplifies consolidation but constrains each company to a common structure. Separate charts give flexibility but make consolidation painful. For most multi-entity SMBs, shared is the right call.
Create your companies in the right order
Once structure is decided, create companies in the right order to leverage BC’s copy functionality.
Start with a template company. Build the configuration (chart of accounts, dimensions, posting groups, number series, workflows) in a clean empty company. Validate it thoroughly. This is your golden template.
Use RapidStart Services to package the configuration. Export a configuration package from the template, including data tables and setup tables. This is your reusable artifact.
Create each real company from the template. Apply the configuration package to each new company. Adjust per-company differences (specific tax setup, local currency, statutory accounts) after the base is in place.
Resist the temptation to short-cut. Companies created in random order, with random configurations, are companies you will spend years fixing.
Intercompany: the feature that saves your closing
BC’s intercompany module automates inter-entity transactions. If you have multi-company, you need to use it.
Set up intercompany partner records linking each company to its counterparts. Define the intercompany chart of accounts (the GL accounts used for cross-company postings). Configure intercompany transactions for sales, purchases, and journal entries.
The payoff: when company A sells to company B, the transaction posts in A and creates a matching transaction in B automatically. No double entry, no reconciliation breakage, no Excel between systems.
Most partners do not set this up properly. They create the intercompany partner records but skip the chart of accounts mapping. The result: transactions flow but post to the wrong accounts. The finance team spends every month reclassifying intercompany entries by hand.
Consolidation: the BC way and the external way
BC has a native consolidation module for combining multi-company financials. It works well for simple structures (less than 10 companies, single currency, common chart of accounts).
For complex consolidation (more than 10 companies, multiple currencies, eliminations, minority interests), the native module shows its limits. The serious 2026 pattern is to use BC as the transactional source and feed a dedicated consolidation tool (LucaNet, OneStream, or Power BI with a Tabular Model).
Decide your consolidation architecture at multi-company setup time, not after. Retrofitting a consolidation tool onto a BC environment that was not designed for it is more expensive than the consolidation tool itself.
Common multi-company traps
Five traps we see repeatedly.
Trap one: number series conflicts. Each company has its own number series. Without naming conventions, you end up with duplicate invoice numbers across companies. Prefix every series with the company code.
Trap two: shared user permissions getting messy. As you add companies, user permissions sprawl. Use permission sets and groups, not individual user permissions. Audit them quarterly.
Trap three: dimensions used inconsistently. If « Department » means something different in each company, your consolidated reporting is meaningless. Standardize dimension values across companies before go-live.
Trap four: intercompany not enforced. If users can post directly to intercompany accounts without using the intercompany module, the system gradually drifts out of balance. Lock direct posting to those accounts.
Trap five: storage and performance. Multi-company BC consumes storage proportionally. Plan your data retention policy from day one. Archive historical transactions to Azure Storage rather than keeping everything live.
The Asio Services way: clean multi-company from day one
We approach multi-company with the same philosophy as everything else: it is much cheaper to do it right the first time than to fix it later. Our multi-company implementations start with a written structure document, validated by the CFO before any technical work begins.
If you are about to set up multi-company in BC, or you have a multi-company environment that is showing strain, we can help you design (or redesign) it cleanly.
→ Book a free discovery call with Asio Services. We will review your multi-company setup and tell you where to clean up.
