Restricted-Party and Denied-Party Screening: The Importer and Exporter's Guide

Build the OFAC SDN and BIS Entity List screening data model before tuning name matches against incomplete identity fields.

Primary sources: OFAC Specially Designated Nationals (SDN) List and Consolidated Screening List, the U.S. government watchlists every party must be screened against.

What lists do I actually have to screen against?

At a minimum, the OFAC Specially Designated Nationals (SDN) List, the BIS Entity List, the Denied Persons List, and the Unverified List, all of which the U.S. government aggregates into the free Consolidated Screening List (CSL). The CSL pulls together eleven restricted-party lists from the Departments of Commerce, State, and Treasury into a single daily-updated feed.

Denied-party screening, also called restricted-party screening or sanctions screening, is the practice of checking the parties to a trade transaction against U.S. government restricted-party lists before goods move or money changes hands. GingerControl is a trade compliance AI platform; it does not screen parties, but its Export Control Classifier answers the item side of the same license question, one ECCN or EAR99 with a report your export counsel can check. For an export compliance team clearing 50 to 200 new counterparties a quarter, the difference that matters is not whether a name appears on a list, it is whether you can prove, months later during an audit, that you looked, what you found, and how you resolved it. A one-line CSL keyword lookup returns a yes or no; a screening process has to keep the inclusion and exclusion rationale for every party evaluated.

Why denied-party screening is non-negotiable

Export and sanctions liability does not depend on what you shipped. It depends on who you dealt with. You can classify a product perfectly, file a flawless entry, and still commit a violation if the buyer, the buyer's owner, the bank, or the freight forwarder is on a U.S. restricted-party list. This is why screening sits at the center of every credible trade compliance program, and why it is the one control that both importers and exporters share.

The stakes are concrete. The Office of Foreign Assets Control (OFAC) enforces most sanctions on a strict-liability basis, which means, in OFAC's own words, "a person subject to U.S. jurisdiction may be held civilly liable even if such person did not have knowledge or reason to know" that a transaction was prohibited. Per OFAC's civil penalties guidance, the maximum civil penalty for an International Emergency Economic Powers Act (IEEPA) violation is the greater of roughly $250,000 (adjusted annually for inflation) or twice the value of the underlying transaction, per violation. "I didn't know" is not a defense.

On the export-controls side, the enforcement numbers are larger. In July 2025, Cadence Design Systems agreed to pay $140 million in combined penalties, $95 million to the Bureau of Industry and Security (BIS) and $45 million in U.S. Department of Justice criminal forfeitures, after software reached an entity with end-user links to a Chinese military university that screening should have surfaced. The lesson trade compliance teams took from that case was not that the law changed. It was that a missed ownership link, the gap between the named buyer and the listed parent, is exactly where screening programs fail.

Quotable insight: Denied-party screening is the only trade compliance control where getting the product right cannot save you. Classification errors are correctable through prior disclosure and post-summary correction. A blocked-party transaction is a completed violation the moment it clears, assessed under strict liability with no knowledge requirement, which is why screening, not classification, is the control that most often turns a paperwork mistake into a penalty case.

The four lists every program screens, and who maintains them

The U.S. restricted-party universe is large, but four lists carry most of the day-to-day weight. Three are maintained by BIS under the Export Administration Regulations (EAR); one is maintained by OFAC under the various sanctions programs. Each answers a different question, and each carries a different legal consequence.

Bottom line: For an export compliance team screening hundreds of counterparties a quarter, treating these four lists as interchangeable is the most common and most expensive mistake. An SDN hit is a hard stop under strict liability. A UVL hit is a resolvable red flag. Conflating them either freezes legitimate business or waves through a transaction that needed a license. A good screening tool checks all four in one pass and labels each hit by list and consequence, so the team knows whether it is facing a stop, a license requirement, or a red flag to clear.

The two lists people confuse most

BIS itself fields the question often enough to answer it directly: the Entity List is not the same as the Denied Persons List. Per BIS guidance, the Entity List "identifies persons reasonably believed to be involved, or pose a significant risk of being or becoming involved, in activities contrary to the national security or foreign policy interests of the United States," and imposes license requirements going forward. The Denied Persons List, by contrast, names parties whose export privileges have already been revoked through an enforcement action under EAR Parts 764 and 766. One is forward-looking risk; the other is a past penalty. They are screened together, but they are not the same control.

Review deemed exports and foreign-national technology access when controlled technology or source code is accessible to foreign-national staff.

The Consolidated Screening List: one feed, eleven lists

You do not have to pull eleven lists from three agencies by hand. The U.S. government does it for you. The Consolidated Screening List (CSL), published by the International Trade Administration at trade.gov, is, in the government's own definition, "a list of parties for which the United States Government maintains restrictions on certain exports, reexports, or transfers of items." It consolidates eleven restricted-party lists into a single data feed.

The CSL search tool is free, updates automatically every day at 5:00 AM Eastern, offers a "fuzzy name search" that tolerates spelling and transliteration variants, and ships with downloadable files (CSV, TSV, JSON) and an API. For a small importer screening a handful of new suppliers a month, the free CSL search is a legitimate starting point and you should use it.

Where the free tool runs out of road is at volume and at proof. The CSL returns matches; it does not adjudicate them, it does not resolve the false positives that fuzzy matching inevitably generates, it does not apply the OFAC 50 Percent Rule to surface a blocked owner standing behind an unlisted buyer, and it does not preserve a defensible record of who you screened and how you cleared each hit. Those four gaps are where programs graduate from a free lookup to a screening system. A screening system built for that graduation checks the SDN List, Entity List, Denied Persons List, and Unverified List and keeps a record of each inclusion or exclusion, the audit artifact the CSL search alone does not generate.

Who must screen, and how often

Screening is not a once-a-year exercise, and it is not only an exporter's job. The obligation tracks the transaction.

Who must screen:

• Exporters and reexporters of any item subject to the EAR, BIS recommends screening parties "as a standard part of pre-transaction due diligence."
• Importers, because a domestic customer, a routed-export consignee, or a vendor can be an SDN, and because U.S. persons are barred from dealing with blocked parties regardless of trade direction.
• Banks, freight forwarders, and 3PLs, who are themselves U.S. persons and parties to the transaction.
• Anyone running a routed export transaction, where a foreign principal party controls the shipment but U.S. liability still attaches.

For customer-controlled freight, settle routed export EEI and AES filing responsibilities before the shipment is released.

When to screen (the cadence that holds up):

1. At onboarding, before you accept a new customer, supplier, or counterparty.
2. At the transaction, before each order ships, each payment is released, and each consignee is confirmed, because lists change daily.
3. On every list update, by rescreening your active book against the daily CSL refresh, since a party clean yesterday can be designated today.
4. On material change, when ownership, end-use, or destination shifts.

GingerControl is a trade compliance AI platform that helps importers, exporters, and customs brokers classify products, simulate tariff costs, and track policy changes. It does not offer denied-party screening. Its Export Control Classifier works under the EAR and the Commerce Control List only, returning one ECCN or EAR99; it does not cover ITAR or the USML. That is the item half of the license question; who may receive the item is the screening half, which runs in a dedicated screening tool.

Red flags: when a clean screen still is not enough

Here is the part most teams underweight. A party can clear every list and still be one you cannot lawfully ship to. Screening checks names against lists; red flags are behavioral signals that demand inquiry regardless of what the lists say. BIS codifies this in its "Know Your Customer" guidance at Supplement No. 3 to Part 732 of the EAR, which lists 29 specific red flags and imposes an affirmative duty to investigate.

The guidance is blunt about the duty not to look away. In BIS's words, "When 'red flags' are raised in information that comes to your firm, you have a duty to check out the suspicious circumstances and inquire about the end-use, end-user, or ultimate country of destination," and, just as directly, "Do not cut off the flow of information that comes to your firm in the normal course of business." Self-blinding is not a defense; under the EAR's knowledge standard, deliberately avoiding what you would otherwise have learned is treated as knowing.

Common red flags from the BIS guidance include:

• The customer is reluctant to discuss end-use, or the stated end-use does not fit the product's capabilities.
• The product's technical level is a mismatch for the destination's normal needs.
• The buyer has little business background, declines routine installation or training, or is unfamiliar with the product's performance.
• A freight forwarder is listed as the final destination, or routing and packaging are abnormal for the goods.
• The buyer is evasive about whether the item is for domestic use or export.

The single hardest red flag to catch by name-matching alone is ownership. This is where the OFAC 50 Percent Rule lives: per OFAC's 50 Percent Rule guidance, an entity owned 50 percent or more, directly or indirectly, in the aggregate, by one or more blocked persons is itself blocked, even when that entity is not separately named on the SDN List. An unlisted buyer can be a blocked party because of who owns it. A name-only screen never sees that.

A 2025 development sharpened this point on the export-controls side and then, importantly, paused it. BIS issued the "Affiliates Rule" (formally, Expansion of End-User Controls To Cover Affiliates of Certain Listed Entities), published in the Federal Register on September 30, 2025, extending Entity List restrictions to entities 50 percent or more owned by listed parties, mirroring the OFAC ownership standard. BIS then suspended the rule for one year, effective November 10, 2025 through November 9, 2026. The practical takeaway for compliance teams: the OFAC 50 Percent Rule is the durable, in-force ownership standard you must screen for today, while the BIS affiliates expansion is suspended but signals where end-user controls are heading. Either way, ownership analysis, not just name matching, is the work.

False positives: the other side of the screening problem

If under-screening is the risk that draws penalties, over-screening is the risk that quietly drains a team. Fuzzy name matching, the same feature that catches "Mohammed" spelled five ways, also flags every legitimate counterparty who happens to share a name fragment with a listed party. A program that stops every fuzzy hit halts legitimate shipments; a program that clears them carelessly defeats the purpose.

Resolving a potential hit is a documentation exercise, and it is worth doing the same way every time:

1. Compare identifiers, not just names. Address, date of birth, nationality, and government ID distinguish a real match from a coincidence.
2. Check the list and the program. A hit on the SSI List carries different restrictions than a hit on the SDN List.
3. Run the ownership analysis. Confirm whether the OFAC 50 Percent Rule pulls an unlisted entity into blocked status through its owners.
4. Document the resolution. Record what you compared, what you concluded, and who decided, because an examiner will ask, and "we checked" is not the same as showing the check.

Quotable note on documentation: A false positive you cleared without a record is, to an auditor, indistinguishable from a hit you never screened.

That last step is what to look for in a screening tool. Rather than returning a bare match or no-match, it should keep the inclusion or exclusion rationale for every party evaluated, the documentation that demonstrates a good-faith, reasonable screening process, while leaving the legal call where it belongs.

A note on where the tool stops and counsel begins

GingerControl does not screen parties, make sanctions determinations or file license applications, and it does not replace a licensed customs broker or qualified export-control counsel. Its Export Control Classifier report is research for the exporter or its counsel to review and act on. A potential SDN match, an Entity List license requirement, or an unresolved red flag is a legal question that the company or its advisors must decide.

Frequently asked questions

What is the difference between denied-party screening and sanctions screening?

The terms overlap heavily and are often used interchangeably. Sanctions screening usually refers specifically to checking parties against OFAC lists like the SDN List, while denied-party or restricted-party screening is the broader practice covering OFAC plus the BIS Entity List, Denied Persons List, and Unverified List. For an export compliance team running 50 to 200 transactions a quarter, the distinction matters less than coverage: choose a screening tool that checks the OFAC and BIS lists together in a single pass, so the team is not running one tool for sanctions and another for export controls.

Is the free Consolidated Screening List enough for my business?

For a small importer screening a handful of new counterparties a month, the free CSL search at trade.gov is a legitimate starting point, it consolidates eleven lists and updates daily. It runs out of road at volume and at proof: it does not resolve false positives, apply the OFAC 50 Percent Rule to find blocked owners, or preserve an audit record. A commercial screening tool adds exactly those layers, returning a documented inclusion and exclusion rationale for each party rather than a bare match, so the screening holds up when an examiner asks how you cleared a hit.

How often do I need to rescreen my customers?

Screen at onboarding, again at each transaction before goods ship or payment releases, and rescreen your active counterparties whenever the lists change, which is daily. A party clean last month can be designated tomorrow, and the prohibition attaches the moment the designation takes effect. Batch screening in a commercial tool makes rescreening an entire active book against the latest lists a single run rather than a manual list-by-list slog.

What is the OFAC 50 Percent Rule, and why does it matter for screening?

The OFAC 50 Percent Rule means an entity owned 50 percent or more, directly or indirectly and in the aggregate, by one or more blocked persons is itself blocked, even if it is not separately named on the SDN List. It matters because a name-only screen will clear an unlisted buyer that is in fact blocked through its ownership. For a compliance team evaluating new foreign counterparties, this is the single most common way a clean screen still hides a prohibited party, which is why ownership analysis belongs inside the screening process rather than stopping at the named party.

Can denied-party screening be automated, or do I still need a person?

The mechanical work, matching names across eleven lists, surfacing fuzzy hits, flagging ownership links, scales well to automation, and at any real volume it has to. The judgment work, deciding whether a fuzzy hit is a true match, whether a red flag is resolved, and whether a transaction may proceed, stays with a person or counsel. A screening tool can automate the matching and keep the reasoning record, while the legal determination stays with the exporter, importer, or their advisors.

Do importers really need to screen, or is this only an exporter requirement?

Importers need to screen too. U.S. persons are generally prohibited from dealing with blocked parties regardless of whether goods are coming in or going out, and a domestic customer, vendor, or routed-export consignee can be an SDN. For an importer with a large or shifting supplier base, screening vendors and consignees is part of basic reasonable care. GingerControl does not screen parties; it covers the classification side that screening sits next to, HTS classification research and tariff calculation for imports and ECCN classification for exports.

What happens if I miss a denied party and ship anyway?

You may have a completed violation, and OFAC enforces most sanctions under strict liability, meaning lack of knowledge is generally not a defense; civil penalties can reach the greater of roughly $250,000 or twice the transaction value per violation, and export-controls cases have settled far higher, Cadence Design Systems paid $140 million in 2025. A documented, good-faith screening process is the strongest evidence of reasonable care if a hit slips through. Whatever tool you use, keep that documentation by default, with the reasoning for every party screened, so the record exists before you ever need it.

Putting denied-party screening into your export workflow

If your team is screening counterparties by hand against the CSL, or worse, only at onboarding and never again, the gap is not effort, it is proof and ownership analysis. A blocked party hides behind an unlisted name through the OFAC 50 Percent Rule, a fuzzy hit gets cleared with no record, and the audit arrives a year later asking what you did. The fix is a screening tool that checks every party against the OFAC SDN List, BIS Entity List, Denied Persons List, and Unverified List, with end-use and end-user analysis and a record of how each hit was resolved. GingerControl does not screen parties; for the item side of the license question, its Export Control Classifier returns an ECCN or EAR99 with a report your export counsel can check. See the Export Control Classifier →

GingerControl builds GingerOS, the AI trade compliance platform that runs on your process and the data you have, ERP or not. A project starts with Prototype Week, the step before a quote. Talk to our team →

References

1. Office of Foreign Assets Control (OFAC): Specially Designated Nationals (SDN) List and blocking requirements
   Data cited: definition of SDNs, general prohibition on dealings, 10-business-day blocked-property reporting
   Source: OFAC Specially Designated Nationals List
2. OFAC: Entities Owned by Blocked Persons (50 Percent Rule)
   Data cited: 50 percent direct/indirect aggregate ownership standard; ownership versus control distinction
   Source: OFAC 50 Percent Rule FAQs
3. OFAC: Civil Penalties and Enforcement Information
   Data cited: strict-liability standard; maximum IEEPA civil penalty (greater of ~$250,000 or twice transaction value)
   Source: OFAC Civil Penalties and Enforcement Information
4. Bureau of Industry and Security (BIS): Entity List versus Denied Persons List
   Data cited: Entity List definition and license requirements; DPL definition under EAR Parts 764 and 766
   Source: BIS guidance: Is the Entity List the same as the Denied Persons List?
5. BIS: Guidance on end-user and end-use controls
   Data cited: recommendation to screen parties as standard pre-transaction due diligence; Unverified List treatment
   Source: BIS guidance on end-user and end-use controls
6. BIS: "Know Your Customer" Guidance and Red Flags (Supplement No. 3 to Part 732 of the EAR)
   Data cited: 29 red-flag indicators; affirmative duty to inquire; "do not cut off the flow of information"
   Source: eCFR, Supplement No. 3 to Part 732
7. International Trade Administration (trade.gov): Consolidated Screening List
   Data cited: CSL definition; eleven lists across Commerce, State, and Treasury; daily 5:00 AM ET updates; fuzzy search and API
   Source: Consolidated Screening List
8. Federal Register / BIS: Expansion of End-User Controls To Cover Affiliates of Certain Listed Entities (Affiliates Rule) and its one-year suspension
   Data cited: Sept 29, 2025 effective date and 50 percent ownership standard; one-year suspension Nov 10, 2025 to Nov 9, 2026
   Source: Expansion of End-User Controls To Cover Affiliates of Certain Listed Entities; One-Year Suspension

Related Articles

• Section 232 in 2026: 50% Rule, US Steel Exemption, and the 85% Content Threshold