A humanitarian organisation operating across multiple jurisdictions discovers that a local partner appears on the UN Consolidated List. Funding has been routed. Staff are already deployed. The question is immediate: can the programme continue, and what authorisation is required before the next disbursement?
The UN sanctions regimes contain humanitarian carve-outs and specific exemption procedures, but these are not self-executing. Each Security Council committee administers its own rules, and the procedural path – request, documentation, timeline, and scope of relief – varies by regime. As of June 2026, no single UN instrument provides a universal humanitarian licence; each committee must be approached on its own terms, and most pathways require prior written authorisation rather than after-the-fact notification.
This guide sets out the procedure for obtaining humanitarian and NGO authorisations under the UN system, compares the principal UN committee approaches with the parallel OFAC, OFSI, and EU tracks that frequently run alongside them, identifies the most common pitfalls, and explains when specialist counsel should be involved.
Step 1: Identify the correct Security Council committee and the applicable exemption provision
The first decision in any humanitarian authorisation matter is identifying which Security Council committee administers the relevant designations and what exemption mechanism that committee maintains. The UN runs more than a dozen sanctions regimes, each with its own committee, its own consolidated list, and its own set of exemptions. Humanitarian carve-outs are not uniform across them.
Some committees maintain standing exemptions for humanitarian activities by recognised organisations – principally UN agencies, the International Committee of the Red Cross, and accredited NGOs. Others require case-by-case approval, meaning an organisation must submit a formal request and receive a written decision before conducting the activity. A small number of regimes operate without a published humanitarian exemption at all, placing the burden on the requesting organisation to establish why the relevant resolution permits the activity.
In our experience, organisations most frequently misidentify the committee at this stage. The UN Consolidated List aggregates designations from across all regimes, but it does not indicate which committee approved a given listing or which exemption procedure applies. Cross-referencing the designation against the relevant Security Council resolution is the only reliable method. The practical consequence of approaching the wrong committee – or assuming a standing exemption exists where it does not – is that disbursements or operations may proceed without the required authority.
A second structural point: some committee exemption procedures require the request to be submitted through a UN member state rather than directly by the NGO. The routing requirement is committee-specific and is set out in the relevant procedural guidelines. Organisations that submit direct requests where state-channel routing is required will find their application procedurally deficient from the outset.
Step 2: Assemble the documentation package
A complete documentation package is the single most important determinant of whether a humanitarian exemption request moves through committee review without a request for further information. Incomplete applications stall. In our cross-border practice, the most time-consuming part of the process is frequently not the committee's decision but the client's internal document-gathering phase, which can extend the overall timeline by several weeks.
The core elements committees expect to see are consistent across most regimes, even where the precise format differs:
- A detailed description of the humanitarian activity, including the target beneficiary population, the geographic scope, and the timeline of the programme.
- Identification of the listed entity or person involved, with an explanation of the specific nexus – whether the listed party is a counterparty, a supplier, a government authority whose consent is required, or an entity through whose territory goods or funds must pass.
- The monetary value of any funds or goods involved, denominated in the relevant currency, and the payment or delivery mechanism.
- Evidence of the requesting organisation's status – UN accreditation, NGO registration in the relevant jurisdiction, and any government endorsement or co-funding documentation.
- An end-use statement and, where goods are involved, a description of the goods and their humanitarian purpose.
- Where the request is routed through a member state, the member state's covering communication to the committee.
Some committees also request a written undertaking that the funds or goods will not be made available to listed persons beyond what the authorisation specifically permits. This is not a waiver of the prohibition; it is a condition of the exemption. The distinction matters because any deviation from the scope of the authorisation – a change in delivery route, an increase in the amount, a substitution of a counterparty – may require a fresh application or a variation request.
What documents cannot substitute for each other? A general mandate letter from a UN agency does not satisfy the end-use statement requirement. A prior exemption granted under a different committee's regime does not carry over. We regularly advise clients that documentation prepared for an OFAC specific-licence application, while useful as a factual source, is structurally different from what the UN committee process requires and should not be submitted directly without adaptation.
Step 3: Submit the request and manage the review period
Once the documentation package is complete, the request is submitted to the relevant committee – either directly or through the member state channel, as the committee's procedural rules require. The committee secretariat acknowledges receipt, but acknowledgement is not approval. The substantive decision is taken by the committee's member states, which operate by consensus in most cases.
Review timelines at the committee level are not fixed by a published deadline in the same way as OFAC's specific-licence procedure or OFSI's licensing process. In practice, timelines vary considerably by regime and by the complexity of the request. Urgent humanitarian situations can sometimes be handled on an expedited basis, but expedited review is not guaranteed and requires a specific request with supporting justification. Organisations that plan their operational timelines assuming a rapid turnaround without that basis may find themselves in a position where operations are delayed pending committee decision.
During the review period, the committee may seek clarification. The requesting party – or its member state intermediary – should be in a position to respond promptly. A delayed response to a committee query will extend the review period and may, in some regimes, result in the request being treated as withdrawn after a defined period of inactivity. Tracking committee queries and responding within the relevant window is an operational compliance task that should be assigned to a named individual within the organisation.
The position above covers the standard case. Your facts – the specific regime, the counterparty relationship, the routing of funds, the member state involved – change the analysis materially. For an assessment of your exposure under the UN system, contact Calder & Vance at info@caldervance.com.
How do parallel OFAC, OFSI, and EU authorisations interact with the UN process?
An NGO operating across jurisdictions will almost never face the UN process in isolation. The same listed person or entity that triggers a UN committee exemption request will frequently also appear on the SDN List (OFAC's list of Specially Designated Nationals and blocked persons), on the OFSI Consolidated List, or on an EU Council regulation list. Each of those regimes maintains its own licensing procedure, and a UN committee authorisation does not serve as authority under OFAC, OFSI, or the EU.
This is the cross-border structural point that humanitarian organisations most frequently misunderstand. The assumption – that a UN humanitarian exemption, once granted, covers all downstream legal exposure – is incorrect. OFAC administers its own humanitarian authorisation process under the relevant IEEPA-based programme, and its specific licence (a case-by-case authorisation to conduct an otherwise prohibited transaction) must be applied for separately. OFSI in the UK operates a licensing regime under the Sanctions and Anti-Money Laundering Act ("SAMLA") and the relevant thematic regulations, with its own documentation and evidential requirements. The EU Council regulation applicable to the relevant regime provides for member-state licensing, with national competent authorities administering the procedure in their respective jurisdictions.
In practice, the UN committee authorisation, once granted, is an important evidential document for parallel OFAC and OFSI applications. OFAC has confirmed in its published guidance that a UN exemption does not substitute for an OFAC licence but that it is a relevant factor in the licence assessment. OFSI takes a similar approach. We have acted for NGOs and humanitarian bodies who submitted coordinated parallel applications to the UN committee, OFAC, and OFSI simultaneously, using the UN committee documentation as the common evidentiary foundation. This sequencing – submitting in parallel rather than waiting for the UN decision before approaching OFAC and OFSI – is generally the more operationally efficient route, provided the documentation package is prepared to meet the requirements of each authority.
Does the EU position differ? It does, in one important respect. EU Council regulations typically include a humanitarian exemption directly in the text of the regulation, which may allow certain payments and transfers to proceed without a separate licence, subject to notification or reporting requirements to the relevant national competent authority. The scope and conditions of that in-text exemption vary by regulation. Where it applies, it can provide faster operational clearance than a full specific-licence procedure, but it does not eliminate the reporting obligation and does not extend to activities or counterparties outside its precise scope.
The divergence between the regimes on this point – OFAC requiring a specific licence in most cases, OFSI requiring a licence under SAMLA, the EU potentially allowing an in-text exemption with notification – creates a situation where an NGO must manage three different procedural tracks, on three different timelines, with three different documentation standards. Misjudging which track is relevant to which element of the operation is a common cause of unintentional non-compliance.
What are the principal risk flags in humanitarian and NGO authorisations?
The most significant risk in humanitarian authorisations is not the failure to apply for an exemption – most organisations know they need one. The risk is the gap between the scope of the authorisation granted and the operational activities actually conducted. Committees and regulators grant exemptions on the basis of the facts as presented. When the operation deviates from those facts – because a delivery route changes, a counterparty is substituted, a programme is extended, or additional funds are required – the original authorisation may no longer cover the activity.
Consider the following categories of risk flag that we regularly see in practice:
- Scope creep: the operation expands beyond the geographic area, beneficiary population, or monetary value described in the application. The exemption does not automatically extend.
- Counterparty substitution: a local implementing partner changes, and the new partner is itself a listed entity or has a listed beneficial owner. The original authorisation does not cover a different counterparty.
- Indirect exposure: funds pass through a local bank or payment intermediary whose parent entity is listed. The 50 percent rule (OFAC's rule treating entities owned 50 percent or more by blocked persons as themselves blocked) and the equivalent ownership and control tests under OFSI and the EU can catch this.
- Dual reporting obligations: some regimes require the organisation to report that it has used a humanitarian exemption within a defined period. Missing a reporting window can convert a lawful use of an exemption into a technical breach.
- Expiry without renewal: committee authorisations are time-limited. Operating under an expired authorisation is equivalent to operating without one. Renewal applications should be submitted with sufficient lead time, typically several weeks before expiry, to avoid a gap.
- Staff and volunteer exposure: in some regimes, the prohibition extends to individuals within the organisation who are themselves listed. The humanitarian exemption covers the programme; it does not necessarily cover an individual designated person's involvement in it.
If a transaction has already been flagged, or an authorisation has expired and operations have continued, an early legal review can preserve options that narrow with time. Contact Calder & Vance at info@caldervance.com for a confidential review.
The myth that a "good cause" protects against enforcement
A persistent misconception in the humanitarian sector is that enforcement authorities treat the charitable or humanitarian purpose of an organisation as a de facto defence against sanctions liability. This misunderstands how the regimes work.
OFAC, OFSI, and the EU do each recognise humanitarian purpose as a relevant factor in their enforcement calculus – in practice, it affects the severity of a penalty or the decision to pursue civil rather than criminal action. It does not, however, eliminate liability for an unlicensed transaction. The legal question is whether a prohibited activity occurred without the required authorisation; the reason for the activity goes to mitigation, not to the existence of the violation. OFSI's published enforcement guidance confirms that a breach of a financial-sanctions prohibition can result in a civil monetary penalty regardless of the purpose behind the payment. The position is analogous under the relevant IEEPA-based programmes administered by OFAC.
In our experience, humanitarian organisations that have relied on this assumption find that the process of regularising their position – through a VSD (voluntary self-disclosure to a regulator), an after-the-fact licence application, or a detailed response to an enforcement query – is considerably more demanding than obtaining the authorisation at the outset would have been. The administrative and reputational costs of a retrospective process also affect an organisation's relationships with donors, partner governments, and co-implementing agencies in ways that a timely licence application does not.
The correct posture is not to assume that the regime will accommodate humanitarian intent; it is to obtain the authorisation before the activity begins, document the scope of the authorisation carefully, and monitor the operation against it throughout.
When to involve sanctions counsel in the authorisation process
Not every humanitarian authorisation requires external legal support. An established UN agency with a dedicated sanctions compliance team and a current relationship with the relevant Security Council committee secretariat may be able to manage a straightforward renewal application in-house. But several situations consistently warrant the involvement of specialist sanctions counsel.
Complexity arises where the designated party is central to the operation – a sole local government authority, a critical infrastructure operator, or an entity that controls access to the beneficiary population. In these cases, the exemption request is not a formality; it requires a careful analysis of the scope of the designation, the exact nature of the nexus, and the available exemption mechanisms across each relevant regime.
Multi-regime exposure – where the same operation requires parallel UN committee, OFAC, OFSI, and EU authorisations – is consistently a situation where uncoordinated applications create gaps. We have acted for humanitarian bodies where an OFSI application was filed on different facts than the UN committee request, resulting in inconsistencies that the authorities queried and that required additional rounds of correspondence to resolve. Coordinated, sequenced applications, prepared on a common evidentiary platform, avoid that outcome.
Urgent situations – where operations are already under way, where an authorisation has lapsed, or where a counterparty designation has occurred mid-programme – require rapid triage, an assessment of whether a temporary cessation is required, and a decision on whether to make a VSD alongside the licence application. These decisions have consequences that benefit from experienced input at the point of decision, not after the strategy has been set.
For NGOs and implementing organisations planning new humanitarian programmes in areas of sanctions exposure, early engagement – at the design stage, before counterparty relationships are formalised – produces the best outcomes. Restructuring a programme after the fact, to accommodate an authorisation that was not obtained at the outset, is both more costly and more disruptive than building the compliance path into the programme design.
Related practices
- Frozen account management under BIS/EAR – managing blocked-account obligations and compliance under US export-control rules.
- Licensing costs and fee structures in Australia – practical guide to sanctions-licence fees and process under the applicable Australian regime.
- Australian sanctions licence – advanced considerations – deeper analysis of Australian autonomous sanctions licensing and cross-regime interaction.