1. Introduction to Risk Classes

Risk classes allow organizations to systematically categorize entities based on their risk level related to money laundering and terrorist financing (ML/TF). By defining risk classes in the Pingwire system, users can implement risk-based approaches to compliance and fraud prevention.

1.1 Purpose of Risk Classes

Risk classes help organizations:

• Categorize Risks: Group entities into different risk levels for better risk assessment.
• Align with Business-Wide Risk Assessment (BWRA): Ensure that the system's risk distribution is consistent with the organization's BWRA framework.
• Enable Risk-Based Procedures: Facilitate automated decision-making, reviews, and additional due diligence based on an entity's assigned risk level.

2. Defining Risk Classes in Pingwire

Users can create and manage risk classes through the Pingwire interface by following these steps:

2.1 Naming the Risk Class

Each risk class must have a unique name that makes it easy to identify.

• Example: Low Risk, Medium Risk, High Risk, Critical Risk.

2.2 Setting Score Intervals

Risk classes are defined based on score intervals (0-100 scale). Users can set a minimum and maximum score range for each class.

Example:

• Low Risk: 0-30
• Medium Risk: 30-60
• High Risk: 60-90
• Critical Risk: 90-100

Note that intervals must be defined so that every possible probability (including decimals) is assigned to a risk class, and when a value falls on a boundary (e.g., 25 in the ranges 0–25 and 25–50), it is assigned to the higher class.

3. Risk Class Management Features

The Pingwire system allows users to create, retrieve, update, and delete risk classes to keep risk classification aligned with evolving compliance policies.

3.1 Retrieving an Existing Risk Class

Users can fetch an existing risk class using its unique identifier.

• Required Parameter: id (ObjectId)
• Response Data:
  • id: Unique identifier for the risk class.
  • name: Risk class name.
  • min: Minimum score threshold.
  • max: Maximum score threshold.
  • createdAt: Date the risk class was created.

3.2 Creating a New Risk Class

To create a risk class, users must provide:

• Name (String, must be unique)
• Minimum Score (Integer, 0-100)
• Maximum Score (Integer, 0-100)

Example:

Name: "Moderate Risk"
Min Score: 40
Max Score: 70

Upon creation, the system will generate a unique ID and timestamp.

3.3 Updating an Existing Risk Class

Users can modify risk classes to update the name or adjust score intervals.

• Updates should maintain a logical order (e.g., Low Risk should not have a higher score range than High Risk).

3.4 Deleting a Risk Class

Users can remove risk classes that are no longer relevant. This action is irreversible.

4. Benefits of Risk Classes in Compliance

By utilizing risk classes, organizations can:

• Automate Decision-Making: Assign different review procedures based on risk classification.
• Improve Monitoring Efficiency: Focus resources on higher-risk entities.
• Ensure Regulatory Compliance: Maintain alignment with risk-based approaches required by compliance frameworks.

5. Summary

Risk classes in Pingwire provide a structured approach to ML/TF risk categorization. By defining clear risk categories and score ranges, organizations can enhance risk assessment accuracy and ensure proactive compliance measures.