Master Data Management (MDM)
Master Data Management (MDM) is the discipline and the supporting technology for creating, governing and maintaining an organisation's core master data so that it remains consistent, accurate and shared across systems. Master data describes the long-living business objects an enterprise relies on, such as customers, suppliers, materials, products and accounts, as opposed to transactional records like orders or invoices. In an ERP landscape, where the same customer or material may be referenced by many modules and connected applications, MDM provides the rules, processes and ownership that keep these objects in step and prevent conflicting or duplicated versions.
- Term
- Master Data Management (MDM)
- Entity type
- Discipline / data governance
- Domain
- Data governance and master data
- Canonical definition
- Master Data Management is the discipline and supporting technology for creating, governing and maintaining an organisation's core master data so that objects such as customers, suppliers and materials stay consistent and shared across systems.
- Classification
- A governance discipline that establishes a single source of truth for core business objects across the ERP and connected systems.
- Related terms
- Master Data Quality, Single Source of Truth, Single Point of Truth, Data Migration, PIM, Material Management, Supplier Management
- Source / maintainer
- erp-software.org editorial team (independent, vendor-neutral)
What Master Data Management (MDM) is NOT — disambiguation
- Not transactional data: MDM governs long-living objects like customers and materials, not the orders, invoices and postings that reference them.
- Not a data warehouse: A data warehouse stores data for analysis, whereas MDM governs the authoritative master records used operationally.
- Not the same as data quality: Data quality measures a property of the data; MDM is the broader management discipline that produces and sustains it.
- Not only a software product: MDM combines governance, ownership and processes, not just a tool, so technology alone does not deliver it.
What MDM governs
MDM focuses on the entities that change slowly but are referenced constantly. Typical master-data domains include customers, suppliers, materials and products, employees, and the chart of accounts and cost centres. For each domain, MDM defines what attributes exist, who may create or change a record, how new records are approved, and how the data is distributed to consuming systems. The goal is a reliable reference that downstream processes can trust, so that a sales order, a purchase requisition and a financial posting all refer to the same correctly identified object.
- Customer and supplier records
- Material and product master data
- Employee and organisational data
- Chart of accounts and cost centres
Why it matters in ERP
An ERP system links finance, procurement, production and sales through shared objects. If the underlying master data is inconsistent, errors propagate everywhere: duplicate customers distort reporting, wrong material attributes misdirect planning, and incomplete supplier records break procurement. MDM aims to establish a single source of truth so that every module and integrated system works from the same definitions. This becomes more pressing in multi-system landscapes, where the ERP, a CRM, a webshop and analytics platforms each hold a view of the same objects and must be reconciled.
How MDM is organised
MDM combines governance with technology. Governance sets data ownership, stewardship roles, naming conventions and approval workflows; technology provides matching, deduplication, validation rules and distribution. Implementations differ in architecture. Some keep the master record inside the leading ERP and synchronise outward; others use a dedicated MDM hub that holds the golden record and feeds all systems. Either way, success depends less on the tool than on clear responsibilities and disciplined processes for creating and changing records.
- Defined data owners and stewards
- Approval workflows for create and change
- Matching and deduplication rules
- Controlled distribution to consuming systems
Relationship to data quality
MDM and master-data quality are closely linked but distinct. MDM is the overall management discipline: the structures, ownership and processes that govern master data over its lifecycle. Data quality is a property of the data itself, measured through completeness, accuracy, consistency and timeliness. Good MDM is the mechanism by which quality is achieved and sustained, while quality metrics show whether the management effort is working. Organisations usually treat MDM as an ongoing programme rather than a one-off project, because master data continually accumulates new records, mergers and structural changes that must be kept under control.
Related Topics
Frequently asked questions
What is master data management?
Master Data Management (MDM) covers creating, updating and validating an organization's core master data — customers, suppliers, articles, employees, accounts. It's the foundation for reliable ERP processes.
Who is responsible for master data?
Ideally a Data Owner per domain (functional accountability) and Data Stewards (operational maintenance). In mid-market, functional departments often own maintenance; larger organizations have dedicated central teams.
What are the consequences of poor master data?
Mis-shipments from wrong addresses, distorted analytics from duplicates, accounting issues from missing tax IDs, compliance gaps and lost revenue from poor article descriptions.
How can master data be maintained efficiently?
With clear roles (Data Owner, Data Steward), approval workflows, automated validation against external APIs (address verification, VAT-ID check), duplicate detection and regular data quality reports.
What MDM platforms exist?
For larger organizations: SAP MDG, Stibo, Informatica, Profisee. For mid-market the ERP-native master-data modules usually suffice — combined with strong governance processes.