Denied Party Screening Process: What Should Companies Screen

Most companies think denied party screening means running the customer's name through a sanctions list before shipping. That's one check out of many. A transaction can involve a customer, a consignee, a notify party, a freight forwarder, a bank, and a handful of owners sitting behind a holding company, and a screening program that only checks the customer misses everyone else in that chain.

This article answers the question directly: which parties need to be screened, which lists they need to be screened against, and where most screening programs actually leave gaps.

Who this matters to

• Trade compliance and export control teams building or auditing a screening program
• Sales and customer onboarding teams who touch new counterparties before compliance ever sees them
• Finance and trade finance teams processing cross-border payments
• Legal and M&A teams evaluating counterparty and ownership risk in a transaction

What denied party screening actually covers

Denied party screening (also called restricted party screening) is the practice of checking every party involved in a transaction against government-maintained lists of individuals and entities that are sanctioned, denied export privileges, or otherwise restricted from doing business.

• It's distinct from product classification (what you're shipping) and goods screening for export control purposes (whether the item itself is restricted)
• It applies because the prohibition attaches to the party, not the product: a fully unrestricted product shipped to a restricted party is still a violation
• It's required of any U.S. person, and any party dealing in items subject to U.S. jurisdiction, regardless of transaction size

Who should actually be screened

This is where most programs fall short. Screening only the direct customer leaves every other party in the transaction chain unchecked.

The practical takeaway: a single international shipment can easily involve six or more screenable parties. A process built to check only the counterparty listed on the purchase order is checking one part of the risk, not the whole transaction.

Which lists to screen against

In the U.S., restricted party lists are maintained separately by three different departments, and no single list covers everything.

(Source: U.S. Department of Commerce, Consolidated Screening List)

To simplify screening, the U.S. government consolidates these into the Consolidated Screening List (CSL), which aggregates eleven separate lists from Commerce, State, and Treasury into a single, daily-updated search tool and API.

(Source: U.S. Department of Commerce, Consolidated Screening List API)

For companies operating outside the U.S. or with non-U.S. counterparties, additional lists typically need to be checked, including the EU Consolidated List, the UN Security Council Consolidated List, and the UK's OFSI Consolidated List. A company operating across multiple jurisdictions generally cannot rely on U.S. lists alone to cover its full exposure.

Beyond name matching: screening ownership, not just names

This is the gap that catches the most companies off guard. A counterparty can pass a clean name screen and still be a blocked party under OFAC's 50 Percent Rule.

• Any entity owned 50% or more, in the aggregate, directly or indirectly, by one or more blocked persons is itself considered blocked, even if the entity's own name never appears on the SDN List
• Ownership stakes are aggregated across multiple blocked persons. OFAC's own guidance gives the example: if Blocked Person X owns 25% of Entity A, and Blocked Person Y owns another 25%, Entity A is blocked, because the combined ownership reaches 50%
• Indirect ownership counts too. If Blocked Person X owns 50% of Entity A, and Entity A owns 50% of Entity B, Entity B is also considered blocked
• The rule applies to ownership, not control. A blocked person who controls a company without owning 50% or more does not automatically trigger blocking under this rule, though OFAC can still designate that entity separately if warranted

(Source: OFAC FAQs 399 and 401, Entities Owned by Blocked Persons)

Why this matters operationally: a name-only screening tool checks the entity in front of you. It does not, by itself, trace whether that entity is majority-owned by someone who is blocked. That requires a separate ownership and beneficial-ownership screening step, layered on top of standard party screening.

Red flags that a clean screen doesn't catch

Passing a screen against every list above doesn't end the compliance obligation. BIS's "Know Your Customer" guidance describes a separate, ongoing duty to recognize red flags in a transaction, independent of list matches.

Examples of red flags BIS specifically calls out:

• A customer or their address closely resembles a party on a restricted list, without being an exact match
• The customer is reluctant to describe the end use of the product
• The ordered product doesn't match the buyer's line of business
• The item is more advanced than the destination country's known technical capabilities would suggest
• The customer offers to pay cash for an expensive item when financing would normally apply
• The customer declines standard installation, training, or maintenance services that are typically included

(Source: 15 CFR Supplement No. 3 to Part 732, BIS's "Know Your Customer" Guidance and Red Flags)

BIS's guidance is explicit that companies cannot deliberately avoid learning this information to sidestep the obligation to act on it, a practice referred to as "self-blinding." If red flags appear and go unresolved, and the transaction proceeds anyway, that can itself support a finding of a knowing violation. BIS added eight new red flag indicators to this guidance as of December 31, 2024, reflecting how this list continues to evolve.

When to screen

Screening isn't a single event. It needs to happen at multiple points, because parties, ownership structures, and list contents all change over time.

A screening program that only checks parties once, at onboarding, will miss designations and ownership changes that occur afterward. This is exactly the failure pattern behind several published OFAC enforcement actions, where a customer base was rescreened only monthly, or not at all, after the initial check.

Common gaps in screening programs

Building a defensible screening process

1. Map every screenable party in a typical transaction, not just the buyer: consignee, notify party, end user, freight forwarder, bank, and known owners.
2. Screen against the full relevant list set, not a single list, and include non-U.S. lists if the business operates outside the U.S. or with non-U.S. counterparties.
3. Add ownership and UBO screening as a distinct step from name screening, to catch 50%-Rule exposure that a name match won't surface.
4. Screen at every meaningful transaction point: onboarding, order, shipment, and payment release, not just once.
5. Rescreen the existing base periodically, since designations and ownership structures change after the initial check.
6. Document how red flags were resolved, not just that a list check came back clean.

Where automation closes these gaps

The gaps above share a common root cause: doing this manually, across every party, every list, and every ownership layer, on every transaction, doesn't scale with volume. Trademo Sanctions & PEP Screening capability screens parties against sanctions and politically exposed person watchlists, and its Sanctioned Ownership Screening and UBO Screening capabilities address the ownership-tracing gap described above, screening beneficial ownership structures rather than relying on name matching alone.

None of this removes the obligation to recognize and resolve red flags that fall outside a list match. It's built to make sure the party-level and ownership-level checks that feed into that judgment are actually being performed, consistently, across every transaction rather than just the ones that stand out.

Where to go from here

The question in the title matters more than it first appears: most screening gaps trace back to companies screening the wrong scope, one party instead of the full transaction chain, one list instead of the full set, or a name instead of the ownership structure behind it, rather than screening badly. Getting the scope right is the foundation everything else in a screening program depends on. For teams building or expanding a screening process across parties, ownership, and multiple list sets, Trademo Global Trade Management platform brings these screening functions together in one place.