Datanovel know-how
When a supplier changes its name
Keep a business recognisable across old records, current documents and future onboarding requests.
An outdated supplier name can make an existing business difficult to find. The next onboarding request may create another record even though the relationship already exists.
Distinguish a name change from an entity change
Compare registration identifiers, jurisdiction and available history. A name change may leave the legal entity unchanged; an acquisition or replacement entity may require a different response. Trading names also need to remain distinguishable from legal names.
Use register information as evidence alongside the operational record. Do not replace identity fields solely because another source returns a similar name.
Update the connected records
When a change is confirmed, identify all records representing that entity across the agreed systems. Update the fields that should be shared while preserving site, payment and other justified differences.
Keep previous names or aliases available for search where the platform supports them. This helps users recognise earlier purchase orders, invoices and correspondence.
Prevent the next unnecessary duplicate
Include current and previous names in the supplier-search process before a new record is created. Revisit identity at suitable review events, and route significant external changes to an owner.
Datanovel can assess name changes within the supplier population and implement the agreed matching, exception review and update workflow in your systems.