Mon – Sat: 9:00 AM – 7:00 PM IST
ERP Basics

What is master data management?

One agreed version of your customers, suppliers and materials — and the ownership that keeps it that way.

In short

Master data management is the discipline of maintaining a single, governed version of the core entities a business shares across systems: customers, suppliers, materials, employees and the chart of accounts. It covers definition, ownership, creation standards, deduplication and distribution.

Why It Matters

Why this matters in practice

Bad master data is quiet and expensive. The same customer under three records makes credit limits meaningless and spend analysis wrong. Duplicate material codes generate excess stock of an item you already hold. None of this shows up as an error; it shows up as decisions made on numbers that were never right.

One version of each entity across systems
Credit, spend and stock analysis become reliable
Clear ownership of who may create and change what
Deduplication at creation, not as periodic cleanup
How It Works

How it works in practice

Definition and ownership

What a customer is, which fields are mandatory, and who owns the record. Ownership is the part most often skipped and most needed.

Creation standards

Naming conventions, mandatory fields and validation at entry. Preventing a bad record is far cheaper than merging it later.

Duplicate prevention

Fuzzy matching at creation against name, registration and address. Duplicates created today are merge projects next year.

Distribution

How the governed record reaches the systems that consume it, and which system is the acknowledged source of truth.

Stewardship

Named data stewards per domain who resolve conflicts and approve changes. Without them governance is policy nobody applies.

Worked example

A worked example: one customer, five records

A business runs a duplicate analysis on its customer master and finds that one large account exists as five records: two created by different sales staff with name variations, one from an acquired company's data load, one created for a different delivery address, and one with a trailing space in the name.

The consequences are not merely untidy. Credit limits are set against individual records rather than the group, so total exposure to that customer exceeds the limit anyone approved. Sales reporting understates the relationship, so it is not prioritised as it should be. Statements go out separately and get queried. And a pricing agreement applies to one record, so the customer is charged differently depending on who takes the order.

Deduplication fixes the history. What prevents recurrence is governance: a defined matching rule applied at creation, a single owner for the customer domain, and a creation process that searches before it creates. Without those, a cleansed master file degrades back to the same state within two years, which is why cleansing projects that do not establish governance get repeated.

Key terms

The vocabulary, briefly

Term What it means
Golden record The single agreed version of an entity, reconciled from all sources.
Data steward The person accountable for the quality of a data domain.
Survivorship rule The logic deciding which value wins when sources disagree.
Match and merge Identifying records that represent the same entity and combining them.
Data domain A category of master data — customer, supplier, item, employee — each with its own owner.
What Goes Wrong

Common mistakes worth avoiding

Cleansing without governance

A cleanup project without creation controls simply regenerates the duplicates over the following year.

No named source of truth

Two systems both authoritative for customers means neither is, and reconciliation never ends.

Validation only at the ERP

Records created in CRM or a webshop bypass it. Validate wherever creation happens.

Stewardship unassigned

If nobody owns a domain, nobody resolves its conflicts and the standards decay.

What to measure

Numbers worth tracking

Metric What it tells you What distorts it
Duplicate rate by domain The headline quality measure, and the one most likely to surprise.
Records failing validation rules Incomplete or inconsistent data, by domain and by field.
Time to create a master record Governance friction. Slow creation drives workarounds and shadow records.
Downstream errors traced to master data The business impact, which is what justifies the governance effort.
FAQ

Questions we are asked about this

Entities shared across processes and systems and relatively stable: customers, suppliers, materials, employees, the chart of accounts. Transactions such as orders and invoices are not master data.
Not necessarily. For a single ERP, governance and validation within it may be sufficient. Dedicated tooling earns its cost where several systems create the same entities and must be reconciled.
With the domain causing the most pain, which is usually customer or item. Measure the duplicate rate and the validation failure rate first, because the numbers are almost always worse than expected and they make the case for the work far better than argument does. Starting with a full multi-domain programme tends to produce a governance framework before it produces any improvement.
Not initially for most mid-market businesses. Clear ownership, defined validation rules enforced at creation, a search-before-create process and periodic duplicate review deliver most of the benefit using the ERP you already have. Dedicated tooling earns its place when you are reconciling master data across multiple systems that each maintain their own version, which is a genuinely harder problem.
A named steward per domain, who is a business person rather than an IT person — someone in finance or credit for customer, in procurement for supplier, in operations or engineering for item. IT owns the platform and the rules; the business owns the content, because the judgements involved are business judgements. Domains with no named owner degrade, reliably and without anyone deciding to let them.
Search before create, enforced in the process rather than encouraged. Match on stable identifiers — tax registration number, registered company number — rather than on name, since names vary endlessly. Restrict creation permission to a small trained group where volume allows. And make the legitimate route fast, because a creation process that takes three days will produce duplicates created under slightly different names by people who need to raise an order today.
Related

Where to read next

Data migration in ERP

Read more

What is a chart of accounts?

Read more

What is iPaaS?

Read more

Need this applied to your own systems?

We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.