How does the Alerts section work? AML

With Pirani you will be able to create alerts of unusual operations that may occur in your organization and make an investigation process to determine if it became a suspicious operation.

The suspicious transactions module is transformed into two new modules, "Risk Factors" and "Alerts," so that you can document all the entities involved in unusual transactions and monitor alerts according to the methodology and regulations of the organization.

→ Remember that you will be able to have this module from the Starter plan ⚡.

The "Alerts" section frames more monitoring features than the previous module of suspicious transactions, as it allows you to register unusual transactions in a specialized section, follow up on all the company's operations, and associate the transactions with the related risk factors.

How to create alerts? 

To create alerts, go to the menu on the left side and click on the "alerts" option; here, you can create and review previously created alerts. When you click on Create alert, you will find a pop-up window with two main sections:

• General information: In this section, you must fill in the primary data of the operation you will report:

  - Report name: what is the name of the operation?

  - Means of detection of report:  you will get a list of options based on what the UIA indicates.

  - Transaction Value: determines the amount of the transaction being reported.

  - Currency: determines the currency of the amount being reported.

  - Transaction Type: selects whether the transaction is domestic or international.

  - Responsible: determines who will be responsible for this operation, as it is confidential information; in this module, we will not have groups responsible for the records, but only one person can be in charge of each suspicious operation.

  - Period analyzed: Select the dates from and until they will be analyzed.

  - Description of operation: Could you provide details of what the report of this operation consists of?

  - Attach evidence: You will have the option to attach evidence that will help strengthen the report.

2.   Persons / Entities

In this section, you can associate the customers, counterparties, and users involved in the operation.

• Customers: Persons or entities that have a commercial contract with the organization.

• Counterparty: Entities with a contract different from the commercial one; these can be suppliers, partners, or investors, among others.

• User: a person involved in the operation but does not have a direct link.

  To relate the entities, click the "Associate" option, and the three association options will be displayed.

After choosing which entity you are going to associate the tool will show you the entities that you have created in the customers and counterparties section previously, to select which entity to associate you must click on the "+" icon located on the right side of the entity's name. You can also add new customers and counterparties, and the tool will take you to that section, saving the alert information in the creation process.

⚡ "Users" must be created directly in this section, 

After associating, you must click on "back". Now, you can indicate the link each entity has with the alert; this type of relationship can be linked central or associated.

Finally, you must click on the "create" button and monitor them in the alerts module.

Now, by selecting the customer, you can view all the detailed data about him and the entities related to the selected customer.

Now, when you select a customer, you will be able to view all the detailed data about him and the related entities, such as:

- Alerts generated
- List queries 
- General information 
- Scoring 
- Segment

Transactional analysis

Access the alerts module, designed to automatically manage the alerts generated by the rules engine you have configured. To adjust it, click on the gear icon at the top of the screen. This will open a pop-up window where you must select “AML” and then click on “Import”.

To load the information, select the entity you are going to work with, either “Customers” or “Counterparties”.

Now you can upload the files you want to upload.

Remember that there are two ways to upload files:

From file: Upload a .csv file directly from your device.

Existing records in the system: Records already stored in the software will be used, where the unique codes will correspond to Pirani (e.g. ORM-1). Make sure to select them correctly for proper association.

Once the files are loaded, click “Next” to continue.

When you click “Next”, the system will take you to the Clients section, where the information to be uploaded will be mapped, identifying the columns of the previously uploaded file. Once completed, click “Upload” to continue.

🔹 Note: File upload may take 5 to 10 minutes.

When the documentation is uploaded, go to the Alerts section, locate the created alert and click on it. A pop-up window will then appear on the right side of your screen, where you will need to click on the pencil icon.

Then, you will find the Transactional Analysis section, where you will be able to view the conditions of the configured alerts.

This allows the analyst to determine whether the condition was met or not.

For example, if a condition states that the number of transactions in the last four months must be greater than 200, the system will display the actual value analyzed, allowing the analyst to evaluate whether the alert was triggered correctly.

If the actual value is less than 200, the condition is not met, but the information is still visible for the analyst to perform his analysis.

Evaluation of transactions and products

The system allows you to review transactions and products analyzed within a specific date range:

• Number of transactions: The transactions evaluated for the customer in question are displayed.
• Number of products: List of products that were analyzed.
  Clicking on “View transactions” displays a table with the details of the evaluated transactions, which facilitates the analysis of the customer's behavior.

Validation of conditions by the analyst

Each condition configured in the rule is analyzed based on actual data. For example, if a rule states that the average value of transactions in the last four months must be greater than 23 million, the system will display:

Condition set: Average greater than 23 million.
Actual value analyzed: Example: 50 million 9 thousand 352 with 37.

The analyst must review this information and validate if the alert was generated correctly according to the parameterized criteria.

How to associate alerts?

You can associate the alert with processes, risks, controls, and risk factors that you have within the tool. For any of these options go to the section of interest and click on the "associate" button, there you will find the registers that you can link to the alert, click on the "+" icon to make the association effective.

What can be filtered?

You can filter your alerts by:

• Date of register: When was the suspicious operation reported in the tool?

• The type of alert: whether it is unusual or suspicious.

• Quick search: filter by name or code.

✨ Try the Alerts module now! ✨

Discover how to empower the monitoring of unusual operations and streamline your investigations. Connect each alert to risk factors efficiently and comply with your organization's regulations.