Keep authority and list identity visible
Preserve the source ID, issuing authority, record reference, and dataset version. A trade restriction, sanctions designation, and other list finding should not be treated as interchangeable.
watchlist screening software
Know which list produced the candidate.
Screen people and businesses against selected supported sources. Keep the list’s purpose visible, compare the identity evidence, and give each possible match an assigned review path.
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
What this helps your team do
Connect the check to the evidence and the next decision.
Review the identity, not just the name
Compare names, reliable identifiers, known dates, and source facts. Record conflicts and missing information without turning a common-name candidate into an allegation.
Revisit meaningful changes
Monitor selected retained subjects against defined coverage and route relevant changes or failures to an owner. Earlier dismissals remain evidence of a prior review, not permanent name-only clearance.
A practical use case
Choose the required source scope
Watchlist screening is a broader label than sanctions screening. Different lists have different purposes and restrictions. Source-specific evidence should remain visible rather than being collapsed into a general blacklist or risk score.
- 01
Choose the required source scope
Map the relationship and jurisdictions, then verify that the actual sources and subject types are supported and available.
- 02
Compare and resolve candidates
Use the dashboard or API result as the starting point for an identity investigation, with required review roles and evidence references.
- 03
Retain distinct conclusions
Preserve the candidate comparison and the separate business action. Reassess when the source, subject, or policy changes.
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 workflowReviewers
Keep the identity comparison explainable
Inspect candidates, preserve unknown facts, document reasoning, and complete the approvals required by policy.
Explore your workflowOperations
Keep continuing checks assigned
Monitor selected relationships, follow source changes and failures, and retain the evidence behind later decisions.
Explore your workflowEvaluate the details
Watchlist screening software: practical questions.
Does watchlist screening mean every global list is included?
No. Use the explicit current coverage catalog. Supported screening sources, reference-only material, and unsupported sources must remain distinguishable.
Are PEPs automatically sanctioned?
No. Politically exposed person status and sanctions designation are different concepts. This product does not infer a sanctions finding or wrongdoing from PEP status.
Can I add an arbitrary internal watchlist?
This page does not promise a custom-list ingestion feature. Use only capabilities and source selection supported by the published product and contract.
What happens when a required source is unavailable?
Treat the check as incomplete under the documented workflow. Do not silently replace the missing source or describe the result as a completed all-source no-match.
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.