....
Laptop and checklist at a desk for ERP data migration planning

Master Data Ownership: Keep Customer, Product and Supplier Records Reliable

Laptop and checklist at a desk for ERP data migration planning

Master Data Ownership: Keep Customer, Product and Supplier Records Reliable

Master data ownership prevents customer, product and supplier records from becoming everybody’s problem and nobody’s responsibility. When teams disagree about a customer name, a product unit or a supplier status, the issue can affect orders, invoices, payments and management reports at once.

At AB Consulting, a practical ownership model connects business definitions with the people who maintain and use the records. Installing an ERP does not settle those decisions. The business must decide which source is authoritative, who approves sensitive changes and how exceptions are resolved.

This executive guide provides an operating framework and illustrative examples. It does not imply that data ownership means legal possession or unrestricted access to personal information.

Define master data ownership by business purpose

Master data describes the relatively stable entities used across transactions: customers, products, suppliers and other core reference records. A sales invoice is a transaction; the customer account and product identifiers it uses are shared records.

Start with the processes that rely on each domain. Customer records may support quoting, delivery, billing and credit control. Product records may drive purchasing, stock quantities, production and pricing. Supplier records may determine ordering, approvals and payment instructions.

The UK government’s data ownership model, published on 16 April 2026, distinguishes accountable owners from operational stewards and technical custodians. It concerns public-sector governance, not a mandatory private-company ERP structure. The distinction offers a useful reference for separating business accountability from day-to-day maintenance.

Write a short domain definition before assigning names. Decide, for example, whether a customer record represents a legal entity, a billing account or a delivery location. A single label that means different things to different teams will not support reliable reporting.

Assign master data ownership without making IT the business approver

Choose an accountable business owner

The owner approves definitions, quality expectations and material changes to the domain’s rules. Choose someone with enough authority to resolve cross-team disagreements. They do not need to type every record, but they must be able to make and enforce the relevant business decisions.

Name operational stewards and technical support

Stewards maintain records, review exception queues and help users apply the rules. Technical support manages permissions, validation and integrations. Keep the distinctions clear: an administrator who can edit a field is not automatically authorized to decide its business meaning.

Document backups for absences and role changes. Ownership assigned to a departed employee is an unowned control, even when the organisation chart still shows the position.

Separate routine changes from sensitive changes

Use proportionate workflows. A corrected spelling and a changed supplier payment instruction should not follow the same approval route. Identify fields that affect payment, pricing, legal identity, credit limits or other material outcomes, then specify evidence and review requirements.

For sensitive requests, use your approved verification process and an appropriate independent review. Do not let an urgent email bypass established checks. Retain change evidence according to applicable privacy, security and retention policies.

Colleagues review shared records and master data ownership
Connect record definitions, maintenance responsibilities and change approval.

Master data ownership: a practical responsibility map

DomainIllustrative ownership decisionEvidence to retain
CustomerAgree legal entity, billing account and site relationshipsApproved definitions and supporting account documents
ProductApprove base units and pack conversionsValidated specifications and conversion rules
SupplierControl identity, approval status and payment changesVerification record and authorized change history

The roles in your company may differ. Finance might own billing and credit fields while commercial teams steward contacts. Record field-level responsibilities when a domain spans several functions; do not hide the split behind a vague “shared owner.”

Illustrative example: a product record defines one carton as 12 units, but a purchasing interface treats the incoming quantity as individual units. An order for 100 cartons should represent 100 × 12 = 1,200 units. If the interface stores 100 units instead, the difference is 1,100 units.

The remedy is not merely changing the on-hand balance. The product owner must confirm the authoritative conversion, technical support must correct the mapping, and operations must assess affected transactions. Reconcile the correction and prevent the same mismatch from re-entering through the next import.

Also avoid merging records solely because names look alike. Two delivery locations may belong to one legal customer but still need separate operational records. Two similar supplier names may represent different entities. Preserve legitimate relationships while resolving genuine duplicates.

Make ownership visible in the exception review

Track issues that matter to operations: duplicate candidates, missing critical fields, rejected interfaces, invalid units and unresolved sensitive changes. For each exception, record the affected process, owner, required evidence, decision and correction date.

Measure quality against a defined use. A marketing contact can be fit for a permitted campaign without being a complete billing account. Do not call an entire domain “accurate” because one completeness percentage looks good.

Review repeat causes and change the creating process. If staff repeatedly invent product codes to complete urgent orders, investigate the request workflow and response time. Cleaning the resulting records every month will not remove that pressure.

Use the ERP data migration checklist for transition validation and ERP benefits tracking for operating outcomes. Master data ownership keeps the records reliable after the project team leaves.

Give shared records a clear business owner. Contact AB Consulting to discuss ERP and process management support covering domain definitions, stewardship and controlled changes.

AB Consulting: Elevate Your Business with Tailored Growth Strategies

Maximize your business potential with AB Consulting’s customized solutions in organizational development, stakeholder management, and leadership development. Achieve sustainable growth and excellence with strategies designed for your unique challenges.