2.3.6 Ranking matches within Entity Name rules
For each entity or vessel name matching rule, matches are ranked according to how
much and how strongly additional data matches between the customer record and the watch
list:
Table 2-22 Ranking matches within Entity Name rules
Match Rule | Summary of Matching Logic | Example Matching Data | Example Matching Data | Example Matching Data |
---|---|---|---|---|
[Entity name rule], city, country | At least one city matches. At least one country matches. | City | Country | - |
New York|London | GB | - | ||
London | GBUS | - | ||
[Entity name rule], city | At least one city matches. | City | - | - |
Paris| London | - | - | ||
Paris | - | - | ||
[Entity name rule], country | At least one country matches. | Country | - | - |
US | - | - | ||
PKIN US | - | - | ||
[Entity name rule] only | The entity name rule returns a match. No data in other fields. | Name | Country | City |
A C M | - | - | ||
A C M | - | - | ||
[Entity name rule] (conflict) | The entity name rule returns a match. Data in other fields do not match. | Name | Country | City |
A C M | UK | London | ||
A C M | FR | Paris | ||
[Vessel name rule] country | At least one country matches. | Country | - | - |
US | - | - | ||
PKIN US | - | - | ||
[Vessel name rule] only | Vessel name rule returns a match. No data in other fields. | Name | Country | City |
Dynasty | - | - | ||
Dynasty | - | - | ||
[Vessel name rule] (conflict) | Vessel name rule returns a match. Data in other fields do not match. | Name | Country | City |
Dynasty | U K | London | ||
Dynasty | F R | Paris |