Entity List, Denied Persons List or Unverified List: Which BIS Source Should You Open?
Route an export-screening match to the official Entity List entry, denial order or Unverified List record before interpreting the restriction.
Signals to watch
- A screening alert says only BIS hit and cannot identify the Entity List, DPL or UVL source record
- An audit, shipment review or vendor renewal has a date but the team cannot reproduce the match against the current official source
- Several authorised groups report stale list labels, missing aliases or restrictions detached from their originating record
Open the source that created the claim. For an Entity List alert, read the current entry in Supplement No. 4 to Part 744 and section 744.16 of the Export Administration Regulations (EAR). For a Denied Persons List (DPL) alert, open the BIS DPL record and the controlling denial order. For an Unverified List (UVL) alert, read Supplement No. 6 and section 744.15. A Consolidated Screening List (CSL) result helps locate these records; it does not replace them.
This source order matters to an export-screening data provider business-development lead monitoring authorised exporter, freight-forwarder and trade-compliance Telegram groups. An illustrative fragment such as “BIS hit—hold supplier” is not enough to interpret a restriction or scope a data problem. A stronger signal appears when an audit, shipment review or screening-vendor renewal has a date and the team cannot reproduce which current official record produced the alert. If the message is found a day late, staff may already be working from a stale label or a match stripped of its legal source.
Which official page should I open first?
Open the named source list first; if the list is not named, use the CSL to locate a candidate and then follow its source field to the originating agency record.
The U.S. Department of Commerce CSL page says the tool consolidates multiple export-screening lists from the Departments of Commerce, State and the Treasury. It also says the tools are an aid for electronic screening and that a possible match requires additional due diligence. The CSL answers “which source may contain this name?” It cannot answer “may this transaction proceed?” without the source entry, identity and transaction facts.
When a screenshot or feed contains only BIS, preserve it as an unresolved source label. Do not guess Entity List because that is the best-known name. DPL and UVL records carry different meanings and instructions.
What does an Entity List entry establish?
It establishes that BIS has published a person or address in the Entity List and specifies entry-level export-control requirements; it does not by itself resolve every transaction involving a similar name.
EAR section 744.16 identifies the Entity List as Supplement No. 4 to Part 744. The regulation describes listed persons or addresses as reasonably believed to be involved, or to pose a significant risk of becoming involved, in activities contrary to U.S. national-security or foreign-policy interests. For a transaction, read the whole entry: name and aliases, address, license-requirement column, license-review policy, Federal Register citations and any footnotes or other entry-specific terms.
A feed that returns only ENTITY LIST — BLOCK has removed information the reviewer needs. The entry may specify which items subject to the EAR trigger a license requirement and how applications are reviewed. Other EAR controls and transaction facts can also apply. The right output is the source record plus an escalation decision by the authorised export-compliance owner—not an automatic legal conclusion from the label.
How is the Denied Persons List different?
The DPL identifies parties that have been denied export privileges under the EAR; its controlling record is the denial order, not an Entity List entry.
The BIS Denied Persons List page states that the DPL provides names of parties denied export privileges under EAR parts 764 and 766. The record can include the party name and address, the denial order and related details. Review the current order for its terms, effective period, prohibited conduct and any specifically named related persons.
Do not rewrite a DPL result as “the item needs an Entity List licence.” The central question is what the denial order prohibits and whether the identified party and conduct match the transaction. A similar trading name, former address or incomplete alias still needs identity review.
What does the Unverified List mean?
The UVL records foreign parties whose bona fides—legitimacy and reliability relating to the end use and end user—BIS could not verify through an end-use check. It is not a finding that the party has been denied export privileges.
EAR section 744.15 and Supplement No. 6 contain the operative source. Section 744.15 describes why a party may be added, including inability to verify the disposition of items, the existence or authenticity of the party, or completion of an end-use check. It also sets conditions for transactions involving a UVL party, including record, filing and UVL-statement requirements in the circumstances described by the EAR and restrictions on license-exception use.
That means UVL match cannot be shortened to either no issue or denied party. The reviewer needs the current entry, party role, item and transaction path, then applies section 744.15 and any other applicable EAR controls.
Can I rely on a fuzzy CSL name score?
No. A fuzzy score ranks text similarity; it does not establish that two entities are the same or that a restriction applies.
The CSL supports exact and fuzzy-name searching because transliteration, spelling and aliases vary. That is useful for finding candidates. Human review must compare names, aliases, addresses, countries, organisation type and transaction role, then investigate meaningful conflicts. A high score with a different country may be a false match. A lower score with a matching alias and address may deserve closer review. Neither score supplies ownership, end use, item classification or authorisation status.
What should a reproducible match record contain?
It should allow another authorised reviewer to run the same search, open the same official source and see which facts remain uncertain. Save:
- the name exactly as screened, normalised version and aliases used;
- the party’s role in the proposed transaction;
- the source list code and direct official record URL;
- the entry, order, addresses, restrictions, footnotes and cited publication record relevant to the candidate;
- the feed version or retrieval timestamp;
- the facts that support or weaken the identity match;
- the item, destination, end use and authorisation questions still requiring the export-compliance owner.
This packet is not a legal decision. It is the minimum evidence needed to stop a vague “BIS hit” from changing meaning between an alert, a case-management screen and an audit export.
For a broader method when a forwarded compliance claim has no link, use the official-source ladder. It explains why the originating legal or regulator record comes before a screenshot or group interpretation.
What can a name match never prove by itself?
A name match cannot prove identity, ownership or control, the party’s transaction role, whether the item is subject to the EAR, which end-use or destination rules apply, or whether an authorisation exists. It also does not complete screening against non-BIS lists.
The three BIS sources answer different questions, and the CSL includes sources from other U.S. agencies. A complete review may need additional lists and rules. This article is a source-routing aid, not legal advice and not a complete export-compliance procedure.
When does source confusion become a commercial signal?
It becomes worth business-development review when the source failure is repeatable, owned and attached to a dated decision. Examples include a screening feed that repeatedly emits only BIS; an audit export that cannot reproduce the official entry used on the review date; or a vendor renewal where aliases, addresses and restrictions arrive without source lineage.
TOP Prospect can find and group those messages in Telegram groups the user has deliberately connected, preserve their original source and time, remove duplicates, and explain why a cluster deserves earlier human review. It does not screen private chats, certify identity, interpret the EAR for the user or contact a listed party. The business-development lead must still confirm who owns the screening process, which system failed and what procurement or audit date is real.
An adjacent source problem appears when import detention evidence is detached from the official notice. The UFLPA detention evidence test shows how to keep the named shipment and response path attached to its records.
FAQ
Where is the official BIS Entity List source?
Use Supplement No. 4 to EAR Part 744 and read the complete entry together with section 744.16. The entry supplies the party or address, license requirement, license-review policy and other entry-specific details.
Is the Denied Persons List the same as the Entity List?
No. The DPL identifies parties denied export privileges under denial orders; the Entity List applies entry-specific end-user and end-use controls. The governing record and legal effect are different.
Does an Unverified List entry mean the party has been denied export privileges?
No. The UVL concerns parties whose bona fides BIS could not verify through an end-use check. EAR section 744.15 imposes specific conditions, but a UVL entry is not a DPL denial order.
Does a Consolidated Screening List name match prove that a transaction is prohibited?
No. Trade.gov calls the CSL an aid to electronic screening and instructs users to conduct additional due diligence on a possible match. The source list, identity and transaction facts still determine the next review.
What must be saved with a screening match?
Save the searched name and aliases, party role, source list, direct official URL, entry or order details, retrieval time, match rationale, applicable transaction facts and every unresolved identity or scope question.
If repeated source-routing failures point to an actual monitoring need, review TOP Prospect plans for authorised trade and compliance groups. The platform can surface the discussion; the official record and an authorised human remain responsible for the decision.
Frequently asked questions
Where is the official BIS Entity List source?
Use Supplement No. 4 to EAR Part 744 and read the complete entry together with section 744.16. The entry supplies the party or address, license requirement, license-review policy and other entry-specific details.
Is the Denied Persons List the same as the Entity List?
No. The DPL identifies parties denied export privileges under denial orders; the Entity List applies entry-specific end-user and end-use controls. The governing record and legal effect are different.
Does an Unverified List entry mean the party has been denied export privileges?
No. The UVL concerns parties whose bona fides BIS could not verify through an end-use check. EAR section 744.15 imposes specific conditions, but a UVL entry is not a DPL denial order.
Does a Consolidated Screening List name match prove that a transaction is prohibited?
No. Trade.gov calls the CSL an aid to electronic screening and instructs users to conduct additional due diligence on a possible match. The source list, identity and transaction facts still determine the next review.
What must be saved with a screening match?
Save the searched name and aliases, party role, source list, direct official URL, entry or order details, retrieval time, match rationale, applicable transaction facts and every unresolved identity or scope question.
Sources and further reading
- BIS Export Administration Regulations, Part 744 section 744.16 and Supplement No. 4 Entity List, accessed 11 August 2026
- BIS: Denied Persons List, accessed 11 August 2026
- BIS Export Administration Regulations, Part 744 section 744.15 and Supplement No. 6 Unverified List, accessed 11 August 2026
- U.S. Department of Commerce International Trade Administration: Consolidated Screening List, accessed 11 August 2026
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.
