Definition · Plain-language
Master data management
Master data management (MDM) is the discipline of creating a single, consistent, authoritative view of an organisation’s core shared entities — such as customers, products and suppliers — across every system that uses them.
The step most authors miss
Doing CRediT right? Don’t stop at the statement.
A CRediT statement credits you inside one paper. The recognition CRediT was built for happens when those roles are tied to you, persistently. Sign in with your ORCID — free — and claim your CRediT contributions on casrai.org, the home of the standard. They become a verified, portable part of your identity, not a line that disappears into one PDF.
Free: claim your contributions, then export a journal-ready CRediT statement, schema.org structured data, JATS XML, CSV or BibTeX — and preview your public profile. A membership publishes that profile publicly and verifies the journals you serve.
What master data is
Master data is the relatively stable, widely shared data that describes the core entities an organisation operates on — customers, products, suppliers, employees, accounts and locations. Unlike transactional data, which records events such as an order or a payment, master data persists and is referenced repeatedly. The problem MDM solves is that the same customer or product is often recorded differently in separate systems, producing duplicates and contradictions. MDM resolves these into one authoritative master record, sometimes called a golden record.
How MDM works
MDM combines governance and technology. Matching and merging rules identify when records across systems refer to the same real-world entity and reconcile them, while survivorship rules decide which attribute values prevail. Data stewards adjudicate the cases automation cannot resolve. The result is distributed to consuming systems either as a central hub or through synchronisation, so that downstream applications draw on the same trusted definition of each entity rather than maintaining their own conflicting copies.
Why it matters
Inconsistent core data is costly: it produces inaccurate reporting, duplicated effort, failed deliveries and poor customer experience. By establishing a single source of truth for shared entities, MDM improves the reliability of analytics, supports regulatory reporting and lets processes that span departments operate on consistent information. It is closely tied to data quality and reference data, and it depends on the broader governance framework to define ownership and the rules that keep the master records authoritative.
Key facts
At a glance
- Definition: a single authoritative view of core shared entities
- Typical domains: customers, products, suppliers, employees, accounts
- Output: the golden record (one trusted master record)
- Key techniques: matching, merging and survivorship rules
- Distinct from: transactional data, which records events
- Depends on: governance, stewardship and data quality
Common misconceptions
What people often get wrong
Often heard: Master data management is just deduplicating a database.
Actually: Deduplication is part of it, but MDM also establishes agreed definitions, ownership, matching and survivorship rules, and ongoing stewardship so the master record stays authoritative over time.
Often heard: Master data and reference data are the same thing.
Actually: Reference data is the set of permitted values used to classify other data, such as country codes; it is effectively a subset of master data. Master data covers the full core business entities, not just code lists.
Often heard: MDM is purely a software product you deploy.
Actually: Tools help, but MDM succeeds only with governance: clear ownership, agreed definitions and stewardship. Without those, an MDM platform simply automates the merging of poorly defined data.
Going deeper
