A trading house finalises a purchase order for a consignment of industrial sensors. The end customer is a well-known distributor in a friendly jurisdiction. Screening against the SDN List (OFAC's list of Specially Designated Nationals and blocked persons) returns clean. The shipment is cleared and booked. Three weeks later, BIS issues a denial notice: the sensors carry a controlled ECCN (Export Control Classification Number under the US Commerce Control List), the distributor appears on the Entity List (BIS's list of foreign parties subject to heightened licence requirements or full denial), and no licence exception applied. The exporter faces a significant civil penalty and a reputational crisis – for a transaction that looked routine at the outset.
Trade-transaction screening under the EAR (the Export Administration Regulations, administered by BIS – the Bureau of Industry and Security within the US Department of Commerce) requires more than a name check against a watchlist. As of January 2026, effective screening combines item classification, party screening across multiple BIS-maintained lists, end-use and end-user review, and a red-flag assessment before the transaction proceeds. Miss any one layer and the legal exposure under the EAR can be severe.
This guide walks through each screening step in sequence, identifies where businesses most commonly fall short, and explains how BIS / EAR screening compares with parallel obligations under OFAC, OFSI, and the EU dual-use regime.
Step 1: Classify the item before you screen the parties
Effective trade-transaction screening under the EAR begins with the item, not the counterparty. You cannot determine which restrictions apply – or whether any licence exception is available – until you know the item's Export Control Classification Number (ECCN) or have confirmed it is designated EAR99 (subject to the EAR but not specifically controlled unless destined for embargoed countries or listed parties).
Classification drives everything downstream. An item on the Commerce Control List carries controls tied to its ECCN: specific reasons for control (national security, anti-terrorism, regional stability, and others), the countries to which those controls apply, and the licence exceptions that may authorise export without a formal application. An EAR99 item is not unrestricted; it still may not go to parties on BIS's restricted-party lists, to embargoed destinations, or for prohibited end uses.
In our experience, misclassification is the single most consequential upstream error. A business that classifies a controlled item as EAR99 bypasses every downstream control that depends on the ECCN. Correcting the classification retroactively – after a shipment has moved – raises questions about what prior shipments also moved without the required licence or applicable exception. Review the technical specifications carefully, use BIS's publicly available classification tools as a starting point, and document the rationale for the classification you reach. Where classification is genuinely ambiguous, a commodity classification request to BIS is available. Verify the current process before relying on it.
Step 2: Screen parties across all relevant BIS lists
Once the item is classified, screen every party to the transaction – the buyer, end user, freight forwarder, financial institution, and any intermediate consignees – against the full suite of BIS-maintained lists, not just a single consolidated watchlist.
The principal BIS lists are distinct in their legal effect. The Entity List identifies specific foreign persons for whom a licence is required for all items subject to the EAR, and BIS's policy is frequently to deny such applications. The Denied Persons List imposes a prohibition on virtually all exports, re-exports, or transfers to the persons named; transacting with a denied person is prohibited regardless of the item's classification. The Unverified List (now formally the UVL) identifies parties in respect of whom BIS has been unable to conduct an end-use check; no licence exceptions are available for transactions with UVL parties.
Screening must also cover the OFAC SDN List and other OFAC-maintained lists. BIS and OFAC sit in different agencies and administer different legal regimes, but the practical consequence of an OFAC hit on a party to a trade transaction is typically a hard stop: the OFAC prohibition is generally broader and does not depend on item classification. Running both checks in parallel – not sequentially – avoids the error of treating a clean OFAC check as a green light under the EAR.
The position above covers the standard case. Your facts – the specific parties involved, the goods, the route, and the destination country – change the analysis. For a confidential review of your screening controls, contact Calder & Vance at info@caldervance.com.
Step 3: Assess end use and end user
A clean party screen is necessary but not sufficient. The EAR imposes end-use and end-user controls that can prohibit a transaction even where every named party is absent from every restricted-party list.
Certain end uses are categorically prohibited regardless of the item's ECCN or the identity of the parties. These include support for weapons-of-mass-destruction programmes (nuclear, chemical, biological, or missile-related end uses), and uses connected with specific activities that BIS has identified as grounds for a licence requirement applicable to all items subject to the EAR. Where an exporter knows or has reason to know that the item is destined for such a use, proceeding exposes the exporter to enforcement action even if all party screens return clean.
End-user review is distinct from party screening. It asks: who will actually use this item, in what application, and is that use consistent with the stated purpose? Distributors pose a particular challenge. A distributor that resells to unknown downstream customers in a range of industries may be clean on every list, but if the exporter has reason to know that a downstream buyer is a prohibited end user, the exporter retains exposure. Obtain an end-user statement or end-use certificate appropriate to the item and the destination. Keep it on file. The record-keeping obligation under the EAR runs for a defined period – verify the current requirement before relying on a specific figure.
We regularly advise clients on the design of end-use certification programmes that are proportionate to their product risk profile and their customer base. A tier-one semiconductor supplier and a manufacturer of general industrial tooling face meaningfully different end-use risks; the controls should reflect that.
How do you identify and assess red flags?
BIS has published guidance on indicators that a transaction may involve a prohibited end use, end user, or destination – commonly referred to as red flags. An exporter who identifies a red flag and proceeds without resolving it cannot rely on ignorance as a defence; the EAR's knowledge standard encompasses what a person in the exporter's position should have known.
Red flags are transactional and contextual. Common examples include: a buyer's unwillingness to provide end-use information or identify the ultimate end user; an order quantity or configuration inconsistent with the buyer's stated business; payment terms or routing that do not follow ordinary commercial practice; a delivery address that differs from the buyer's business address without explanation; and a request to omit standard export documentation. Any one of these indicators, in context, warrants a pause and a documented review before the transaction proceeds.
The red-flag analysis under the EAR is not binary. A single flag in an otherwise well-documented, long-established relationship may warrant a phone call and an updated end-use certificate. Multiple flags in a new relationship warrant escalation and, in some cases, a decision not to proceed. Document the flags identified, the steps taken to resolve them, and the reasoning behind the decision to proceed or decline. That documentation is the foundation of any penalty mitigation argument if the matter later comes to BIS's attention.
If a transaction has already been flagged, or a filing has been questioned, an early review can preserve options that narrow with time. Contact us at info@caldervance.com for a confidential assessment.
Step 4: Confirm licence requirements and available exceptions
Once item classification, party screening, end-use review, and red-flag assessment are complete, the next step is to determine whether a licence is required and whether a licence exception is available to authorise the transaction without a formal application to BIS.
Whether a licence is required depends on the ECCN, the destination (country-based controls under the EAR assign countries to groups that determine which controls apply), the end use, and the party. Some transactions require a licence for reasons of item classification but qualify for a named licence exception – for example, exceptions tied to the type of transaction, the value, the technology content, or the established relationship between the parties. Licence exceptions have conditions and recordkeeping requirements; satisfying the exception in principle is not enough if the documentation and procedural conditions are not met.
Where no exception applies and a licence is required, the exporter must submit a licence application to BIS and await a determination before the shipment moves. Proceeding without a licence is a violation of the EAR, regardless of the exporter's belief about the likelihood of approval. In our practice, we have seen transactions held up not because BIS would have denied the licence, but because the exporter was unaware a licence was required at all. Early classification and a clear licence-determination step in the screening workflow prevents that outcome.
Licence applications require supporting documentation, including technical specifications, end-use certificates, and information about the parties and the transaction. Processing times vary and are not subject to a statutory deadline in most cases – verify the current BIS position before building a licence application into a transaction timeline.
How does BIS / EAR screening compare with OFAC, OFSI, and EU obligations?
BIS / EAR screening and OFAC sanctions screening are legally distinct but operationally linked for any business exporting goods subject to the EAR. Understanding where the regimes converge and where they diverge is essential for cross-border B2B compliance.
OFAC's regime is asset-blocking in structure: a transaction involving a blocked person is prohibited regardless of what is being traded, unless a licence is obtained. The BIS / EAR regime is item-and-party based: controls depend on the item's classification, the destination, the end use, and the listed status of the parties. A transaction can be OFAC-clean and EAR-problematic (an unlicensed controlled item to an Entity List party), or EAR-clean and OFAC-problematic (an uncontrolled item to an SDN). Running both checks is not optional; it is the minimum standard for a trade transaction involving US-origin goods or US-content goods above the applicable de minimis threshold.
The UK regime under OFSI and the ECJU operates in parallel. OFSI's financial-sanctions prohibitions apply to UK persons and UK-nexus transactions; the ECJU administers UK strategic export licensing for items on the UK Military List and the UK Dual-Use List. Post-2021, the UK list-based controls have diverged from their EU predecessors, so a transaction that satisfied the EU dual-use regime before a relevant date may not automatically satisfy the current UK position. Businesses exporting goods with dual-use characteristics from the UK, or re-exporting US-origin goods through the UK, need to check both regimes independently.
The EU dual-use regime requires an export authorisation for items listed in the EU Dual-Use Regulation's annex when exported from the EU to non-EU countries. The EU regime also includes a catch-all clause that can require a licence even for unlisted items where the exporter has been informed by the competent authority, or has reason to believe, that the items are destined for certain end uses or end users. That catch-all is structurally similar to, but not identical with, the EAR's general prohibition on facilitation of prohibited exports. Where a transaction involves US-origin goods re-exported from the EU, both the EAR's re-export rules and the EU export-authorisation requirements apply; the stricter prohibition governs in practice.
Singapore, the UAE, and Japan each operate their own export-control regimes that can apply to goods transiting or re-exported through those jurisdictions. Where a supply chain passes through one of those jurisdictions, a review of the applicable country regime is a standard part of a comprehensive screening workflow.
Common risk flags and when to involve compliance counsel
Several recurring patterns in trade-transaction screening under BIS / EAR consistently produce enforcement exposure. Identifying them early changes the outcome.
The first is the assumption that a clean OFAC check is a complete trade compliance check. OFAC and BIS address different legal questions; a clean SDN screen does not clear an Entity List issue or resolve a licence-requirement question under the EAR. Compliance programmes that treat these as interchangeable will miss BIS exposure systematically.
The second is screening only at the point of sale. The EAR's controls on re-export and in-country transfer mean that a transaction does not end when goods cross the first border. Distributors and resellers can generate downstream EAR exposure for the original exporter if their onward-sale activities are not covered by end-user undertakings and periodic review.
The third – and the one we see most often in practice – is inadequate ownership screening. An end user that is clean in its own name may be owned or controlled by a party on the Entity List or on the OFAC SDN List. The EAR does not apply the same mechanical 50 percent ownership rule that OFAC uses for its blocking analysis, but end-user review must extend beyond the immediate counterparty to the ultimate beneficial owner and any entities that can direct the use of the goods. Stopping at the first layer of ownership is not sufficient.
A fourth pattern is the failure to address country-based controls separately from party-based controls. Certain destinations carry licensing requirements for a broad range of ECCNs regardless of the listed status of any party. Where a shipment moves through an intermediate country before reaching its stated destination, the transit country's destination-based controls also apply.
Involve sanctions and export-control counsel when: the transaction involves a novel jurisdiction or end-user type; a party screen returns a potential match that the internal team cannot resolve; an end-use concern has been raised and cannot be answered on available information; a shipment has moved and the team is uncertain whether the correct licences or exceptions applied; or a BIS inquiry or denial notice has been received.
Related practices
- Correspondent banking and de-risking under OFAC – screening, exposure management, and OFAC licensing for financial institutions in cross-border trade.
- Trade-transaction screening under Canadian export-control rules – step-by-step guide for the Canadian regime, with cross-border comparison.
- Cross-border trade-transaction screening guide – multi-regime framework covering OFAC, BIS, OFSI, EU, and others in one workflow.