Introduction to Consent Management

Processing personal data is generally prohibited, unless allowed by law, or the data subject has consented to the processing. Consent is one of the well-known legal basis for processing personal data under the Data Protection Regulation.

Consent must be freely given on voluntary basis and must be specific, informed and unambiguous. For consent to be informed and specific, the data subject must be notified of the following:

• Data to be processed
• Usage of data
• Purpose of the processing operations

The consent must be bound to one or several specified purposes. The data subjects must be informed of their rights to withdraw consent anytime. The withdrawal must be as easy as giving consent.

Temenos offers Consent Management as part of the Compliance and Regulation suite of products.

Consent Product Introduction

The consent management feature offers the following functionalities:

• Creating a new consent arrangement
• Amending a consent arrangement
• Closing a consent arrangement

The Consent Product line is built using the Arrangement Architecture (AA) framework and this section provides an overview of the construction of the consent product feature.

Property Classes

The AA.PRODUCT.LINE table provides a high-level definition of the business components (property classes) that may be required to construct a product belonging to that line.

The product lines are defined by Temenos and cannot be created by the user. A product line is described by the property classes which constitute it. A financial institution may use these ‘building blocks’ of functionality to construct the individual products which are available.

The above example for consent shows AA.PROPERTY.CLASS records that constitute a consent product. The minimum required classes are marked as Yes (mandatory) and optional classes are marked as No. The mandatory classes manage the minimum required components when creating a new product in the subsequent AA.PRODUCT.GROUP and AA.PRODUCT.DESIGNER records. However, a particular class may not be mandatory at a product line level. Mandatory classes can be defined in AA.PRODUCT.GROUP. This further controls the overall consolidated mandatory classes according to the product defined.

Product Builder

The application allows the user to construct banking products by combining different business components. PRODUCT.LINES provides functionality for different banking areas, which are licensed by Temenos. Each product line uses a number of property classes (business components) that can be fully configured.

The main features of the product builder are:

• Build families of products
• Inherit properties from the product family structure
• Determine the properties that a product comprises
• Control of default values to be applied for product arrangements
• Dated conditions for products
• Full control of scope of negotiation between product and arrangement conditions
• Control of negotiation of attributes over time
• Design or proof or publish lifecycle for product management

AA.ACTIVITY.CLASS records for Retail Consent

Each AA.ACTIVITY.CLASS record defines the list of actions applicable on the given list of property classes for a given process in the activity.

Temenos releases AA.ACTIVITY.CLASS records for product lines and its property classes for the arrangement.

When properties are linked to AA.PRODUCT.GROUP, the system generates the related AA.ACTIVITY records automatically. When the activity is triggered, the actions are determined by referring the AA.ACTIVITY.CLASS.

The following AA.ACTIVITY.CLASS records are released for the Consent product line:

• CONSENT–CLOSE–ARRANGEMENT
• CONSENT-NEW-ARRANGEMENT
• CONSENT–UPDATE–CDP.CONSENT
• CONSENT–UPDATE-OFFICERS
• CONSENT-VIEW-ARRANGEMENT

Every modification to the Consent Arrangement is considered as a change activity. This activity is effected on the date mentioned in the Effective Date of the activity.

Read the AA Product Builder user guide for more information on the product construction and configuration process.

Read the AA Property Classes user guide for more information on all Property Classes.

Illustrating Model Parameters

CK module records the status of a customer’s consent and allows a fully configurable set of consent types and sub types to be recorded within the system. Currently, consent is only used in relation to the Customer Data Protection (CZ) module.

Some of the key functionalities include:

• Creating a new consent arrangement
• Amending a consent arrangement
• Closing a consent arrangement

S.No.	Parameter	Description
1	CK.CONSENT.TYPE	This application captures different consent types for which the customer consent is sought. It contains the purposes for which consent is recorded and associated with the consent sub types. Records stored are mainly used for the purpose of Customer Data Protection processing.
2	CK.SUB.TYPE	The sub type of consent is the lower level of consent that a customer can give or retract. The sub types that are defined are allowed to be attached to the respective consent type. For example, Direct Marketing can be defined as a consent type, for which there could be many sub types such as Phone, Email, SMS or Post.
3	CK.PARAMETER	This is a table which is enabled with Automated workflow for Consent Creation and Consent Blocking. Also, it has the feature which will create the consent for Both customer and Prospect as well. When this feature is not enabled the consent creation and process will be carried out manually by the bank.

Illustrating Model Products

Model Products are not applicable for this module.