Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Configuring the Applicability Matrix mechanism

Updated on June 11, 2021

The KYC Applicability Matrix includes the following three key data elements to determine the applicability of the KYC types that Pega Know Your Customer Regulatory Compliance provides: the customer type, the AML DD profile, and the customer risk. In addition, the locators are used as an intelligent way to logically group the KYC types into categories and subcategories and drive their applicability on the cases created under each orchestration mode. For more information, see Configuring Locators in KYC Engine.

The locators have two key attributes: Purpose and Key. The Purpose is presented as the category, and the Key is analogous to the subcategories. The following table includes some examples of locators that are used in Pega Client Lifecycle Management and KYC.

KYC Type/Due DiligencePurposeKey
AML GlobalAMLGlobal
AML USAMLUS
AML SpainAMLSP
AML UEAMLEU
AML IndiaAMLIN
Regulatory USRegUS
Regulatory EURegEU
Tax FATCATaxFATCA
Tax CRSTaxCRS

When the application creates a due diligence case, it initializes the locators that determine the KYC Types managed by that case (DDPurpose and DDKey properties). These locators are compared against those provided in the KYC Applicability Matrix to display the appropriate KYC questionnaires to the case.

The data transform GetKYCTypeLocators programmatically populate the initialization of the locators at the case. In Pega Client Lifecycle Management and KYC, each case type has a copy of this data transform, which uses the due diligence orchestration mode configuration to set the right locators. For example, for a customer onboarded in Australia with products in the United States and Spain, the values for the locators set on the cases under each of the case orchestration modes are shown in the following tables.

Standard mode

Case TypePurposeKey
Global KYC/AMLAML

Global

EU

US Local AMLAMLUS
AU Local AMLAMLAU
SP Local AMLAMLSP
US RegulatoryRegUS
UE RegulatoryRegEU
FATCATaxFATCA
CRSTaxCRS
RegulatoryNot applicableNot applicable
TAXNot applicableNot applicable

Intermediate mode

Case TypePurposeKey
Global KYC/AMLAML

Global

US

AU

SP

EU

US Local AMLNot applicableNot applicable
AU Local AMLNot applicableNot applicable
SP Local AMLNot applicableNot applicable
US RegulatoryNot applicableNot applicable
UE RegulatoryNot applicableNot applicable
FATCANot applicableNot applicable
CRSNot applicableNot applicable
RegulatoryREG

US

EU

TAXTAX

FATCA

CRS

Simplified mode

Case TypePurposeKey
Global KYC/AMLAML

Global

US

AU

SP

EU

REG

US

EU

TAX

FATCA

CRS

US Local AMLNot applicableNot applicable
AU Local AMLNot applicableNot applicable
SP Local AMLNot applicableNot applicable
US RegulatoryNot applicableNot applicable
UE RegulatoryNot applicableNot applicable
FATCANot applicableNot applicable
CRSNot applicableNot applicable
RegulatoryREGNot applicable
TAXTAXNot applicable

In the intermediate mode, a single Global KYC/AML case is created to address all the global, regional and local regulations. Thus, while setting the DDPurpose and DDKey on the case, all the keys that apply to the customer under the AML category are set in the Global KYC/AML case itself, thereby driving the applicability of the corresponding KYC Types. The same is for the simplified mode where all the relevant purposes and keys are populated on the single Global KYC/AML case that is created to cover all the due diligence categories and subcategories.

You can update the applicability of the KYC types provided with Pega Know Your Customer Regulatory Compliance or configure the applicability of your custom KYC types by copying and updating the KYCApplicabilityMatrix decision table and the GetKYCTypeLocators data transform in your implementation layer classes. Or you can also configure even Standard Filtering applicability. However, use the KYC Applicability Matrix to configure the applicability without overriding the KYC Types, unlike the Standard Filtering applicability.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us