Configuring Compliance Checks > Denied Party List Check > System Values Related to the DPL Check
  
System Values Related to the DPL Check
Compliance Checks in PRECISION lists the system values that control Denied Party behavior. Access these system values from the Y2 option. For more details, see Precision Base Web UI Administration Guide.

Denied Party List System Values
 
Category
Keyword
Value
COMPLIANCE
ACTION ON DPL SUBSET
Set this value to Yes or No.
Enables you to set the check to fail when the name being screened is a subset of the denied party name. This always returns a 100% match. By default, this value is set to No.
COMPLIANCE
DPL ALGORITHM
The only valid value is Soundex.
COMPLIANCE
DPL ALLOW REVERSE SCORING
Set this value to Yes or No.
The first step in the DPL engine is to return a subset of names from the DPL content, where at least one word in the name being checked exactly matches one word in the name from the content. If this parameter is turned on, it reverses the scoring in addition to the normal checking. It checks each of the names in the content returned from the first step against the name being screened.
This parameter helps to return extra matches that may be considered as failures.
For example, screening “John Richard Smith” against “John Smith” does not return a 100% match. However, if this parameter is turned on, it does return a 100% match.
COMPLIANCE
DPL MAX MATCHES PER TYPE
This value is a number.
This parameter determines the maximum number of matches displayed on the screen and the number of matches to be added to the white list when the partner is manually passed.
For example, there are 200 matches and the parameter is set to 100. Only 100 are displayed on screen and 100 added to the white list.
COMPLIANCE
DPL MINIMALWORD LENGTH
This value is an integer. The default value is 1.
This value indicates the minimum length a word in the name must be to trigger a match for the DPL scoring process to continue.
For example, the parameter is set to 6 and the name being checked is John Desmond Arthur Smith. There must be a match on the words Desmond or Arthur with words in at least one name. Alternatively, there must be a Soundex match on one of the words being checked against one of the words in the content for the DPL process to continue.
You can reduce the number of false positives by increasing the default value. However, it is recommended to keep the value to (<=3). If this parameter is increased, it can have an adverse effect and ignore names with potential matches in the DPL content.
This parameter applies to the name and the address check.
COMPLIANCE
DPL_RUN_C/O_CHECK
Set this value to Yes or No.
If this parameter is set to Yes and the first address line of the address begins with C/O, then the name on the first address line is also screened.
COMPLIANCE
DPL_RUN_CONTACT _CHECK
Set this value to Yes or No.
When set to Yes, the contact name associated with the partner is checked.
COMPLIANCE
DPL_RUN_ISMATCH
This value applies to the address screening and is a percentage.
When the percentage match exceeds the specified value, the check fails. It is recommended to set the warning threshold to between 75% and 80%.
COMPLIANCE
DPL_RUN_ISMATCH_WARN
This value applies to the address screening and is a percentage.
When the percentage match exceeds the specified value and the value is less than the failure percentage level, a warning is returned. It is recommended to set the warning threshold to between 65% and 70%.
A warning does not trigger a compliance failure.
COMPLIANCE
DPL_RUN_LISTS
The default value of this parameter is *ALL. This value runs the DPL check against all DPL lists.
To run the DPL check against only a certain number of DPL lists, set this parameter to this set of lists; for example, OFAC,ENTITY,UKF,OFAC,BIS,CBW.
COMPLIANCE
DPL_RUN_NAME_CHECK
Set this value to Yes or No.
The Denied Party Check consists of the Name check and the Address check. By default, this parameter is set to Yes and the Name check is run as part of the DPL screening. In the unlikely scenario that you have addresses without any names, the name check can be turned off by setting this parameter to No.
COMPLIANCE
DPL_RUN_NAME_ISMATCH
This value applies to the name screening and is a percentage.
When the percentage match exceeds the specified value, the check fails. It is recommended to set the threshold to between 80% and 85%.
COMPLIANCE
DPL_RUN_NAME_ISMATCH_WARN
This value applies to the name screening and is a percentage.
When the percentage match exceeds the specified value and the value is less than the failure percentage level, a warning is returned. It is recommended to set the warning threshold to between 75% and 80%.
A warning does not trigger a compliance failure.
COMPLIANCE
DPL_UPDATE_COMMON
A comma-separated list of common words.
The words in this list are ignored during the check; for example, Corporation, Inc, Ltd, Limited. Precision provides a list as a starting point.
COMPLIANCE
COUNTRY MANDATORY
Set this value to Yes or No.
The default value is No, which means that the country code associated with the party being checked is not mandatory. The address check does not fail when the country code is blank. To make the country code mandatory, set this parameter to Yes. In this case, the check fails when the country code is blank.
COMPLIANCE
SECURITY – DPL
This value is in the format action,client,user group
The three values specify a user group that can override the results of a DPL check; for example,
Override,TGL,ALL-ECO
For more details on this system value, see Security.
COMPLIANCE
USE CACHED DPL RESULTS
The value of this parameter is a comma-separated list of compliance statuses. Values are PA (Pass), PW (Pass Warning), FA (Fail), PM (Passed Manually), FM (Fail Manually).
When there has been no content update and you rerun a DPL check, the cached results for the partner are used instead of running the check again to obtain the same result.
This parameter defines the status for which the cached result is used.
Example: PA,PW. In this case, if a partner passed or passed with warning previously, the system reuses this status the next time a DPL check is run on this partner. Otherwise, the system does not reuse the cache and reruns the DPL algorithm on the partner.
It is recommended to use this parameter as it improves the overall response times of the DPL check.
Notes:
This parameter should be set to blank during the implementation phase until you have decided the threshold levels.
If using data scrub and processing compliance transactions and the percentage threshold levels for each may be different, this parameter must be set to blank permanently.