What is watchlist screening? Choose lists and read the result

A watchlist check has a defined source scope

Watchlist screening compares a person or business with selected lists. Those might concern sanctions, export controls or another defined purpose. SanctionsKit checks supported sources you choose and saves evidence for review. The word watchlist does not mean every relevant database was searched.

Read coverage to understand the categories, then open New screening in the dashboard. Identify the legal party and subject type before selecting the policy or sources. A customer, company representative and end user may be different identities requiring separate checks.

Confirm the sources can be used for this check

The selector shows eligible sources for the subject. An integration can call GET /api/v1/sources for the current data array. Inspect each required source's id, availability, capabilities, rightsStatus, qualification, fresh and currentVersion. Requests use the returned ID, not the display name.

Send exactly one of sources or package, plus a published policy reference when required. Keep a required unavailable list visible as a gap. Do not quietly remove it from the request. Availability may change after discovery, so handle errors returned when screening actually runs as well.

For example, suppose you need two named lists for a supplier check. Selecting one larger-sounding package does not prove both are included. Read its actual source scope. Keep a missing required list visible until the check can be completed under the approved policy.

Keep the authority and underlying list with the result

Choose Run screening or follow the API request guide. A completed result contains status, matches, coverage and versions. Retain each candidate's authority, list, source ID and record. A red watchlist flag alone hides information the reviewer needs.

A CSL entry, OFAC SDN record and public-office record mean different things. First compare identity, then ask the authorized reviewer to assess the relevant activity or policy question. A broad source category cannot tell your team to reject every relationship in the same way.

Review evidence and finish outside tasks

Open the retained case in Review queue. Compare the subject with every candidate and add relevant identity evidence. Missing fields stay unknown. Save identity decisions and the separate business action, then complete required external checks and approval.

SanctionsKit does not provide comprehensive PEP or adverse-media screening. Use a separately evaluated process if your policy requires those checks, and record the evidence through required external checks. A task label does not add a database to the search.

Monitor the scope you actually selected

For an party that needs later checks, create a monitor with the intended subject and approved coverage. Check that the first run succeeds. Later changes may need renewed review. Monitoring repeats the chosen check; it does not silently expand it to every possible watchlist.

Practice with the synthetic demo. The source-category guide helps label findings accurately in your application. Keep the original coverage and evidence references so a later reviewer can explain what was searched at the time.

Different lists can lead to different follow-up

The source tells you what the finding means. An OFAC SDN entry, a BIS-related entry and a PEP profile raise different questions even if each names the same party. The Commerce Consolidated Screening List itself combines lists with different rules.

Keep the original source visible and link to its authority. If your app puts the same blocked badge on every record, a reviewer may take the wrong action. First explain which list produced the entry. Then assess the rule and the planned activity.

Frequently asked questions