Master data is the controlled core information about business entities used consistently across transactions, systems and reporting. Common domains include customers, suppliers, products, accounts, locations and currencies.
What belongs in master data?
- Stable identifiers and legal names
- Addresses and organizational relationships
- Product descriptions and units
- Payment and tax attributes
- Approved statuses and classifications
- Effective dates and ownership
Master data vs. transaction data
Master data describes the parties and objects used repeatedly. Transaction data records events such as quotes, orders, invoices and payments. A supplier record is master data; a supplier invoice is transaction data.
Why does quality matter?
Duplicate or stale master records cause payment errors, reporting fragmentation, inconsistent pricing and failed integrations. Correct transaction processing depends on reliable identifiers and attributes.
How should changes be governed?
Assign data owners, validation rules, approval workflows, effective dates and audit history. Sensitive changes such as supplier bank details should require independent verification.
What should be monitored?
Track duplicates, completeness, invalid values, unauthorized changes, stale records and reconciliation conflicts across systems. Merge records only after confirming that they represent the same entity.
