A European trading company has identified a buyer in a third market. Legal counsel has confirmed that the transaction falls within the scope of the relevant EU Council regulation. The goods are not prohibited outright, but a specific licence (a case-by-case authorisation to conduct an otherwise prohibited or restricted transaction, issued by the competent authority of the relevant EU member state) is required before the deal can close. The compliance team now faces a question that determines whether the contract is viable: how does a specific licence application actually work under the EU regime, and what determines whether it succeeds?
As of June 2026, specific licence applications under EU sanctions are submitted to the competent authority of the relevant member state – not to a central EU body. Each member state operates its own national procedure under the authority of the applicable Council regulation. The substantive standard is set at EU level; the procedural mechanics, documentation requirements, and processing timelines are determined nationally. Businesses must understand both layers before they apply.
This guide walks through the EU-specific licence process step by step: who grants it, what the application must contain, how the competent authority assesses it, where the process commonly fails, and how it compares with the equivalent procedures under OFAC and OFSI. A cross-regime perspective is not optional – secondary-sanctions risk and divergent licensing standards can each affect the same transaction.
Step 1 – Determine whether a specific licence is the right instrument
The first task is to establish whether a specific licence is legally available for the activity in question and whether it is genuinely required, or whether a general licence (a standing authorisation that permits a defined category of transactions without a separate application) already covers the proposed activity.
Under the EU regime, general licences are published within the relevant Council regulation or in implementing and delegated acts. They authorise defined categories of transactions – humanitarian payments, diplomatic missions, certain pre-existing contractual obligations – without requiring a separate application. If a general licence applies, filing a specific licence application creates unnecessary delay and may draw scrutiny to a transaction that needed no authorisation at all.
Where no general licence applies and the activity is not outright prohibited, a specific licence is the route. The distinction between a restricted activity and a prohibited one matters enormously here. A prohibited transaction cannot be licensed. A restricted transaction – one that requires prior authorisation – can be. In our experience, businesses regularly misread this boundary. They either attempt to licence the unlicensable or fail to apply when authorisation is available and the transaction is commercially and legally justifiable.
The preliminary analysis should therefore identify: (a) which Council regulation applies to the activity; (b) whether the transaction is prohibited or merely restricted; and (c) whether any applicable general licence already covers it. Only once these three questions are answered should an application be prepared.
Step 2 – Identify the competent authority and applicable national procedure
There is no single EU licensing body. Each member state designates its own competent authority – a ministry of finance, foreign affairs, or economy, depending on the member state – and publishes its own procedural requirements under the relevant Council regulation.
The jurisdictional question turns on where the applicant is established or, in some cases, where the transaction is executed. A company incorporated in Germany applies to the German competent authority. A French bank seeking authorisation for a payment applies in France. Where a transaction touches multiple member states – a cross-border supply chain, a multi-bank payment – it is possible that more than one authority has jurisdiction, and in practice the lead jurisdiction is usually the member state with the closest connection to the activity.
This decentralised architecture is one of the EU regime's most consequential features. The substantive licensing criteria are set by the Council, so the threshold question (does this transaction qualify for authorisation?) is answered by reference to EU law. But documentation requirements, form formats, submission channels, and processing timelines differ between Amsterdam and Valletta, between Stockholm and Rome. We regularly advise clients who have submitted correctly reasoned applications but used the wrong procedural format for the authority they filed with – a fixable problem, but one that costs weeks.
A practical consequence: before preparing any documentation, obtain the current procedural guidance from the competent authority in the relevant member state. That guidance overrides any general description of the process, including this one.
Step 3 – Assemble the application package
The substantive content of a specific licence application under the EU regime must address the authority's threshold questions: who is the applicant, what is the proposed activity, who are the counterparties, and why does the activity satisfy the licensing criteria set in the applicable Council regulation?
Most competent authorities require, as a minimum: a formal application letter or completed official form; a description of the transaction or activity for which authorisation is sought; identification of all parties involved, including any intermediaries; evidence of the applicant's compliance with the applicable screening and due-diligence requirements; and a statement of the legal basis under which the licence is sought – typically the specific provision of the Council regulation that permits a competent authority to authorise this category of activity.
Supporting documentation should be proportionate to the sensitivity of the application. A straightforward humanitarian payment to a licensed entity may need relatively light supporting materials. An application to unfreeze an asset held by a party whose ownership structure involves entities in multiple jurisdictions requires detailed ownership and control analysis, corporate documentation, and – where relevant – evidence relevant to the ownership and control test (the EU test for whether a non-listed entity is caught through a listed person's ownership or control).
The ownership and control analysis deserves particular attention. Under EU sanctions, an entity owned or controlled by a designated person is itself subject to the same asset-freeze obligation, even if it is not separately listed. An application that does not address the ownership chain of the counterparty – or that papers over an obvious control question – will draw questions from the competent authority and may be refused. Prepare this analysis thoroughly before submission, not in response to the authority's queries.
One common error is submitting an application package that is complete in form but thin in substance. Competent authorities in member states with high enforcement activity are not rubber-stamp offices. They read the applications. They identify gaps. And where a gap suggests that the applicant has not fully analysed the sanctions exposure of the transaction, they will ask – or refuse. The position above covers the standard case. Your facts – the counterparty, the goods, the route, the regime in play – change the analysis. For an assessment of your specific application under the EU regime, contact Calder & Vance at info@caldervance.com.
Step 4 – Submit and manage the review process
Once the package is ready, submission follows the competent authority's stated channel – which may be electronic, postal, or a combination. Acknowledge the submission and retain proof of filing. Clock management matters: in some member states the statutory review period begins from the date of a complete submission, and an incomplete filing resets the clock.
During the review, the competent authority may issue requests for further information. These should be treated as opportunities, not obstacles. A well-reasoned response to a query – addressing the concern directly, providing the missing evidence, and confirming the legal basis – keeps the application moving. An incomplete or evasive response gives the authority grounds to extend the review or proceed to refusal.
Processing timelines vary. Some competent authorities publish indicative timelines; others operate under statutory deadlines. These figures are not consistent across the EU. In practice, the timeline depends on the complexity of the transaction, the completeness of the initial filing, the workload of the authority, and – where the asset or transaction touches a sensitive sector or a high-profile designation – the level of internal scrutiny the authority applies. Plan for the process to take longer than the authority's published indicative period. Transaction parties need to build that contingency into their contractual arrangements.
Where a competent authority refuses an application, the refusal will normally state reasons. Under EU law, the applicant has procedural rights, and in many member states there is an administrative review or appeal route before the courts. An appeal to the EU General Court against the designation itself is a separate and distinct route – relevant where the underlying designation is contested, not where the licensing assessment is the issue. 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 to discuss next steps.
How does the EU licensing process compare with OFAC and OFSI?
Comparing the EU specific-licence procedure with its OFAC and OFSI equivalents reveals three significant structural differences that affect how applications should be prepared and how long businesses should expect the process to take.
Under OFAC, the specific licence equivalent is a formal licence application submitted directly to OFAC in Washington. There is one licensing office for the United States, regardless of where in the US the applicant is based. OFAC applies a policy framework that is published and reasonably consistent across similar applications. Processing can take a substantial period – it is not unusual for complex applications to remain pending for many months. The OFAC licensing policy framework, including the general categories of transactions OFAC will and will not licence, is more publicly accessible than the equivalent EU-level guidance. For businesses managing simultaneous applications in both regimes, the procedural asymmetry requires parallel workstreams. Our guide on specific licence applications under OFAC sets out the US process in detail.
Under OFSI in the United Kingdom, specific licence applications are submitted to OFSI in London. OFSI administers UK financial sanctions under SAMLA and the relevant thematic regulations. The UK licence framework, post the UK's departure from the EU, has developed its own categories of grounds for authorisation – broadly similar to the EU grounds in their origins, but now diverging as UK and EU sanctions lists and legislative frameworks evolve separately. OFSI publishes detailed licensing guidance and maintains a general-licence regime for defined categories. Applicants dealing with both UK and EU exposure on the same transaction need to assess whether the grounds for authorisation are materially aligned between the two regimes – in recent practice, they sometimes are not.
For the EU specifically, the decentralised competent-authority architecture means there is no single authoritative source of published licensing policy comparable to the OFAC framework documentation. Businesses and their counsel must work from the Council regulation, published guidance from the specific competent authority, and the developing practice of member-state licensing offices. In a multi-member-state transaction, differences in interpretation between national competent authorities are possible and have been observed in practice.
One cross-regime principle holds across all three systems: where the activity is otherwise prohibited, no licence will issue. Where the activity is merely restricted, the case for authorisation must be made clearly on the applicable grounds. The stricter prohibition governs where regimes overlap, and no licence under one regime authorises a breach of another.
Risk flags and common failure points
Most application failures are preventable. In our cross-border practice, the following patterns appear most consistently in applications that are refused, stalled, or returned for correction.
The first risk is submitting before the ownership and control analysis is complete. An application that cannot confirm whether the counterparty is caught by the designation – whether through direct ownership, layered intermediate holdings, or the control test – is not ready to file. The authority will either ask, or refuse. Filing prematurely does not accelerate the outcome; it creates a record of incomplete analysis.
The second risk is failing to account for the multi-regime dimension. A business that obtains EU authorisation but ignores OFAC secondary-sanctions risk, or that files with one member state's competent authority while ignoring a connected restriction in a second member state, has not solved the problem. It has solved part of it. The transaction may still be blocked, or may expose an affiliate in another jurisdiction.
The third risk is documentation that does not match the legal basis stated in the application. If the applicant relies on a specific provision of the Council regulation that authorises competent authorities to licence a particular category of activity, every element of the licensing criteria must be addressed in the documentation. A mismatch between the stated legal basis and the supporting evidence signals either a misunderstanding of the applicable provision or a failure to gather the right materials.
The fourth risk – common in large organisations – is insufficient coordination between legal, compliance, treasury, and commercial teams. Licensing applications are legal filings. They require precision and internal sign-off. Applications assembled in haste, without legal review, with missing signatures, or with internally inconsistent descriptions of the transaction, fail for reasons that have nothing to do with the merits of the underlying request.
A related myth worth addressing directly: some businesses assume that a general licence is a blanket permission that removes the need to assess individual transactions. It is not. General licences are narrowly drafted. They contain conditions, dollar or value limits (where such limits are specified in the instrument), and activity-scope limitations. A transaction that exceeds those parameters is not covered and requires a specific licence. Assuming coverage without reading the terms is a compliance failure, not a licensing solution.
When to involve sanctions counsel – and what that looks like in practice
Not every specific licence application requires external counsel. A straightforward application under a well-established licensing category, with a complete documentation package and a competent authority whose process is familiar to the applicant's in-house team, can often be prepared internally. The question is whether the facts of your application fall within that description.
Counsel adds most value in four situations. First, where the ownership and control analysis is genuinely complex – layered structures, multiple jurisdictions, trustee or nominee arrangements, or uncertain beneficial ownership. Second, where the licensing criteria are ambiguous and the applicant is not certain which provision of the Council regulation supports the application, or whether any provision does. Third, where the application involves a simultaneous multi-regime position – EU plus OFAC, or EU plus OFSI – requiring coordinated filings and consistent legal analysis across different standards. Fourth, where a prior application has been refused and the applicant needs to assess whether an appeal is viable, whether a revised application should be filed, or whether the transaction structure needs to change.
In a recent matter, a logistics business operating across multiple EU member states sought authorisation to make a payment to a supplier whose parent company had been designated under the relevant Council regulation. The supplier itself was not listed. The ownership analysis was straightforward on the immediate-parent level but revealed a second-tier beneficial owner whose listed status was ambiguous under the EU control test. We assessed the control question against the applicable Council regulation, prepared the ownership analysis, and structured the application to address the competent authority's likely questions directly. The matter proceeded to authorisation.
We assess eligibility, prepare and submit the licence application, and manage the competent authority's queries. For complex cross-border matters we coordinate filings across multiple competent authorities or jurisdictions, ensuring that the legal positions are consistent and that no regime is addressed in isolation.
Related practices
- Frozen account management under BIS/EAR – managing blocked or frozen assets under US export-control rules
- Specific licence applications under the Japan regime – step-by-step guide to the Japanese licensing process
- Specific licence applications under OFAC – how the US licensing procedure compares with the EU