Which system should be the source of truth for supplier master data?

In most manufacturers, the ERP is the primary system of record for supplier master data that drives purchasing, payment, and basic supplier identity. That is usually the default answer.

But the complete answer is not that one system should own every supplier-related field. In practice, supplier data is a domain-based master data problem. Different systems often own different attributes:

• ERP: supplier ID, legal entity, remit-to information, payment terms, purchasing status, approved buying relationships
• QMS or supplier quality system: approval status, audits, corrective actions, nonconformance history, qualification evidence
• SRM, portal, or sourcing system: onboarding workflow, contacts, commercial documents, performance metrics
• PLM or engineering-related systems: supplier-part relationships, approved sources for specific items, technical document linkage where applicable

So if the question is whether there should be one operational source of truth for all supplier data, the answer is usually no. If the question is which system should be the authoritative master for core supplier identity and transactional vendor records, that is most often ERP.

What works in practice

A workable model is:

• Use ERP as the authoritative source for the core vendor master used in procurement and finance.
• Define field-level ownership for supplier attributes that belong in quality, compliance, or collaboration systems.
• Publish those ownership rules in a governed data model, with clear stewardship and change control.
• Synchronize data between systems through controlled interfaces, not duplicate manual maintenance.

This matters because trying to force QMS, MES, PLM, or a supplier portal to replace ERP as the vendor master often creates reconciliation problems, approval conflicts, and audit trail gaps. The opposite mistake also happens: teams try to push every quality and qualification attribute into ERP even when ERP is not the real process owner.

Key dependencies and tradeoffs

The right answer depends on your operating model and system landscape:

• If finance and procurement are centralized, ERP usually must remain authoritative for core supplier master records.
• If supplier approval is tightly regulated, quality status may need to be mastered in QMS and only referenced in ERP.
• If plants run mixed ERPs or acquired business units, a separate MDM layer or canonical model may be needed to manage cross-system consistency.
• If integration quality is weak, declaring a source of truth on paper will not solve duplicate, stale, or conflicting records.

The tradeoff is straightforward: a single-system model is simpler to explain, but often inaccurate in brownfield environments. A federated ownership model is more realistic, but it requires stronger governance, mapping, validation, and monitoring.

Brownfield reality

In regulated, long-lifecycle operations, full replacement is rarely the safest answer. Replacing ERP, QMS, or supplier quality workflows just to create a single supplier master commonly fails because of qualification burden, validation effort, downtime risk, integration complexity, and the need to preserve traceability across existing processes.

For that reason, many plants keep the existing ERP as the vendor master, then integrate it with QMS, SRM, and other systems that own supplier-specific evidence, status, or performance data. That is less elegant than a clean-sheet architecture, but often more reliable and lower risk.

What to decide explicitly

Do not stop at naming one source system. Define:

• which system owns each supplier attribute
• which system assigns the primary supplier identifier
• which changes require review or approval
• how records are matched across plants and business units
• how approval, block, or disqualification status propagates to buying and receiving processes
• how audit trails and historical changes are retained

If those rules are not explicit, the organization does not really have a source of truth. It has competing copies.

So the practical answer is: ERP is usually the source of truth for core supplier master data, but not for all supplier-related data. In most regulated brownfield environments, the better pattern is field-level ownership with controlled synchronization, not a blanket single-system claim.