Master Data

Master data is the nouns the enterprise agrees on: customers, products, suppliers, locations — the core entities every system references. Get them consistent and systems cooperate; let each maintain its own version and the organisation spends its days reconciling the word 'customer' with itself. Master data is boring, valuable, and the hidden cause of most 'systems don't talk to each other' problems.

What It Is

Master data is the consistent, authoritative set of core business entities an organisation uses across its processes and systems — customers, patients, products, suppliers, employees, sites — as distinct from transactional data (the events those entities generate) and reference data (standardised codes and enumerations). Master Data Management (MDM) is the discipline of maintaining one authoritative version: identifying golden records, governing ownership (which system is the source of truth for which attribute), and synchronising consumers. Its absence manifests as duplicates, conflicting records, and the perennial matching projects that follow mergers.

Why It Matters to You

Every large organisation's most expensive data problem is usually master data. The symptoms are familiar: the same customer existing four times with four spellings, mail-merges embarrassing themselves, regulatory reports undercounting because entities were deduplicated differently in each source. For executives, two levers: insist on named ownership per master entity (data without an owner decays), and treat new system onboarding as a master-data event — every new application that creates its own customer records adds a future reconciliation project. In vendor selection, whether a system consumes your master data or insists on creating its own is an architectural commitment with a long tail.

When You'll Meet It

In data-governance programmes, system integration, and post-merger harmonisation. The diagnostic question: 'how many systems can create a new customer?' — every answer above one is future reconciliation work.