AML profile calculation
The system performs the profile calculation during the synchronization of the Master Profile. The system reacts dynamically to any changes in the data that might trigger changes in the AML profile, for example, a change in risk. The value is based on risk, but you can consider the other variables.
For example, the orchestration engine automatically ensures that the appropriate level of due diligence is carried out using eScreening results and the current customer risk assessment. The logic is fully configurable to meet your business needs.
The AMLCDDProfilesSynchronization data transform invokes the logic, which provides access to a set of decision tables that manage distinct scenarios. As different business scenarios require different data, there is a corresponding set of data transforms to ensure that all data is available at the time of execution. The application provides the following decision tables:
|Contracting party – Individual
|Contracting party – Organization
|Contracting party – Fund
|Related party – Individual
|Related party – Organization
|Related party – Fund
If there are changes required in the logic to calculate the AML profiles (for example, a new data variable is required, or the values are different), you can overwrite the rules and implement the necessary logic.
In addition, if you need to use another variable instead of using the type of party to categorize the logic across multiple tables, you overwrite the AMLCDDProfilePartyRouter decision table.
KYC due diligence profile
The Pega Know Your Customer Regulatory Compliance application is the source of regulatory intelligence for Pega Client Lifecycle Management for Financial Services and contains KYC types configured to manage the same AML profiles that Pega Client Lifecycle Management for Financial Services does (CPSDD, RPSDD, and so on).
The system configures the AML profiles by using a new KYC Due Diligence Profile Suite rule type that is create in the Pega Know Your Customer for Financial Services application. All profiles are recorded under an instance of the Default rule and placed under the PegaKYC-Data-Type-Policies-Global rule type.
Although the AML profiles represent the same business scenarios, the profiles under the PegaKYC-Data-Type-Policies-Global rule have different codes than those that the Pega Client Lifecycle Management for Financial Services gives. The mapping between the Pega Client Lifecycle Management for Financial Services AML profiles and the Pega Know Your Customer Regulatory Compliance AML profiles is done in the PegaFS-Work.DDProfilesMap decision table. To change the mapping, either because you changed the AML profiles in the Pega Client Lifecycle Management for Financial Services layer or in the Pega Know Your Customer for Financial Services layer, overwrite this extension point.