Restricted Party Screening

Restricted Party Screening

This page is accessed via Restricted Party Screening > Restricted Party Screening.

Ad hoc Restricted Party Screening allows you to screen the data of any party without creating a party in GTM. You can provide all the information about the party on this screen. On this screen, information in all of the fields is compared to restricted party information already on file. The more fields you can complete, the more accurate the screening will be. Any empty field will be ignored. You can also provide a single or multiple service preferences (profile) to perform the screening.

Screening Criteria

  1. Enter the first and last name of the entity that is to be screened in the First Name and the Last Name fields respectively.
    OR
    Enter the name of the company associated with the entity in the Company Name field.
  2. Enter the address details of the entity in the Address field.
  3. Enter the name of the city associated with the entity in the City field.
  4. Enter the name of the province associated with the entity in the Province field.
  5. Select the code of the country associated with the entity from the Country drop-down list.
  6. Enter the postal code associated with the entity in the Postal Code field.
  7. If you prefer to screen using a specific service preference, select an option from the Service Preference drop-down list.
    OR
    If you prefer to screen using multiple service preferences, select an option from the Restricted Party Screening Profile ID drop-down list.
  8. Click Screen Party.

Any information you provide in this section will generate screening match(es), based on the service preference(s) used if there is a restricted party with similar information. Once the screening is completed, the list of restricted parties matched will be displayed. For every restricted party match, GTM shows the match factor, indicating the percentage of match.

Note: The maximum number of records displayed on this page can be controlled via the gtm.rpsservice.redwood.maxresponse property.

Note: If your screening criteria are an exact match to an excluded party, no screening will be performed. If any restricted party in the results is a complete match to an excluded party, the party will not appear in the returned results.

Note:
If you do not provide a service preference or a screening profile, the screening will be run using a default service preference.
You can set up a default service preference/screening profile for ad hoc Restricted Party Screening on the GTM Logic Configuration page.

If you don't configure a default service preference/screening profile for ad hoc Restricted Party Screening on the GTM Logic Configuration page, the application uses the out of the box AD_HOC_PARTY_SCREENING_SERV_PREF preference.

Note: The application is configured to automatically purge and archive the Restricted Party List Screening ad hoc audit results after 60 days.

Note: Highlighting of the matching characters is not supported for this page.

Review Match Factor

Select a record from the list of potential matches to view the processing details of matching the party with the restricted party in the Review Match Factor section.

Additional properties that control the behavior of match factor determination are as follows. The default values 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.redwood.maxresponse property specifies the maximum number of screening matches that are returned. The default value for the property is 15.
  • gtm.rpls.prorateEmptyParamterWeight property 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 property is set to “true” 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
    The default value of the property is false.

Note: Inverted Index matching engine is supported by this action for a quicker performance.

Related Topics