The Entity List is a US Commerce Department list that restricts exports, reexports, and transfers to named foreign parties seen as national-security or foreign-policy concerns. Maintained by the Bureau of Industry and Security, it imposes license requirements that vary by entity, making it an export-control tool separate from OFAC financial sanctions.
What is the Entity List, in plain English?
The Entity List names foreign parties that the US government sees as a national-security or foreign-policy risk in the export context. Being on it does not freeze the party's money; it imposes license requirements on exports, reexports, and transfers of items to that party. In many cases those licenses are subject to a presumption of denial, which effectively blocks the trade.
It is maintained by the Bureau of Industry and Security (BIS) at the Commerce Department, under the Export Administration Regulations. Crucially, the license policy varies by entity. Two parties on the same list can carry very different restrictions, so there is no single blanket rule that applies to all of them.
Because it is an export-control tool rather than a financial sanctions list, a party can sit on the Entity List without being blocked for payments. That split is exactly where programs get tripped up.
Entity List vs OFAC block
What changes | OFAC SDN block | Entity List |
Issuing body | Treasury, via OFAC. | Commerce, via BIS. |
Effect | Freezes property, blocks transactions. | Requires a license for exports to the party. |
Applies to | Financial dealings broadly. | Exports, reexports, and transfers of items. |
Uniformity | Blanket block on dealings. | License policy varies entity by entity. |
Who is involved
Who | Their role |
Bureau of Industry and Security | Maintains the Entity List and sets each listing's license policy. |
Exporter | Screens parties against the list and applies the specific license requirement per entity. |
Trade compliance team | Distinguishes export obligations from financial ones so payments and shipments follow the right rules. |
Payment provider | May clear a party for payments while export controls still restrict the underlying trade. |
What it looks like in practice
In practice
A technology supplier lines up a sale to a foreign firm. Financial-sanctions screening clears the buyer, and the payment could settle without issue. Treating that as the green light, a less careful team would ship.
The trade-compliance analyst screens the buyer against the Entity List and finds it there, with a license requirement carrying a presumption of denial for the specific items involved. The export cannot proceed without a license the government is unlikely to grant. The lesson: a clean payment does not mean a clean export, and each Entity List entry demands its own license analysis.
Why it matters to operators
The Entity List breaks the assumption that a party is either fully allowed or fully blocked. A firm can clear a party for payments while still being barred from exporting to it. Trade and export compliance has to screen against the list specifically and, just as important, apply each entity's particular license policy rather than a single rule for everyone on it.
Treating the Entity List like a financial block list backfires in both directions. Read it as a blanket ban and you may over-restrict payments that are actually fine. Ignore the per-entity license terms and you may miss the specific export authorization a given listing demands. The entry-by-entity nuance is the whole point.
What to watch in the data
- Separate screening stream. Screen exports against the Entity List specifically; OFAC financial feeds do not cover it.
- Per-entity license policy. Read each listing's terms; a presumption of denial is very different from a case-by-case review.
- Payments vs exports. A party clear for payments can still be export-restricted; keep the two decisions distinct.
- Item scope. The restriction attaches to items subject to the EAR; know what you are actually shipping.
- Cross-list checks. Parties may also appear on the DPL or OFAC lists; screen them together, not in isolation.
Quick questions
Does the Entity List freeze a party's assets?
No. It imposes license requirements on exports, reexports, and transfers to the party, not a financial freeze. That is the key difference from an OFAC block, where property is frozen and transactions are stopped.
Can a party be on the Entity List but fine for payments?
Yes. Because it is an export-control tool, a party can be export-restricted while still clearing financial-sanctions screening. Treating the two as the same leads to either over-restricting payments or missing the export license each listing requires.
Why does license policy vary by entity?
BIS sets the license requirement individually for each listing based on the concern it reflects. Some carry a presumption of denial, others a case-by-case review. There is no blanket rule, so each entry has to be assessed on its own terms.
How is the Entity List different from the DPL?
Both are BIS export-control lists, but the Denied Persons List revokes export privileges outright, while the Entity List imposes license requirements that vary by entity. Strong programs screen both, alongside OFAC financial lists.
Who has to screen against it?
Anyone exporting, reexporting, or transferring items subject to the Export Administration Regulations, including manufacturers, technology suppliers, and their trade-compliance teams. Financial-only screening will not catch it.
Go deeper
- OFAC, US Treasury ↗ — Administers US sanctions programs, the SDN list, and licensing.
- European Banking Authority ↗ — EU banking regulator. Strong Customer Authentication under PSD2 and AML guidance.