2.2 Input Fields for Entity Screening

This section lists the inputs fields used when screening entities via the real-time process. Seven input attributes are available for the entity screening process. They are available for any additional inputs required by your screening process.

The following table lists the entity input fields in order, the data format expected for each field, attribute requirement, maximum character length, and description on their use in screening:

Table 2-2 Input fields for Entity screening

Field Expected Data For mat Attribute Requirement Maximum Character Length Field Name and Description
Jurisdiction String Mandatory 4

Jurisdiction:

This field enables your firm to restrict access using geographic locations. You can only see cases that are assigned to the same jurisdictions.

Note:

This is the metadata which admin has to configure in ECM kdd_jrsdcn table (JRSDCN_CD column).

Business Domain String Mandatory 1

Business Domain:

This field layer enables your firm to restrict access along operational business lines and practices. You can only see cases that are assigned to at least one of the same business domains.

Note:

This is the metadata which admin has to configure in ECM kdd_bus_dmn table (BUS_DMN_CD column).

EntityName

 String Mandatory 255

EntityName:

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.

Note:

This is a user input. The entity name is screened against watchlist.
City String Recommended No restriction

City:

City data is used to strengthen potential match information.
AddressCountryCode String Recommended No restriction

Address Country:

Address country data is used to strengthen potential match information.

Note:

This is the user input. The value is used to screen against watchlist. Ideally this field will be the address country code of the Entity being screened.
RegistrationCoun tryCode String Recommended No restriction

Registration Country:

The entity's registration country can be used in optional country prohibition screening.

Note:

This is the user input. The value is used to screen against watchlist. Ideally this field will be the registration country code of the Entity being screened.
OperatingCountry Codes String Recommended No restriction

Operating Countries:

Any of the entity's operating countries can be used in optional country prohibition screening.

Note:

This is the user input. The value is used to screen against watchlist. Ideally this field will be the operating country code of the Entity being screened
External IdType String Recommended No restriction

External ID Type:

The external ID type of the entity.

Note:

This is the metadata that admin can configure in KDD_CODE_SET_TRNLN table (CODE_DISP_TX column).

External Id String Mandatory if external ID type field is selected No restriction

External ID:

External identification number that contains unique record identifier.
Identifi cationNumbers String Recommended No restriction

IdentificationNumber:

Unique Identification Number, which is issued to the entity.
Original ScriptName String Recommended No restriction

Original Script Name:

The name of the entity in native written version or in native language.
SourceRequestID String Optional 3000

Source Request ID:

The source request Id can be used to provide the customer ID while screening.
Action String - - Action parameter is added internally to differentiate between Scan and Scan & Investigate