The 'Rule Engine' Module is there to serve one specific purpose to the compliance team, and that is to specifically zone into events, scenarios, that are of concern to the Subject Person / Obliged Entity - doing away with False Positives and False Negatives and purely alerts the compliance team when there is something of concern that needs seeing to.
Selecting the 'Rules & Criteria' menu item shall direct the user a screen similar to the figure shown above (provided that the current logged in user has the appropriate privileges to access the module). Using this module, the compliance user, or typically, the MLRO would be able to create bespoke rules based on any internal business process they subject person / obliged entity follow.
For ease of reference, the Rule Engine is also segregated between the four risk factor pillars, solely to provide the compliance user with the ability to segregate the rules being created throughout the different risk factor pillars. Nevertheless, irrelevant on where the rule resides throughout the four risk factor pillars, the process and end result will be the same.
Throughout the different tabs as shown in the figure above, each tab would have a table providing a list of rules that currently reside within the solution (which had been created previously.
From the list, as an MLRO user, you may perform a variety of functions and would need to understand a variety of information. Starting from the top, working our way down towards the table list:
When an MLRO would have access (therefore typically be the MLRO on multiple companies or licenses) to more than one environment / integration, the MLRO user would be able to alter the environment by selecting the integration dropdown. Selecting another integration shall load the rules which are specific and which had been created for that specific chosen environment.
Selecting this button shall direct the MLRO user to the creation of a rule page which is explained in detail in the 'Creating & Defining a Rule' section of this user manual.
The Rule Engine within KYCMATIC works in a sequential manner - executing rules sequentially one after another. It therefore would make more business sense having the more important rules on top, thus being executed before lesser important rules which would be further below within the list.
MLRO users are therefore able to change the order of the Rule Engine list by selecting the 'Up' or 'Down' arrow which are found to the left of the Rule name. These arrows would only be shown on screen provided that there is more than one rule within the list.
As rules are created, the MLRO user would be required to state to KYCMATIC when the rule is to be invoked. For example, if the rule being created is checking based on customer data, then the rule should be executed when customer's information has been added or altered.
Alternatively, if for a example a rule being created is to check a deposit threshold (such as the €2K threshold for Remote Gaming Operators under the MGA license), then the rule should be executed when a deposit event takes place from the customer / player.
The same rational would apply for other types of rules being created. This column within the list shall therefore aid the MLRO user in understanding when the Rule is to be invoked.
The remaining list of columns shall provide further information on the rule such as:
No. of Conditions: A rule may be made up of 1 or 'n' conditions. Ideally, a rule is kept as simple as possible - therefore the lesser the amount of conditions, the better. This is solely to keep a maintainable and sustainable practise when creating rules.
Active: Defining whether the rule is in use or not.
Last Updated Date: Providing information on when the rule was last updated.
Last Updated By: Providing information on who had last updated the rule - by which user.
Selecting the 'Eye' icon shall direct the MLRO user to the rule in view mode as shown below, which shall describe the rule and provide an explanation on what the rule is aiming to capture as well as what the outcome of the rule would be if the rule had to be invoked.
Selecting the 'Pencil' icon shall direct the MLRO user to a screen similar to the Add Rule screen which would have the details of the rule pre-populated.
More information is explained in detail in the 'Creating & Defining a Rule' section of this user manual.
Selecting the 'Copy' icon shall direct the MLRO user to the Add Rule Screen with the selected rule information pre-populated (similar to that of the Edit), yet with the exception that the MLRO user may save the rule under a different name and may alter it slightly.
This feature would typically come in handy when the MLRO user would need to create a similar rule to one already created, yet having slight changes. Therefore, rather from starting from scratch, the MLRO user would be able to use this feature to copy most of the rule information, amend the name and the criteria and save it as a new rule.
The 'Bin' icon would be available from the table towards the far right of the rule. Selecting this icon shall provide a pop-ip to the user asking for confirmation to delete the rule.