Skip to main content
The Risk Score is a quantitative assessment that evaluates how risky an AML hit entity is. This score is used to determine the final AML status (Approved/In Review/Declined) based on the highest risk score among all non-false-positive hits.
โš ๏ธ Important: The Risk Score determines the final AML status, NOT individual hit classification. Individual hits are first classified as False Positive vs Unreviewed using the Match Score.

Overview

Each AML hit receives a risk score from 0-100, calculated by combining three key risk factors. This score answers the question: โ€œIf this is a true match, how risky is this entity?โ€

Risk Score vs Match Score


How Risk Score Determines Final AML Status

The final AML status is determined by the highest risk score among all hits that are NOT classified as False Positive:
Default thresholds:
  • Approve Threshold: 80
  • Review Threshold: 100
Example: With default thresholds:
  • Highest risk score = 50 โ†’ Approved (low risk)
  • Highest risk score = 90 โ†’ In Review (medium risk, needs manual review)
  • Highest risk score = 101 (impossible, but >100) โ†’ Declined (high risk)

Risk Score Formula

The overall risk score is calculated using a weighted average:

Risk Levels

Based on the calculated risk score, entities are classified into three risk tiers:

Component Scoring Details

Country Score (30% Weight)

The country score reflects the inherent AML/CFT risk associated with a jurisdiction. Factors include:
  • Money laundering and terrorist financing risks
  • Compliance with FATF recommendations
  • Presence of international sanctions
  • Corruption perception indices
  • Regulatory framework strength
Scoring Range: 0-100 (higher = more risk)
Note: When a hit is associated with multiple countries, the highest country score is used in the calculation.

Country Risk Scores

233 countries ยท Risk scores based on AML/CFT factors


Category Score (50% Weight)

The category score reflects the inherent risk level based on the type of watchlist the entity appears on. This is the most heavily weighted component because the listing type directly indicates regulatory and compliance risk.
Note: When a hit belongs to multiple categories, the highest category score is used.

Category Risk Tiers


Criminal Records Score (20% Weight)

The criminal records component evaluates any criminal history associated with the entity.
Note: Criminal records carry significant weight despite the 20% allocation because a conviction can dramatically change the risk profile of an entity.

Configuration Options

Risk Score Thresholds (Determine Final AML Status)

Match Score Threshold (Determine Hit Classification)


Complete Flow: From Screening to Final Status


Calculation Examples

Example 1: High-Risk PEP from Sanctioned Country

Hit Data:
  • Country: Iran (Score: 81.66)
  • Category: Sanctions (Score: 100)
  • Criminal Records: None (Score: 0)
Risk Score Calculation:
Result: Risk Score 74.50 โ†’ Entity Risk Level: High ๐Ÿ”ด
  • If this is the highest risk score among unreviewed hits and thresholds are default (86/100):
  • 74.50 < 86 โ†’ Final AML Status: Approved (entity is risky but below review threshold)

Example 2: PEP Level 1 from High-Risk Country

Hit Data:
  • Country: Russia (Score: 71.25)
  • Category: PEP Level 1 (Score: 100)
  • Criminal Records: Convicted by court (Score: 100)
Risk Score Calculation:
Result: Risk Score 91.38 โ†’ Entity Risk Level: High ๐Ÿ”ด
  • With default thresholds (86/100): 86 โ‰ค 91.38 โ‰ค 100 โ†’ Final AML Status: In Review

Example 3: Low-Risk Business Entity

Hit Data:
  • Country: United Kingdom (Score: 24.79)
  • Category: Business (Score: 40)
  • Criminal Records: None (Score: 0)
Risk Score Calculation:
Result: Risk Score 27.44 โ†’ Entity Risk Level: Low ๐ŸŸข
  • With default thresholds (86/100): 27.44 < 86 โ†’ Final AML Status: Approved

API Response Example

Each hit in the AML response includes both scores:
The overall AML result includes the final status based on the highest risk score:
In this example:
  • Hit 2 is a False Positive (match_score 88 < threshold 93), so itโ€™s excluded
  • The highest risk_score among unreviewed hits is 91 (from Hit 1)
  • 86 โ‰ค 91 โ‰ค 100 โ†’ Final status: In Review

Managing Hit Review Status

You can manually update each hitโ€™s review status after the initial classification:

Tip: Update hit review status in the Console by navigating to the AML overview or clicking on a specific hitโ€™s details.


Best Practices

  1. Understand the two-score system โ€” Match score filters false positives; risk score determines urgency.
  2. Review high-risk hits first โ€” Use risk score to prioritize your compliance teamโ€™s workload among unreviewed hits.
  3. Adjust thresholds based on your risk appetite:
    • Lower Match Score Threshold โ†’ More hits considered as unreviewed
    • Lower Approve Threshold โ†’ More sessions auto-approved
    • Lower Review Threshold โ†’ More sessions auto-declined
  4. Document your decisions โ€” When manually reviewing hits, record why you approved or escalated based on both match confidence and risk factors.
  5. Monitor trends โ€” Track your organizationโ€™s hit distribution by both match score and risk level to identify patterns.