Practical perspectives
How to Resolve Duplicate Supplier Records Across ERPs
A buyer worksheet for distinguishing duplicate vendors from related legal entities and reconciling approved supplier data.
Two supplier records can share a trading name yet represent different legal entities. The same entity can also appear under different names in separate ERPs. A merge based only on text similarity can misroute orders, invoices or payments.
This worksheet follows one candidate duplicate from detection to approved resolution. The supplier master data software guide describes the product approaches.
1. Surface the conflict without merging
List the source system, internal ID, legal name, registration and tax identifiers, address, parent relationship, payment country and recent transactions for each record. Record which values came from a supplier and which were imported. A fuzzy-match score is a triage signal, not a legal-entity decision.
| Field | ERP A | ERP B | Question |
|---|---|---|---|
| Trading name | Apex Components | Apex Components Ltd | Same legal entity or group? |
| Registration ID | A-102 | B-774 | Which authority issued each ID? |
| Bank account | On file | Different account | Has either account been independently verified? |
2. Distinguish duplicate, subsidiary and separate supplier
Compare authoritative identifiers and executed contracts. If the records represent the same legal entity, preserve both legacy IDs while mapping them to an approved master. If they represent parent and subsidiary, keep the relationship without collapsing payment or contracting identity. If evidence conflicts, leave the case unresolved for review.
HICX supplier information management ↗ and Ivalua supplier management ↗ publish approaches to governed supplier records. Evaluate how each models local ERP IDs and business-unit qualification.
3. Treat banking and tax changes as separate decisions
A legitimate merge does not verify a changed bank account. Keep proposed payment details out of active payment processing until the organization’s independent verification and approval have finished. Record the evidence and reviewer without exposing sensitive account values in general supplier notes.
- Identity reviewer: confirms legal-entity match.
- Payment-data reviewer: verifies bank ownership by an approved channel.
- System owner: maps IDs and authorizes write-back.
4. Update each system and retain lineage
Document which system owns each field, what the downstream mapping changes and how open POs and invoices keep their references. Test one failed write-back: the master case should show which ERP remains stale, who owns the retry and whether a payment or order must pause. Fragment’s supplier-data page ↗ describes cross-ERP conflict detection and repair; a buyer should inspect the approval and rollback boundaries.
5. Score resolution quality, not match count
For a pilot, use a true duplicate, a subsidiary pair and a false match. Score correct entity treatment, field provenance, approval separation and reconciliation after a failed write. A high number of suggested merges is not a useful outcome if a payment identity is collapsed incorrectly.