Companies that operate through multiple legal entities, business units, or geographic regions typically maintain separate vendor masters for each. Sometimes the separation is by design (different ERPs in different entities, different operational requirements). Sometimes it is accidental (legacy from acquisitions, organic growth that never consolidated).
The same vendor often appears in multiple of these masters. The vendor that serves the parent entity also serves two acquired subsidiaries. Each entity created its own vendor record. The records have inconsistent data. Pricing differs because each entity negotiated separately. Volume that would qualify for enterprise pricing is fragmented across the masters.
Multi entity vendor governance is the discipline of recognizing these shared vendor relationships, managing the data consistently across entities, and capturing the commercial benefits of treating the same vendor as a single relationship rather than multiple unrelated relationships.
The Cross Entity Vendor Problem
Several specific issues arise when the same vendor exists in multiple entity masters.
Inconsistent data across records
The same vendor has different addresses, different payment terms, different tax classifications, or different banking details across the entity masters. The inconsistency creates operational confusion and tax reporting challenges.
Lost negotiating leverage
Each entity negotiates with the vendor independently. Combined volume that would qualify for better pricing is fragmented. The vendor benefits from price discrimination across the entities.
Duplicate compliance work
Each entity onboards the vendor separately, runs sanctions screening separately, collects tax documentation separately. The compliance work duplicates across entities for the same underlying vendor.
Fragmented spend reporting
Spend with the vendor is split across entity reports. Group level views of total spend require manual aggregation, often with errors because entity coding differs.
Inconsistent risk management
Each entity may have different risk assessments of the same vendor. Without coordination, the group level view of vendor risk is unclear.
Master Record Consolidation Approaches
Three approaches to managing the cross entity vendor problem, with different levels of investment and capability.
Approach 1: Single consolidated master
All entities share a single vendor master. Each vendor exists once, with entity specific attributes (entity assignments, entity specific terms) tracked as variations within the single record.
Highest level of consolidation and benefit, but typically requires shared ERP or substantial integration between separate systems. Often the appropriate target state but rarely the current state.
Approach 2: Federated master with cross reference
Each entity maintains its own vendor master, but a cross reference layer identifies when the same underlying vendor exists in multiple masters. Group level reporting and negotiations use the cross reference layer.
Moderate investment, maintains entity autonomy, captures most of the consolidation benefits. The common middle ground for multi entity organizations.
Approach 3: Periodic reconciliation
Entity masters remain fully separate. Periodically (often annually), procurement or finance reconciles across entity masters to identify shared vendors and assess consolidation opportunities.
Lowest investment, but provides only point in time visibility. Useful for organizations where full federation is not feasible or warranted.
Local vs Global Ownership
Even with consolidated visibility, the operational ownership of vendor relationships needs to be allocated between global and local levels.
What benefits from global ownership
- Commercial negotiations and pricing for vendors serving multiple entities
- Compliance and risk assessment for the underlying vendor entity
- Group level vendor master data standards and quality
- Strategic relationship management for major suppliers
What stays local
- Day to day operational relationship management within each entity
- Local performance monitoring against entity specific SLAs
- Tactical procurement decisions on specific orders and releases
- Local commercial nuances that reflect entity specific operating conditions
The interaction model
Local entity teams handle the operational relationship. Global procurement provides the commercial framework and consolidation strategy. The interaction needs to be defined explicitly so neither layer accidentally undercuts the other.
The Governance Model
Effective multi entity vendor governance has five components.
Global vendor registry
A single registry that identifies vendors operating across multiple entities. The registry connects to each entity master through cross references. Updates to global vendor information flow through the registry.
Designated category leads
For each major category, a designated global lead manages the strategy and the major vendor relationships across entities. The category lead coordinates with local procurement teams but provides the global perspective.
Group commercial agreements
For vendors serving multiple entities, group level commercial agreements that all entities can transact under. The agreement defines pricing, terms, and other commercial provisions at the group level.
Shared data standards
Consistent data standards apply across entity masters: same field structures, same coding conventions, same data quality requirements. Standards make consolidation possible even with separate masters.
Periodic group reviews
Regular group level reviews surface cross entity vendor situations: opportunities for consolidation, emerging concentration risks, performance issues affecting multiple entities.
Handling Acquisitions
Acquisitions create predictable cross entity vendor issues. Approach matters for the integration outcome.
- During diligence, identify shared vendors. The acquired company's vendor master is compared against the parent master to identify vendors that exist in both.
- During the first 100 days, prioritize the most material shared vendors. Engage these vendors on the combined relationship and assess consolidation opportunities.
- Within the first year, integrate the vendor master following the chosen approach (consolidated, federated, or periodic reconciliation). Data standards get applied to the acquired master.
- Over the following 12 to 18 months, capture the consolidation benefits through renegotiated commercial agreements, eliminated duplicate compliance work, and unified performance management.
- Beyond two years, the acquired vendor master is operating consistently with the parent. The discipline established during integration prevents new divergence.
Reporting Consolidation
Group level vendor reporting requires consistent data and explicit consolidation logic.
- Total spend with each vendor across all entities, with the cross reference layer providing the aggregation
- Vendor concentration at the group level, which is typically higher than concentration in any single entity
- Compliance status at the group level, including any vendor with compliance issues affecting any entity
- Performance trends across entities, showing whether issues are isolated or systemic
Group level reporting is what makes the multi entity vendor governance investment visible. Without the reporting, the consolidation benefits exist but cannot be demonstrated, which makes ongoing investment in the discipline harder to justify.
Start Here
Identify the top 20 vendors at each major entity. Cross reference to see how many appear in multiple entity masters. The exercise reveals the immediate consolidation opportunity set.
From the cross reference, prioritize three to five shared vendor relationships for consolidation. These become the proof points that justify broader investment in multi entity governance.
