
Define each record’s destination and access boundaries when commissioning a multi-company Business Central integration.
Index
A business group may use one external application across several companies. Business Central integration must distinguish the target environment and company. Correct authentication without proper routing can send a valid transaction into the wrong business context.
Routing is a business rule
Microsoft documentation describes endpoints containing an environment and company identifier. The project question is which authorized information selects those values. Business unit, contract and sales portfolio can imply different destinations. Avoid inferring the company solely from a display name or one global application setting.
An external installation per company simplifies some isolation requirements but multiplies maintenance. A shared application can centralize operations if context remains explicit in reads, writes and execution logs. Include permissions and environment-switching procedures in the decision; do not copy production credentials into testing.
Items that must be clearly bounded
- An authorized company and environment map, identifying who approves each association and how it is maintained.
- Operations by destination: specify which records may be read or created, including customizations requiring further analysis.
- Contextual history: store company and environment on every attempt so investigation does not mix group transactions.
Test one reference in two companies
In a hypothetical example, two records share an external reference but belong to different companies. Acceptance must show that each operation uses the correct association. Add a removed destination and a user without access to one company. The expected outcome is an understandable block or a routed issue, never an attempt in another available company.
Reference for assessing scope
Business Central endpoint structure — Microsoft
Prepare your project with Quantum9
Send Quantum9 the company, environment and journey map supported by the external application. An initial delivery can validate one business route before extending integration across the group.