Practical guide
Restricted-party screening vs sanctions screening
Understand restricted-party screening, sanctions and export-control lists, and source context without treating every candidate as an OFAC match.
On this page
Restricted-party screening is broader terminology
Restricted-party screening often describes checks against lists relevant to trade, exports, procurement, or other restricted activities. Sanctions screening is one related category. The meaning of a candidate depends on the actual authority and list.
The U.S. Consolidated Screening List combines multiple U.S. government sources. It is useful for finding potential parties requiring further review, not as a single uniform prohibition.
Keep the underlying list visible
A reviewer needs the issuing agency, source list, record identifier, published details, and reason the candidate was returned. Do not replace that context with a generic “denied” label. Different sources can involve different licensing, eligibility, or other requirements.
SanctionsKit’s US CSL coverage and BIS coverage explain supported scope and limitations. A direct BIS Denied Persons selector is not equivalent to every BIS restriction.
Resolve identity before interpreting the activity
Compare the known legal party with the source candidate, including identifiers and source aliases where available. An unrelated company with a similar trading name should not inherit the source restriction without a reasoned identity finding.
At the same time, a completed no-match result does not determine whether goods, software, technology, destinations, end users, or end uses require authorization. Those are separate trade-compliance questions.
Map the actual parties in the transaction
A trade workflow may involve buyer, consignee, end user, intermediary, carrier, or another relevant party. Define which roles matter under the organization’s policy and obtain reliable identifying information. Do not assume the invoice contact represents every legal party.
For an invented shipment, the contracting buyer and the stated end user are different organizations. Screening only the buyer does not establish anything about the end user.
Connect the result to a qualified review
Retain the source evidence and identity reasoning, then route the applicable trade or sanctions question to the authorized team. Record the specific proposed activity and unresolved issue so the handoff is actionable.
SanctionsKit screens submitted subjects against selected supported sources. It does not classify goods, determine export licenses, validate end use, or guarantee a shipment can proceed.
Test source overlap and coverage gaps
A party can appear in several aggregated sources. Preserve the original provenance rather than treating repeated entries as independent evidence. Test missing required sources, unsupported entity types, and ambiguous identifiers.
Use international trade solutions, global source guidance, and current authority material together. The list search is a checkpoint in the workflow, not the entire export-control decision.