Match Attributes Selection

This page is accessed via Master Data > Power Data > Configurations > Service Parameter.

Restricted party screening is all about matching the party with a restricted party list. As part of this process, one of the important points is to identify the right attributes of the party to be matched with a restricted party to determine if it is a potential match or not. You can specify the list of attributes that should be considered during the screening process using the Service Parameter page. The service parameter is assigned to a service preference which is used during restricted party screening.

One practice is to use direct matching attributes, such as:

• Country attribute of the Party is matched with Country attribute of the Restricted Party
• Province attribute of the Party is matched with Province attribute of the Restricted Party
• City attribute of the Party is matched with City attribute of the Restricted Party
• First Name attribute of the Party is matched with First Name attribute of the Restricted Party
• Last Name attribute of the Party is matched with Last Name attribute of the Restricted Party
• Company Name attribute of the Party is matched with Company Name attribute of the Restricted Party

This means that when you are creating or modifying party information, you should be sure to enter the right value in the right field. Add first name in the First Name attribute or add city in the City attribute instead of entering both these attributes in the Address attribute field.

However, there may be instances where name, city or country information is entered in the Address attribute field. In such a situation, you can use a parameter such as “nameCompanyAddressCityProvinceCountry”. This parameter will internally concatenate all the attribute values of name, company, address, city, province, and country for both the party and the restricted party and then perform the match.

Note: It is strongly recommended that you use direct matching attributes (e.g. country parameter) wherever possible and enter the right value in the right field. By using a parameter such as “nameCompanyAddressCityProvinceCountry”, the quality of the match results might decrease and could produce a large number of false positives or might not identify valid matches.

Other key points related to parameter selection are match factor and weight, which contribute towards the overall matching of a party with a restricted party.

For every parameter (match attribute) configured, GTM determines a match factor (matching percentage) between the party and the restricted party and then compares it against the corresponding threshold. The threshold field can be used to filter out the restricted parties which have low match factor for a particular parameter with the result that they are not considered possible match. You can define a threshold between 0 and 1.

Once GTM determines that a parameter is a match between the party and the restricted party, its match factor is used along with the weight to calculate the adjusted match factor for that parameter. After all the parameters are screened and determined to be a match, an overall match factor is calculated using the adjusted match factor of individual parameters according to the following formula. The sum of all parameter weights should be equal to 1.

Overall Match Factor = (Match Factor * Weight) of Parameter1

+ (Match Factor * Weight) of Parameter2

+ ………………….+ (Match Factor * Weight) of last Parameter

where, Adjusted Match Factor of parameter1 = (Match Factor * Weight) of Parameter1

Note: It is strongly recommended that you provide a higher threshold (1 or near to 1) for parameters wherever possible. By default, the restricted party screening process will first match those parameters that have the highest threshold. If the match threshold fails, GTM stops matching other parameters immediately and thereby increases restricted party screening performance.

Note: It is strongly recommended that you set the weight of parameters (match attributes) such as country and/or city as 0. Setting the weight of parameters to 0 means that these specific parameters (e.g. country or city) will have to pass the individual parameter match factor threshold, but they would not contribute towards the overall match factor. Another way of looking at it could be that you want the country and city attributes to match completely, while you want other attributes like address, company name to contribute more towards the overall match factor.

Additional properties that control the behavior of match factor determination are described below. The default values, which are shown below, are the recommended values.

• gtm.rps.match.useCountryCode=true specifies that the country code will be matched instead of Country Name.
• gtm.rpls.match.setMatchFactorToZero=true nullifies the contribution of unknown or empty parameter towards the overall match factor.
• gtm.rpsservice.maxresponse property specifies the maximum number of screening matches that are returned. The default value for the property is 500.

Note: You can use the optional feature "PRORATE RPLS EMPTY PARAMETER WEIGHT" to exclude an empty parameter as part of the Overall Match Factor and hence, reduce the number of false positives returned during restricted party screening. When the feature is enabled and the Match Default is MATCH, weightage of the empty parameters is prorated among the non-empty parameters while calculating the overall match factor and is then compared with the threshold on the service preference.
Overall Match Factor without prorating = Sum of weighted Match Factor for all non-empty parameters
Overall Match Factor with prorating = Sum of weighted Match Factor for all non-empty parameters/Sum of weight of all non-empty parameters