A technology exporter in the United States receives an order from a foreign distributor. The distributor serves customers across several markets. One of those markets is subject to a broad OFAC programme. Can the exporter ship? A general export licence exception might apply – but only if the facts satisfy a specific eligibility sequence. Get that sequence wrong and the shipment constitutes an apparent violation from the moment it leaves the dock.
Licence-exception eligibility under OFAC is determined by a structured, multi-step analysis: identify the applicable sanctions programme, confirm the transaction is not already authorised by a general licence, check whether a statutory or regulatory exception applies to the specific goods, persons, and end-use, and then assess whether the exception conditions are satisfied in full. As of May 2026, OFAC administers more than thirty active sanctions programmes, each with its own exception provisions; there is no single universal exception list.
This guide walks through each step, identifies where businesses most often misapply the analysis, and explains when a specific-licence application is the only viable path.
Step 1: Identify the governing OFAC programme and its legal basis
Before any exception analysis can begin, the applicable OFAC programme must be identified with precision, because exceptions are programme-specific and what is permitted under one programme may be prohibited under another.
OFAC sanctions programmes are authorised primarily under the International Emergency Economic Powers Act (IEEPA) or, for older programmes, the Trading with the Enemy Act (TWEA). Each programme is implemented by a set of programme-specific regulations. Those regulations define the scope of the prohibitions and, crucially, the scope of the exceptions and general licences available within that programme. An exception valid under one programme's regulations does not carry across to another programme by implication.
The starting point is therefore simple: which programme applies to your counterparty, destination, or goods? In our experience, the most common preliminary error is treating OFAC as a single undifferentiated regime. Practitioners who approach it that way consistently miss programme-specific carve-outs – and programme-specific additional restrictions.
A single transaction can, in principle, touch more than one OFAC programme simultaneously. A shipment involving a counterparty with ties to two separate sanctioned contexts will need separate exception analyses for each programme. That is not an edge case; it arises regularly in trade involving large trading hubs.
Step 2: Establish whether the transaction is fully prohibited or only conditionally restricted
Not every transaction involving a sanctioned context is absolutely prohibited. Some OFAC programmes operate through targeted designations of specific persons and entities, rather than through broad country-wide or sector-wide prohibitions. Understanding which type of restriction applies determines whether an exception analysis is even relevant.
Where the programme applies blanket prohibitions, exceptions tend to be narrow and specifically enumerated. Where the programme applies targeted restrictions – through the SDN List (OFAC's list of Specially Designated Nationals and blocked persons) – the question is whether the counterparty or any entity caught by the 50 percent rule (OFAC's rule treating entities owned 50 percent or more by blocked persons as themselves blocked) appears on that list.
If the counterparty is not on the SDN List, is not owned 50 percent or more by listed persons, and the transaction does not involve a country or sector under a programme-wide prohibition, the exception question may not arise at all. Confirm the baseline first. Jumping to the exception analysis before establishing the baseline prohibition is a common structural error that wastes time and creates inaccurate risk conclusions.
The position above covers the standard case. Your facts – the counterparty, the goods, the route, the regime in play – change the analysis.
For an initial assessment of your exposure under OFAC and how the applicable programme applies to your transaction, contact Calder & Vance at info@caldervance.com.
Step 3: Identify and read all general licences in force under the programme
A general licence (a standing authorisation that permits a defined category of transactions without a separate application) is the closest equivalent to a licence exception in OFAC's scheme. General licences are published in the programme-specific regulations or, increasingly, as standalone instruments on the OFAC website.
General licences under OFAC programmes typically cover categories such as personal remittances, official government business, certain humanitarian transactions, informational materials, and the exportation of certain agricultural commodities and medicines. Each general licence has defined scope conditions, and those conditions are usually strict. They address who may act (US persons only, or all persons?), what goods or services are covered (and which are explicitly excluded), who the counterparty may be (and who it may not be), and how the funds may be routed.
Reading a general licence requires attention to the exclusion clauses. In our practice, we regularly see exporters identify that a general licence exists for a broad category and then fail to read the carve-outs. Humanitarian medicine licences, for instance, routinely exclude transactions with certain specifically listed entities even where the underlying goods would otherwise qualify. The carve-out governs.
General licences are not static. OFAC amends, adds, and revokes them without advance notice. Verify the current text of any general licence against the OFAC website immediately before relying on it; a version printed weeks earlier may be out of date.
Step 4: Test the specific exception conditions against your transaction facts
Once the applicable general licence or exception has been identified, the eligibility test requires mapping each condition of the authorisation against the specific facts of the transaction. This step is analytical, not administrative: it is an exercise in statutory interpretation applied to a particular set of facts.
The conditions typically operate conjunctively. All conditions must be satisfied; satisfying most of them is not sufficient. An exporter that meets the goods condition, the end-use condition, and the counterparty condition, but whose payment route passes through a channel that the licence explicitly excludes, does not qualify for the exception. The payment route alone defeats eligibility.
Work through the conditions in this order:
- Persons and entities: Is the exporter a US person or otherwise within the scope of the authorisation? Is the counterparty expressly excluded (for example, because it is a Specially Designated National, or owned by one, regardless of the goods)?
- Goods, technology, or services: Do the items fall within the described category? Are any of the items on an exclusion list within the licence (certain controlled goods, software, or technology are frequently carved out even within a broad general licence)?
- End-use and end-user: Is the intended end-use permitted? Does the end-user fall within an excluded class?
- Geographic scope: Is the destination country, or the country of a transit hub, excluded from the authorisation's geographic scope?
- Payment and financial flows: Does the proposed payment mechanism involve any prohibited financial institution, or route funds through a blocked person or a jurisdiction excluded from the authorisation?
- Procedural conditions: Does the licence require prior notification, post-shipment reporting, record-keeping of specific documents, or any other procedural step to activate the authorisation?
Each of these elements needs a documented answer tied to the transaction evidence. The documentation is not merely good practice; under OFAC's enforcement approach, the ability to demonstrate a good-faith eligibility analysis – with records to support it – is a material mitigating factor if the transaction is later queried.
Step 5: Apply the cross-regime check – BIS/EAR, OFSI, and EU controls
An OFAC exception does not resolve export-control licence requirements under the Export Administration Regulations (the EAR), administered by the Bureau of Industry and Security (BIS). These are separate legal regimes with separate authorisation structures. A transaction that qualifies under an OFAC general licence may still require a BIS licence if the goods carry a controlled ECCN (Export Control Classification Number under the US Commerce Control List) and the licence exception under the EAR does not apply.
Beyond the US domestic stack, any transaction involving a UK or EU party – as exporter, re-exporter, transit hub, or end-user – requires a parallel analysis under OFSI and the relevant UK sanctions regulations, and under the applicable EU Council Regulation. The three regimes are not harmonised. What OFAC permits, OFSI may restrict; what the EU authorises, OFAC may still prohibit by virtue of secondary sanctions or the breadth of a particular programme. Where the regimes conflict, the stricter prohibition governs the conduct of any person within its territorial or personal jurisdiction.
Secondary sanctions add a further layer. For businesses not themselves subject to US jurisdiction, certain OFAC programmes impose secondary-sanctions risk on conduct that assists or facilitates transactions with designated parties, even where the primary prohibition does not apply. This risk sits outside the normal exception framework and requires separate evaluation. Our practice addresses secondary-sanctions exposure as a distinct element of any cross-border transaction analysis.
For businesses operating under both US export controls and OFAC sanctions, see our service page on deemed exports and technology controls under BIS and the EAR, which addresses the intersection of classification, licence exceptions, and end-use controls in that specific context.
When does the exception analysis fail – and what are the risk flags?
Licence-exception eligibility fails more often from procedural omissions and mis-scoped exception reading than from outright ineligibility. Several patterns appear in enforcement contexts and in voluntary self-disclosure submissions.
Relying on a superseded general licence. General licences are amended without fanfare. A compliance team that last reviewed the position six months ago may be relying on a version that has since been restricted or revoked. Build a standing calendar trigger to re-verify any general licence you rely on regularly, not only when a new transaction arises.
Ignoring transit-country exposure. A transaction that begins and ends in permitted territories may transit through a port, bank, or intermediary located in a sanctioned context. The transit itself can constitute a prohibited transaction under programme-specific regulations, even where the origin and destination are not. Mapping the full transaction route – financial and physical – is not optional.
Failing to aggregate SDN ownership. The 50 percent rule operates on aggregate, indirect ownership. A counterparty is blocked if a combination of SDN-listed persons collectively own it at or above the threshold, even if no single listed person does. Screening tools that check only direct, single-entity holdings will miss this pattern. Who owns the counterparty, all the way up the chain?
Treating a partial match as clearance. Finding that a transaction falls partly within a general licence does not mean the whole transaction is authorised. If any element of the transaction – a particular good, a financial routing, a specific end-user – falls outside the exception, the entire transaction is not covered unless it can be restructured to separate the covered and uncovered elements cleanly.
Missing the record-keeping obligation. Several OFAC programmes require that persons relying on a general licence retain records demonstrating their eligibility. Failing to retain those records does not automatically void the exception, but it removes the evidentiary foundation for a good-faith defence in an enforcement context. Records should be maintained for the period required by the applicable regime.
If a transaction has already been flagged, or a filing has been refused, an early review can preserve options that narrow with time.
To discuss a flagged transaction or a compliance query under OFAC, contact Calder & Vance at info@caldervance.com.
When is a specific-licence application the right path?
A specific licence (a case-by-case authorisation to conduct an otherwise prohibited transaction) is the appropriate route when no general licence covers the transaction, when a general licence's conditions cannot be met on the available facts, or when the transaction involves goods, persons, or routes that sit in a genuinely grey area requiring OFAC's own judgment.
Specific-licence applications are submitted directly to OFAC and require a clear identification of the parties, the goods or services, the financial routing, the purpose, and the policy basis on which OFAC might grant the authorisation. OFAC considers applications under a policy of general licence or specific authorisation, and the processing time varies substantially by programme and by the volume of applications in the queue at any given time. There is no guarantee of approval; outcomes depend on the facts of the application and on OFAC's current programme policy priorities.
In our experience, the quality of the supporting documentation in a specific-licence application has a direct bearing on the speed of processing and on the likelihood of a positive outcome. Applications that clearly identify the policy rationale, address foreseeable OFAC concerns pre-emptively, and supply complete supporting evidence move faster than those that leave questions for the reviewer to raise. A well-prepared application is not a formality; it is the primary advocacy document.
A decision matrix for the two paths:
- General licence / exception available and conditions fully met: proceed with the transaction, document the eligibility analysis fully, retain records, and build in a re-verification step before each future reliance.
- General licence exists but one or more conditions cannot be met: assess whether the transaction can be restructured (different routing, different counterparty role, different goods split) to bring it within the licence. If not, evaluate the specific-licence route.
- No general licence applies and the transaction falls within a prohibition: consider a specific-licence application, assess whether a voluntary self-disclosure (VSD) obligation has arisen under the applicable programme, and take legal advice before proceeding.
Related practices at Calder & Vance covering adjacent areas of this analysis:
Related practices
- Deemed exports and technology controls under BIS and the EAR – classification, licence exceptions, and end-use controls for technology transfers
- Licence-exception eligibility: OFAC and BIS compared – regime comparison for exporters managing both US sanctions and US export controls
- Licence exceptions under the EAR: the full BIS analysis – detailed step-by-step guide to the EAR licence-exception structure