Plain definition
Master data is the core reference information used repeatedly across transactions: customers, suppliers, products, employees, chart-of-accounts codes, tax settings, bank details, and organisational units. It tells systems how to classify, route, calculate, and report activity. Because it is reused widely, a small error can affect many transactions before anyone sees it.
Master data needs defined ownership, standards, validation, approval, controlled change, access restrictions, and periodic review. It is not just an IT concern: finance, tax, procurement, HR, and operations often understand different consequences of the same record.
Illustrative example
Suppose a new product is added to an ERP system. A product-data analyst enters its description, but the proposed tax code and revenue account are uncertain. Before the record is released, the tax specialist confirms the tax treatment and the financial controller confirms the reporting account. They test a sample sales invoice in a separate environment, compare the tax and ledger result with the approved setup, then authorise release.
The company avoids discovering later that hundreds of invoices used the wrong tax or revenue classification. If a change is needed, the record of who requested, reviewed, and approved it makes the correction traceable.
Master data is distinct from transaction data: it defines the recurring reference values used when individual transactions are processed.
Why it matters
It protects consistent processing and reporting across systems and teams.
It prevents repeated errors in tax, payment, pricing, accounting, or reporting from one uncontrolled record change.
Practical consequence
Assign a business role responsible for each critical data domain and define validation, evidence, approval, and periodic review rules.
Restrict change access, test high-impact changes before release, and monitor for duplicate, incomplete, or unusual records that indicate weak setup.