Configure AML Screening

Global vs. Level Settings

AML screening parameters follow a Global-first, Level-override model:

By default, every Level inherits the Global configuration — no per-Level setup is needed. When a Level needs different screening parameters, enable the Use Custom toggle to override Global values for that Level only.

Key principle: Configure once at the Global level, customize only where needed. This keeps your screening policy consistent and reduces maintenance overhead.

How Configuration Resolves at Runtime

When a screening request is submitted against a Level, the system determines the effective configuration using the following logic:

1. If the Level has Use Custom AML Screening Settings enabled → the Level's own AML configuration is used.
2. If the toggle is off (default) → the Global AML Settings are used.
3. Any field left blank in the selected source → falls back to system defaults (see table below).
4. List Screening (listSwitch, listList) is always read from the Level — it is a Level-only feature that does not exist in Global Settings.

Global AML Settings

Navigate to Configuration > Global Settings > AML Screening to configure the account-wide AML defaults.

Global AML Settings always show the full configuration editor. The "Use Custom" toggle does not appear here — it is only relevant at the Level.

The Global AML Settings page includes:

• Search Configuration (Name Matching, Warning Types, PEP Level)
• Ongoing Monitoring / Re-screening
• AML Input Mapping

Changes saved here take effect immediately for all Levels that follow Global settings.

---

Level AML Settings

Navigate to Configuration > Levels > [select a Level] > AML Step to view or customize the AML configuration for a specific Level.

Use Custom AML Screening Settings

At the top of the Level's AML configuration, a toggle controls whether this Level uses its own settings or follows Global:

When you turn the toggle off after having customized settings, the system clears all Level-side AML configuration — only { useCustomLevelSettings: false } is persisted. Your custom values are not retained; if you re-enable the toggle later, defaults are restored.

Confirmation safeguard: When editing an existing Level and switching from Custom back to Follow Global, a confirmation dialog appears before the change takes effect.

Level-Only Features

The following features are configured exclusively at the Level and are not available in Global Settings:

• List Screening — screen against your own custom watchlists

These Level-only fields are always read from the Level regardless of the Use Custom toggle state.

---

Search Configuration

Name Matching

Controls the minimum similarity score required for a screening result to be considered a match. Availability depends on your configured data source.

Default: Exact or Nearly Exact (94).

Warning Types

Select which risk categories to screen against. Matches belonging to categories not in your selection are automatically filtered out at the screening stage — they will not appear in Case Review.

Default: All categories selected.

Validation: At least one warning type must be selected.

PEP linkage: If the PEP category is deselected, the PEP Level setting below is automatically disabled and its value cleared.

Warning Types filtering applies to all supported data sources. The filtering is performed during screening result processing — matches whose risk categories do not intersect with your configured warning types are excluded before they enter Case Review.

PEP Level

Controls the depth of Politically Exposed Person screening. A lower level number captures higher-risk, more prominent political figures; higher levels progressively include lower-profile positions. Availability depends on your configured data source.

Default: Level 1.

---

How It Works

When enabled, the system compares the following fields between your screening input and each matched entity:

Note: Date of Birth is intentionally excluded from secondary field filtering. DOB differences often occur due to data quality issues and would cause excessive false negatives if used as an automatic filter.

When a mismatch is detected (e.g., screening subject is Male but matched entity is Female), the match is automatically excluded from the screening results. This filtering is applied consistently across all supported data sources.

---

Ongoing Monitoring / Re-screening

Configure how the system handles periodic review of screened profiles.

Ongoing Monitoring Options

When Ongoing Monitoring is selected:

• Auto Renew: When enabled, the 365-day monitoring period is automatically renewed upon expiry. Default: Enabled (when first switching to Ongoing Monitoring mode).

Re-screening Options

When Re-screening is selected:

• Re-screening Interval: Number of days between periodic re-screens (1–365). Default: 1 day.

---

AML Input Mapping

Map metadata fields from your Application data to AML screening input parameters. This allows you to enrich screening requests with additional identity attributes stored in your application metadata.

Each mapping consists of:

• Maximum 20 mappings per configuration.
• Both Source Key and AML Input Value are required for each mapping row.
• Mappings are available in both Global and Level AML settings.

---

List Screening

Level-only feature — List Screening is configured exclusively at the Level and does not appear in Global AML Settings. It is always read from the Level regardless of the Use Custom toggle state.

List Screening allows you to screen applicants against your own custom watchlists (sanctions lists, internal risk lists, etc.) in addition to standard AML screening.

Enable List Screening

1. Navigate to Configuration > Levels > [select Level] > AML Step.
2. Scroll to the Scan List section at the bottom.
3. Toggle the switch to enable List Screening.
4. Add one or more lists from the dropdown (up to 10 lists per Level).

Configure Lists

• Each list can only be selected once per Level.
• The dropdown only shows active watchlists from your account.
• You cannot disable the Scan List toggle while list entries still exist — remove all entries first.

How List Hits Appear in Case Review

When List Screening produces a hit:

• The Alert's Check Type is displayed as "List" (distinct from standard AML screening hits).
• Each Match card shows a List Type tag identifying the source list.
• The Comparison View displays List-specific fields: First Name, Middle Name, Last Name (or full Name), Date of Birth, Gender, Nationality, ID Number, Country of Location, Status, and Source.
• Multiple Positive matches are allowed per List Alert (unlike AML Alerts which allow at most one Positive).
• Confirmed list hits (Positive matches) are written to the Profile's metadata as list-hit markers, available for downstream consumption by other Steps (e.g., ScoreCard).

---

Filter Pipeline Summary

When AML screening results are returned from the data source, the system applies four filter rules in a fixed order before matches enter Case Review:

All enabled filters evaluate every match independently — there is no short-circuit. A match must pass all active filters to appear in Case Review.