Creating & Defining a Rule

Selecting the 'Add Rule' (or performing an Edit on a rule) from the 'Rule Engine Module' shall direct the MLRO user to a screen similar to that of the figure below. 

When creating a new rule, the MLRO user would be required to enter a:

• Rule Name: This would be typically a name that can aid any user quickly identify what the rule is earmarked to achieve.

• Code: A code is given to the rule to uniquely provide a reference to the rule. Ideally, a naming convention is created to create a standard on how rules are coded. Example; If the rule is under the Customer Risk Factor, the code may start with 'CRF_' followed by the initials or first 3 letters f the name such as 'CRF_NAT' for a nationality rule which is under the customer risk factor.

• Integration: This is set to read only yet being exposed to clearly provide visibility to the MLRO user where the rule is being created.

• Description: This area shall be used to enable the MLRO user clearly describe what the rule is set out to achieve and how. The more information on the rational / methodology of the rule that is entered shall simply provide more value later on down the line when the rule is to be maintained, altered or even more, explained to other stakeholders.

• Trigger Events: As explained in the 'Rule Engine Module', the MLRO user is required to select the Trigger Events for KYCMATIC to identify when the rule is to be triggered, such as when customer information has been created / updated or when a certain event, such as a deposit event would have taken place.

Example Rule

When a rule is triggered, their are a variety of outcomes that may occur. A dedicated explanation on this is defined in the 'Outcome of a Triggered Rule' section of this user manual.