AML Watchlist Report

Our AML screening process cross-references the user's information against numerous global watchlists and sanctions databases. This comparison ensures compliance with regulatory requirements and helps identify potential risks. Below is a detailed explanation of the fields you can expect in an AML Watchlist Report.

Report Structure

The AML Watchlist Report returns a JSON object with a root-level aml object containing all screening results.

Core Response Fields

interface AMLScreeningResponse {
  aml: {
    status: 'Approved' | 'Rejected' | 'In Review' | 'Not Started';
    total_hits: number;
    score: number;  // Range: 0-100
    hits: Array<{
      id: string;
      match: boolean;
      score: number;  // Range: 0-1
      target: boolean;
      caption: string;
      datasets: string[];
      features: Record<string, number>;
      last_seen: string;
      first_seen: string;
      properties: {
        name: string[];
        topics: string[];
        country: string[];
        firstName: string[];
        sourceUrl: string[];
        fatherName: string[];
        motherName: string[];
      };
    }>;
  };
}

Response Fields

Status Fields

• status: Overall screening status indicating risk level
• total_hits: Number of potential matches found across all watchlists
• score: Overall risk score for the screening

Hit Details

• id: Unique identifier for the watchlist entry
• match: Boolean indicating if this is a confirmed match
• score: Similarity score for this specific hit (Range: 0-1)
• target: Boolean indicating if this hit matches the primary search target
• caption: Name or identifier of the matched entity
• datasets: List of watchlists where the match was found
• features: Detailed matching criteria and their scores
• properties: Additional information about the matched entity

Sample Response

{
  "aml": {
    "status": "In Review",
    "total_hits": 1,
    "hits": [
      {
        "id": "cl-info-probidad-3fd0f04facc53bd94ebec9aaedf56d18",
        "match": false,
        "score": 0.4,
        "target": true,
        "caption": "PABLO ALFONSO ESCOBAR NAVARRO",
        "datasets": ["cl_info_probidad"],
        "features": {
          "country_mismatch": 1.0,
          "person_name_phonetic_match": 0.67
        },
        "last_seen": "2024-10-28T02:50:03",
        "first_seen": "2024-01-17T02:50:01",
        "properties": {
          "name": ["PABLO ALFONSO ESCOBAR NAVARRO"],
          "topics": ["role.pep"],
          "country": ["cl"]
        }
      }
    ],
    "score": 40.0
  }
}

Understanding the Results

Status

• "Approved" indicates no significant matches were found
• "Rejected" suggests a high-confidence match with a sanctioned individual
• "In Review" indicates potential matches requiring further investigation
• "Not Started" indicates that the screening has not been performed yet

Score

• Ranges from 0 to 100, with higher scores indicating greater risk
• A score of 40.0 (as in the example) suggests moderate risk
• Thresholds can be customized based on your risk tolerance

Hit Features

• country_mismatch: Indicates geographical discrepancy (1.0 = complete mismatch)
• person_name_phonetic_match: Similarity of name pronunciation (0.67 = moderate match)

Properties

• Contains detailed information about the matched entity
• May include full name, country, roles, and source references
• Useful for manual review and enhanced due diligence

Customizing Risk Thresholds

You can customize the risk thresholds in your verification settings to control when an AML screening should be:

• Automatically approved (low risk)
• Sent for manual review
• Automatically declined (high risk)

For example:

• Score < 30: Automatic approval
• Score 30-70: Manual review
• Score > 70: Automatic decline

These thresholds can be adjusted based on your risk tolerance and compliance requirements.

Compliance Considerations

• Results should be reviewed by trained compliance personnel
• Document review decisions and reasoning
• Maintain audit trails of screening activities