An aid organisation has secured funding and a delivery contract for a programme in a sanctions-affected territory. Its banking partner then signals that payment to the local implementing partner is frozen. The legal question is immediate: does an EU humanitarian authorisation cover this transaction, and if not, which instrument does?
EU sanctions regulations contain specific carve-outs and licensing pathways for humanitarian and non-governmental activities. Those pathways are real and workable. They are also conditional, variable by sanctions regime, and frequently misread. As of June 2026, the EU maintains distinct humanitarian provisions across its major sanctions regimes, each with its own scope, procedural requirements, and competent-authority designation.
This guide sets out how EU humanitarian and NGO authorisations work in practice, where they sit in relation to the UK and US equivalents, and what compliance steps a business or organisation must complete before a transaction can proceed.
What the EU humanitarian carve-out actually covers
EU humanitarian authorisations are instrument-specific standing permissions, or member-state licences, that allow transactions otherwise prohibited by Council regulations to proceed where the purpose is humanitarian delivery or recognised NGO activity. They do not override the underlying prohibition; they authorise an exception to it.
The scope differs by sanctions regime. Some Council regulations contain a self-executing general derogation. It permits competent authorities to authorise transactions for humanitarian purposes without a separate application for each payment. Others require a specific authorisation granted on a case-by-case basis by the member state competent authority. In our cross-border practice, this distinction is the first and most consequential question a finance team or treasury department must answer before structuring a payment.
Recognised humanitarian actors typically include bodies with United Nations mandates, International Committee of the Red Cross affiliates, and NGOs operating under formal institutional donor agreements. Commercial contractors supporting humanitarian programmes occupy a more complicated position. Their eligibility depends on whether they fall within the definition of "humanitarian assistance" as applied by the relevant regime, or whether their role is ancillary rather than primary. That line is not always clear from the text of the regulation alone.
The position above covers the standard case. Your facts – the counterparty, the territory in question, the banking route, the regime in play – change the analysis. For a preliminary assessment of your transaction's eligibility, contact Calder & Vance at info@caldervance.com.
How the authorisation procedure works step by step
Obtaining an EU humanitarian authorisation requires engaging the competent authority of the member state in which the applicant is established, or through which the relevant transaction flows, and presenting evidence of humanitarian purpose against the applicable regulatory test.
The procedural sequence typically follows this structure:
- Regime identification. Confirm which Council regulation governs the target territory and the specific transaction. Different programmes have different derogation provisions. An application pitched at the wrong instrument will be returned.
- Competent authority mapping. Identify the relevant national authority. Competent authorities vary by member state and, within a state, by transaction type. In Germany, France, and the Netherlands, for example, different bodies handle financial-sanctions licensing and trade-related authorisations. Applications lodged with the wrong body are delayed, sometimes significantly.
- Eligibility pre-assessment. Before filing, confirm that the applicant and the intended beneficiary both satisfy the regime's humanitarian-actor definition. A short written analysis at this stage prevents a full application being rejected on threshold grounds.
- Application package preparation. Prepare the formal application, including evidence of organisational mandate, a programme description, a counterparty ownership-and-control screen, a payment-flow narrative, and, where required, end-use undertakings. In our experience, incomplete packages are the primary cause of delays at this stage.
- Submission and query management. Submit to the competent authority and manage supplementary information requests. Authorities handling humanitarian applications often raise queries on beneficial-ownership structure or on the identity of the ultimate beneficiary population. Prompt and precise responses reduce processing time.
- Licence issuance and conditions review. Once granted, read the licence conditions with care. Most authorisations include conditions on record-keeping, permitted transaction values, permitted counterparty categories, and reporting obligations. Breach of a condition voids the protection of the authorisation.
- Ongoing monitoring and renewal. Humanitarian authorisations are typically time-limited. Build a renewal calendar and monitor regulatory changes. Council regulations are amended, sometimes rapidly; a derogation that exists today may be narrowed or reformulated on short notice.
The timeline for processing varies by member state, by regime complexity, and by the completeness of the application. Some authorities have published indicative timescales; many have not. Plan conservatively and build buffer time into programme delivery schedules.
Which EU regimes contain humanitarian provisions, and what do they require?
Not every EU sanctions programme treats humanitarian activity identically. Across the major programmes currently in force, three broad categories of provision appear.
First, programmes that include a direct member-state authorisation route for humanitarian purposes. Under these regimes, the competent authority has explicit power to grant a time-limited licence permitting an otherwise-prohibited financial transfer or service where it is directed at humanitarian relief. The applicant must demonstrate both its own status and the humanitarian character of the end use.
Second, programmes that contain a self-executing derogation for certain enumerated actors. Where a United Nations body, a recognised international humanitarian organisation, or a bilateral development agency is the direct contracting party, the transaction may proceed under the derogation without a prior member-state authorisation. The obligation then falls on the transacting party to satisfy itself – and to document the basis – that the conditions of the derogation are met. This is a compliance determination, not a rubber stamp.
Third, programmes under which no explicit humanitarian derogation exists. In those cases, the only route is a specific authorisation application, and the grounds for grant are more constrained. Several regimes require the applicant to demonstrate that the humanitarian need cannot be met by any alternative means not subject to a prohibition. That is a demanding test.
The practical implication: do not assume that a derogation available under one EU programme applies under another, even where the factual situation looks identical. We regularly advise organisations that have mapped their compliance position against the wrong instrument and then discover the mismatch when a bank escalates the transaction.
Cross-border comparison: how does the EU position differ from UK and US regimes?
A cross-border operator – a UK-incorporated NGO with EU-based donor funding delivering a programme through a US-dollar payment corridor – can face three overlapping humanitarian authorisation regimes simultaneously. They do not align.
Under the UK regime, OFSI administers financial-sanctions licensing. General licences for humanitarian purposes exist and are published. They typically allow a wider range of operators than EU equivalents, but carry strict conditions on reporting and record-keeping. An NGO relying on an OFSI general licence must satisfy itself, and be able to demonstrate, that each payment falls within its terms. The UK Export Control Joint Unit handles export-related authorisations separately from OFSI financial licences; the two regimes do not merge into a single humanitarian clearance.
Under the US regime, OFAC issues both general licences and specific licences for humanitarian activity. General licences for food, medicine, and certain NGO programmes exist under several sanctions programmes. They are narrow in scope and contain carve-outs for activities deemed to benefit restricted parties. Where a US-dollar correspondent-banking chain is involved, the US general licence must cover the transaction even if the EU and UK positions are already clear. OFAC's extraterritorial reach means that a European NGO transacting in dollars is within US jurisdiction for these purposes regardless of where the payment originates. This is a point many compliance teams underestimate until a US correspondent bank rejects the payment.
The divergence between regimes on who qualifies as a "humanitarian actor" is material. The EU definition, as applied by member-state competent authorities, tends to be institution-specific. OFAC's approach is more activity-based. OFSI takes an intermediate position. Where all three regimes apply, the programme must satisfy the most restrictive applicable definition.
If a transaction has already been flagged by a correspondent bank or a payment has been blocked, an early review can preserve options that narrow with time. Contact Calder & Vance at info@caldervance.com to discuss the cross-regime position.
What risk flags should compliance teams identify before applying?
Humanitarian authorisations are not automatic. Several recurring risk patterns emerge in applications that are delayed, refused, or later challenged.
Ownership-and-control exposure in the delivery chain. An NGO implementing partner that itself has ownership links to a designated entity does not become eligible for humanitarian treatment simply by acting in a humanitarian programme. The ownership and control test – the EU and UK analysis of whether a non-listed entity is caught through a listed person's ownership of it – applies to counterparties in the delivery chain, not only to the direct recipient. A layered ownership structure requires a full mapping exercise.
Commingling of humanitarian and commercial flows through a single account or legal entity is a second significant risk flag. Competent authorities expect clear functional separation between humanitarian programme accounts and other operational flows. Where that separation is absent, the humanitarian character of individual transactions becomes difficult to demonstrate, and a good-faith defence in any enforcement review is correspondingly weakened.
Sub-grant chains present a third concern. An EU humanitarian authorisation covers the named parties and specified transactions within its terms. Where the implementing NGO sub-grants to a local partner organisation, that sub-grant must itself be within scope. In our experience, programme managers sometimes assume that an umbrella authorisation extends automatically to all downstream partners. It does not; each link in the delivery chain requires assessment.
Finally, consider the banking correspondent's independent position. A bank operating the payment route will conduct its own sanctions screening and may apply a stricter threshold than the regulatory minimum. A valid humanitarian authorisation does not compel a bank to process the transaction; it removes the legal prohibition but does not override the bank's own risk appetite. Early engagement with the correspondent bank – before the programme is designed around a particular payment route – avoids discovering this constraint at the point of first disbursement.
Common misconceptions in humanitarian and NGO authorisation practice
One persistent belief is that humanitarian status provides blanket protection from sanctions liability. It does not. An authorisation, whether a general or specific licence, permits a defined category of activity within defined conditions. Transactions outside those conditions remain prohibited. Liability can arise where an organisation exceeds the scope of its authorisation, fails to maintain the required records, or continues operating under an expired instrument.
A second misconception is that UN-mandated bodies operate entirely outside the sanctions regime. They do not. UN agencies benefit from particular derogations under most EU programmes, but those derogations are themselves conditional and may not extend to contractors or commercial sub-suppliers engaged by the UN body. A company supplying goods or services to a UN humanitarian programme must assess its own position independently; it cannot assume that the UN's status extends to it.
A third misunderstanding concerns timing. Some organisations treat the application as a post-hoc step – something to regularise after a programme has begun. The EU regime does not support this approach. Conducting a prohibited transaction in the expectation that authorisation will follow, or relying on a licence application as a substitute for a granted licence, exposes the transacting parties to liability for the intervening period. An authorisation must be in place before the transaction proceeds, unless a self-executing derogation unambiguously applies.
When to involve sanctions counsel
Not every humanitarian payment requires an external legal review. Several situations, however, consistently benefit from early counsel involvement.
Where the delivery chain includes a counterparty with any ownership or beneficial-interest link to a listed person, the analysis moves beyond standard compliance screening and requires a legal opinion on whether the ownership-and-control test is triggered. Counsel can map the structure, assess the thresholds, and advise on whether an authorisation application or a transaction restructuring is the appropriate response.
Where a programme spans two or more sanctions regimes – EU, UK, and US, for example – the practical complexity of satisfying all three simultaneously is material. Each regime has its own authorisation form, its own competent authority, and its own licence conditions. We have acted for organisations that structured a programme assuming regime equivalence, then discovered mid-delivery that one regime required a separate application their compliance team had not made. Bringing counsel in at programme design stage is significantly less disruptive than correcting an omission during delivery.
Where a payment has been blocked, a correspondent bank has requested a sanctions compliance certificate, or a competent authority has raised queries about an existing authorisation, immediate advice is warranted. The statutory windows for responding to regulator queries are short, and an uncoordinated response can complicate a position that was initially manageable.
For a confidential review of your programme's authorisation position, contact Calder & Vance at info@caldervance.com.
Related practices
Related practices
- Frozen account management under BIS/EAR – unblocking and managing restricted accounts under US export-control rules
- EU humanitarian authorisations: advanced practice guide – deeper treatment of multi-programme applications and delivery-chain screening
- Humanitarian authorisations under the Japan regime – procedural requirements and competent authority process in Japan