Supplier master data: what it is and why it underpins procurement and supply

Supplier master data is the set of information that identifies, qualifies and keeps up to date every partner that sells products or provides services to your company. Legal name, CNPJ (Brazil's company registration number), registration status with the Receita Federal (Brazil's federal tax authority), bank details, payment terms, supply category, vendor approval documentation. All of that is master data. And it is that set that decides whether a purchase order goes out on time, whether the payment lands in the right account and whether the company is really dealing with who it says it is.

I have implemented SAP at companies large enough to see purchasing paying a supplier with an expired boleto (a Brazilian bank payment slip) because nobody updated the payment terms in the record. I have seen a contract signed with a company that had been in irregular registration status with the Receita for months. The system blocked nothing, because it only sees what is in the record. If the data is wrong, the purchase order goes out wrong in the most expensive way: after it has already gone into production.

What supplier master data is in practice

The supplier record is not just the name and the CNPJ. In a mature MDM structure, it brings together at least four blocks of information: the tax and legal block, with CNPJ, state registration (Brazil's state-level tax registration), tax regime and status with the Receita Federal; the financial block, with bank details, currency, payment terms and linked cost center; the supply block, with supply category, purchasing group, incoterm and standard delivery time; and the compliance block, with vendor approval documentation, certificates, contracts and due diligence history.

Each of those blocks has a different owner inside the company, which already explains a good part of the mess. Tax takes care of one piece, finance of another, purchasing of a third, and nobody looks at the record as a whole until the day the payment fails or the invoice is denied.

How supplier record maintenance works in practice

In SAP, the supplier is treated as a Business Partner, created with transaction BP, which replaced the old XK01 and the LFA1 table in the most recent S/4HANA versions. The creation goes through a general view, a purchasing view and a finance view, each filled in by a different area. In other ERPs such as TOTVS and Oracle the logic repeats: the record is born in one module and needs validation in another before becoming a supplier able to receive a purchase order.

The ideal path starts with a creation request, made by whoever is negotiating with the supplier, usually purchasing. That request enters an approval workflow, goes through document checks, through tax status validation and only then is released for use in the ERP. When that flow does not exist, the analyst creates the supplier directly in the database so as not to block an urgent purchase, and formal vendor approval becomes a pending item that nobody chases anymore.

This is the point where most Brazilian companies really lose money. Unlike customer master data, where the CNPJ or CPF (Brazil's individual taxpayer number) works as a key and easily prevents duplication, the supplier's risk is rarely the repeated record. The real risk is the supplier that operates without being approved, the expired clearance certificate (certidão negativa), or the registration status that no longer matches what is registered with the Receita. This kind of failure does not show up in a duplication report. It only shows up when there is a problem.

Who is responsible for supplier master data

The correct answer is more than one area, and that is why a formal data owner is needed. Purchasing defines the need and starts the record creation. Tax and legal validate the documentation and the regulatory status. Finance confirms bank details and payment terms. IT maintains the integration between the registration system and the ERP. And the data steward, when the company has that function, makes sure the quality rules are applied before the supplier becomes an active record.

Without a clear owner, each area looks after only its own part and the record is never treated as a single asset. Master data governance is not about buying a new tool. It is about deciding who answers when the record is wrong. As long as that question does not have a first and last name, the problem will keep repeating.

Which tools support supplier MDM

The MDM market offers specific solutions for this domain, often inside a multi-domain suite that also covers customers and materials. Among the most widely used platforms in Brazil and worldwide are SAP Master Data Governance, natively integrated into the SAP ecosystem, Informatica MDM, Stibo Systems, which has a dedicated supplier MDM solution, Reltio, Semarchy, Profisee and Ataccama, the latter also strong in data quality.

For due diligence, tools come in for looking up registration status, certificates and public CNPJ data, integrated through API directly into the vendor approval workflow. And for those without the budget for a full platform, a well-designed workflow routine inside the ERP itself, with step-by-step approval and a document checklist, already solves a good part of the problem. The tool matters less than the process it automates.

How to learn to work with supplier master data

Those who want to enter or grow in this area need to master three fronts at the same time: the procurement and supply process, the record creation logic inside the ERP the company uses and the data governance concepts that support all of it. Understanding how an RFP works and what due diligence is makes as much difference as knowing where each field sits on the record creation screen.

The CDMP certification from DAMA International is the most recognized reference in data management in the world, and it covers the MDM, quality and governance fundamentals that apply to the supplier domain. Courses focused on master data, SAP and MDM, like the ones we structured at MDM Academy, complement that knowledge with the practical part the professional will use day to day.

Career opportunities in this area

Demand for those who understand suppliers, purchasing and master data together has been growing, and it is not a fad. Every company that goes through an ERP migration, a compliance project or an external audit quickly discovers that its supplier master data is full of holes, and needs people who know how to fix it. Master data analyst, supplier data steward, MDM specialist and governance consultant are positions that appear frequently in midsize and large companies, especially those with SAP, Oracle or TOTVS operations.

Those who master this specific domain, with knowledge of purchasing, tax and data at the same time, usually stand out quickly, because it is a rare profile. Most data professionals understand technology, but not the purchasing process. Those who close that gap have room to grow.

Main questions about supplier master data

What happens if the supplier is not properly approved? The company runs tax risk, the risk of paying someone who should not receive payment and reputational risk, besides potentially being exposed in an audit or compliance due diligence.

What is the difference between creating a supplier record and approving a supplier? Creating the record is the technical registration in the ERP. Approval validates whether that supplier is fit, in terms of documents and operations, to do business with the company. A supplier can have a record without being approved, and that is more common than it seems.

Is supplier duplication a real problem in Brazil? Less so than material duplication, because the CNPJ works as a natural key. The greater risk with suppliers is expired documentation and outdated registration status.

Is supplier MDM only for large companies? No. Smaller companies suffer the same kind of error, just in smaller volume. In a large company, the error multiplies faster and costs more to fix later.

Can the vendor approval workflow be automated? Yes, and it is one of the automations with the fastest return in MDM projects, because it reduces approval time and creates an auditable history of each step.

MDM Academy: where to really learn master data

MDM Academy is 4MDG's school of master data governance. We created it because I realized, after almost thirty years among SAP, purchasing and data projects, that Brazil lacked a place that taught MDM the way it happens in practice, without wrapping the subject in empty technical jargon.

The courses range from the fundamentals of governance and data quality to specific training on material, supplier and customer master data, with real examples from purchasing, supply chain and SAP. We also have Data Club, a community for exchanging experience with other professionals who live the same kind of problem every day. If you work with master data, purchasing or governance, it is worth getting to know MDM Academy or joining Data Club.

Conclusion

Supplier master data is not the flashiest field of a data project, but it is one of those that most quickly shows the cost of being ignored. A blocked purchase order, a payment to the wrong account, a supplier without approval inside an audit: all of that is born in the same place, a record that nobody treats as a priority until the day it fails.

Treating the supplier as master data, with a defined owner, a clear vendor approval process and periodic review, is one of the cheapest and most profitable decisions a purchasing area can make. At your company, who is responsible when a supplier's record is wrong?