Accelerate the Value of Data

Match rules for Financial Services

Learn what match rules are included for organization and individual entity types in Reltio for Financial Services.

Reltio for Financial Services brings together systems including banking, investment, and CRM systems. Most of these systems duplicate customer information. Match rules define the criteria Reltio uses to determine whether two records are duplicates.

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

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

Financial Account entity type match rules (Financial Services)

This table identifies the Reltio for Financial Services match rule used to master data for the Financial Account entity type. Use this match rules to create a record for a financial account.

LabelDescriptionMatch queries
Exact (Account Name, Number, and Type)Automatically merges records
(
  Exact on
    Account Name
    and
    Account Number
    and
    Account Type
)
Exact (Account Number and Type) Fuzzy (Account Name)Creates a potential match
(
  Exact on
    Account Number
    [Comparator class:BasicStringComparator]
    [Match token:ExactMatchToken]
    and
    Account Type
    [Comparator class:BasicStringComparator]
    [Match token:ExactMatchToken]
)
and
  Fuzzy on
    Account Name
    [Comparator class:BasicStringComparator]
    [Match token:FuzzyTextMatchToken] 

Financial Professional entity type match rules (Financial Services)

This table identifies the Reltio for Financial Services match rule used to master data for the Financial Professional entity type. Use this match rules to create a record for a financial professional.

LabelDescriptionMatch queries
Rule1: Fuzzy(First Name, Last Name);Exact(Email, Phone)Creates a potential match
  Exact on
  Email/Email Address
and
(
  Fuzzy on
    Phone/Phone Number
    [Comparator class:PhoneNumberComparator]
    [Match token:ExactNumberMatchToken]
    and
    First Name
    [Comparator class:DoubleMetaphoneComparator]
    [Match token:DoubleMetaphoneMatchToken]
    and
    Last Name
    [Comparator class:DoubleMetaphoneComparator]
    [Match token:DoubleMetaphoneMatchToken]
)
Rule2: Fuzzy(First Name, Last Name);Exact (Address Line1, Zip5); ExactOrNull(NameSuffix, Email)Creates a potential match
(
  Exact on
    Address/Address Line 1
    and
    Address/Zip/Zip5
)
and
(
  Exact Or All Null on
    Email/Email Address
    and
    Name Suffix
)
and
(
  Fuzzy on
    First Name
    [Comparator class:DoubleMetaphoneComparator]
    [Match token:DoubleMetaphoneMatchToken]
    and
    Last Name
    [Comparator class:DoubleMetaphoneComparator]
    [Match token:DoubleMetaphoneMatchToken]
)
Rule4: Fuzzy (First Name, Last Name); Exact(email)Creates a potential match
  Exact on
    Email/Email Address
and
(
  Fuzzy on
    First Name
    [Comparator class:DoubleMetaphoneComparator]
    [Match token:DoubleMetaphoneMatchToken]
    and
    Last Name
    [Comparator class:DoubleMetaphoneComparator]
    [Match token:DoubleMetaphoneMatchToken]
)
Rule5: Fuzzy (First Name, Last Name); Exact(Phone)Creates a potential match
  Exact on
    Phone/Phone Number
    [Match token:ExactMatchToken]
and
(
  Fuzzy on
    First Name
    [Comparator class:DoubleMetaphoneComparator]
    [Match token:DoubleMetaphoneMatchToken]
    and
    Last Name
    [Comparator class:DoubleMetaphoneComparator]
    [Match token:DoubleMetaphoneMatchToken]
)
Rule6: Exact (First Name, Last Name, DOB, Address1)Creates a potential match
(
  Exact on
    Last Name
    [Match token:ExactMatchToken]
    and
    First Name
    [Match token:ExactMatchToken]
    and
    configuration/entityTypes/FinancialProfessional/attributes/DoB
    [Match token:ExactMatchToken]
    and
    Address/Address Line 1
    [Match token:ExactMatchToken]
)

Individual entity type match rules (Financial Services)

This table identifies the Reltio for Financial Services individual match rules used to master data for individuals. Use these match rules to create a record for an individual. For information on match rules, see topic Configure match rules overview.

LabelDescriptionMatch queries
Rule1: Fuzzy(First Name, Last Name);Exact(Email, Phone)Creates a potential match
(
  Exact on
    Email/Email Address
    and
    Phone/Formatted Number
    [Comparator class:PhoneNumberComparator]
    [Match token:ExactNumberMatchToken]
)
and
(
  Fuzzy on
    First Name
    [Comparator class:DoubleMetaphoneComparator]
    [Match token:DoubleMetaphoneMatchToken]
    and
    Last Name
    [Comparator class:DoubleMetaphoneComparator]
    [Match token:DoubleMetaphoneMatchToken]
)
Rule2: Fuzzy(First Name, Last Name);Exact (Address Line1, Zip5); ExactOrNull(NameSuffix, Email)Creates a potential match(
(
  Exact on
    Address/Address Line 1
    and
    Address/Zip/Zip5
)
and
(
  Exact Or All Null on
    Email/Email Address
    and
    Name Suffix
)
and
(
  Fuzzy on
    First Name
    [Comparator class:DoubleMetaphoneComparator]
    [Match token:DoubleMetaphoneMatchToken]
    and
    Last Name
    [Comparator class:DoubleMetaphoneComparator]
    [Match token:DoubleMetaphoneMatchToken]
)
Rule3: Fuzzy(First Name, Last Name);Exact (SSN, ITIN)Creates a potential match
  Exact on
    SSN
    [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]
)
and
  Exact on
    Individual Taxpayer Identification Number
    [Comparator class:BasicStringComparator]
    [Match token:ExactMatchToken]
Rule4: Fuzzy (First Name, Last Name); Exact(email)Creates a potential match
  Exact on
    Email/Email Address
and
(
  Fuzzy on
    First Name
    [Comparator class:DoubleMetaphoneComparator]
    [Match token:DoubleMetaphoneMatchToken]
    and
    Last Name
    [Comparator class:DoubleMetaphoneComparator]
    [Match token:DoubleMetaphoneMatchToken]
)
Rule5: Fuzzy (First Name, Last Name); Exact(Phone)Creates a potential match
  Exact on
  Phone/Formatted Number
  [Match token:ExactMatchToken]
  and
(
Fuzzy on
  First Name
  [Comparator class:DoubleMetaphoneComparator]
  [Match token:DoubleMetaphoneMatchToken]
  and
  Last Name
  [Comparator class:DoubleMetaphoneComparator]
  [Match token:DoubleMetaphoneMatchToken]
)
Rule6: Exact (First Name, Last Name, DOB, Address1)Creates a potential match
(
  Exact on
    Last Name
    [Match token:ExactMatchToken]
    and
    First Name
    [Match token:ExactMatchToken]
    and
    Address/Address Line 1
    [Match token:ExactMatchToken]
    and
    Date of Birth
)

Location entity type match rules (Financial Services)

This table identifies the Reltio for Financial Services match rule used to master data for the Location entity type. Use this match rules to create a record for a specific location.

LabelDescriptionMatch queries
[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 (Financial Services)

This table identifies the Reltio for Financial Services organization match rules used to master accounts, companies, and businesses. Use these match rules to create a record for an organization. For information on match rules, see topic Configure match rules overview.

LabelDescriptionMatch queries
Rule1: Exact (Name, Identifier)Creates potential 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]
)
Rule3: Fuzzy (Name), Exact (Address1, State)Creates potential 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]
Rule3: Fuzzy (Name), Exact (Address1, Zip)Creates potential 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]