This rule is skipped for records that have a jurisdiction code (legal_entity_jurisdiction_code).
Field | Value |
Status and Priority | |
Confidence Level | Medium |
Match Reason | Changes based on context |
Summary
This flow determines the best legal entity match when an input record has an exact name match (legal or trading name) and jurisdiction country code (the country from the record’s address is the same as the country from the candidate’s jurisdiction code). The process follows three main steps: candidate retrieval, active status tiebreaker, and home/branch family tiebreaker.
This rule uses Matched Attributes (MAs). For additional information, see this article.
Match Logic
Step 1 - Valid Candidates Retrieval
All candidates where all of the conditions below apply are considered valid candidates:
legal_nameortrading_name(or both) matched attributes are available.jurisdiction_country_codematched attribute is available.Candidate’s jurisdiction code’s country is not “us” or “ca”!
If the list has at least one valid candidate, the flow proceeds to the next step. Otherwise, the flow ends.
Step 2 - Active Status Tiebreaker
Uses the values in the inactive field for each candidate as a tiebreaker according to the following priority:
Active -
inactive=false.Unknown -
inactive=null.Inactive -
inactive=true.
After applying this tiebreaker, if there is no tie at the top of the list, then first-ranked candidate is selected as the best match.
Match confidence: Medium.
Match reason: “Exact name and jurisdiction country code - active status tiebreaker”.
Step 3 - Home/Branch Family Tiebreaker
If there is still a tie at the top of the list, the home/branch relationship between the tied candidates is evaluated - see this for additional details: https://tealbook.atlassian.net/wiki/x/LwDn3g.
If a candidate is selected:
Match confidence: Medium.
Match reason: “Exact name and jurisdiction country code - home/branch family tiebreaker”.
If the active status narrowed down the original list, then the reason should be: “Exact name and jurisdiction country code - home/branch family and active status tiebreakers”.
Examples
Example 1: Active Status Tiebreaker
In this case we have a clear winner and there is no tie at the top of the list because C1 is active while the other candidates are not.
Candidate | Active Status Tiebreaker | Home/branch Family Tiebreaker |
|---|---|---|
C1 | Active | Family A |
C2 | Unknown | Family A |
C3 | Unknown | Family A |
C4 | Inactive | Family A |
C5 | Inactive | Family B |
C6 | Inactive | Family B |
C7 | Inactive | Family B |
C8 | Inactive | Family B |
C9 | Inactive | Family B |
C10 | Inactive | Family B |
Example 2: Home/Branch Family Tiebreaker
In this example, C1 to C4 are from the same family. C3 is the home company of this family and therefore it gets selected as the best match. If C11 was the home company, it would have been selected even though it is not on the list.
Candidate | Active Status Tiebreaker | Home/branch Family Tiebreaker |
|---|---|---|
C1 | Active | Family A branch |
C2 | Active | Family A branch |
C3 | Active | Family A home company |
C4 | Active | Family A branch |
C5 | Unknown | Family A |
C6 | Unknown | Family B |
C7 | Unknown | Family B |
C8 | Inactive | Family B |
C9 | Inactive | Family B |
C10 | Inactive | Family B |
Example 3: No Winner
Here, we have a tier with C1 to C4 because they are all active, however, they are a part of 2 families (A and B), and in this case none of the candidates should get selected.
Candidate | Active Status Tiebreaker | Home/branch Family Tiebreaker |
|---|---|---|
C1 | Active | Family A branch |
C2 | Active | Family A branch |
C3 | Active | Family B home company |
C4 | Active | Family A branch |
C5 | Unknown | Family A |
C6 | Unknown | Family B |
C7 | Unknown | Family B |
C8 | Inactive | Family B |
C9 | Inactive | Family B |
C10 | Inactive | Family B |