Practical guide
What is AML screening? Scope, checks, and review workflows
Learn where sanctions and watchlist screening fit into AML, what the checks can establish, and which identity, ownership, and transaction controls remain separate.
On this page
AML screening is one part of a wider program
AML means anti-money laundering. In software, “AML screening” commonly refers to checks against sanctions, politically exposed person information, and other selected risk sources. The exact package varies, so the label should never substitute for a coverage specification.
AML programs can include policies, training, responsible personnel, independent review, and activity-related controls. FinCEN’s customer due diligence material also distinguishes customer identification, beneficial ownership, relationship understanding, and ongoing due diligence for covered institutions.
Separate four different questions
Identity verification asks whether the customer is who they claim to be. Sanctions screening asks whether submitted information resembles a party on selected lists. PEP screening concerns a defined public-function category. Transaction monitoring examines behavior or activity. These may share a customer ID while requiring different evidence and actions.
A system can support one of these controls without delivering all four. SanctionsKit supports selected-source screening, review, and monitoring. It should not be treated as a complete identity-verification, PEP, adverse-media, or transaction-monitoring service.
Use a coverage matrix instead of a broad promise
For each required check, identify the source, jurisdiction, purpose, entity types, update handling, and responsible reviewer. Explain whether it is supported in the application, handled by another provider, or outside the current process.
This makes procurement and control testing more useful. A vendor’s “AML compliant” badge does not tell you whether the necessary source is available or whether a failed check stops the workflow.
- Sanctions: preserve list and program context with each candidate.
- PEP: apply the relevant definition and risk-based process, not a sanctions decision.
- Other watchlists: identify the particular restriction or informational purpose.
- Activity review: keep transaction analysis and reporting decisions in their authorized workflow.
Design a review path for possible matches
A possible match is not an allegation of money laundering. Compare identity details before attaching a source fact to the customer. Preserve the original result and record why the evidence supports, conflicts with, or leaves the comparison unresolved.
In an invented onboarding case, the customer shares a name with a source record but no comparable birth date or identifier is available. The outcome remains unresolved until the evidence standard is met. It is not “low risk” merely because the software returned only one candidate.
Connect screening to ongoing customer review
A customer’s details and source records can change after onboarding. Decide which changes require new screening and who reviews the resulting alerts. Updating the customer’s name in a CRM without updating the monitored subject can leave the controls out of alignment.
Ongoing sanctions monitoring rescreens retained subjects against selected coverage. It does not analyze customer spending patterns or replace the institution’s broader ongoing due diligence.
What to ask an AML screening provider
Ask for the exact source catalog, unavailable-source behavior, match explanations, retained evidence, reviewer controls, and monitoring cadence. Test the workflow with missing dates, common names, changed identifiers, and failures.
The AML software evaluation guide turns these questions into a buying checklist. Choose controls for the actual obligations and operating model, with appropriate legal and compliance review.