Match rules for B2B
Learn about the match rules used in Reltio for B2B that are defined out-of-the-box.
Reltio for Customer Data (B2B) v3 brings together systems and most of these systems duplicate customer information. Match rules define the criteria Reltio uses to determine whether two records are duplicates.
Organization, Contact, and Location entity types are likely to be duplicated, so match rules help you reconcile any variations.
For information on working with match rule properties, see topic Preconfigured User Interface for B2B.
B2B comes with predefined match rules specific to the business to business industry. Take a look at the match rules types defined for a specific entity in .
For general information on match rules, see topic Reltio match, merge, and survivorship. For information on working with match rules, see topic Configure match rules overview. For descriptions of the match rules that come with Reltio for B2B, see the following sections.
B2B has the following match rules predefined out of the box:
| S. No | Rule |
|---|---|
| 0 | Exact (Name, Address, Phone) - Automatic Merge |
| 1 | Exact DUNS Number - Automatic Merge |
| 2 | Fuzzy (Name), EOAN (Identifier), EON (Phone), Exact (Address1, Zip5, Tax ID) - Automatic Merge |
| 3 | Exact (Name, Identifier) - Potential Match |
| 4 | Fuzzy (Name), Exact (Tax ID) - Potential Match |
| 5 | Fuzzy (Name), Exact (Address1), Exact (City or Zip) - Potential Match |
| 6 | Fuzzy (Name Metaphone), Exact (Address1), Exact (City or Zip) - Potential Match |
| S. No | Rule |
|---|---|
| 1 | Fuzzy(First Name, Last Name) With Exact OR Null on Phone/Email - Potential Match |
| 2 | Fuzzy(First Name, Last Name); Exact (Address1, Zip5); ExactOrNull(Suffix, Email) - Potential Match |
| S. No | Rule |
|---|---|
| 1 | Exact (Address1, City, State, Zip5, Verification Level) - Potential match. |
| 2 | Exact (Addr1, City, State), EOAN (Addr2, Zip, Bldg, Sub Bldg) - Auto Merge |
| 3 | Exact (Address1, City, State, Zip, Verification Level) - Potential Match |