Calder & Vance International Sanctions & Compliance Counsel

Licensing & Authorizations · EU

Specific licence applications under EU: a practical guide

A logistics group operating between the EU and a third market instructs its bank to release payment under a long-term supply agreement. The bank declines. A counterparty name has triggered a match against an EU Council regulation, and the funds are frozen. The commercial team asks: is there any authorisation that permits this payment? The answer is yes – but only if the company can identify the right licensing route, build a credible application, and move before the commercial window closes.

A specific licence (a case-by-case authorisation issued by a competent national authority permitting an otherwise prohibited transaction under an EU sanctions regulation) is the primary tool for unlocking frozen assets, completing restricted transactions, and meeting humanitarian obligations inside the EU regime. As of June 2026, each EU Member State designates its own competent authority to receive and decide applications; there is no single EU-level licensing body. The procedure is demanding, the grounds are defined by the relevant Council regulation, and an incomplete application is not merely delayed – it is refused.

This guide walks through the governing regime, the step-by-step application procedure, the cross-border dimension that most applicants miss, the most common points of failure, and when to involve specialist counsel before the deadline passes.

How does the EU specific-licence regime work, and who administers it?

The EU specific-licence regime is grounded in the Council regulation establishing the sanctions programme in question. Each thematic regulation sets out the categories of transaction that are prohibited, the grounds on which a derogation may be authorised, and the obligation to apply to the competent authority of the Member State in which the applicant is established or in which the relevant funds or assets are held. The Council regulation is directly applicable across all twenty-seven Member States, but licensing is administered nationally, not centrally.

That architecture creates an important practical point. If a French company holds an account in the Netherlands and that account is frozen under an EU regulation, the competent authority may be the Dutch authority, not the French one. In our cross-border practice, applicants frequently approach the wrong authority at the outset, losing days or weeks in the process.

The grounds for a specific licence vary by programme. Common derogation categories include: satisfaction of basic needs of a listed person or their dependants; payment of professional legal fees; humanitarian purposes; and – in some programmes – transactions that serve the ordinary operation of a diplomatic mission or an international organisation. The grounds are exhaustive. An applicant who cannot bring the transaction within one of the defined categories will not succeed, however meritorious the commercial case may appear.

Member State authorities have discretion within those defined grounds, but that discretion is not unlimited. The EU General Court has confirmed in successive annulment proceedings that authorities must give reasons and must respect fundamental rights. In our experience, authorities in different Member States exercise their discretion with markedly different degrees of stringency. Choosing the correct competent authority – not simply the most convenient one – is the first strategic decision in any application.

Step 1 – Identify the applicable regulation and the derogation ground

Before drafting a single word of an application, a practitioner must confirm which Council regulation applies to the transaction, which specific prohibition has been engaged, and which derogation ground is available. These are three separate questions, and conflating them is the most common error we see.

Start with the designation or the asset freeze. Is the counterparty on the EU Consolidated List? Is the asset held in an EU Member State? Does the transaction involve funds, economic resources, or services caught by the relevant regulation? If the answer to any of these is uncertain, a preliminary screening and ownership analysis should precede the licence application itself. A specific-licence application filed without first confirming that the prohibition is engaged wastes the authority's time and can create an adverse record.

Once the prohibition is confirmed, identify the derogation ground precisely. The relevant Council regulation will list the authorised grounds. Some grounds are mandatory – the authority must grant the derogation if the conditions are met. Others are discretionary. Knowing which category applies changes the tone and structure of the application. A mandatory ground is argued as a matter of right; a discretionary ground requires a fuller evidential case.

Finally, confirm jurisdiction. The competent authority is defined by Member State law transposing or implementing the regulation. If funds are held in more than one jurisdiction, or if the applicant is established in a different Member State from the relevant bank, it may be necessary to coordinate across two authorities simultaneously. Have you confirmed which authority holds the power to authorise your specific transaction?

Step 2 – Prepare the application file

The application file must be complete on submission. An authority that receives an incomplete file will request further information, extending the timeline significantly; some authorities will simply refuse and require a fresh application. Building the file correctly before submission is therefore the single most time-effective step in the process.

A complete file for a standard specific-licence application under the EU regime typically includes the following elements:

  • A covering letter or application form (as prescribed by the competent authority) that identifies the applicant, the counterparty, the regulation, the specific prohibition engaged, and the derogation ground relied upon.
  • A clear description of the transaction: the amounts, the currencies, the date, the purpose, and the commercial or humanitarian context.
  • Evidence establishing the applicant's identity and, where relevant, its establishment in the Member State of the competent authority.
  • Ownership and control documentation for the counterparty, including corporate structure charts going back to ultimate beneficial owners. This is critical where a listed person's ownership interest is relevant to the prohibition.
  • Supporting evidence for the derogation ground: for basic-needs applications, evidence of the listed person's dependants; for legal-fees applications, a fee agreement; for humanitarian applications, evidence of the operational context.
  • A legal analysis or explanatory memorandum setting out why the transaction falls within the derogation ground and why the competent authority is the correct recipient of the application.

Authorities in Germany, France, and the Netherlands, among others, publish application guidance or standard forms. Where guidance exists, follow it precisely. Where it does not, structure the file in the order described above. In our experience, authorities respond more quickly to files that are clearly structured, indexed, and cross-referenced than to those that are comprehensive but disorganised.

Step 3 – Submit and manage the authority's review

Once the file is submitted, the applicant enters a period of regulated waiting. EU Member State authorities operate under their own procedural timelines, which are set by national administrative law rather than directly by the Council regulation. Some authorities publish indicative timelines; others do not. The absence of a published deadline does not mean the process is indefinite – it means the applicant must manage the relationship with the authority proactively.

Proactive management means three things in practice. First, confirm receipt of the application promptly. Most authorities issue an acknowledgement; if one is not received within a few business days, follow up in writing. Second, respond to requests for further information promptly and completely. A delayed or partial response to an information request can reset an authority's internal clock. Third, maintain a contemporaneous record of all correspondence, including dates, the name of the officer handling the file, and the content of any telephone conversations.

Where a transaction is time-sensitive – a payment falling due under a contract, an asset sale with a closing date, a legal fee deadline – advise the authority in writing of the commercial timeline and request expedited treatment. Some authorities will accommodate this; others will not. The request should be made early, not on the eve of the deadline.

In a recent matter, a financial institution in a Northern European Member State held a payment instruction from a customer whose counterparty was subject to an asset freeze under an EU regulation. We assessed the applicable derogation ground, prepared the application file, and managed correspondence with the competent authority over a period of several weeks. The authority granted the authorisation in time for the payment to be completed before the contractual longstop date. The lesson was straightforward: the outcome depended entirely on the quality of the file submitted at the outset and on consistent communication during the review.

What is the cross-border dimension, and how does it differ from OFAC and OFSI?

EU-specific licence applications do not exist in isolation. Many cross-border transactions sit simultaneously within the reach of the EU regime and at least one other major sanctions programme – OFAC, OFSI, or both. Obtaining an EU specific licence does not authorise the transaction under OFAC or OFSI, and vice versa. The licensing regimes are legally independent.

This divergence has concrete operational consequences. Consider a transaction involving a US-dollar payment routed through a US correspondent bank. Even if an EU specific licence is granted, the payment may be blocked by the US correspondent if the beneficiary or an intermediate party appears on the SDN List (OFAC's list of Specially Designated Nationals and blocked persons). EU authorisation provides no protection from US sanctions consequences. In our cross-border practice, we regularly advise clients to assess all applicable regimes before filing any single-regime application, because a licence that covers one dimension of the transaction but not another can give a false sense of security.

The ownership-and-control tests also differ across regimes. Under OFAC, the 50 percent rule (OFAC's rule treating entities owned 50 percent or more by blocked persons as themselves blocked, regardless of intent or management) is mechanical and aggregative. Under the EU regime, the ownership and control test (the test for whether a non-listed entity is caught through a listed person's ownership or control) extends beyond a single numeric threshold to include effective control through other means. OFSI in the United Kingdom applies a broadly comparable ownership-and-control test to the EU but operates under its own statutory authority under the Sanctions and Anti-Money Laundering Act ("SAMLA") and its thematic regulations. A transaction cleared by reference to EU ownership thresholds may still require separate analysis under OFAC and OFSI.

For businesses operating in Singapore, Japan, or the UAE alongside their EU operations, the analysis extends further still. Those regimes typically implement UN Security Council measures through their own national instruments, and their licensing procedures – where they exist – are structured differently from the EU Member State model. A cross-border transaction may require coordinated parallel applications in multiple jurisdictions, each proceeding on its own timetable and before its own authority.

Does your compliance programme have a clear procedure for managing parallel licensing applications across regimes?

Risk flags: where specific-licence applications fail

Applications are refused, delayed, or returned for the same categories of reason in the jurisdictions where we practise. Understanding these failure modes before submission prevents them.

The first and most frequent risk is a mismatch between the stated derogation ground and the facts presented. An applicant who characterises a commercial supply payment as a humanitarian derogation without adequate evidential support will not succeed. Authorities are experienced in identifying this pattern. The derogation ground must be supported by the specific facts of the transaction, not asserted at a general level.

The second risk is incomplete ownership disclosure. Where the prohibition is triggered by the listed person's ownership or control of the counterparty, the authority will require evidence of the ownership chain. An application that presents only the immediate counterparty structure, without mapping beneficial ownership, will attract an information request at best and a refusal at worst. The ownership and control test under EU regulations reaches any entity effectively controlled by a listed person, not merely those with a formal majority holding.

The third risk is a jurisdictional error. Filing with the wrong competent authority causes delay and, in time-sensitive matters, can forfeit the authorisation window entirely. The correct authority is determined by the regulation and by the location of the relevant funds or assets, not by the applicant's convenience.

The fourth risk is underestimating the record-keeping obligation. EU sanctions regulations impose a duty to maintain records of licensed transactions for a defined period. Failure to maintain those records is itself a breach, separate from the underlying transaction. A compliance programme that secures a licence but does not record its use is only half-compliant.

One myth worth addressing directly: the belief that obtaining an EU specific licence is a routine administrative step that any compliance officer can handle without specialist input. In straightforward cases – a basic-needs derogation for a low-value payment by a listed individual – that may be true. But for commercial transactions, multi-party structures, or cases where the derogation ground is discretionary and contested, the application is effectively a legal submission to a public authority. Preparing it without legal input increases the risk of refusal and, if the transaction has already occurred in anticipation of a licence, of enforcement exposure.

If a transaction has already been flagged, or an application has been refused, an early review of the options can preserve routes that narrow with time. Contact Calder & Vance at info@caldervance.com for a confidential assessment of your position.

When to involve sanctions counsel and what to expect

Counsel should be instructed at the earliest practicable point in the process. The question of when an application is needed often arises under commercial pressure: a frozen payment, a blocked account, a transaction that cannot close without authorisation. The instinct is to file quickly. That instinct is correct in one respect – delay is rarely helpful – but filing a flawed application quickly is worse than filing a complete application slightly later.

A sanctions lawyer advising on a specific-licence application under the EU regime will typically do the following. First, assess whether a licence is the right route or whether the transaction can be restructured or re-characterised to avoid the prohibition without an application. Second, confirm the correct competent authority and the applicable derogation ground. Third, map the ownership and control chain of the counterparty, including beneficial ownership. Fourth, draft the application file, including the legal analysis. Fifth, submit and manage the authority's review, responding to information requests and maintaining the correspondence record. Sixth, advise on record-keeping obligations once the licence is granted.

The position above covers the standard case. Your facts – the counterparty structure, the transaction type, the regime in play, the applicable derogation ground – change the analysis materially. To discuss a specific-licence application or to assess whether a licence is required, contact Calder & Vance at info@caldervance.com.

Related practices

Frequently asked questions

What are the steps to apply for a specific licence under EU?
A specific-licence application under the EU regime proceeds in five steps: (1) confirm the applicable Council regulation, the specific prohibition engaged, and the derogation ground available; (2) identify the correct competent national authority by reference to where the funds, assets, or applicant are located; (3) build the application file, including transaction description, ownership documentation, and evidential support for the derogation ground; (4) submit to the competent authority and respond promptly to any information requests; and (5) maintain records of the authorisation and its use for the period required by the regulation.
What is the most common mistake in specific licence applications?
The most common mistake is a mismatch between the derogation ground claimed and the evidence presented. Applicants frequently characterise a commercial transaction in humanitarian or basic-needs terms without the facts to support that characterisation. The second most common error is filing with the wrong competent authority because the applicant assumed that its own Member State of establishment is always the correct recipient. Neither mistake is unavoidable; both are prevented by preliminary legal analysis before submission.
How does EU differ from other regimes here?
The EU regime is distinctive in two respects. First, licensing is administered by twenty-seven separate competent national authorities, not a single body; the applicable authority depends on where funds or assets are held and where the applicant is established. Second, the ownership and control test extends beyond a fixed ownership percentage to include effective control through non-ownership means, which is broader than OFAC's mechanical fifty percent threshold. An EU specific licence provides no authorisation under OFAC or OFSI, so parallel applications may be required for cross-border transactions.

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.