A mid-sized trading house operating across three continents closes a purchase order for a batch of high-performance processing units. The buyer is a registered commercial entity, long-established and previously unproblematic. Screening against the SDN List (OFAC's list of Specially Designated Nationals and blocked persons) returns no hits. The shipment is prepared and the export documentation drafted. Then an analyst notices a distribution address listed in the order that maps to a geography associated with a known diversion network under the EAR (the Export Administration Regulations, administered by the Bureau of Industry and Security). The shipment halts. Was this a licensing issue, a red-flag failure, or something more serious?
As of January 2026, trade-transaction screening under the BIS / EAR case framework requires exporters to look beyond designated-person lists. The EAR imposes end-use and end-user controls, denial-order checks, and a positive duty to evaluate red flags before proceeding. A clean SDN screen does not constitute a complete EAR compliance check. In our cross-border practice, the gap between those two steps is where enforcement exposure concentrates.
This case comment walks through an anonymised matter involving exactly that gap. It examines the legal question the matter raised, how the BIS / EAR analysis resolved it, where cross-border regime interactions complicated the picture, and what the episode teaches compliance teams running trade-transaction screening today.
The Situation: What the Business Was Doing and Where It Went Wrong
The business – a trading house sourcing components from multiple suppliers and re-exporting them to end customers in several markets – had built a screening programme around its primary sanctions obligations. It screened counterparties against published designation lists, maintained records of customer due diligence, and submitted to periodic internal audit. That programme was, on its own terms, functioning.
What it lacked was a structured BIS / EAR layer. The items the business traded included dual-use goods (items with both civilian and military application that are controlled under the EAR's Commerce Control List). Several had Export Control Classification Numbers (ECCN – the alphanumeric codes on the Commerce Control List that determine which export licence requirements and exceptions apply). The business had not classified these items with precision, relying instead on a broad assumption that none of its products required a licence for its customer base.
That assumption was never stress-tested. When the analyst flagged the distribution address, the business had no procedure to evaluate what the flag meant under the EAR, no record of having assessed the items' classification, and no documented review of the end-use certificates it had received. In our experience, this pattern – strong sanctions-list screening, weak export-control substance – is among the most common structural weaknesses in trading-company compliance programmes.
The specific red flag here was an address linked to a logistics intermediary that had appeared in BIS enforcement communications as associated with diversion into a controlled-goods destination. The EAR is explicit: a licence applicant or exporter who proceeds despite a red flag of this kind, without resolving it, is on notice. Unresolved red flags do not disappear; they become evidence of knowledge.
The Legal Question: What Does BIS / EAR Actually Require in Trade-Transaction Screening?
The EAR's transaction-screening obligation is broader than most non-specialist compliance teams appreciate. The core rule is that a US-origin item, or an item containing US-controlled content above the applicable de minimis threshold, cannot be exported, re-exported, or transferred to a destination, end-user, or end-use that is prohibited without a licence, unless a licence exception applies.
Four distinct checks run in parallel under a complete EAR screen.
- Item classification. Does the item have an ECCN? If so, which Country Chart columns does it trigger? Classification drives everything that follows. An item that is EAR99 (the residual category for items not specifically controlled) carries lighter obligations than an item with a controlled ECCN, but even EAR99 items cannot be exported to denied parties or for prohibited end-uses.
- Denied-party and restricted-party screening. The Entity List, the Denied Persons List, the Unverified List, and the Military End-User List are each BIS-maintained lists that impose different levels of restriction, distinct from OFAC's SDN List. Screening against SDN alone misses all of these.
- Country-destination analysis. Certain destinations trigger per-item licensing requirements based on the Country Chart, independently of who the end-user is.
- End-use and red-flag review. Even where the item classification and the counterparty screen return clean results, the EAR imposes a duty to evaluate red flags that a reasonable exporter would recognise as suggesting possible diversion, prohibited end-use, or misdeclared end-user.
The trading house in this matter had, in effect, performed only step two – and only the SDN portion of step two. Steps one, three, and four had no documented presence in its process.
The cross-border angle compounded the exposure. The business was incorporated outside the United States but handled items containing US-origin components. The EAR's re-export rules extend US jurisdiction to items that have left US territory, provided they meet the controlled content threshold. This extraterritorial reach is not hypothetical. BIS has pursued enforcement actions against non-US entities on exactly this basis, and the risk was live in this matter.
The position above covers the standard case. Your facts – the counterparty, the goods, the route, the jurisdictions in play – change the analysis considerably. For a structured review of your export-screening obligations, contact Calder & Vance at info@caldervance.com.
How the BIS / EAR Issue Was Resolved: The Analysis and the Steps Taken
Resolving the matter required working backwards before working forwards. The first task was classification: a systematic review of the items in the business's trading inventory to assign each an ECCN or confirm EAR99 status. This was not a simple exercise. Several items fell into dual-use categories under BIS technical parameters. One product line required a licence for re-export to the geography associated with the flagged distribution address. No licence had been sought. No licence exception had been identified that would have applied.
The second task was scoping the apparent violation. The EAR distinguishes between a transaction that proceeded despite a known red flag and one that proceeded through a classification error made in good faith. The evidential picture here was mixed. The red flag had been caught before the shipment departed, which was significant: no prohibited export had in fact occurred. The compliance failure was prospective – the system would have allowed a prohibited shipment to proceed – rather than retrospective. That distinction matters for voluntary self-disclosure analysis.
A voluntary self-disclosure (VSD – a proactive report to BIS of a potential violation before the agency initiates an investigation) was considered. The analysis weighed the absence of a consummated export, the systemic nature of the classification gap, and the fact that the red flag had been caught internally. In cases of this structure – where the harm is prospective and the company has acted promptly on discovery – our practice is to advise that a well-prepared VSD, clearly scoped and supported by an internal investigation, typically places the disclosing entity in a materially better position than passive non-disclosure. No outcome can be guaranteed. But the disclosure route and the remediation record speak directly to the mitigating factors BIS considers.
The third task was remediation: redesigning the screening programme to incorporate all four EAR checks, documenting the classification outcomes, rebuilding the red-flag evaluation procedure, and establishing a training module for the trade team. The remediated programme was documented before the disclosure was submitted, demonstrating that the company had moved to fix the systemic cause, not merely the individual transaction.
If a transaction has already been flagged, or a filing or shipment has been stopped, an early review preserves options that narrow quickly. Reach our team at info@caldervance.com for a confidential assessment.
Cross-Border Regime Interactions: Where OFAC, the EU, and the UK Added Complexity
A BIS / EAR matter rarely exists in isolation. Three cross-border complications arose in this case, each requiring separate analysis.
First, OFAC. The distribution address that triggered the initial flag was associated with a logistics network that had appeared in OFAC-related commentary. The SDN screen had not flagged the specific address entity – but a more granular review against OFAC's 50 percent rule (the rule treating any entity owned 50 percent or more in the aggregate by a blocked person as itself blocked, whether or not that entity is listed) identified a potential indirect ownership connection through a parent company. That connection required its own analysis before the transaction could be cleared or rejected on OFAC grounds. The EAR issue and the OFAC issue were legally distinct but practically intertwined: both pointed to the same counterparty risk.
Second, the UK. One of the distribution routes passed through a UK-based freight forwarder. UK export controls, administered by the ECJU (Export Control Joint Unit), impose their own classification and end-user requirements for controlled goods transiting the United Kingdom. OFSI's financial-sanctions obligations were also live for the UK-incorporated entity in the chain. We co-ordinated the EAR analysis with a parallel review of the UK position, identifying where the UK classification overlapped with the ECCN and where it diverged. Where two regimes both cover the same item, the stricter prohibition governs the transaction.
Third, the EU. The trading house had a European subsidiary that was involved in the documentation chain. EU dual-use rules operate independently of the EAR and impose their own catch-all provision: even an uncontrolled item may require an authorisation if the exporter knows or has grounds to suspect that it is intended for a prohibited end-use. The flagged address was sufficient to engage the catch-all analysis under the EU rules, adding a third regulatory strand to what had initially appeared to be a single BIS problem.
This layering – BIS / EAR as the primary regime, OFAC, ECJU, and EU dual-use rules as concurrent obligations – is the normal condition for a trading company operating across major markets. A screening programme designed to satisfy only one of those regimes will routinely under-serve the others.
For a review of how your screening programme addresses concurrent BIS / EAR, OFAC, and UK or EU obligations, see also our work on correspondent banking, de-risking, and OFAC service and on the wind-down exposure BIS / EAR matter.
Risk Flags That Signal an EAR Screening Gap
Not every BIS / EAR screening failure begins with a dramatic enforcement notice. Most begin quietly, as small procedural gaps that compound over time into systemic exposure. The following patterns – each drawn from matters we have worked on – are the most reliable early signals.
- SDN-only screening without BIS list coverage. If your screening tool does not query the Entity List, the Denied Persons List, and the Unverified List separately from OFAC lists, you have a structural gap regardless of how frequently you screen.
- Unclassified inventory. If you cannot state the ECCN (or confirm EAR99 status) for each item you trade, you cannot know whether a licence is required for a given destination. Classification is not optional; it is the prerequisite to the rest of the analysis.
- Intermediaries in the distribution chain. Freight forwarders, re-sellers, and logistics intermediaries that are themselves screened but whose ultimate customers are not reviewed introduce end-user risk. The EAR's red-flag duty extends to indicators visible anywhere in the chain.
- End-use certificates that are never verified. Collecting end-use certificates is good practice. Accepting them without any review or periodic spot-check is not: it creates a paper record that may not reflect operational reality.
- No documented red-flag procedure. The absence of a written procedure is itself a governance finding. It signals that red-flag awareness exists at individual level but is not embedded in process – meaning it will be inconsistently applied and poorly evidenced.
- De minimis miscalculation. A business that believes its products contain no US-origin content, but has never formally calculated the US-content percentage against the applicable de minimis threshold, is relying on an assumption rather than a compliance finding.
Any one of these gaps, taken alone, may not generate enforcement exposure in a given year. In combination, they form the profile of a company that BIS enforcement priorities identify as a diversion risk. The pattern matters as much as the individual item.
The Myth of the "Low-Risk" Exporter and When to Involve Counsel
A persistent belief among trading companies that do not manufacture controlled technology themselves is that export controls are primarily a concern for defence contractors and semiconductor firms. That belief is incorrect, and it is the most common objection we encounter when a trading company first comes to us after a flag has been raised.
The EAR's reach does not depend on whether you designed the technology. It depends on whether you are exporting, re-exporting, or transferring an item that is subject to the EAR. Items become subject to the EAR by virtue of their origin or their content – not by virtue of who is handling them downstream. A trading house that sources US-origin components from a supplier and re-exports assembled products has EAR obligations whether or not it considers itself to be in the technology sector.
The second part of the myth is that the EAR only applies to final end-users. The re-export and in-country transfer rules extend US jurisdiction through the distribution chain, including to intermediaries who hold items briefly before forwarding them. If your logistics model includes transit, transshipment, or third-party warehousing, US jurisdiction may follow the goods into each of those nodes.
Counsel should be involved at the earliest point at which any of the following is true: a red flag has been identified and cannot be resolved through internal review; a transaction involves a counterparty in a geography associated with known diversion networks; the item classification is uncertain; a denial order or entity-list match has returned during screening; or the business is restructuring its distribution chain in ways that change the countries through which goods move.
Earlier engagement consistently produces better outcomes. In our experience, the cost of a pre-transaction EAR review is a fraction of the cost of managing a post-shipment enforcement inquiry. Have you reviewed your classification decisions and your screening logic in the past twelve months?
We regularly advise trading companies, manufacturers, and logistics businesses on exactly this question. For matters involving concurrent jurisdictions – BIS / EAR alongside OFAC, UK, or EU controls – see our analysis of the trade-transaction screening Canada matter for a parallel treatment of how a different jurisdiction's rules interact with the US position.
The Lesson: What Compliance Teams Running Trade-Transaction Screening Should Take From This Matter
Three operational conclusions follow from this matter, each applicable to any business handling goods with potential US-origin content across multiple markets.
First, treat BIS / EAR screening as structurally distinct from OFAC screening. Both are necessary. Neither substitutes for the other. A compliance programme that merges them into a single "sanctions and export controls" screen without distinguishing the different list types, the different triggers, and the different legal standards will systematically under-perform on the EAR side. Separated workflows, with separate documented procedures, are a practical minimum.
Second, classification is compliance infrastructure, not a one-time exercise. Item classifications change when BIS revises the Commerce Control List. Product designs change when engineering makes modifications. A classification library that was accurate three years ago may not be accurate today. Build a review cycle into the programme – triggered by regulatory updates, by product changes, and by the addition of new markets.
Third, red-flag procedures need to be written, trained, and tested. The trading house in this matter had staff who understood, at an individual level, that something was wrong with the distribution address. The system did not support them: there was no documented escalation route, no decision log, and no standard for what constituted a resolved flag versus an unresolved one. Written procedures operationalise individual awareness into institutional process. Without them, compliance depends on the alertness of a single analyst rather than the reliability of a system.
In a recent matter, a distribution company in the industrial components sector faced an unresolved red-flag question under the EAR regarding a re-export route that passed through an intermediary in a sensitive geography. We classified the items, confirmed the applicable licence requirements, evaluated the red-flag record, and designed an end-use monitoring procedure. The matter was managed without enforcement escalation. That outcome reflects early action and thorough documentation, not any guarantee of result.
Related practices
- Correspondent banking and OFAC de-risking – screening, due diligence, and OFAC compliance for financial-institution relationships
- Trade-transaction screening: Canada matter – how concurrent Canadian and US controls interact in a cross-border supply chain