Ask three people how many active suppliers your company has. Your finance director says 847. Procurement says 612. The ERP vendor master shows 1,203. None of them is wrong, exactly. They are each counting from a different list.
Supplier master data management is the practice of fixing that. One authoritative record per supplier. Every system reads from the same source. Changes go through a process. Duplicates cannot be created because the system rejects them at entry.
Most organizations know they have a supplier data problem. Few have fixed it, because the path from “our data is a mess” to “we have a working governance model” is not obvious. This post covers what supplier master data includes, what breaks when nobody manages it centrally, and how to start.
What supplier master data actually includes
The vendor master in your ERP is a starting point, not the full picture. Each department needs different attributes from the same supplier, and those attributes are scattered across different systems.
No single system holds all of these. Your ERP has the financial fields. Your procurement portal has categories and contacts. Compliance certificates live in email attachments or a shared folder. Logistics requirements are in a spreadsheet someone built three years ago and nobody wants to touch.
The data exists. It just is not in one place, and the pieces do not always agree.
What breaks without central management
Duplicate payments
When “Siemens AG” and “Siemens Industries” are two separate records in your ERP, invoices can match against either one. If the same invoice gets processed against both, you pay twice. Finance catches some of these during reconciliation. The ones that slip through become credit notes, AP audit findings, or losses if the supplier never flags it.
The cause is not AP carelessness. The system allowed two records for the same legal entity, and nobody enforced uniqueness at creation.
Fragmented spend data
If your total IT hardware spend is split across six supplier records — some under the parent company, some under subsidiaries, some miscategorized — procurement cannot calculate the real number. They negotiate volume discounts without knowing total spend. They approve a new subsidiary as a supplier without realizing four are already active.
The spend consolidation case for supplier MDM is often stronger than the compliance case. Companies rarely measure it, but lost negotiation leverage is real money.
Slow supplier onboarding
Without a defined supplier record structure and an approval step, onboarding a new vendor is a chain of email threads. Procurement sends a form. Finance needs the IBAN. Legal needs a signed questionnaire. Two weeks later the invoice arrives and the ERP record is still half-empty. The PO gets blocked.
Good supplier MDM makes onboarding a structured intake with required fields and one approval step. New suppliers go live in a day, not a week.
What good supplier MDM looks like
One record per supplier. A unique identifier — VAT number in the EU, EIN in the US, DUNS globally — is a required unique field at creation. The system rejects a save if that identifier already exists on another record. Duplicates cannot be entered.
Required fields for core attributes: legal name, VAT, IBAN, payment terms, category. Empty required fields are validation errors, not warnings. You cannot save a partial record and come back to it later. Partial records are how most duplicates start.
An approval workflow for new suppliers and significant changes — bank account updates especially. The approval step catches things automated validation misses. A data steward who knows the supplier list will spot “Siemens Netherlands” when “Siemens EMEA” is already active.
Downstream systems read from the master. They do not maintain their own copies. When payment terms change, it changes once, in one place, and every connected system picks it up.
Where to start
Scope the first phase tightly: suppliers who received a purchase order in the last 12 months. That is probably 20 to 40 percent of your total vendor master but covers 80 to 90 percent of your spend.
- Export the active supplier list from your ERP.
- Deduplicate using VAT number as the key. Two records with the same VAT number are the same legal entity. Merge them.
- Define your required fields. Six to eight is enough to start: legal name, VAT, IBAN, payment terms, category, status.
- Load into a central system with unique key enforcement and an approval workflow.
- Block new records without required fields. Require a data steward to approve before a supplier goes live.
- Measure before and after: time to onboard a new supplier, duplicate payment credits per quarter, AP query volume.
You do not need a Chief Data Officer or a governance committee. You need one procurement lead who owns supplier data quality, a system that enforces the rules automatically, and the willingness to start narrow. Most teams cover their active supplier base in a few weeks. Inactive suppliers and other domains can wait.
Common questions
What is supplier master data management?
It is the practice of maintaining one authoritative record per vendor, covering legal name, VAT number, bank details, payment terms, spend category, and the other fields procurement, finance, and operations each need. Every system reads from that record. None maintains its own copy.
What fields should a supplier master record include?
A minimum viable record covers: legal name (as registered, not a trading name), VAT number, IBAN, default payment terms, spend category, primary contact, address, and active or inactive status. Compliance-heavy industries add vendor screening status, certificate expiry dates, country of incorporation, and risk tier. Those eight baseline fields are what most procurement and AP teams need without manual workarounds.
How do duplicate supplier records cause duplicate payments?
When the same supplier exists as two records, invoices get matched against whichever one AP opens first. If the same invoice is processed against both, it gets paid twice. Finance rarely catches this until the supplier sends a credit note or an audit surfaces it. The underlying cause: the system let two records for the same legal entity exist, and nobody enforced uniqueness at creation.
How do you start centralizing supplier master data?
Scope tightly: suppliers with purchase orders in the last 12 months. Export from your ERP, deduplicate on VAT number, define six to eight required fields, load into a central system. Make VAT number a mandatory unique field. Assign one owner who approves new suppliers before they go live. That is a working governance model. Expand later.
What is the difference between a vendor master and supplier master data management?
The vendor master is a table in your ERP: account codes, payment terms, tax IDs. Supplier master data management is the governance around it: who can create records, what fields are required, how changes get approved, and whether the data matches what procurement and finance actually use. Most companies have the first. Few have the second.
Ready to centralize your supplier master data?
Primentra gives you a structured supplier model with required field enforcement, VAT uniqueness validation, and a built-in approval workflow. It runs on SQL Server and deploys in a day. The data quality rules are configurable per entity. The 60-day trial includes everything.