Datanovel know-how
Linking necessary supplier records
Keep legitimate operational differences while maintaining shared identity consistently.
A supplier may need several records for different locations, payment arrangements or approval routes. Linking those records makes them easier to maintain and understand without forcing every field to be identical.
Record the relationship and its reason
Identify the legal entity behind each record, the primary identity reference and the reason another operational record exists. The relationship might concern a supplier site, currency, payment arrangement, tax treatment or local approval process.
Distinguish this relationship from membership of a supplier group. Two sister companies are separate entities even when procurement wants a consolidated view of their spend.
Synchronise only what should be shared
Agree the fields that belong to the shared identity and the fields that reflect local arrangements. A confirmed legal name change may need to reach several records. Payment terms or a site address may need to remain different.
Use supported relationship structures in the client's master-data or integration environment. Where the source system cannot represent every link, design an approved mapping with clear ownership rather than overloading an unrelated field without governance.
Make the links useful beyond maintenance
Consistent relationships allow teams to consolidate spend, contact a supplier once during cleansing and restore the intended hierarchy after migration. They also make exceptions easier to investigate when one record diverges.
Datanovel helps define, populate and maintain these relationships with the client's team, including the rules for reviewing changes and preserving operational differences.