Practical guide

What is sanctions screening? A practical business guide

Understand sanctions screening, the difference between matching and identity review, and how source coverage, ownership, and monitoring affect the result.

On this page

Compare a known subject with selected sanctions data

Sanctions screening compares information about a person, company, or other supported entity with selected sanctions records. It is intended to surface possible matches for further review. The comparison is only as broad as the sources, identity fields, and matching policy used.

An authority’s list and a screening service are different things. OFAC publishes official sanctions data; software can organize that data into a searchable, reviewable workflow. A vendor does not create the authority’s designation by returning a candidate.

Three layers need to remain distinguishable

The first layer is the screening outcome: a candidate was returned, none was returned, or the check did not complete. The second is identity review: does the candidate represent the submitted subject? The third is the business or legal disposition: what action is appropriate for this relationship and activity?

Collapsing all three into a single red or green score loses useful information. A confirmed identity is not necessarily a universal instruction to reject every activity, and a completed no-match result is not a general compliance certificate.

Select lists for their purpose

OFAC SDN, OFAC Non-SDN, UK sanctions data, and export-control lists do not all carry the same restrictions. Preserve the issuer, list, program, source record, and version. The coverage directory explains supported and reference-only sources.

Global coverage should be defined by named sources and their scope, not by a large number of countries in a marketing claim. Multiple overlapping lists can contain the same underlying party. More rows do not necessarily mean more unique identities.

Use identity facts without inventing them

Name matching can accommodate some spelling, ordering, or script variations. It cannot establish that two people are the same merely because their names are similar. Compare additional reliable facts and classify each as supporting, conflicting, or unknown.

For an invented organization, a verified registry identifier can help distinguish a similarly named company. That is useful only when the source identifier is of the same kind and from a comparable issuer. An unexplained number in a note is not equivalent evidence.

Account for what the search does not cover

A direct-list check does not discover all owners, investigate every restricted service, or evaluate a transaction’s behavior. OFAC’s 50 Percent Rule guidance is one reason an unlisted company can still raise a sanctions question.

Keep ownership, identity verification, country controls, and other required diligence connected to the screening result without pretending they were performed by it. This is especially important when presenting the result to commercial users.

Build the whole workflow

A useful implementation includes input validation, explicit source selection, candidate review, retained reasoning, escalation, and appropriate rescreening. Test unavailable-source and timeout paths as carefully as ordinary results.

SanctionsKit combines a screening API with a dashboard for the people reviewing retained results. Start with a representative set of synthetic cases, agree the handoff between engineering and compliance, and expand after testing the complete process.

Official references