Calder & Vance International Sanctions & Compliance Counsel

Licensing & Authorizations · EU

How to choose the right licence route under EU

A trading business in the Netherlands identifies a buyer in a third market. Before the contract closes, the compliance team flags a question: does this transaction fall within an existing EU general authorisation, or does the firm need a specific licence from the competent authority? The answer determines whether the deal can proceed in days or weeks – and whether the wrong choice exposes the company to a potentially significant penalty.

Choosing between specific and general licences under EU sanctions law turns on four variables: the type of transaction, the goods or services involved, the counterparty and its ownership chain, and the humanitarian or statutory ground relied upon. General licences (standing authorisations embedded in the applicable Council Regulation that permit a defined category of transactions without a separate application) apply where the facts precisely match the listed criteria. Where they do not, a specific licence (a case-by-case authorisation issued by the member state's competent authority) is required. As of June 2026, EU licensing practice continues to tighten around extraterritorial asset-freezes and dual-use-adjacent humanitarian scenarios.

This guide walks through the decision sequence a compliance counsel or general counsel should apply before committing to either route, how the EU position compares with OFAC and OFSI, and the common errors that turn a manageable licensing matter into an enforcement question.

Step 1 – Identify the applicable Council Regulation and competent authority

Every EU sanctions licensing question begins with the applicable Council Regulation: the instrument that creates the prohibition and defines the permitted exceptions. The EU does not operate a single consolidated licensing regime; each thematic programme is governed by its own Council Regulation and corresponding Council Decision. The competent authority for licensing is not the Council itself – it is the national authority of the member state in which the funds, assets, or transaction nexus are located.

In our practice, this first step is where businesses most often lose time. A Dutch bank and a French subsidiary of the same group may face different competent authorities for what is, economically, the same frozen asset. The applicable Council Regulation defines what is prohibited; the member state's competent authority decides whether a licence may be granted and on what conditions. Identifying both – the instrument and the authority – before drafting any application is not optional. It shapes everything from the evidence requirements to the expected decision window.

The cross-border dimension matters immediately here. A transaction touching a US person or a US-dollar leg may simultaneously engage OFAC. A UK entity in the ownership chain brings OFSI into the picture. EU licences do not authorise prohibited acts under those regimes. We regularly advise clients at this stage simply to map all the regulatory touchpoints before selecting any licensing route, because a general licence that covers the EU leg may leave the OFAC exposure entirely unaddressed.

The position above covers the standard case. Your facts – the counterparty, the goods, the transaction structure, the member state, and the programme in play – change the analysis materially.

For an initial assessment of your EU licensing exposure, contact Calder & Vance at info@caldervance.com.

Step 2 – Test whether a general licence covers your transaction

A general licence under an EU Council Regulation covers your transaction only if every element of the fact pattern falls within the precise terms of the authorisation, without exception or extrapolation. General licences in EU sanctions instruments authorise specific categories of activity – for example, the release of frozen funds to meet basic needs, certain diplomatic transactions, or defined humanitarian operations – and they are construed strictly.

The practical test involves three questions. First, does the listed authorisation apply to the specific type of transaction? Second, does the counterparty or beneficiary satisfy every criterion set out in the authorisation? Third, are there conditions attached – reporting to the competent authority, record-keeping, a spending cap – and can your business satisfy them? If the answer to any of these three questions is "not clearly yes," the general licence route is not available.

Conditions attached to general licences are often underestimated. Some require prior notification to the competent authority before the transaction is executed. Some require post-transaction reporting within a short window. Failure to comply with attached conditions can convert a technically authorised transaction into an unlicensed one for enforcement purposes. In our experience, businesses that treat a general licence as a blanket permission – rather than a conditional authorisation with operational requirements – create their own compliance failures without any underlying substantive breach.

One structural difference from the OFAC general-licence model is worth noting here. OFAC general licences are issued as self-standing regulatory instruments and can be amended or revoked independently of the underlying sanctions programme. EU general licences are embedded in the Council Regulation itself; amending them requires a formal Council amendment. This makes EU general licences somewhat more stable in text but subject to longer legislative cycles when the market needs adjustments. OFSI operates a separate general-licence power under the applicable UK thematic sanctions regulations, which can be issued more rapidly as a stand-alone instrument.

Step 3 – Decide whether a specific licence is necessary and viable

A specific licence is necessary whenever the transaction is prohibited under the applicable Council Regulation and no general licence precisely covers it. Viability is a separate question: does a licensing ground exist in the applicable instrument that could support the application, and do your facts satisfy it?

EU Council Regulations typically provide a defined list of licensing grounds. These commonly include humanitarian purposes, the satisfaction of prior judicial, administrative, or arbitral decisions, basic expenses, legal fees, and extraordinary expenses. The licensing ground is not a discretionary catch-all. It is a legal precondition. An application that does not identify and satisfy a specific ground in the applicable Regulation will be refused, regardless of the equities of the case.

The decision sequence at this stage is:

  1. Identify the prohibition that applies to the transaction.
  2. Confirm that no general licence covers the full fact pattern.
  3. Identify the specific licensing ground in the applicable Council Regulation that could support authorisation.
  4. Assess whether the competent authority of the relevant member state has issued guidance on its application of that ground.
  5. Determine what evidence the competent authority requires to support the application.
  6. Prepare the application and submit to the competent authority.

Processing timescales for specific-licence applications vary significantly between member states. Some competent authorities operate with well-resourced licensing teams and issue decisions within weeks. Others operate under resource constraints that extend the timeline considerably. We have managed applications across multiple member state authorities, and the variance in practice – not just in law – is material to transaction planning. If a closing deadline is fixed, the viability of the specific-licence route must be assessed against the realistic processing window of the relevant authority, not against a theoretical average.

If a transaction has already been flagged as potentially unlicensed, or a filing has been refused, an early review can preserve options that narrow with time. Contact Calder & Vance at info@caldervance.com.

How does EU licensing differ from OFAC and OFSI?

The EU, OFAC, and OFSI licensing regimes share the same underlying function – they permit otherwise prohibited transactions in defined circumstances – but they differ structurally in ways that directly affect how a cross-border application should be managed.

Under OFAC, both general and specific licences are administered centrally by a single federal agency. There is one application point, one set of processing standards, and one decision-maker regardless of the applicant's location or the asset's location. The EU system, by contrast, is decentralised: the competent authority is the member state in which the relevant asset or transaction nexus sits. This means that a cross-EU transaction involving assets in two member states may require two separate licensing applications, to two separate competent authorities, under the same Council Regulation but with potentially different procedural requirements.

OFSI under the UK regime operates a centralised licensing function, more analogous in structure to OFAC than to the EU model. OFSI also has the power to issue general licences as stand-alone instruments under SAMLA, which gives it faster adaptation capacity than the EU Council-amendment process. In practice, OFSI and OFAC have each issued general licences in response to rapidly evolving enforcement needs; the EU has generally relied on Council Regulation amendments to achieve similar policy outcomes.

A further divergence concerns the ownership-and-control test. Under OFAC, the 50 percent rule (OFAC's rule treating entities owned 50 percent or more by blocked persons as themselves blocked) is a mechanical ownership aggregation test. Under the EU regime and the OFSI equivalent, the test captures both ownership – typically above a defined threshold – and control, which is a broader and more fact-specific assessment. A counterparty that falls below the OFAC 50 percent threshold may still be caught under the EU control limb. Clients operating under both regimes must apply the stricter prohibition that governs each leg of the transaction.

For guidance on how EU licensing interacts with OFAC authorisation requirements, see our guide at choosing between specific and general licences under OFAC. For a comparison with the Japanese regime, see choosing between specific and general licences under the Japan regime.

What are the risk flags that indicate you need specialist counsel?

Several fact patterns reliably indicate that a business should involve sanctions counsel before selecting a licensing route, rather than after a problem has emerged. Recognising these patterns early is a practical risk-reduction measure, not a formality.

The first risk flag is a counterparty whose ownership chain includes a designated person at any level. Even where direct ownership falls below the threshold that activates the EU's ownership-and-control test, indirect or layered holdings require careful analysis. Screening tools vary in their depth of ownership-chain coverage; manual verification is often necessary at the upper layers of a complex group.

The second flag is a transaction that involves dual-use goods, technology, or software alongside a sanctions question. The EU's dual-use export-control rules operate in parallel with sanctions prohibitions, and EU dual-use regulations contain their own licensing requirements. A specific sanctions licence does not authorise a controlled export; a separate export authorisation may be required. Businesses in manufacturing, technology transfer, and financial services that support dual-use supply chains face this overlap routinely. Our colleagues at Calder & Vance who handle export controls and dual-use matters regularly work alongside the licensing practice on exactly this intersection. For a related perspective on US-side export-control licensing, see our BIS/EAR service page.

The third flag is a transaction that has a humanitarian character but involves a counterparty with a UN nexus. The UN Security Council Consolidated List and the EU list do not always align. A transaction permitted under EU humanitarian grounds may still require separate authorisation if the counterparty appears on the UN Consolidated List. The applicable Council Regulation will reflect UN Security Council requirements, but the member state competent authority's interpretation of the humanitarian ground may not automatically extend to the full scope of the underlying UN obligation.

The fourth flag is any situation in which an existing general licence has been relied upon for a series of transactions, and the underlying facts have changed – new counterparty, revised goods, altered route – without a fresh analysis. General licences do not adapt to changed facts. Continued reliance after a material factual change is, in effect, unlicensed activity.

Common mistakes in EU licensing decisions – and how to avoid them

The most common mistake in choosing between specific and general licences under EU sanctions law is treating the two routes as alternatives of roughly equivalent risk, where the general licence is simply faster and the specific licence is simply slower. They are not alternatives in that sense. A general licence either covers your transaction or it does not. If it does not, using it anyway is a breach, regardless of whether the business believed in good faith that it applied.

A second persistent error involves record-keeping. EU sanctions obligations require businesses to retain records of licensed transactions – the analysis, the basis for relying on a general licence, correspondence with competent authorities, and transaction documentation. The applicable Council Regulations and implementing guidance set out retention requirements. A business that cannot demonstrate, from contemporaneous documentation, why it concluded a general licence applied is in a materially weaker position if that conclusion is subsequently questioned in an enforcement review.

One myth we encounter regularly is that obtaining a specific licence from one member state's competent authority provides EU-wide cover. It does not. A specific licence issued by the German competent authority authorises the transaction insofar as it falls within German jurisdiction under the applicable Council Regulation; it does not bind the French or Dutch competent authority if a separate nexus arises in those jurisdictions. This misunderstanding is most acute for financial institutions that process euro-denominated payments and assume that one licence covers the chain. It does not.

A third error is failing to account for the time cost of the specific-licence route in transaction structuring. Businesses frequently sign heads of terms or letters of intent before a licensing analysis has been completed, then discover that the applicable Council Regulation requires a specific licence and that the competent authority's processing window is longer than the agreed closing timeline. The correct sequence is to complete the licensing analysis before signing any binding commitment – not after.

When to involve EU sanctions counsel

The threshold for involving counsel is lower than most compliance teams assume. For transactions that are straightforwardly within a clearly-worded general licence, with no ownership-chain complexity and no dual-use element, a well-resourced internal team can manage the analysis. For everything else, the risk of error – and the consequence of error – supports early external input.

In our cross-border practice, the matters that become enforcement questions almost always had a point early in the decision process where the licensing analysis was not completed, was delegated to a non-specialist, or was assumed to align with a prior transaction. The EU sanctions regime is updated frequently through Council Regulation amendments; a position that was correct under last quarter's Regulation may not be correct today. Does your team have a process for checking whether recent Council amendments have altered the general licences or licensing grounds relevant to your transaction pipeline?

We assess eligibility, prepare and submit licence applications to the relevant member state competent authority, and manage the competent authority's queries through to decision. Where a specific licence is unlikely to succeed on the available facts, we advise on restructuring the transaction within the permitted exceptions, or on challenging the underlying designation where that is the commercial priority. We do not advise on circumventing or evading sanctions.

Related practices

Frequently asked questions

What are the steps to choose the right licence route under EU?
The decision follows a defined sequence. First, identify the applicable Council Regulation and the competent authority in the relevant member state. Second, test whether a general licence in that Regulation precisely covers every element of your transaction, including any conditions attached. Third, if no general licence applies, identify a specific licensing ground and assess whether the competent authority's processing window is compatible with your transaction timeline. Fourth, prepare the application with the evidence the competent authority requires. Each step depends on the facts of the transaction; the sequence does not change, but the analysis at each step does.
What is the most common mistake in choosing between specific and general licences?
The most common error is applying a general licence to a transaction whose facts do not precisely satisfy every criterion in the authorisation – then relying on the good-faith belief that the licence applied. A general licence is a legal authorisation with defined boundaries, not a general permission. Where a single element of the transaction falls outside the authorisation's scope, the licence does not apply. A close second is failing to maintain contemporaneous records of the licensing analysis; without that documentation, a business cannot demonstrate its reasoning to a competent authority during an enforcement review.
How does EU differ from other regimes here?
The EU licensing system is decentralised: the competent authority is the member state in which the relevant asset or transaction nexus sits, not a single central agency. This contrasts with OFAC, which operates a centralised federal licensing function, and with OFSI, which similarly administers UK licensing centrally. The practical consequence is that a cross-EU transaction may require applications to multiple competent authorities under the same Council Regulation. Additionally, the EU's ownership-and-control test captures both ownership above a threshold and control, a broader assessment than OFAC's mechanical 50 percent ownership rule.

Talk to Caldervance

For a scoped view of your exposure, contact info@caldervance.com.

Discuss your matter

This publication is general information and does not constitute legal advice. For advice on your situation, contact info@caldervance.com.