Match rules for Insurance
Learn what match rules are preconfigured in entity types for Reltio for Insurance.
Reltio for Insurance brings together systems including policy administration, underwriting, and CRM systems. Most of these systems duplicate customer information. Match rules define the criteria Reltio uses to determine whether two records are duplicates.
Organization and Individual entity types are highly likely to be duplicated, so match rules help you reconcile any variations. Policies, insured assets, and claims, on the other hand, tend not to have duplicates, so they do not need match rules.
For general information on match rules, see topic Reltio match and merge. For details on the preconfigured entity types that come with Reltio for Insurance, see Entity types for Insurance .
For information on working with match rule properties, see topic Preconfigured User Interface for Insurance.
Broker Agent entity type match rules (Insurance)
This table identifies the Reltio for Insurance v3 match rules used to master data for the Broker/Agent entity type. Use these match rules to create a record for a specific insurance broker or agent.
| Label | Description | Rule |
|---|---|---|
| Fuzzy (Name) Exact (Phone or Email) | Creates a potential match when the name and either the phone number or email address is an exact match. | ( ( Fuzzy on First Name [ Comparator class: DoubleMetaphoneComparator ] [ Match token: DoubleMetaphoneMatchToken ] and Last Name [ Comparator class: DoubleMetaphoneComparator ] [ Match token: DoubleMetaphoneMatchToken ] ) ) and ( ( Exact on Email/Email [ Comparator class: BasicStringComparator ] [ Match token: ExactMatchToken ] or Phone/Formatted Number [ Comparator class: BasicStringComparator ] [ Match token: ExactMatchToken ] ) ) |
Individual entity type match rules (Insurance)
This table identifies the Reltio for Insurance match rules used to master data for the Individual entity type. Use these match rules to create a record for a specific person.
| Label | Description | Rule |
|---|---|---|
| Rule1: Exact (First Name, Last Name, DOB, Address1, City) | Creates a potential match when the first name, last name, DOB, address1 and city are an exact match. | ( 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 ] ) |
| Rule2: Rule2: Exact (First Name, Last Name, SSN, Address1, City); EON (Middle Name, Prefix, Suffix) | Creates a potential match when the first name, last name, Social Security Number, Date of Birth, address1 and city are an exact match AND when the middle name, prefix and suffix are an exact match or are null. | ( Exact on Last Name [ Comparator class: BasicStringComparator ] [ Match token: ExactMatchToken ] and First Name [ Comparator class: BasicStringComparator ] [ Match token: ExactMatchToken ] and SSN [ 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 Prefix [ Comparator class: BasicStringComparator ] [ Match token: ExactMatchToken ] and Suffix Name [ Comparator class: BasicStringComparator ] [ Match token: ExactMatchToken ] and Middle Name [ Comparator class: BasicStringComparator ] [ Match token: ExactMatchToken ] ) |
| Rule3: Fuzzy(First Name, Last Name); Exact (Address1, Zip5); ExactOrNull(Suffix, Email) | Creates a potential match when the first name, last name, address line and zip code are an exact match. The suffix and email may or may not be an exact match. | ( Exact on Address/Address Line 1 [ Comparator class: AddressLineComparator ] [ Match token: ExactMatchToken ] and Address/Zip/Zip5 [ Comparator class: BasicStringComparator ] [ Match token: ExactMatchToken ] ) and ( Exact Or Null on Email/Email [ Comparator class: BasicStringComparator ] [ Match token: ExactMatchToken ] and Suffix Name [ Comparator class: BasicStringComparator ] [ Match token: ExactMatchToken ] ) and ( Fuzzy on First Name [ Ignored in token ] [ Comparator class: DoubleMetaphoneComparator ] [ Match token: DoubleMetaphoneMatchToken ] and Last Name [ Comparator class: DoubleMetaphoneComparator ] [ Match token: DoubleMetaphoneMatchToken ] ) |
| Rule4: Fuzzy(First Name, Last Name); Exact (Identifier, Identifier Type) | Creates a potential match when the first name, last name,identifier ID and identifier type are an exact match. | ( Exact on Identifiers/ID [ Comparator class: BasicStringComparator ] [ Match token: ExactMatchToken ] and Identifiers/Type [ Comparator class: BasicStringComparator ] [ Match token: ExactMatchToken ] ) and ( Fuzzy on First Name [ Ignored in token ] [ Comparator class: DoubleMetaphoneComparator ] [ Match token: DoubleMetaphoneMatchToken ] and Last Name [ Comparator class: DoubleMetaphoneComparator ] [ Match token: DoubleMetaphoneMatchToken ] ) |
| Rule5: Fuzzy (First Name, Last Name); Exact(Email) | Creates a potential match when the first name, last name and email are an exact match. | 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 ] ) |
| Rule6: Fuzzy (First Name, Last Name); Exact(Phone) | Creates a potential match when the first name, last name and phone are an exact match. | Exact on Phone/Phone Number [ Comparator class: PhoneNumberComparator ] [ Match token: ExactMatchToken ] and ( Fuzzy on First Name [ Comparator class: DoubleMetaphoneComparator ] [ Match token: DoubleMetaphoneMatchToken ] and Last Name [ Comparator class: DoubleMetaphoneComparator ] [ Match token: DoubleMetaphoneMatchToken ] ) |
| Rule7: Fuzzy (First Name, Last Name); Exact(SSN); EON (DOB) | Creates a potential match when the first name, last name and Social Security Number are an exact match AND the date of birth is an exact match or is null. | Exact on SSN [ Comparator class: PhoneNumberComparator ] [ Match token: ExactMatchToken ] and Exact Or Null on Date of Birth [ 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 ] ) |
Location entity type match rules (Insurance)
This table identifies the Reltio for Insurance match rule used to master data for the Location entity type. Use this match rules to create a record for a specific location.
| Label | Description | Rule |
|---|---|---|
| [Auto] Exact (Addr1, City, State, Country, Zip5, Verification Status) EOAN(Addr2, Zip4, Building, SubBuilding) | Automatically merges records when address line 1, City, State, Country, and the Zip code are and exact match AN address line 2 and Zip, Building, and Sub Building are an exact match or are null AND the verification status value is verified or partially verified. | ( Exact on Address Line 1 and City and State and Country and Zip/Zip5 and Verification Status ) and ( Exact Or All Null on Address Line 2 and Zip/Zip4 and Building and Sub Building ) and Equals on Verification Status values : Verified,Partially Verified |
Organization entity type match rules (Insurance)
This table identifies the Reltio for Insurance match rules used to master data for the Organization entity type. Use these match rules to create a record for a specific insurance organization, such as a brokerage, company, or businesses.
| Label | Description | Rule |
|---|---|---|
| Rule 1: Exact (Name, Identifier) | Creates a potential match when the name, and identifier are an exact match. | ( Exact on Name [ Comparator class: BasicStringComparator ] [ Match token: ExactMatchToken ] and Identifiers/ID [ Comparator class: BasicStringComparator ] [ Match token: ExactMatchToken ] and Identifiers/Type [ Comparator class: BasicStringComparator ] [ Match token: ExactMatchToken ] ) |
| Rule2: Fuzzy (Name), Exact (Tax ID) | Creates a potential match when the name, and tax ID are an exact match. | Exact on Tax ID [ Comparator class: BasicStringComparator ] [ Match token: ExactMatchToken ] and Fuzzy on Name [ Comparator class: BasicTokenizedOrganizationNameComparator ] [ Match token: BasicTokenizedOrganizationNameMatchToken ] |
| Rule3: Fuzzy (Name), Exact (Address1, Zip) | Creates a potential match when the name and address1 are an exact match. | ( Exact on Address/Address Line 1 [ Comparator class: AddressLineComparator ] [ Match token: ExactMatchToken ] and Address/Zip/Zip5 [ Comparator class: BasicStringComparator ] [ Match token: ExactMatchToken ] ) and Fuzzy on Name [ Comparator class: OrganizationNamesComparator ] [ Match token: OrganizationNameMatchToken ] |
| Rule4: Fuzzy (Name), Exact (Address1, State) | Creates a potential match when the name, address1, and state are an exact match. | ( Exact on Address/Address Line 1 [ Comparator class: AddressLineComparator ] [ Match token: ExactMatchToken ] and Address/State [ Comparator class: BasicStringComparator ] [ Match token: ExactMatchToken ] ) and Fuzzy on Name [ Comparator class: OrganizationNamesComparator ] [ Match token: OrganizationNameMatchToken ] |