MDM Academy lessons and materials are in Portuguese. You can take the program from any country, and an English version is on our roadmap, with no committed date. The certificate is issued in Brazil, in Portuguese, and is valid in Brazil. To earn it you need to follow the lessons in Portuguese.

BlogGovernança

Segregation of duties in master data: how to prevent supplier record fraud

Segregation of duties in master data: what it is, how to apply it to supplier and material records, and how it prevents ERP fraud.

Paulo Cordeiro7 min read

Segregation of duties in master data is the practice of separating, across different people, who registers, who approves and who audits a supplier, customer or material record in the system. It sounds like bureaucracy. In practice it is what keeps a single person from being able to create a fake supplier, approve their own record and release the payment, all alone, without anyone noticing.

I have seen that gap in large companies, running SAP for years. The supplier master data had a single analyst with full access: creating records, changing bank account details, and in some cases even approving them. Nobody set it up that way on purpose. It built up, one access request after another, until a single analyst became a single point of risk for the whole company.

What segregation of duties in master data means

Segregation of duties, or SoD, is the internal control principle that keeps one person from holding, at the same time, the power to initiate, approve and execute a critical transaction. In master data this comes down to three roles that must stay in different hands: whoever requests or enters the record, whoever approves the change after validating the data, and whoever has access to the most sensitive fields, such as a supplier's bank details or a customer's payment terms.

Supplier and material master data is one of the most exploited points in corporate fraud precisely because it concentrates decisions about money. A supplier created without a tax status check, without bank data validation, can become the simplest path to divert a payment. And the worst part: on paper, the process was approved. Someone signed off on it.

How the process works day to day

In a well designed control structure, the supplier or material registration flow passes through distinct stages, each with a different owner. The procurement team, or the supplier itself through a self service portal, fills in the data. The master data analyst checks documentation, tax status, and whether the category fits what will be purchased. A second level, outside the chain of whoever made the request, approves the release. And an audit trail records who did what and when, in a way nobody can erase afterward.

The key point is that the person who creates the record can never be the same person who approves a change to that same supplier's bank details. The same applies to a material price change, a customer's payment terms, and any field that touches the company's cash directly. A well configured approval workflow, with an authorization limit rule and an automatic block on self approval, solves most of this without depending on anyone's good will.

Who is responsible for applying segregation of duties

Segregation of duties usually starts with internal control or audit, but the team that keeps it working day to day is data governance, together with IT and access security. Procurement owns the supplier onboarding process. The data steward, where that role exists, is the one tracking whether the segregation matrix is actually being respected in the record, not just on paper.

A common mistake is treating this as only an audit problem, reviewed once a year. Segregation of duties in master data is daily operational control. Each analyst's access to the ERP needs to be reviewed as often as the company creates new roles, promotes people and hires.

What tools help apply the control

Companies running SAP have SAP Master Data Governance, SAP MDG, with a native approval workflow and a segregation rule that can be configured by master data object type. For access control and authorization conflict analysis inside SAP, GRC tools such as SAP Access Control map out where a single user accumulates conflicting transactions, including the ones used for registration.

Outside the SAP world, MDM platforms such as Informatica, Stibo Systems, Reltio, Semarchy, Profisee and Ataccama also offer configurable approval workflows, with separate roles for whoever proposes and whoever approves a golden record change. No tool, however robust, replaces the decision of how to design the process. Software enforces the rule. Governance defines the rule.

How to learn to structure segregation of duties

This topic sits at the crossing of data governance, internal controls and audit, so it is worth studying both sides. The most solid path starts with the fundamentals of data governance and MDM, and moves into information security controls and access management. DAMA's CDMP certification covers the governance and quality axis. On the control and audit side, it is worth knowing frameworks such as COSO, used as a reference for internal controls in Brazil and worldwide.

Anyone working with SAP gets ahead by understanding how profile and role configuration works in the system, because that is where segregation of duties becomes an enforced rule, not just a policy written in a document nobody reads.

Career opportunities in this field

Demand for people who understand access control applied to master data grows alongside regulatory pressure and the fraud cases that make the news. Companies that have already suffered a diverted payment through a fraudulent supplier record start investing heavily in this, fast. Data governance, information security and internal audit professionals who can move between all three areas become a rare, highly valued asset inside the company.

This is one of those topics where the master data professional stops being seen as someone who just enters information and starts being seen as someone who protects the company's cash. That shift in perception changes a career.

Frequently asked questions about segregation of duties in master data

Is segregation of duties the same as access control? Not exactly. Access control defines who can open which screen or transaction. Segregation of duties goes further and makes sure that, even with access granted, the same person does not accumulate conflicting roles, such as creating and approving the same record.

Does a small company also need segregation of duties in its records? Yes, just in a simpler form. When there are not enough people to fully separate the functions, the fallback is to compensate with targeted double checks and approval by authorization level even in lean teams.

Who should approve a change to a supplier's bank details? Never the same person who registered or changed that supplier. The right approach is a second level, outside the area that requested the change, with direct verification of the account with the supplier through an already known channel, never through the same email that requested the change.

Does the ERP system already solve this on its own? No. The ERP applies the rule that was configured in it. If the company never designed a segregation of duties matrix for master data, the system will let through exactly the same risks that would slip through a spreadsheet.

Is this related to data protection law? There is an indirect link. Bank and registration data are personal data when they belong to an individual, and poorly designed access control is also a data protection risk, on top of being a financial one.

MDM Academy

MDM Academy is 4MDG's school for data governance and master data. It was created to train, with practical and applied content, the professionals who will sustain this kind of control inside companies, from entry level all the way to the data steward and governance manager seat. Its tracks cover MDM, data quality, data cleansing, SAP applied to master data, and careers in data, built for people who live the daily reality of master data and want to grow in this field.

MDM Academy lessons and materials are in Portuguese. You can take the program from any country, and an English version is on our roadmap, with no committed date. The certificate is issued in Brazil, in Portuguese, and is valid in Brazil.

If you want to understand better how to structure control, process and segregation of duties in your company's master data, it is worth getting to know MDM Academy. And if you would rather exchange experience with other professionals in the field before deciding, the Data Club is our free WhatsApp group in English, just for this subject: https://chat.whatsapp.com/H4RudT3peYA1PDBAgOFqXG

Conclusion

Fraud in supplier master data almost never starts with a sophisticated attack. It starts with a poorly designed process, where one person holds too much power over a critical piece of data. Segregation of duties in master data is not an audit formality. It is the difference between a company that finds out about the problem in a quarterly report and one that finds out after the money has already left the account.

In your company, is the person who registers the supplier the same one who approves a change to their bank details?

Want to become a data governance specialist? Talk to our specialists now and get to know MDM Academy

I want to be a student

By submitting your email, you agree to the privacy policy of MDM Academy | 4MDG.

Talk to a specialist