A Name Appears in Screening. Is It Sanctions, Export Control or a Federal Exclusion?
Route a potential match to OFAC sanctions data, the US Consolidated Screening List or SAM.gov exclusions before treating three different restrictions as one result.
Signals to watch
- A buyer asks for OFAC screening but the workflow also covers export transactions or federal award eligibility
- A screening result has a name and score but no source list, official record identifier or restriction text
- An unlisted counterparty has ownership links to blocked persons that a direct name search cannot resolve
OFAC sanctions data, the US Consolidated Screening List and SAM.gov Exclusions answer different questions. OFAC supports sanctions analysis. The Consolidated Screening List helps identify parties for which the US government maintains certain restrictions on exports, reexports or transfers. SAM.gov Exclusions concerns parties excluded from specified federal transactions or awards. A name appearing in one source should not be relabelled as a hit in all three.
A screening-data or compliance-integration provider’s sales director needs that separation in authorised trade-compliance, banking and public-procurement Telegram groups. “Vendor failed sanctions screening” can hide an Entity List record, a SAM exclusion, a fuzzy false positive or an OFAC ownership issue. A one-day delay can miss the architecture call; a one-source promise can leave the buyer with the wrong decision route.
Route by the business decision, not by the word “screening”
Start with the decision the buyer must make:
- Can a US person or US-connected transaction deal with this party or property under an OFAC sanctions program? Start with OFAC’s official sanctions sources and the applicable program.
- Does an export, reexport or transfer involve a party subject to a US government trade restriction? Start with the Consolidated Screening List, then open the underlying agency list record and rule.
- Is the party excluded from a covered US federal procurement or non-procurement transaction? Start with SAM.gov Exclusions and the award official’s process.
One organisation can appear in more than one system, but the authority, consequence and next reviewer remain separate. TOP Prospect can surface which source and transaction words appeared together; it does not perform the legal screening decision.
OFAC: sanctions lists plus program and ownership analysis
The OFAC Sanctions List Service provides the Specially Designated Nationals and Blocked Persons List (SDN List), non-SDN consolidated lists, downloads and links to official sanctions search. A potential match needs identity resolution against names, aliases, addresses, dates, identifiers and the relevant list entry.
A no-match result does not itself clear a counterparty. OFAC’s 50 Percent Rule FAQs explain that an entity owned 50 percent or more in the aggregate, directly or indirectly, by one or more blocked persons is considered blocked even when the entity is not separately named. OFAC also distinguishes ownership from control for that rule and urges caution in dealings involving blocked persons.
The transaction’s program, jurisdiction, property, parties and authorisations still matter. Search is an input to sanctions analysis, not a legal clearance certificate.
Consolidated Screening List: open the underlying restriction
The Consolidated Screening List describes itself as a tool for finding parties for which the US government maintains restrictions on certain exports, reexports or transfers of items. It consolidates multiple official lists for search and data use.
“CSL match” is not a single legal consequence. The reviewer must retain the originating list, agency, record identifier and restriction text. A Denied Persons List entry, Entity List entry and other export-related record can differ in scope, licensing requirement and affected conduct.
Product classification, destination, end use, end user and transaction parties can matter even where the immediate name is absent. A screening integration should route the official record to an authorised export-control reviewer rather than compress every result to red or green.
SAM.gov Exclusions: federal transaction eligibility
SAM.gov Exclusions supports searches for parties excluded from certain US federal procurement and non-procurement programs. The relevant decision is federal award or transaction eligibility, not whether the party is automatically blocked under an OFAC program or subject to every export restriction.
Preserve the exclusion record, active status, excluding agency, exclusion type, dates and any identifiers used to resolve the party. The contracting or award official’s process remains authoritative for the transaction.
A vendor may therefore need SAM.gov screening for public-sector onboarding even when its ordinary commercial payment is not an OFAC sanctions event. Conversely, a clean SAM result says nothing conclusive about OFAC ownership or export licensing.
Use one routing record, not one universal “hit” field
This article’s original contribution is a source-routing record with six blocks:
| Block | Required evidence |
|---|---|
| Identity | queried name, aliases, address, country and reliable identifiers |
| Official source | OFAC list/program, originating CSL list or SAM exclusion record |
| Restriction | exact list text, authority, status and relevant dates |
| Relationship | ownership, control, agents, end users and other transaction parties |
| Transaction | product, service, payment, export route, end use or federal award |
| Decision | reviewer, unresolved questions, disposition and timestamp |
The routing record allows a buyer to use one technical intake while preserving three different legal and operational routes. A match score can help order review; it cannot replace the restriction text or reviewer decision.
Example: one supplier, three searches, no automatic clearance
The following incomplete exchange is a routing exercise, not customer evidence:
“US grant project supplier got a screening hit. Name is almost the same.”
“Hardware ships via Dubai. Finance searched OFAC; procurement says check SAM too.”
The messages identify a federal-grant context, supplier, fuzzy name, hardware, a reexport route, OFAC search and SAM request. They do not provide the legal name, address, unique identifier, originating list, ownership, item classification, end user, exclusion status or award role.
The routing record creates three work items:
- Resolve the supplier identity and inspect any OFAC source entry plus ownership facts.
- Search the CSL, open the originating export-control record, and pass product, destination and end-use facts to the export reviewer.
- Search SAM.gov Exclusions using reliable identifiers and pass the record to the grant or award owner.
None of the three should be marked “cleared” because a different database returned no match.
Discovery can route the request, not approve the transaction
The product can filter and combine fragments from Telegram groups the user deliberately connects and is authorised to access. It can preserve original messages, sources and times; join the named party, source reference, export route and award context; remove obvious duplicates; and rank the request for human review.
It cannot search private customer systems, resolve identity conclusively, calculate ownership without evidence, classify items, interpret sanctions or export rules, determine award eligibility, approve a transaction or contact group members. Pricing and access options describe discovery only.
For deeper OFAC ownership treatment, use the 50 Percent Rule ownership-chain article. The official-source ladder shows how to recover the primary record when a request begins with a screenshot.
Key facts
- OFAC’s Sanctions List Service includes the SDN List, non-SDN lists, downloads and official search routes.
- OFAC’s 50 Percent Rule can block an unlisted entity owned 50 percent or more in the aggregate, directly or indirectly, by blocked persons.
- The Consolidated Screening List helps search parties with certain US export, reexport or transfer restrictions.
- A CSL result must retain and open its originating agency list and specific restriction.
- SAM.gov Exclusions addresses exclusions from specified federal procurement and non-procurement transactions.
- A no-match result in one source does not clear a different legal question.
- List search, identity resolution and match scoring are inputs; transaction approval remains with authorised reviewers.
FAQ
Are OFAC, the Consolidated Screening List and SAM.gov Exclusions interchangeable?
No. OFAC sources support sanctions analysis; the Consolidated Screening List helps find parties subject to certain US export, reexport or transfer restrictions; SAM.gov Exclusions concerns parties excluded from specified federal transactions and awards.
Does no OFAC name match mean a counterparty is cleared?
No. OFAC restrictions can extend to entities owned 50 percent or more in the aggregate, directly or indirectly, by blocked persons. Program rules and transaction facts also matter.
Is every Consolidated Screening List match a complete export prohibition?
No. The reviewer must open the underlying source record and read the specific restriction, list authority and licensing consequence. Different lists carry different rules.
What evidence should a screening workflow preserve?
Preserve the queried identity, aliases and identifiers, timestamp, source list and record, match rationale, ownership information, transaction context, reviewer and disposition.
The useful question is never just “Did the name hit?” It is “Which official restriction answers this exact transaction?”
Frequently asked questions
Are OFAC, the Consolidated Screening List and SAM.gov Exclusions interchangeable?
No. OFAC sources support sanctions analysis; the Consolidated Screening List helps find parties subject to certain US export, reexport or transfer restrictions; SAM.gov Exclusions concerns parties excluded from specified federal transactions and awards.
Does no OFAC name match mean a counterparty is cleared?
No. OFAC restrictions can extend to entities owned 50 percent or more in the aggregate, directly or indirectly, by blocked persons. Program rules and transaction facts also matter.
Is every Consolidated Screening List match a complete export prohibition?
No. The reviewer must open the underlying source record and read the specific restriction, list authority and licensing consequence. Different lists carry different rules.
What evidence should a screening workflow preserve?
Preserve the queried identity, aliases and identifiers, timestamp, source list and record, match rationale, ownership information, transaction context, reviewer and disposition.
Sources and further reading
How a Signal worth attention is found
See how Top Prospect finds and organizes Signals worth checking, keeps the original Telegram context, removes duplicates, and helps you decide what to review first. You decide whether to follow up and what to do next.
