A cross-border trading group has a shipment ready. The goods are dual-use items destined for a research institution overseas. The compliance team suspects a general licence might cover the transaction – but they are looking at two separate regulatory regimes at once. Does the OFAC general licence eligibility analysis track the same logic as the BIS / EAR analysis? The answer is no. The instruments are different in structure, different in trigger, and different in what they require before a business can rely on them.
General licence eligibility under OFAC is governed by the applicable sanctions programme regulations issued under IEEPA or TWEA, and assessed against the specific prohibitions in force for that programme. General licence eligibility under the BIS / EAR is governed by the Export Administration Regulations, where the comparable instruments are licence exceptions – standing authorisations that permit a defined category of export, re-export, or in-country transfer without a prior case-by-case application. As of May 2026, the two regimes operate in parallel and can both apply to a single transaction; satisfying one does not satisfy the other.
This analysis compares how OFAC and BIS / EAR construct their general authorisation regimes, where they diverge in eligibility logic, and what a compliance team must do before it relies on either.
How are general licences structured under OFAC?
A general licence under OFAC is a standing authorisation published in a sanctions programme's regulations that permits a defined category of transactions without a separate application to the Office of Foreign Assets Control. It is not a licence in the conventional regulatory sense – there is no application, no certificate, and no document to produce at the point of transaction. The burden falls entirely on the party relying on it to confirm that every condition is satisfied before the transaction proceeds.
Eligibility analysis for an OFAC general licence starts with the programme. Each sanctions programme – whether directed at a particular country regime, a thematic list such as narcotics trafficking or weapons proliferation, or a hybrid – publishes its own set of general licences within its own regulations. A general licence in one programme does not carry across to another. A business that exports to a counterparty subject to a separate programme must check the licences for that programme independently.
The conditions attached to each general licence vary widely. Some are straightforward: authorising personal remittances or the receipt of intellectual property royalties. Others carry multiple eligibility conditions: a geographic limit, a counterparty exclusion, a commodity restriction, a value cap, or a destination-end-use requirement. A single unmet condition defeats eligibility entirely. In our experience, compliance teams working at volume make the most errors when they assume a general licence applies because a broadly similar transaction was authorised before – without checking whether the conditions are identical in this programme and this counterparty pairing.
Reporting and record-keeping obligations attach to several OFAC general licences. Where reporting is required, the obligation is non-waivable. Failure to report does not invalidate the licence for the completed transaction, but it is itself a violation. Every compliance programme that relies on OFAC general licences should map which of those licences carry a reporting condition and when that condition triggers.
The position above covers the standard case. Your facts – the counterparty's designation status, the goods, the value, the territorial route, the end use – change the analysis entirely. To assess whether a specific general licence covers your transaction, contact Calder & Vance at info@caldervance.com.
How does BIS structure licence exceptions under the EAR?
Under the Export Administration Regulations, BIS does not use the term "general licence" in the same sense as OFAC. The functional equivalent is the licence exception – a standing provision in the EAR that authorises an export, re-export, or in-country transfer that would otherwise require an individual licence. Licence exceptions are grouped by category and each carries a distinct set of eligibility conditions.
The eligibility analysis for a BIS licence exception runs through two gates before reaching the exception itself. First, a business must classify the item under the Commerce Control List using the applicable ECCN (Export Control Classification Number – the alphanumeric code that identifies a controlled item and the reasons for control). Second, it must confirm that the licence exception is available for that ECCN, that destination, and that end use. If the item is not on the CCL, it falls under the catch-all designation EAR99, and licence exceptions operate differently for EAR99 items than for listed ECCNs.
End-use and end-user controls are particularly important in the BIS / EAR regime. Even where a licence exception is technically available by ECCN and destination, it is unavailable if the exporter has knowledge, or reason to know, that the item will be diverted to a prohibited end use or end user. The Entity List, the Denied Persons List, and the Unverified List each carry specific consequences for licence exception availability. BIS's concept of red flags – indicators that a transaction may not be as presented – imposes a diligence obligation that is heavier than the condition-checking model that applies to most OFAC general licences.
Record-keeping under the EAR extends to the export transaction documents, the classification analysis, and the end-use checking record. BIS sets out the record-keeping period for export transactions in its regulations. Practitioners advising on BIS / EAR matters note that the record-keeping obligation runs from the date of the last act under the transaction, which can push the practical retention period well beyond the date of export.
Where do the regimes diverge on general licence eligibility?
The most consequential divergence between OFAC general licences and BIS licence exceptions is the underlying legal question each asks. OFAC asks: is this counterparty or transaction prohibited by a sanctions programme, and does the general licence carve it out of that prohibition? BIS asks: is this item controlled for export to this destination for this end use, and does the licence exception remove the requirement for an individual licence? The OFAC analysis is fundamentally about persons and transactions; the BIS analysis is fundamentally about items, destinations, and end uses.
A transaction can be covered by an OFAC general licence and still require an individual BIS export licence – or it can satisfy a BIS licence exception while remaining prohibited under OFAC because no general licence applies. The two authorisation regimes are legally independent. Neither regulator treats the other's authorisation as a substitute for its own. This is the single most common structural error we see: a business confirming OFAC clearance, proceeding to ship, and later discovering that the BIS analysis was never completed.
Counterparty-exclusion conditions illustrate the divergence in another way. Several OFAC general licences exclude named persons or categories of persons – for example, persons subject to a separate, heavier programme, or persons on the SDN List even where the underlying country restriction is otherwise covered. BIS licence exceptions exclude parties on the Entity List, denied persons, and parties identified in the Unverified List for certain transactions. The lists are not co-extensive. A party excluded from an OFAC general licence may not appear on any BIS list; a party on the Entity List may be fully cleared under OFAC.
The geographic scope of the two regimes also diverges. OFAC general licences operate within the parameters of the relevant sanctions programme, which may be country-specific or thematic. BIS licence exceptions operate by reference to the Commerce Country Chart, which groups destinations by control reason rather than by sanctions designation. The two classification systems do not map onto each other. A destination that falls within a permissive tier for BIS purposes may nonetheless be subject to comprehensive OFAC prohibitions with narrow general licence coverage.
If a transaction has already been flagged under either regime, or a filing has been refused, an early review can preserve options that narrow with time. Contact Calder & Vance at info@caldervance.com for a confidential assessment.
Which regime is stricter on general licence eligibility?
Neither regime is uniformly stricter; the relative rigour depends on the transaction type, the counterparty profile, and the item. For transactions involving designated persons, OFAC general licences tend to be the harder gate: the prohibition is absolute at the person level, and any interaction with a blocked person that falls outside a general licence requires a specific licence. BIS does not operate a blocking mechanism in the same sense – it controls items and routes, not persons as such – so the comparison is not symmetrical.
For dual-use goods destined for sensitive end uses or destinations, the BIS / EAR regime is often the harder analysis. The ECCN classification, the licence exception availability check, the end-use control requirement, and the red-flag diligence obligation together constitute a multi-layered test that exceeds what most OFAC general licences impose. BIS's extraterritorial reach through the de minimis rule (which applies BIS controls to foreign-made items incorporating more than a defined threshold of US-controlled content) and the foreign direct product rule (which captures foreign-made items that are the direct product of certain US technology) means that even non-US exporters must conduct the BIS analysis before assuming their goods are outside the EAR entirely.
The secondary-sanctions dimension adds a further layer for businesses operating outside the United States. OFAC's secondary sanctions – which can affect non-US entities transacting with certain designated parties or in certain sectors – do not map cleanly onto any BIS instrument. A non-US business that is not itself subject to primary OFAC jurisdiction may nonetheless face correspondent-banking risk, reputational exposure, or direct OFAC designation if it engages in conduct that triggers secondary-sanctions concerns. No BIS licence exception addresses this risk. Businesses operating across multiple jurisdictions must assess OFAC secondary-sanctions exposure separately from the primary licensing analysis.
Extraterritorial reach: the cross-border dimension
Both OFAC and BIS assert extraterritorial jurisdiction, but they do so through different mechanisms. Understanding which mechanism applies to a given transaction is essential before relying on any general authorisation.
OFAC's primary jurisdiction covers US persons, US-dollar transactions routed through the US financial system, and goods or services of US origin. The general licences in each programme are scoped to this primary jurisdiction; their application to non-US parties depends on whether the non-US party is acting on behalf of or in concert with a US person, or processing US dollars in a way that brings the transaction within OFAC's reach. Non-US subsidiaries of US parents are typically treated as US persons for OFAC purposes, which means the US parent's OFAC general licence analysis governs the subsidiary's conduct too – a point that multinational compliance functions regularly underestimate.
BIS jurisdiction extends to items subject to the EAR, which includes all US-origin items wherever they are in the world, and – through the de minimis and foreign direct product rules – to certain foreign-made items. A European manufacturer sourcing components from US suppliers may be exporting an item that is subject to the EAR regardless of where the item is assembled or sold. If that is the case, the full BIS licence exception analysis applies, and no European export licence exemption is a substitute. In our cross-border practice, this is one of the most underappreciated structural features of the BIS / EAR regime.
The interaction between OFAC and BIS extraterritorial reach and the UK OFSI and EU sanctions regimes creates a four-way analysis for some transactions. OFSI operates under the Sanctions and Anti-Money Laundering Act and applies a distinct ownership and control test that differs from the OFAC 50 percent rule in important respects. EU Council regulations apply their own standard for when a non-listed entity is caught through a listed person's ownership or control. A transaction that clears the OFAC general licence and the BIS licence exception may still require attention under OFSI or EU regulations, and vice versa. The stricter prohibition governs: where two regimes both apply, the more restrictive condition sets the floor.
For businesses with operations or counterparties spanning the US, UK, and EU, the only defensible approach is to run all three analyses in parallel. Relying on one clearance as a proxy for another is not a recognised compliance methodology under any of the three regimes.
Common eligibility errors and risk flags
General licence eligibility failures fall into predictable patterns. Recognising them in advance reduces the risk of inadvertent violation and simplifies the analysis for the compliance team.
The most common error is programme-mismatch: assuming that a general licence reviewed for one counterparty or transaction type applies to a counterparty in a different programme. As noted above, each OFAC programme publishes its own set of general licences. The conditions in one programme's general licence for, say, authorised trade or information services may be substantially different from the equivalent in another programme. Compliance teams that maintain a single general-licence checklist across all programmes without customising it per-programme will eventually encounter a mismatch.
A related error is stale reliance. OFAC amends its general licences and can revoke or narrow them with effect from the date of publication. A general licence that was available last quarter may have been narrowed, amended, or revoked since. Compliance calendars should include a regular review of the general licences the business is actively relying on, not just a one-time eligibility check at the outset of the transaction.
For BIS, the most common eligibility failure is incomplete ECCN classification. Many exporters classify items at the category level without completing the full CCL analysis, then assume a licence exception applies when it does not because a specific parameter – the performance specification, the software function, or the origin of a component – brings the item into a different, more restricted ECCN. Classification must be completed before licence exception eligibility is assessed; the two steps are sequential, not concurrent.
Red-flag failure is the other dominant pattern in BIS matters. A licence exception that was technically available at the time of classification is nonetheless unavailable if the exporter knew, or had reason to know, of a diversion risk and proceeded without resolving it. Red flags include: an unusually high price accepted by the buyer without negotiation, a request to omit standard documentation, a buyer whose stated business is inconsistent with the technical sophistication of the goods ordered, or a routing that makes no commercial sense given the stated destination. Have you documented how you assessed and resolved each red flag before relying on the exception?
Finally, voluntary self-disclosure is relevant in both regimes. Where a business discovers that it relied on a general authorisation without meeting all the conditions, a VSD (voluntary self-disclosure to the relevant regulator) can be a significant mitigating factor in any subsequent enforcement action. The decision to make a VSD – and how to present it – requires careful analysis. Timing, scope, and framing all affect the regulator's response. In our experience, businesses that delay the VSD decision lose the credibility benefit that early disclosure provides.
When to involve counsel, and what to prepare
Compliance teams can manage straightforward general licence eligibility checks internally, provided the analysis is programme-specific, documented, and reviewed against the current version of the general licence. The involvement of external sanctions counsel becomes important in four situations.
First, where the transaction spans both OFAC and BIS / EAR – and particularly where it also implicates OFSI or EU regulations – the parallel analysis is complex enough that an uncoordinated internal approach risks missing the interaction between the two regimes. We regularly advise compliance teams that have completed a thorough OFAC analysis and have not yet identified that the BIS analysis is separately required, or vice versa.
Second, where there is any uncertainty about whether a condition of the general licence or licence exception is met, the correct course is to resolve the uncertainty before transacting – not to proceed and hope. An unresolved eligibility question is not a minor administrative issue; reliance on a general authorisation for a transaction that does not qualify is a violation. If the uncertain condition is a counterparty-exclusion condition or an end-use condition, the stakes are particularly high.
Third, where the business is considering a specific licence application because no general licence applies, the groundwork done in the general licence analysis is directly useful. A well-documented eligibility analysis that identifies why no general licence covers the transaction, and that maps the policy considerations, gives the specific licence application a stronger factual foundation.
Fourth, where a potential prior violation has been identified – a transaction that was completed under a general licence that may not have applied – counsel should be involved in the VSD decision. The regulator's treatment of a self-disclosed violation is different from its treatment of a violation discovered through its own enforcement process, and that difference is most pronounced when the VSD is presented comprehensively and promptly.
A micro-scenario illustrates the point. In a recent matter, a logistics and freight business operated at the intersection of the BIS / EAR and an OFAC sanctions programme. The business had correctly identified an OFAC general licence for its regular transaction type and had been relying on it for some months. When the transaction route changed to include a transshipment point, neither the OFAC nor the BIS analysis was updated. The transshipment introduced a destination-leg that was outside the geographic scope of the BIS licence exception the business had been using. We assessed the exposure, scoped the apparent violation, advised on voluntary self-disclosure, and worked with the business to prepare the disclosure and correct the procedure. The matter resolved without formal enforcement proceedings, though no outcome of that kind can be guaranteed.
Related practices
- BIS / EAR frozen account management – practical support for accounts blocked or frozen under BIS / EAR enforcement
- OFAC vs EU: general licence eligibility compared – parallel analysis across OFAC and EU Council regulations
- General licence eligibility: OFAC and EU – extended analysis – deeper treatment of the EU ownership and control dimension