Accelerate the Value of Data

Match rules for Supplier

Learn what match rules are preconfigured in entity types for Reltio for Supplier.

Reltio for Supplier brings together systems, where most of these duplicate customer information. Match rules define the criteria Reltio uses to determine whether two records are duplicates.

Location and Organization entity types are highly likely to be duplicated, so match rules help you reconcile any variations.

For general information on match rules, see topic Reltio match and merge. For details on the preconfigured entity types that come with Reltio for Supplier, see Entity types for Supplier .

For information on working with match rule properties, see topic Preconfigured User Interface for Supplier.

Individual entity type match rules

This table identifies the Reltio for Supplier match rules used to master data for the Individual entity type. Use these match rules to create a record for a specific individual.

LabelDescriptionRule
BaseRule01: Exact(FirstName, LastName, DOB, Address1, City); EON(MiddleName, NamePrefix, NameSuffix)Automatically merge( Exact on Last Name [ Comparator class: BasicStringComparator ] [ Match token: ExactMatchToken ] and First Name [ Comparator class: BasicStringComparator ] [ Match token: ExactMatchToken ] and Date of Birth [ Comparator class: BasicStringComparator ] [ Match token: ExactMatchToken ] and Address/Address Line 1 [ Comparator class: BasicStringComparator ] [ Match token: ExactMatchToken ] and Address/City [ Comparator class: BasicStringComparator ] [ Match token: ExactMatchToken ] ) and ( Exact Or Null on Name Prefix [ Comparator class: BasicStringComparator ] [ Match token: ExactMatchToken ] and Name Suffix [ Comparator class: BasicStringComparator ] [ Match token: ExactMatchToken ] and Middle Name [ Comparator class: BasicStringComparator ] [ Match token: ExactMatchToken ] )
BaseRule02: Exact(FirstName, LastName, Address1, City); EON(MiddleName, NamePrefix, NameSuffix)Automatically merge( Exact on Last Name [ Comparator class: BasicStringComparator ] [ Match token: ExactMatchToken ] and First Name [ Comparator class: BasicStringComparator ] [ Match token: ExactMatchToken ] and Address/Address Line 1 [ Comparator class: BasicStringComparator ] [ Match token: ExactMatchToken ] and Address/City [ Comparator class: BasicStringComparator ] [ Match token: ExactMatchToken ] ) and ( Exact Or Null on Name Prefix [ Comparator class: BasicStringComparator ] [ Match token: ExactMatchToken ] and Name Suffix [ Comparator class: BasicStringComparator ] [ Match token: ExactMatchToken ] and Middle Name [ Comparator class: BasicStringComparator ] [ Match token: ExactMatchToken ] )
BaseRule03: Fuzzy(FirstName, LastName); Exact(Address1, Zip5); EON(NameSuffix, Email)Create potential matches( Exacton Address/Address Line 1 [Comparator class:AddressLineComparator] [Match token:ExactMatchToken] and Address/PostalCode/Zip5 [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] ) and ( Exact Or Nullon Email/Email [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Name Suffix [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] ) and ( Fuzzyon First Name [Ignored in token] [Comparator class:DoubleMetaphoneComparator] [Match token:DoubleMetaphoneMatchToken] and Last Name [Comparator class:DoubleMetaphoneComparator] [Match token:DoubleMetaphoneMatchToken] )
BaseRule03: Fuzzy(FirstName, LastName); Exact(Address1, Zip5); EON(NameSuffix, Email)Create potential matches( Exacton Identifiers/Value [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Identifiers/Type [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] ) and ( Fuzzyon First Name [Ignored in token] [Comparator class:DoubleMetaphoneComparator] [Match token:DoubleMetaphoneMatchToken] and Last Name [Comparator class:DoubleMetaphoneComparator] [Match token:DoubleMetaphoneMatchToken] )
BaseRule05: Fuzzy(FirstName, LastName); Exact(Email)Create potential matches(Exact on Email/Email [ Comparator class: BasicStringComparator ] [ Match token: ExactMatchToken ] and ( Fuzzy on First Name [ Comparator class: DoubleMetaphoneComparator ] [ Match token: DoubleMetaphoneMatchToken ] and Last Name [ Comparator class: DoubleMetaphoneComparator ] [ Match token: DoubleMetaphoneMatchToken ] )
BaseRule06: Fuzzy(FirstName, LastName); Exact(Phone)Create potential matches(Exacton Phone/Number [Match token:ExactMatchToken] and ( Fuzzyon First Name [Comparator class:DoubleMetaphoneComparator] [Match token:DoubleMetaphoneMatchToken] and Last Name [Comparator class:DoubleMetaphoneComparator] [Match token:DoubleMetaphoneMatchToken] )
BaseRule07: Fuzzy(FirstName, LastName); EON(DOB)Create potential matches(Exact Or Nullon Date of Birth [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and ( Fuzzyon First Name [Comparator class:DoubleMetaphoneComparator] [Match token:DoubleMetaphoneMatchToken] and Last Name [Comparator class:DoubleMetaphoneComparator] [Match token:DoubleMetaphoneMatchToken] )

Location entity type match rules

This table identifies the Reltio for Supplier match rules used to master data for the Location entity type. Use these match rules to create a record for a specific supplier location.

LabelDescriptionRule
BaseRule01: Exact(Address1, City, State, Country, Zip5, Verification Status); EOAN(Address2, Zip4)Automatically merge( Exacton Address Line 1 and City and State or Province and Country and PostalCode/Zip5 and Verification Status ) and ( Exact Or All Nullon Address Line 2 and PostalCode/Zip4 ) and Equalson Verification Statusvalues : Verified,Partially Verified)
BaseRule02: Exact(Address1, City, State, Country, PostalCode, Verification Status); EOAN(Address2)Automatically merge( Exacton Address Line 1 and City and State or Province and Country and PostalCode/Postal Code and Verification Status ) and Exact Or All Nullon Address Line 2 and Equalson Verification Statusvalues : Verified,Partially Verified)

Organization entity type match rules

This table identifies the Reltio for Supplier match rules used to master data for the Organization entity type. Use these match rules to create a record for a specific organization.

LabelDescriptionRule
Rule1: Exact on DUNS NumberAutomatically merge(Exacton DUNS Number)
Rule2: Fuzzy (Name), EOAN (Identifier), EON (Phone), Exact (Address1, Zip5, Tax ID)Create potential matches( Exacton Address/PostalCode/Zip5 [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Address/Address Line 1 [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Tax ID [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] ) and Exact Or All Nullon Identifiers/Value [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Exact Or Nullon Phone/Formatted Number [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Fuzzyon Name [Comparator class:OrganizationNamesComparator] [Match token:OrganizationNameMatchToken])
Rule3: Exact (Name, Identifier)Create potential matches( Exacton Name [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Identifiers/Value [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Identifiers/Type [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] )
Rule4: Fuzzy (Name), Exact (Tax ID)Create potential matches(Exacton Tax ID [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Fuzzyon Name [Comparator class:OrganizationNamesComparator] [Match token:OrganizationNameMatchToken])
Rule5: Fuzzy (Name), Exact (Address1), Exact (City or Zip)Create potential matches( Exacton Address/Address Line 1 [Comparator class:AddressLineComparator] [Match token:ExactMatchToken] and Fuzzyon Name [Comparator class:OrganizationNamesComparator] [Match token:OrganizationNameMatchToken] ) and ( ( Exacton Address/PostalCode/Zip5 [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] or Address/City [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] ) )
Rule6: Fuzzy (Name Metaphone), Exact (Address1), Exact (City or PostalCode)Create potential matches( Exacton Address/Address Line 1 [Comparator class:AddressLineComparator] [Match token:ExactMatchToken] and Fuzzyon Name [Comparator class:DoubleMetaphoneComparator] [Match token:MultiWordSelfCleaningPhoneticToken] ) and ( ( Exacton Address/PostalCode/Postal Code [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] or Address/City [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] ) )
Rule7: Exact (Name, Address, Phone)Automatically merge( Exacton Name [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Address/Address Line 1 [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Address/City [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Address/State or Province [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Phone/Formatted Number [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] ) and Exact Or All Nullon Address/PostalCode/Postal Code [Comparator class:BasicStringComparator] [Match token:ExactMatchToken])
Rule8: Fuzzy (Name), Exact (Address1, PostalCode)Create potential matches( Exacton Address/Address Line 1 [Comparator class:AddressLineComparator] [Match token:ExactMatchToken] and Address/PostalCode/Postal Code [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] ) and Fuzzyon Name [Comparator class:OrganizationNamesComparator] [Match token:OrganizationNameMatchToken])
Rule9: Fuzzy (Name), Exact (Address1, State)Create potential matches( Exacton Address/Address Line 1 [Comparator class:AddressLineComparator] [Match token:ExactMatchToken] and Address/State or Province [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] ) and Fuzzyon Name [Comparator class:OrganizationNamesComparator] [Match token:OrganizationNameMatchToken])