Permit, licensing, and inspection systems each store slightly different spellings and tax IDs for the same contractor companies, causing wrong notifications and duplicate vendor payments. What problem does this primarily motivate?
Select an answer to reveal the explanation.
Short Explanation
When three desks keep three versions of 'Acme Plumbing,' the city is not arguing about plumbing—it is arguing about who Acme is. That shared contractor identity is classic party master data. MDM exists so processes stop inventing competing company records.
Full Explanation
Inconsistent shared reference entities—especially organizations and people—across operational processes are a primary driver for MDM. Contractor (party/organization) records reused by permitting, licensing, and inspection must resolve to a trusted identity so notifications, payments, and compliance history attach correctly. Treating the issue as an ERP rewrite, a temporary notification freeze, or an analytics-only cleanup misses the operational need for mastered shared entities.