A humanitarian organisation operating across multiple jurisdictions discovers that a planned cash transfer – routed through a regional bank and earmarked for medical supplies – cannot proceed. The recipient country sits within a sanctions perimeter. The bank has flagged the transaction. The organisation's compliance team now faces a question that is simultaneously urgent and technical: does the UAE's applicable sanctions regime provide an authorisation route, and if so, what does the procedure actually require? Answering that question correctly, and quickly, can determine whether the programme delivers at all.
As of June 2026, the UAE operates its own autonomous sanctions regime, administered primarily through the Executive Office for Control and Non-Proliferation and the UAE Central Bank's financial-intelligence function. Humanitarian and NGO authorisations are available under the applicable UAE country regime, but the process is distinct from OFAC general-licence pathways, OFSI licensing, or EU humanitarian derogations. The application must be structured to meet the UAE's specific statutory criteria, and the cross-border implications – particularly where OFAC or EU rules also apply – must be addressed in parallel.
This guide walks through the authorisation process step by step: the legal basis, the eligibility assessment, the documentation package, the submission procedure, the cross-regime overlay, and the risk flags that counsel typically see at each stage.
Step 1: Understand the UAE's Legal Basis for Humanitarian Authorisations
The UAE's sanctions regime rests on its own national legal instruments – distinct from, though influenced by, UN Security Council obligations – and the Executive Office for Control and Non-Proliferation ("EOCN") is the principal competent authority for licensing and authorisation questions, operating alongside the Central Bank for financial-sector matters. The starting point for any humanitarian or NGO authorisation is a clear-eyed reading of the applicable national instrument as currently in force, not a transposition of OFAC or EU rules onto the UAE position.
UAE sanctions law incorporates UN Security Council Consolidated List obligations by reference. Where a counterparty, a transit hub, or a delivery partner appears on the UN Consolidated List, the UAE regime treats that listing as binding. Any authorisation package must therefore address UN obligations as a threshold matter before reaching the UAE-specific authorisation criteria. This layering – UN obligations beneath UAE national rules – is a structural feature practitioners must map before assembling documentation.
The applicable regime distinguishes between transactions that are prohibited outright and those for which a specific or general authorisation is available. Humanitarian and NGO activities typically fall in a category for which a case-by-case authorisation can in principle be sought. The burden, however, rests with the applicant to demonstrate that the proposed activity meets the statutory criteria – and that burden is substantially higher than many NGO compliance teams expect when they first engage with the UAE process.
Step 2: Assess Eligibility Before Filing Anything
Eligibility for a humanitarian authorisation under the UAE regime is not automatic for organisations that hold a general or special consultative status with the United Nations, are accredited by a recognised international body, or operate under a government-backed mandate. The UAE evaluates each application on its own facts. Organisations that assume a UN mandate or ICRC status confers automatic approval are routinely surprised by the level of scrutiny applied.
The eligibility assessment has three practical components. First, the organisation itself must not appear on any UAE, UN, or OFAC-related list – and neither may its key personnel, its local delivery partners, or its principal funders. In our experience, this beneficial-ownership and personnel screen is where NGO authorisation requests most often stall before formal submission. Many organisations run cursory name-matching on their own entity without screening the full ownership and funding chain.
Second, the proposed activity must qualify as humanitarian in the applicable regulatory sense. The UAE regime, like OFSI and the EU regime, draws a distinction between relief of essential human need and development or capacity-building programmes. A vaccine distribution programme in an affected population will typically qualify. A governance training programme run by the same organisation may not – or may require a separate legal basis. Practitioners must characterise the activity precisely, not generically.
Third, the financial routing must be identified in advance. Which bank in the UAE is processing the transfer? Does that bank itself have a compliance policy that is more restrictive than the UAE regulatory minimum? Bank-level de-risking – where an institution exits or refuses transactions even when the regulatory position would permit them – is a significant operational obstacle in the humanitarian space. Identifying the banking channel before submitting the authorisation request is not merely good practice; it is often dispositive. A grant of authorisation from EOCN is of limited practical use if the correspondent bank refuses to process the payment regardless.
Step 3: Assemble the Documentation Package
The documentation package for a UAE humanitarian authorisation is more detailed than the standard EU or OFSI humanitarian licence application. Practitioners who submit under-documented packages face substantial delay – and, in some cases, refusal on procedural grounds alone.
A complete package typically covers the following elements:
- Applicant identity documentation – constitutional documents, registration certificates in the country of incorporation and in the UAE if the organisation has a local presence, and a current list of board members and senior officers, together with identification for each.
- Beneficial ownership and funding-source disclosure – a chart showing, at minimum, any entity or individual that contributes more than a specified share of the organisation's funding, with passports or equivalent for natural persons. The UAE regime applies a control test that looks through corporate and charitable structures in a manner broadly comparable to the EU ownership and control test.
- Programme description – a precise description of the humanitarian activity, the target beneficiary population, the geographic scope, and the timeline. Vague programme descriptions ("humanitarian assistance in [region]") are routinely returned for clarification.
- Financial flow diagram – a diagram showing every transfer leg: origin bank, correspondent banks, local delivery agent, and ultimate recipient. Where cash is used at the last mile, the mechanism for tracking and reporting must be described.
- Partner due-diligence records – screening records for each delivery partner, local sub-grantee, and implementing agency, with date of screen and list versions checked. These records must be current – screens run more than a short period before submission may be regarded as stale.
- End-use and diversion-risk assessment – a written assessment of the risk that goods or funds will be diverted from the stated humanitarian purpose, together with proposed mitigation measures (monitoring, reporting, clawback provisions).
Preparing this package is not a one-person task. In a recent matter, an international health NGO sought to deliver medical equipment through a UAE-registered entity to a population in a restricted region. The initial documentation was strong on programme description but weak on beneficial-ownership disclosure for the local delivery partner. We rebuilt the ownership section, conducted a fresh screen, and resubmitted. The resubmission progressed without further procedural challenge. The lesson is straightforward: invest in the documentation before submission, not in remediation after a refusal.
Step 4: Submit to the Correct UAE Authority – and Anticipate the Process
The submission route for a humanitarian authorisation under the UAE regime depends on the nature of the transaction. Financial transfers go through the EOCN and – for bank-intermediated payments – typically require a parallel notification or filing with the UAE Central Bank. Non-financial authorisations (for example, the delivery of goods or services) may be handled through the EOCN alone, though sector-specific authorities may also have a role depending on the goods in question.
There is no publicly published standard processing timeline for UAE humanitarian authorisation requests. Unlike OFAC, which gives indicative timelines for specific-licence applications, or OFSI, which publishes guidance on its licensing queue, the UAE regime does not commit to a defined window. In practice, straightforward applications from well-documented organisations can move within a matter of weeks. Complex cases – those involving layered ownership, novel delivery mechanisms, or counterparties with any adverse-screening history – take considerably longer. Planning for that uncertainty is itself a compliance obligation: an organisation that structures a programme on the assumption of a short authorisation window and then faces delay has, in effect, created an operational breach risk.
Applicants should expect queries. The EOCN may request supplementary information, clarification of the ownership chart, or additional screens. Respond to queries promptly and completely. Partial responses or requests for extensions without good reason can stall the file materially. Designate a single point of contact within the organisation – someone with full visibility of the documentation – and make sure that person can respond within a short window of a query being received.
One question that arises regularly: can the UAE authorisation process be run in parallel with OFAC specific-licence applications or EU derogation requests, where the activity also touches those regimes? The answer is yes – and often it must be. The regimes do not wait for one another. A parallel-track strategy requires careful coordination to ensure that the descriptions of the activity, the financial flows, and the due diligence are consistent across all filings. Inconsistencies between a UAE submission and an OFAC application for the same programme are a serious risk-management problem.
Step 5: Manage the Cross-Regime Overlay
The UAE regime does not operate in isolation. Any humanitarian or NGO activity that involves a UAE nexus – a UAE bank, a UAE-registered entity, a UAE-based staff member – will need to be assessed against all other regimes that could apply. The governing principle across major regimes is that the stricter prohibition governs: where the UAE permits an activity but OFAC prohibits it without a licence, the OFAC prohibition controls for any US-person involvement.
The key cross-regime pressure points for UAE-nexus humanitarian work are:
- OFAC (US): If the humanitarian programme involves any US-person participation – a US-incorporated NGO, a US-dollar transaction, a US-citizen employee – OFAC jurisdiction attaches. OFAC does maintain general authorisations for certain humanitarian activities, and specific-licence routes exist. But the OFAC analysis must be run separately and in full. A UAE authorisation does not satisfy OFAC requirements.
- OFSI (UK): UK-chartered NGOs, UK-domiciled funders, or sterling-denominated transfers bring OFSI into the analysis. OFSI has its own humanitarian licensing track, with its own criteria and its own processing timeline. The UK regime's ownership and control test for listed-person influence over the implementing partner is also distinct from the UAE approach and must be analysed on its own terms.
- EU Council regulations: EU-member-state-based NGOs, euro-denominated payments, or any transaction touching an EU-person entity engage the relevant EU Council regulation. The EU provides humanitarian derogations within its sanctions regulations, but the conditions, the authority, and the procedure differ by member state. A Brussels-based NGO submitting a UAE authorisation request should also be mapping its EU obligations simultaneously.
- UN Consolidated List: As noted, the UAE regime incorporates UN List obligations. But the UN process for adding and removing listings, and the Focal Point mechanism for de-listing requests, operates independently. Where a delivery partner or counterparty appears on the UN Consolidated List, neither the UAE authorisation nor any OFAC or OFSI licence resolves the UN-level prohibition. That requires a separate track.
We regularly advise NGOs and their funders on exactly this multi-regime mapping. The organisations most at risk are those that treat the UAE authorisation as the primary filing and assume that other regimes follow automatically. They do not.
For organisations seeking to understand the UN Consolidated List process in depth, Calder & Vance has published a companion guide on humanitarian authorisations under the UN regime and a related analysis covering practical steps for UN-level humanitarian authorisation requests.
Step 6: Recognise the Risk Flags That Practitioners See Most Often
Certain patterns appear repeatedly across UAE humanitarian authorisation matters. Identifying them in advance avoids the delays, the remediation costs, and – in the worst cases – the compliance failures that follow from missing them.
Risk flag 1: The local delivery partner has not been screened at the entity and personnel level. NGOs regularly screen their own entity, their named bank, and the end beneficiaries. The local implementing partner – the organisation that actually distributes goods or cash at the last mile – is sometimes screened only by name, with no review of its directors, funders, or sub-contractors. The UAE regime's ownership-and-control analysis reaches through to that level. So does OFAC.
Risk flag 2: The financial route passes through a jurisdiction with its own sanctions overlay. A payment that runs from a UAE bank through a transit jurisdiction before reaching the delivery region may encounter a separate sanctions perimeter at the transit point. Correspondent-bank compliance teams in transit jurisdictions have their own screening obligations. A UAE authorisation does not bind those banks. Map the full payment route before filing.
Risk flag 3: The programme description in the authorisation does not match the programme description in the grant agreement. When these documents diverge – and they often do, because the authorisation application was drafted before the grant agreement was finalised – the organisation is potentially operating outside the scope of its authorisation. This is a self-inflicted compliance problem. Lock down the programme description before submitting the authorisation, and treat it as a constraint on the final grant document.
Risk flag 4: The organisation assumes the authorisation, once granted, is indefinite. UAE authorisations, like OFSI licences, are typically time-limited and may be subject to conditions. Monitoring, reporting, and renewal obligations attach at grant. The organisation must build those obligations into its programme management from day one, not discover them at the expiry date.
Risk flag 5: Senior leadership is not aware that the authorisation covers only the described activity. NGO compliance teams sometimes secure the authorisation and then operate on the implicit assumption that it covers programme variations, geographic expansions, or new delivery partners. It does not. Material changes to the activity require a fresh assessment and, typically, a new or amended authorisation. This is a governance and communication issue as much as a legal one.
What happens when one of these flags materialises mid-programme? The answer depends on the specific regime, the nature of the deviation, and how quickly it is identified. Early identification and a structured response – including, in appropriate cases, a VSD (voluntary self-disclosure to the relevant regulator) – can materially limit the consequences. Delay or concealment makes them worse. Have you built an incident-escalation pathway into your humanitarian programme governance?
Step 7: When to Involve Counsel – and What to Ask For
Not every humanitarian authorisation request requires external counsel from the outset. Well-resourced organisations with experienced in-house teams and a clean sanctions history can often manage the eligibility assessment and the documentation assembly internally. The moment to bring counsel in is when the matter presents any of the following:
- A delivery partner, funder, or key personnel member with any adverse screening result – even a potential false positive.
- A financial route that touches more than one sanctions perimeter simultaneously.
- A programme that has already started and for which no authorisation was obtained.
- A query or a refusal from the EOCN or the Central Bank.
- A parallel OFAC, OFSI, or EU filing requirement.
- A board or donor that is asking for a legal opinion on compliance.
In each of these situations, the cost of early counsel engagement is a fraction of the cost of a delayed programme, a failed authorisation, or a regulatory inquiry. The position above covers the standard case. Your facts – the counterparty structure, the delivery mechanism, the banking channel, the regime perimeter – change the analysis materially.
For organisations that also need to manage export-control requirements alongside financial-sanctions authorisations – for example, where humanitarian programme goods are dual-use items or medical devices with classification questions – the overlap between licensing tracks requires a coordinated approach. Calder & Vance's work on BIS/EAR licensing and account management addresses the US export-control dimension that can arise where equipment is sourced from, or transits through, US-jurisdiction supply chains.
A common misconception is worth addressing directly: many organisations believe that holding a valid tax exemption or charity registration in a Western jurisdiction gives them a preferred or automatic track for UAE humanitarian authorisations. It does not. The UAE regime evaluates applications on their merits under its own criteria. International charity status is relevant background context; it is not a substitute for the substantive eligibility assessment or the documentation package described in this guide.
If a transaction has already been flagged, or an application has been returned or refused, an early review preserves options that narrow with time. Contact Calder & Vance at info@caldervance.com for a confidential review of your authorisation position.
Related practices
- Frozen account management and BIS/EAR licensing – US export-control and account-management services for cross-border programmes
- Humanitarian authorisation under the UN regime – step-by-step guide to the UN Consolidated List and Security Council humanitarian carve-outs
- UN humanitarian authorisation: practical steps – companion analysis for UN-level filing and de-listing questions