3.1.2 Entity private watch list input attributes

This section lists the private PLI fields used for entities. In addition to a number of prescribed fields, fifty customizable input attributes are available for entity private lists. Forty of these are string attributes, five are date attributes and five are number attributes. They are available for any additional inputs required by your private watch list. The following table lists the entity PLI fields in order, the data format expected for each field, and notes on their use in screening:

Table 3-2 Entity private watch list input attributes

Field Name	Expected Data Format	Notes
ListSubKey	String	This field is used to identify the source list of the watchlist record (for example, Private List, Accounting Private List, Financial Private List and so on). It is included in the alert key.
ListRecordType	String	[Mandatory attribute]This field is used when filtering alerts, to determine whether the record is a sanctions, PEP or enhanced due diligence record. It must contain a value of SAN, EDD, or PEP or a combination of these values. If you want to include a combination of values, the values should be comma- separated, and enclosed by double quotation marks. For example: "SAN, EDD, PEP"
ListRecordOrigin	String	This field is used to record the provenance of a record when it is part of a consolidated list.
ListRecordId	String	[Mandatory attribute] This attribute is not used as part of the matching process, but is used to create the case key. Therefore, it should be populated with a unique identifier.
RegistrationNumber	String	This is an optional field that may be used to capture entity registration numbers where known for use in the review process. Note that entity registration numbers are not used for matching in the default screening rules.
Identifiers	String	Identifier scan be registration ID or any other identity.
EntityName	String	[Mandatory attribute] The entity matching process is based primarily on the name supplied for the entity. An entity name or original script name must be submitted to the screening process for screening to proceed.
NameType	String	This is an optional field used in the review process only. Multiple names may exist for the same entity. The Name Type therefore denotes if the name is the primary name of the listed party, or an additional name (such as an Alias, or Alternate Spelling). If two private list records were derived from a single source with multiple names, you may wish to denote one as the primary name and one as an alias.
NameQuality	String	This field may be assigned a value of Low, Mediumor High to indicate the quality of the individual name. Highis used for Primary names and specified Good/ High quality aliases.
PrimaryName	String	For alias records, this field indicates the main name for that record.
OriginalScriptName	String	[Mandatory attribute] The entity matching process is based primarily on the name supplied for the entity. An entity name or original script name must be submitted to the screening process for screening to proceed. If you populate the Original Script Name, then you will also need to enable two facets of Match processor configuration that are disabled by default: the Original Script Name Cluster and some or all of the Match Rules that include Original script name in their name. To adapt Match Processor configuration, you will need to open the Watchlist Screening project within the Director user interface, and make the changes to every process used by your Oracle Financial Services Customer Screening installation. There are separate processes for different types of screening. Examples include Entity Batch PEP Screening, Entity Real-time Screening and Entity Batch EDD Screening. Each of these processes will include a match processor with a name that is the same as the process name (for example, in the Entity Batch SAN Screening process, the Match processor will also be called Entity Batch SAN Screening).
AliasIsAcronym	String	If this field is set to Y, this flags an alias as an acronym as opposed to a full entity name. Leaving the field blank or setting it to any other value has no effect (i.e. an alias is assumed to be a full entity name). NOTE: This flag is used during matching.
VesselIndicator	String	This field should be set to Y if the entity is a vessel (a ship). It should be left empty or set to Nif the entity is not a vessel.
VesselInfo	String	If the entity is a vessel, you can populate this field with information about it: for example, its call sign, type, tonnage, owner, flag and so on.
Address1	String	These are optional fields that may be used in the review process.
Address2	String
Address3	String
Address4	String
City	String	[Recommended attribute] City data is used to strengthen potential match information.
State	String	[Recommended attribute] State data is used to strengthen potential match information.
PostalCode	String	[Recommended attribute] Postal code data is used to strengthen potential match information.
AddressCountryCode	String;ISO 2-character country code.	[Recommended attribute] Address country data is used to strengthen potential match information.
RegistrationCountryCod e	String;ISO 2-character country code.	[Recommended attribute] The entity's registration country can be used in optional country prohibition screening.
OperatingCountryCodes	String;ISO 2-character country code.	[Recommended attribute] Any of the entity's operating countries can be used in optional country prohibition screening.
ProfileHyperlink	String;a hyperlink to an Internet or intranet resource for the record.	This field may contain a hyperlink to an Internet or intranet resource that can provide reviewers with additional information about the entity.
RiskScore	Number,between 0 and 100	This field is included where the risk score for a customer is calculated externally instead of using the Watchlist Screening rules. It is normally populated using Watchlist Screening’s risk scoring process. NOTE: It is possible to eliminate records if their risk score is below a certain threshold.
RiskScorePEP	Number,between 0 and 100	A number indicating the relative ‘riskiness’ of the entity, considered as a PEP. The risk score is expressed as an integer between 1 and 100, with higher numbers indicating a higher risk.
AddedDate	String,representing a date, in the format 'YYYYMMDD'	These are optional fields for use in the review process.
LastUpdatedDate	String,representing a date, in the format 'YYYYMMDD'
DataConfidenceScore	Number,between 0 and 100
DataConfidenceComment	String
InactiveFlag	String	If populated, this optional field should contain either Y orN.
InactiveSinceDate	String,representing a date, in the format 'YYYYMMDD'	If populated, this optional field should contain either the current date or a date in the past.
PEPclassification	String	This field can be used to indicate the type of PEP (for example, whether it relates to an international organization or government, and at what level). It can be used to filter watch list records, and is primarily used by the World-Check watch list, but could be used by a private watch list if required. See section 3.2 of the Oracle Financial Services Customer Screening Implementation guide for more information about filtering.
customString1to customString40	String	Fifty custom fields are provided in the private list data interface for entities. Forty of these are intended to hold string data, five hold dates and five numeric data. NOTE: The interface file is a comma-separated value (.csv) file, and so all fields intrinsically contain strings. However,during the processing of Private watch lists, the custom date and number fields are checked to ensure that they include appropriate data, and warning messages are output if they do not.
customDate1 to customDate5	String,representing a date, in the format 'YYYYMMDD'
customNumber1to customNumber5	Number