AML Statuses

Integrations guide

This page sets out possible statuses and explanatory status codes for AML Screening & Monitoring.

• No risk code is generated for AML Screening & Monitoring.
• To confirm potential hits or rule them out as false positives, you must have AML Investigation configured.


Possible statuses include:

scheduledScreening only: The clientId exists and screening is pending.Wait.
doNotExistScreening only: The clientId wasn't found.Ensure you have created a client profile for this client or check the clientId is correct.
recentlyScreenedScreening and monitoring: The client has already been screened/monitored today.Try again tomorrow.
wrongMonitoringTypeScreening only: You made a Start screening request for a monitoring client.Update the client's profile, setting monitoringType to 1 and re-start screening.
otherScreening and monitoring: A system error occurred.Try again.
screeningInProgressScreening only: Screening is in progress.Wait.
manualReviewRequiredScreening and monitoring: We found a potential hit that requires AML Investigation.Wait.
pendingManualReviewScreening and monitoring: Investigation is in progress.Wait.
completedScreening and monitoring: Screening/monitoring is completed.
If we found hits, check the status code for more information.
If there are confirmed hits, download the Confirmed Hit Report.

Status flow diagram

The status pathway is as follows:

AML Screening & Monitoring

AML Screening & Monitoring

Status codes

Statuses can be accompanied by one or multiple of the following status codes:

Status codeDescription
100False positive sanctions or adverse media hit
110False positive PEP hit
120Confirmed PEP hit
140Potential sanctions or adverse media hit
141Potential PEP hit
4110Confirmed sanctions or adverse media hit
4112Confirmed sensitivity list hit
4160More hits than agreed threshold

Top of page