A mid-sized trading house has identified a counterparty whose assets are frozen under a UN Security Council sanctions programme. The goods are humanitarian in nature. The relationship is commercially critical. The compliance team asks: is there a lawful route through? And if so, who grants it?
Specific licence applications under the UN framework are not submitted to the United Nations directly. They are submitted to the competent national authority that has implemented the relevant Security Council resolution into domestic law – and the procedure, the timeline, and the evidentiary standard all follow that national regime. What the UN layer determines is whether the transaction is prohibited at all, and whether a humanitarian, diplomatic, or other exemption category applies at the resolution level before the national authority exercises its own licensing discretion.
This guide walks through the practical steps: identifying the correct authority, mapping the applicable UN exemption category, structuring the application, managing the cross-regime dimension, and knowing when the position is strong enough to proceed.
Step 1: Identify the Correct Competent Authority for a UN-Linked Specific Licence
The first step in any specific licence application linked to the UN is to determine which national implementing authority holds the licensing function – because the United Nations Security Council has no direct licensing window for private parties. The Security Council imposes the prohibition; domestic law converts it into an enforceable obligation; and the national authority designated under that domestic law decides whether to authorise a departure from it.
In the United Kingdom, that authority is the Office of Financial Sanctions Implementation (OFSI), operating under the Sanctions and Anti-Money Laundering Act and the relevant thematic sanctions regulations. OFSI's licensing regime is independent of any UN-level determination. In the United States, the Office of Foreign Assets Control (OFAC) administers the implementing regulations under IEEPA and related authorities. In the European Union, each Member State's competent authority holds the licensing function under the relevant Council regulation, though the Council's designation decision is binding across all Member States. In Switzerland, Singapore, Japan, Australia, and the UAE, parallel implementing legislation gives equivalent functions to SECO, the relevant ministry, and so on.
Identifying the correct authority is not merely procedural. An application filed with the wrong body wastes time, and in urgent humanitarian or time-sensitive commercial matters time is the scarcest resource. In our experience, the most common early error is assuming that a single UN-level application resolves the position across all jurisdictions in which a group operates. It does not. A multinational with entities in London, Paris, and New York may need concurrent applications to OFSI, the relevant EU Member State authority, and OFAC – each on that authority's own form, and each evaluated under its own licensing policy.
Step 2: Establish Which UN Exemption Category the Transaction Falls Within
Before a national authority will engage seriously with a specific licence application, the applicant must demonstrate that the proposed transaction falls within a recognised exemption category at the UN level – or, where no UN exemption applies, that national discretion permits an authorisation that goes beyond what the resolution requires. The distinction matters for how the application is framed.
Security Council resolutions typically contain several standing exemption categories: humanitarian assistance, basic expenses, extraordinary expenses, and certain diplomatic or legal costs. Each category has its own conditions. The humanitarian exemption, for example, is not a blanket licence for any goods with a benign end-use. The goods must fall within the category as defined in the resolution, the recipient must not be the listed person themselves in most configurations, and the national authority must be satisfied that the conditions are met on the specific facts.
Where the resolution contains no applicable exemption, the analysis turns to national law. Under OFSI's regime, the licence grounds are set out in the relevant thematic regulations; the UN designation is the trigger for the prohibition, but UK law determines whether a licence can be granted. The same is true under the EU's implementing regulations. This is where the cross-regime dimension becomes operationally significant: a transaction that qualifies for a humanitarian exemption at the UN level and therefore receives an OFSI licence may still require a separate OFAC authorisation before a US-person correspondent bank can process the payment. The UN resolution does not bind OFAC; OFAC's rules bind US persons and US financial institutions, full stop.
Practitioners advising on UN matters note that applicants frequently conflate the UN exemption (which conditions the international obligation) with the national licence (which conditions what the private party can do lawfully). Both analyses must run in parallel. The absence of a UN exemption does not necessarily preclude a national licence in all regimes; and the presence of a UN exemption does not guarantee that every national authority will grant one.
Step 3: Assemble the Application Package
The strength of a specific licence application turns almost entirely on the quality and completeness of the supporting documentation. A covering letter that describes the transaction accurately but provides no supporting evidence is unlikely to succeed. The competent authority needs to be able to determine, on the papers alone, that all conditions are met.
The core package for a UN-linked specific licence typically includes: a detailed description of the goods, services, or funds at issue; evidence of the end-use and the end-user; an ownership and control analysis establishing the position of the listed person in the transaction; supporting documentation for the exemption category claimed (for humanitarian applications, this includes operational reports from the delivering organisation, evidence of prior deliveries if available, and letters of endorsement from relevant bodies); and a clear statement of the legal basis for the application under the applicable national regime.
Ownership and control mapping deserves particular attention. If the counterparty is not itself listed but is linked to a listed person through a shareholding or directorship, the application must address that linkage directly. Under OFAC's rules, the 50 percent rule (OFAC's test under which any entity owned 50 percent or more in the aggregate by blocked persons is itself treated as blocked) operates mechanically: a 49 percent-owned entity is not blocked by that ownership alone, but the analysis does not stop there. Under OFSI, the test extends to ownership and control (the UK and EU concept under which a non-listed entity may be caught if a listed person holds effective control, even below ownership thresholds). Both tests must be worked through on the specific facts before the application is filed.
In a recent matter, a humanitarian organisation sought an authorisation to deliver essential supplies through a logistics provider whose sole director was a designated individual. The entity was not itself listed. The application addressed both the OFAC ownership threshold and the OFSI control test, confirmed that neither caught the entity on the facts, and documented that position in the application package. The authority granted the licence within a commercially workable period. The lesson is that doing the legal analysis before the application – rather than leaving it to the authority to investigate – materially shortens the process.
How Does the UN Regime Differ from OFSI, OFAC, and EU Licensing in Practice?
The UN does not grant licences to private parties, whereas OFSI, OFAC, and the EU national competent authorities all do. That structural difference defines the entire UN-specific licensing process. A business operating under US, UK, and EU implementing law is simultaneously subject to three distinct licensing regimes, each of which has implemented the same UN designation through its own national lens.
Under OFAC, a specific licence (a case-by-case authorisation to conduct an otherwise prohibited transaction) is applied for directly with OFAC in Washington. OFAC has published licensing policies for various transaction categories, and it issues both specific licences and general licences (standing authorisations permitting a defined category of transactions without a separate application). Where a general licence already covers the proposed transaction – for example, certain humanitarian-related dealings – a specific licence application may be unnecessary. Checking whether a general licence applies before filing a specific licence application is a basic step that saves significant time.
Under OFSI, the licensing function is exercised by OFSI in London, and the licence grounds are defined in the relevant thematic UK sanctions regulations. OFSI publishes licensing guidance and processes applications for specific licences across a defined set of grounds including legal expenses, basic needs, extraordinary situations, and humanitarian assistance. OFSI operates a separate licensing tracker and engages with applicants on queries after submission.
Under the EU, each Member State's competent authority (the French DGSIEE, the German Bundesamt für Wirtschaft und Ausfuhrkontrolle, and so on) holds the function for persons and transactions within that state's jurisdiction. There is no single EU licensing window. The Council issues the designation; the Member State grants the licence. This fragmentation creates operational complexity for businesses with EU-wide operations that need consistent authorisations across multiple Member States.
The practical divergence that most frequently trips up a cross-border applicant is timeline. National authorities set their own processing times, and those times vary significantly. Where concurrent applications to multiple authorities are necessary – for example, to OFSI and to an EU authority – the business must manage the risk that one authority grants a licence while the other is still reviewing. Interim operational decisions then need to be made, sometimes under commercial pressure. We regularly advise clients to submit concurrent applications from the outset rather than sequencing them, precisely because sequencing extends total elapsed time and creates legal uncertainty during the gap.
Step 4: Managing Common Risk Flags and Errors
Specific licence applications linked to the UN Consolidated List fail for a small number of recurring reasons. Identifying them in advance is more efficient than remedying them after a refusal.
The first and most common error is insufficient end-use and end-user documentation. The authority needs to be able to verify that the goods or funds will actually reach the stated recipient for the stated purpose. Vague assertions – "the goods are for humanitarian use in the region" – are consistently inadequate. The application must name the recipient, describe the distribution mechanism, and provide supporting evidence from the delivering organisation or from government counterparts where available.
The second error is failing to address the listed person's role in the transaction. If the listed individual or entity appears anywhere in the ownership chain, the distribution network, or the counterparty's governance structure, the application must confront that directly and explain why the transaction does not benefit the designated party in a prohibited manner. Omitting this creates the impression that the applicant has not conducted a proper analysis – which itself undermines credibility with the authority.
The third error is failing to check whether a general licence already covers the transaction. Filing a specific licence application for a transaction that is already covered by a standing general licence wastes the authority's time and delays the applicant. The check takes minutes. Skipping it costs weeks.
The fourth error is mismatch between the description of the transaction in the application and the underlying commercial documents. Where the authority conducts a document review, any inconsistency between the application narrative and the contract, invoice, or shipping documents undermines the application. Documents should be reviewed for consistency before filing.
A fifth risk flag, particular to UN-linked applications, is the interaction between the UN Consolidated List and the domestic implementing lists. The UN Consolidated List is maintained by the Security Council committees. National implementing lists may differ from it in timing, in the precise scope of designations, or in the accompanying conditions. An applicant must work from the correct list for the applicable regime, not from a generic UN-sourced document. In our cross-border practice, we have seen applications delayed because the applicant referenced the UN Consolidated List entry rather than the relevant domestic implementing instrument, and the authority declined to process it on that basis.
Step 5: After Submission – Timelines, Queries, and Refusals
After a specific licence application is submitted, the competent authority may issue requests for further information, and the applicant's response time to those requests is operationally critical. Delays in responding to a query extend the overall timeline by the full period of the applicant's silence. Authorities are not obliged to hold an application open indefinitely, and some have published guidance on the period within which queries must be answered before a file is treated as inactive.
Where a licence is refused, the options available to the applicant depend on the regime. Under OFSI, there is no formal appeal to OFSI itself, but a refusal can be challenged by judicial review in the UK courts. Under OFAC, an applicant can seek reconsideration and, in appropriate circumstances, pursue administrative remedies or, eventually, US court proceedings. Under the EU, the annulment route runs to the EU General Court on the grounds that the licensing refusal was unlawful under EU law. Each route has its own standing requirements, evidentiary threshold, and timeline.
The refusal of a specific licence in one jurisdiction does not automatically preclude success in another. A business that is refused by an EU national authority may still obtain an OFSI licence, because the two regimes apply different licensing grounds and policy criteria. Managing concurrent processes across regimes requires careful coordination to ensure that the position taken in one application is consistent with positions taken elsewhere.
Is a refusal always the end of the matter? Not necessarily. Where the application was refused on procedural or documentary grounds rather than on a substantive policy objection, a re-filed application with corrected documentation can succeed. Where the refusal reflects a policy objection to the transaction itself, re-filing without a material change in the facts is unlikely to produce a different result. Distinguishing between these two types of refusal is one of the most practically significant steps in the post-refusal analysis.
When to Involve Sanctions Counsel
The point at which sanctions counsel adds the most value is before the application is filed, not after a refusal. Once an application is on file, the authority has formed an initial view of the transaction. A poorly structured first application can anchor that view in a way that a subsequent re-filed application must work against.
The clearest triggers for involving counsel early are: the counterparty or its ownership chain involves a listed person; the transaction spans multiple jurisdictions and requires concurrent applications; the transaction is time-sensitive and a refusal would be commercially damaging; or the applicable UN exemption category is unclear on the specific facts. Each of these situations multiplies the cost of getting the application wrong.
The myth that specific licence applications are straightforward form-filling exercises is persistent and costly. A licence application under a UN-implementing regime is a legal submission to a regulator. It must be accurate, complete, internally consistent, and grounded in the correct legal basis. An error in the ownership analysis, a gap in the end-use documentation, or an inconsistency between the narrative and the commercial documents can convert a grantable application into a refusal. Correcting a refusal takes longer than getting the application right the first time.
The position above covers the standard case. Your facts – the counterparty, the goods, the route, the regime in play, and the applicable UN resolution – change the analysis. Contact Calder & Vance at info@caldervance.com for an early assessment of your position before the application is filed.
If a transaction has already been flagged or a prior application has been refused, an early review of the refusal grounds can preserve options. Reach our team at info@caldervance.com to discuss next steps.
Related practices
- Frozen Account Management under BIS/EAR – assessing access to frozen accounts under US export-control licensing rules
- Specific licence applications under UN: advanced issues – ownership-chain mapping and concurrent applications across regimes
- Specific vs general licence: Australia guide – comparing Australia's DFAT licensing routes under the Autonomous Sanctions regime