Data classes are used to organize, store, and reference instances of KYC Type rules. You should create data classes to store specialized KYC Type rules for the institution.

Know Your Customer for Financial Services is shipped with a distinct set of rulesets grouped by the AML regulations, Product-based regulations and Tax-based regulations of due diligence. The AML group is further split into Global, Regional and Local regulations. Within these rulesets, there are Pega-provided classes that organize the preconfigured due diligence rules shipped with the system. Both the rules and classes serve as a design model, and are reusable assets for production implementations.

The design is intended to facilitate configuration and maintenance updates while allowing clients to logically separate their due diligence rules. You should construct specialized data classes to store the client’s specialized due diligence rules. The client’s specialized data classes can be configured to inherit from the PegaKYC-Data-Type-Policies- classes to promote reuse.

You can use the KYC Type rule design form to configure when, and how, a due diligence data capture form is presented to the end user within a case.

Type definition

The Type Definition tab displays to business users all the configurable attributes that control when, and how, a KYC Type is selected and displayed at run-time:

• KYC Type Name – Represents the name of the KYC Type that is displayed in the case user interface at runtime. This label can include spaces.
• Class – The Applies to class for the KYC Type.

• Applies When condition – Defines when the KYC Type is applicable and selected for display within the case.

  • By default, all KYC Types are never applicable if no Applies when condition is configured. Specifically, the KYC Type is turned off using a Boolean condition set to false.
  • All KYC Types require an explicit condition that can be evaluated to true to apply the KYC Type, and to make it visible within a case.
  • You can use several types of decision rules, including when, map value, decision table, and decision tree rules. For ease of configuration, a condition of always is available if the KYC Type is required to always be selected for every case.
  • There are three main decision table rules configured as Applies When in the KYC Types available in the system OOTB -  
    • AMLRegulationMasterAppliesWhen – for KYC Types related to AML regulations.
    • ProdRegulationMasterAppliesWhen – for KYC Types related to Product-based regulations
    • TaxRegulationMasterAppliesWhen – for KYC Types related to Tax-based regulations.

  • For more information on KYC Types applicability, see the KYC Type Applicability article on the knowledgebase site for Pega Know Your Customer.

• Display Order –This attribute is used to configure the horizontal (or vertical) display order for the KYC Type in the case user interface. To view the ordering of all available KYC Types, click Info.
  • For example, if StandardDueDiligence_Entity is selected to apply to the case, then it appears first in the case, because its sequence number is set to 1.
  • If navigation is configured to use a horizontal layout, then the KYC Type order begins at the furthest position to the left.
  • If configured as a horizontal layout, the KYC Type order begins at the furthest position to the top.
  • Multiple KYC Types can share the same ordering sequence number. In this case, the secondary sequence is alphabetical from lowest to highest (A-Z). Then the next group of ordering sequences are sorted and displayed.
• Read Only Condition – This attribute controls when the entire KYC Type (all KYC Items) should be read-only to the end user. Specialized when, map value, decision tree, and decision table can also be used.
  • When this read-only condition evaluates as true, all the KYC Items associated with this KYC Type are rendered as read-only to the user.
  • If no decision rule is configured, the KYC Type is displayed as editable by default.

• Data Transform – This data transform is invoked when the KYC Type is initialized/loaded in the case. For cases like this, to set the values for applicable KYC items when the clipboard has the data required, a data transform rule can be configured to initialize the KYC Item Response properties at the time of initialization. This feature is used to prevent users from re-entering data values, if they are already available.

• Refresh Data Transform – This data transform is used to re-initialize only specific attributes, unlike the above data transform. It is useful whenever a case is refreshed, or the KYC Type is re-initialized. For example, if the basic information of a related party is updated in the case, resulting in a refresh of the KYC case. To avoid the KYC case having stale data, a data transform can be configured on the KYC Type to the questionnaire of the party.

• Profile suite & Profiles list – A Profile Suite is a set of KYC Profiles. A Profile Suite provides a way to filter those questions at a higher level, based on the attributes of the party to which the questionnaires are applied. Out-of-the-box, the application offers profiles for different levels of required due diligence activity. These levels are: Simplified, Full, or Enhanced. The logic that drives the required level of due diligence comes from the AML Due Diligence Profiles. In addition, separate profiles apply to a customer and a Related Party.

  • The profile value drives the level of due diligence that is required, as well as differentiating between the customer and their related parties. This allows different logic to be applied, based on various factors like type of the party (acting as contracting party or related party), risk, positive screening hits, etc.

  • The user can associate each question with one or multiple profiles from the profile suites, and the association follows either an inclusion or exclusion mechanism. In inclusion, the question displays only for the selected profiles. In exclusion, the question is skipped for selected profiles.

  • For example, the question ‘Is the customer linked to any Related Party who is a PEP?’ is applicable only to a party acting as contracting party, and not to a related party. In that case, the profile configured for this will be inclusion only for profiles related to a contracting party, that is, Contracting party simplified (CPSDD), etc.

  • For more information on due diligence profiling, see the Due Diligence Profiling article on the knowledgebase site for Pega Know Your Customer. 

  • In addition, see the section on Related Party Management in: Pega Client Lifecycle Management Implementation Guide

• Post-processing Data Transform – When data transform rules are referenced in this field, the rule runs immediately after the KYC Type is submitted, that is, after the data collection step in the case flow. Any answers to the questions can be saved in the customer master profile, so that data can be used in further evaluations of the customer.

Item Definition

A KYC Type can be configured to have Item groups and Items. KYC Item groups logically group and segment the KYC Items within the KYC Type. KYC Item groups should be used when a questionnaire form contains many KYC Items, which makes it difficult for the end user to identify which question they are working on, or to locate specific questions in a large set of KYC Items.

For example, a set of items requesting basic information such as name fields, different addresses or contact information can be logically grouped into a ‘Basic Information’ item group. Similarly, questions related to customer risk can be logically grouped into a ‘Customer Risk’ item group.

The Item Definition tab contains all KYC Item configurations of the KYC Type.

When a new KYC Type is created, the Item Definition tab shows the following information by default. There are no listed KYC Items, and a single Add Item button is displayed.

To add an item group -

Click Add, and select Item group from the dropdown. The following descriptions apply to each attribute which is displayed in the configuration window:

• Item Group – This checkbox is displayed as read-only, and is selected by default to indicate it is an item group.
• Item Group Name – This is for reference, and should contain the same text that is used for the display text.
• Field Value – Only field values are available for KYC Item groups. Click the open rule button to create/edit a field value that displays in the KYC item group header at run-time.
• Profiles association type and associated profile(s) – This is to display the item group only for selected profiles available in the profiles list. The profiles association type can be inclusion, exclusion or show all. If the association type is inclusion, the item group will be displayed for the selected profiles. If it is exclusion, the item group will be skipped for the selected profiles. If it is show all, the item group is displayed for all the profiles.
  • For example, consider there are three profiles, which are: Simplified, Full, and Enhanced. If the item group has the profile association type as inclusion and the selected profiles are full and enhanced, then the item group and its associated items will be displayed only when the customer comes under either of the profiles selected.
• Display Condition – An entire KYC Item group (and all of its KYC Items) can be conditionally shown or hidden by configuring a decision rule.
  • When, map value, decision tree, and decision table rules are available. Use autocomplete to select an existing decision rule, or enter a new rule name, and click Edit to create the rule.
  • If no decision rule is configured, the item group is displayed by default.
• Audit note – Enter audit information when adding, deleting, or updating existing KYC Item groups. This allows for change tracking and reporting across versions of KYC Types.
• Show expanded – On submit, the item group is added to the KYC Type. Click on the show expanded arrow, to display the associated KYC Items in the item group.

To add an item -

Click Add, and select Item from the dropdown to create a KYC Item. The following descriptions apply to each attribute which is displayed in the Item Configuration window:

• Item Group – This checkbox is displayed as read-only, and is un-checked by default for an item
• Item Property – This field references the simple or complex response properties that define the data to be displayed and captured at runtime. To define response properties, carry out one of the following tasks:
  • Use autocomplete to locate and select readily-available properties created in the prior steps.
  • Create a new property by entering a dot, and then enter a property name and click the magnifying glass icon to open and define the new property.
• Edit Section - This is a section rule that defines the layout to capture response for a single-value property or multiple values for the complex (page list) property. It is displayed under the KYC item text.
  • Either use autocomplete to select an existing section rule, or enter a rule name and click the open rule icon to open the new rule form editor.
• IsComplete Condition - Unlike single-value properties, in its current design, the system does not know when a complex property and all of its required values are completed.
  • To validate completeness of complex properties, a custom decision rule must be constructed. The rule must be configured to evaluate all of the data values captured within the Edit Section rule.
  • Either use autocomplete to display and select a pre-existing rule, or enter a rule name, and click Edit to open and create a new decision rule.
• Item Text – Select the type of rule to use to display the KYC Item text at runtime in the case UI.
  • For simple display text, select Field Value and then click the open rule icon to create a new rule or edit an existing one.
  • For display text that requires complex formatting, for example, Guidance links or italic fonts, select Paragraph rule to use Pega’s rich text editor. In the autocomplete field, select an existing paragraph rule, or enter a new rule name and then click open rule icon to open or create the paragraph rule.
• Profile association type and associated Profile(s) ​​​​​​ – This is to display the item group only for selected profiles available in the profiles list. The profiles association type can be inclusion, exclusion or show all. If the association type is inclusion, the item group will be displayed for the selected profiles. If it is exclusion, the item group will be skipped for the selected profiles. If it is show all, the item group is displayed for all the profiles.
• Display condition – This is one of the most commonly used attributes, because it determines whether the KYC Item is hidden, or displayed, to the end user.
  • If no decision rule is configured, the KYC Item is displayed by default. To be conditionally hidden or displayed, a condition must be configured and referenced in this attribute.
  • Select the decision rule type available (when, map value, decision tree, decision table). Select an existing rule from autocomplete, or enter a rule name, and click the open rule icon to open the rule form edit to create/edit the decision rule.
• Initiate Type Re-Evaluation – When this checkbox is selected, the system automatically triggers the processing required to evaluate Applies When logic of other KYC Type rules. When the conditions are met, other KYC Types are displayed in the case for data collection.
• Initiate Profile Re-Evaluation – When this checkbox is selected, the system automatically triggers the processing required to re-evaluate the active profile. If the profile is updated, the KYC Type is refreshed to display the items/item groups to be displayed/hidden.
• Required condition – When a decision rule is configured and referenced in this attribute, and its logic evaluates to true, a response is required for the KYC Item and denoted with the default orange * icon.
  • By default, all KYC Items are NOT mandatory.
  • By default, this attribute works only for single-value properties. KYC Items using complex properties require mandatory conditions to be configured within the edit section attribute associated with it.
  • Select the decision rule type available (when, map value, decision tree, decision table). Select an existing rule from autocomplete, or enter a rule name and click the open rule icon to open the rule form edit to create/edit the decision rule.
  • If no decision rule is configured, the item is treated optional by default. Configure a decision rule to make it mandatory whenever required.

• ReadOnly Condition –Controls the edit permissions of the KYC Item’s response property value within the case user interface. By default, all KYC Item are Read/Write.

  • This attribute works only for single-value KYC Items. Items using complex properties require read-only conditions to be configured within the edit section associated with it.
  • Select the decision rule type available (when, map value, decision tree, decision table). Select an existing rule from autocomplete, or enter a rule name, and click the open rule icon to open the rule form edit to create/edit the decision rule.
  • If no decision rule is configured, the KYC item is displayed editable by default. Configure a decision rule to make it read-only whenever required.
  • If a KYC Type’s read-only condition is set in the Type Definition tab, then its logic overrides the logic set at the KYC Item level.
• Supporting evidence – When configured this attribute will enable a link against the item for ‘supporting evidence’. When clicked the user will be presented with the supporting evidence screen from which they select evidence to support the item.

  Out-of-the-box, implementors can use the following three evidence types:

  • Customer documents (documents that have been attached to the case manually, or were already uploaded in earlier customer journeys).
  • Customer requirements (completed Requirement cases that are available for the party undergoing due diligence i.e. Contracting party, or related party).
  • Customer documents and requirements (this allows a multi-tabbed view of customer documents and the completed requirements for that party).
• Supporting evidence condition – This attribute is defined to conditionally associate supporting evidence for the items.
  • Several types of decision rules, including when, map value, decision tree, decision table rules are available to be selected. For ease of configuration, a condition of always is available, if the supporting evidence is always required.
  • Select the decision rule type available (when, map value, decision tree, decision table). Select an existing rule from autocomplete, or enter a rule name, and click the open rule icon to open the rule form edit, to create/edit the decision rule.
• On-Change launch data transform – When data transform rules are referenced in this field, the rule runs when the OnChange event for the KYC Item property is triggered. OnChange is triggered when the user clicks or tabs away from the Response Property field. This can be used to automatically change risk or set values of other KYC Items.
  • Use autocomplete to reference an existing data transform rule, or to create a new data transform rule enter a new rule name, and then click the open rule icon to open the new rule form editor.
  • For example, to update the risk of the customer on responding any questionnaire, a data transform rule can be configured on the item to update the risk.

• On-Change transition data transform– When data transform rules are referenced in this field, the rule runs after the evaluation of Items in the KYC type, in the case when the evaluation of items is performed due to an OnChange event for the KYC Item property is triggered. OnChange is triggered when the user clicks or tabs away from the Response Property field. This can be used to automatically change risk or set values of other KYC Items.

  • To create a new data transform rule, enter a new rule name, and then click Edit to open the New Rule Form editor.
  • To reference an existing data transform rule, use autocomplete to locate and select the rule.
• Audit note – Enter audit information when adding, deleting or updating KYC Items. This allows for change tracking and reporting across versions of KYC Types.

For more information, see Configuring KYC Item and KYC Item group actions.