AML screening software

Keep AML screening connected to the evidence.

Screen selected customers and counterparties, investigate possible sanctions matches, and retain the reasoning behind your team’s decisions. Use the API and dashboard as one screening workflow.

API and compliance dashboard included in every plan.

SanctionsKitIllustrative workflow

Potential match

Your subject

Names & aliases

Available identifiers

Dates & locations

Source record

Names & aliases

Available identifiers

Dates & locations

Compare supporting facts and conflicts.

Record the evidence behind your decision.

Open Confirm or dismiss with a note
Compare the identity before deciding

What this helps your team do

Connect the check to the evidence and the next decision.

Define what the check covers

Select supported sources or an approved versioned package. Preserve the source scope and versions behind the result instead of describing a limited check as a complete AML assessment.

Make the next review step clear

Potential matches can enter the shared review queue. Compare reliable identity facts, record per-candidate conclusions, and apply required independent approval before the separate business action.

Retain the actual decision history

Keep submitted details, source evidence, notes, supported external-document references, and review activity connected. Original externally referenced document bytes remain in the approved external repository.

A practical use case

Map the customer control

SanctionsKit supports sanctions and selected watchlist screening within a broader AML process. It does not verify identity documents, analyze transaction patterns, assign a complete customer-risk rating, or file regulatory reports.

  1. 01

    Map the customer control

    Identify the subject, screening purpose, required sources, and the other controls that remain outside sanctions matching.

  2. 02

    Screen and investigate

    Submit through the API or dashboard, keep incomplete checks distinct, and assign candidates with the available supporting and conflicting evidence.

  3. 03

    Document and monitor selected relationships

    Retain the identity conclusion and business decision separately. Choose monitoring scope and cadence for continuing subjects under policy.

For the people behind the process

One capability. Useful to the whole team.

Developers

Integrate the actual screening contract

Use scoped server-side keys, explicit coverage, idempotent operations, and separate result and error paths.

Explore your workflow

Reviewers

Keep the identity comparison explainable

Inspect candidates, preserve unknown facts, document reasoning, and complete the approvals required by policy.

Explore your workflow

Operations

Keep continuing checks assigned

Monitor selected relationships, follow source changes and failures, and retain the evidence behind later decisions.

Explore your workflow

Evaluate the details

AML screening software: practical questions.

Is this a complete AML compliance platform?

No. It supports selected-source screening and related review. Identity verification, customer due diligence beyond list matching, transaction monitoring, reporting, and other program requirements remain separate.

Does AML screening include PEPs and adverse media here?

Do not infer those capabilities from the AML label. Check the actual current source catalog. SanctionsKit does not claim comprehensive PEP or adverse-media screening.

Can an API result approve a customer?

No. A result describes the selected-source comparison. Your required checks, identity review, approvals, and business decision remain distinct.

Can customers be monitored after onboarding?

Selected retained subjects can be rescreened after qualified source updates and on six-hour, daily, or weekly schedules. This is sanctions monitoring, not transaction-pattern monitoring.

See SanctionsKit in action

Explore a defined screening and review workflow for your team.

Try the interactive demo with synthetic examples. Compare plans for your team’s screening volume.