A multinational enterprise coordinates business activity across national boundaries. To understand how it works, trace a real transaction: who sells, produces, pays, holds information, and resolves an exception. The organization chart explains only part of that journey.
Separate the enterprise group from its relationships
The OECD’s statistical framework describes a multinational enterprise group through enterprises under the same ultimate controlling parent, across economies. A separate supplier or distributor can be essential to the work while remaining outside that controlled group. Label ownership and commercial relationships separately.
Start a practical map with the legal entities involved, their locations, and the business role each performs. Then add the team or person responsible for each handoff. A group brand on an email or package is insufficient to identify the contracting entity, data owner or decision authority.
For one product line, collect the order, internal transfer instructions, delivery record and customer contact path. Ask the people performing the work to explain where the records disagree. This often reveals dependencies that a high-level presentation leaves out.
Follow a fictional cross-border order
On narrow screens, scroll horizontally. Keyboard users can focus the table region and use the arrow keys.
| Stage | Role to identify | Handoff evidence |
|---|---|---|
| Customer order | Selling entity and account owner | Accepted specification and promised date |
| Production | Manufacturing entity and planning team | Capacity confirmation and approved product version |
| Shipment | Logistics owner and responsible trade specialists | Release criteria and shipment records |
| Delivery or problem | Receiving party and customer-service owner | Receipt, discrepancy and next action |
| Settlement | Relevant finance teams | Agreed records and reconciliation responsibility |
Imagine a fictional group with a sales company in one country, a factory in another, and a shared service team elsewhere. A customer requests a revised component after production planning has started. The sales team needs a named route to confirm technical feasibility and timing before changing the commitment.
The change record should connect the old specification, the approved revision, affected quantity and customer decision. A shared spreadsheet can support a small operation if ownership and access are clear; more complex systems still need those same definitions. A system connection alone does not assign authority.
Agree what is shared and what is decided locally
Identify decisions that need a common definition: product identification, reporting periods, exception categories and escalation contacts. For local choices, name the limits of delegated authority and the evidence that triggers a group-level review. Describe the actual decision instead of writing “head office approval” without a person or response route.
Time zones make handoff quality visible. A request sent at the end of one location’s workday may wait through another’s night. Provide the inputs needed to act, state urgency and the applicable timezone, and agree a backup for genuinely time-sensitive exceptions.
Keep business coordination distinct from legal, tax and regulatory conclusions. Employment, trade restrictions, data handling and intercompany pricing require the applicable current rules and responsible specialists. A common operating checklist should identify those review owners without pretending to replace their analysis.
Rehearse a dependency failure
Use the cross-border responsibility map to record the normal route, dependency and fallback. Rehearse with invented or sanitized records, then fix unclear ownership before a live interruption.
Include consequences beyond the internal handoff
The 2023 OECD Guidelines for Multinational Enterprises on Responsible Business Conduct are government recommendations addressing areas including human rights, labor, environment, disclosure and supply-chain due diligence. They provide a broader lens for asking how operations and relationships affect others; applicable legal obligations still require jurisdiction-specific review.
At a regular review, select one completed transaction and one exception. Check whether records agree, the right people could act, and the response created another problem elsewhere. Update the map when entities, suppliers, systems or responsibilities change.