Calder & Vance International Sanctions & Compliance Counsel

Licensing & Authorizations · UAE

General licence eligibility under UAE: step by step

A trading house based in Europe finalises a contract with a counterparty in the Gulf. The goods are dual-use items. The internal compliance team identifies that the transaction may touch a sanctioned sector. Someone asks: is there a general licence that covers this? Under the UAE regime, that question is more nuanced than it first appears. The UAE maintains its own autonomous sanctions regime, and its approach to standing authorisations differs materially from the models familiar to practitioners working with OFAC or OFSI.

General licence eligibility under the UAE regime turns on a combination of factors: the nature of the designated party or prohibited activity, the category of transaction, and the specific authorisation published by the relevant UAE authority. As of June 2026, the UAE's Executive Office for Control and Non-Proliferation administers the regime, and practitioners should verify the current list of available standing authorisations before relying on any of them. The regime is not a mirror of US or UK practice, and eligibility conditions are not always interchangeable.

This guide walks through the eligibility assessment in sequential steps, maps the key cross-regime differences, identifies the most common risk points, and explains when early legal advice changes the outcome.

Step 1: Understand how the UAE sanctions regime is structured

The UAE operates an autonomous sanctions regime administered principally through the Executive Office for Control and Non-Proliferation ("EOCN"), with additional layers arising from the UAE's implementation of UN Security Council measures. The legal basis is found in the relevant UAE counter-terrorism and anti-money-laundering legislation together with the UAE's Cabinet decisions on the domestic list and the implementation of UN-listed designations.

Two lists are relevant to any eligibility analysis. First, the UN Consolidated List – designations issued by the Security Council committees under Chapter VII resolutions, which the UAE implements directly. Second, the UAE's own domestic list of designated persons and entities, maintained by the EOCN. A general licence issued under one of these lists does not automatically apply to the other. The threshold question in any eligibility assessment is therefore: which list, or which legal basis, generates the prohibition you are trying to work within?

In our cross-border practice, we see multinationals assume that a general authorisation available under the OFAC model – or a general licence issued by OFSI – signals an equivalent standing authorisation in the UAE. That assumption is wrong and potentially costly. The UAE regime has its own taxonomy. Step one is confirming which prohibitions are engaged and under which authority they arise.

Step 2: Identify whether a standing authorisation exists for your transaction category

A general licence (a standing authorisation that permits a defined category of transactions without a separate application) exists in the UAE regime, but the categories are narrower and less elaborated than those familiar from OFAC practice. Common categories where standing authorisations are published include: humanitarian transactions, transactions involving international organisations, certain legal services, and maintenance of basic account functions for designated persons.

The key practice point is that you cannot assume a category exists. You must identify the specific published authorisation, confirm that it is currently in force, and read its conditions precisely. The UAE does not maintain a single consolidated general-licence register in the way that OFAC publishes its general-licence index. Authorisations may be embedded in Cabinet decisions, in EOCN guidance documents, or in regulatory circulars from the Central Bank of the UAE for financial transactions.

What does this mean in practice? It means a compliance team working a UAE-related transaction must check multiple sources, not a single public register. It also means that the absence of a published authorisation is itself a meaningful finding: if no general authorisation covers the category, the default position is prohibition, and a specific authorisation must be sought.

The position above covers the standard case. Your facts – the counterparty, the goods or services, the route, the regime in play – change the analysis. For a first assessment of whether a standing authorisation applies to your transaction, contact Calder & Vance at info@caldervance.com.

Step 3: Map the eligibility conditions against your transaction facts

Once a potentially applicable standing authorisation is identified, the next step is a systematic eligibility check. This is not a casual read of the authorisation header. Each condition must be mapped, in writing, against the specific facts of the transaction.

Eligibility conditions typically address five variables. First, the type of designated party: is the authorisation limited to individuals, entities, or both? Second, the nature of the transaction: does it cover payment, delivery, provision of services, or all of these? Third, the geographic scope: does the authorisation extend to transactions involving UAE-listed parties operating outside the UAE? Fourth, the end-use or end-user conditions: are there restrictions on what the counterparty may do with what it receives? Fifth, the documentation and reporting obligations: must you notify the EOCN, retain records, or make a contemporaneous declaration?

Failure at any one of these five variables means the transaction does not fall within the authorisation. In our experience, the end-use and reporting conditions are the variables that most often catch businesses by surprise. A transaction that looks clean on the party-type and category tests can still fall outside the authorisation if a reporting obligation is not met.

We regularly advise exporters and financial institutions that the mapping exercise should produce a written eligibility memorandum. If a transaction is later challenged by the EOCN or by a correspondent bank, the memorandum is your primary evidence that a good-faith eligibility assessment was conducted.

How does the UAE eligibility test differ from OFAC, OFSI, and EU approaches?

Cross-regime comparison is essential for any business that operates across multiple jurisdictions. The UAE regime shares the prohibitory structure of the major regimes, but its authorisation practice diverges in ways that matter operationally.

Under OFAC, general licences are published individually, numbered, and consolidated on a publicly searchable index by programme. The authorisation is self-executing: if you meet the conditions, you may proceed without any further application or notification unless the licence text requires one. OFAC also issues specific licences on a case-by-case basis, and its published guidance on each programme is extensive. The UAE does not offer the same depth of published programme-specific guidance.

Under OFSI, the UK model relies more heavily on specific licences than on general ones. General licences under OFSI cover narrower categories, and OFSI has historically been more restrictive in publishing broad standing authorisations. The UK regime imposes a reporting obligation: where a relevant firm knows or suspects that a customer is a designated person, it must report to OFSI. This obligation sits alongside, and is separate from, any licensing condition.

Under the EU, general authorisations – sometimes framed as derogations in the relevant Council regulation – are regime-specific and conditions vary significantly. The EU has moved in recent years toward more explicit published derogations, particularly for humanitarian and legal services. But the EU also applies its own ownership and control test (the test for whether a non-listed entity is caught through a listed person) which turns on control as well as ownership, creating a different perimeter than the OFAC 50 percent rule.

The UAE's position is closer in structure to the UN model: authorisations are published through the relevant committee or through domestic implementing legislation, and the list of standing authorisations is shorter than under the OFAC or EU models. Practitioners moving between regimes should treat each as requiring its own fresh eligibility analysis.

If a transaction has already been flagged, or a filing has been refused, an early review can preserve options that narrow with time. Reach Calder & Vance at info@caldervance.com for a confidential review.

Step 4: Address the cross-border extraterritorial dimension

A standing authorisation issued under the UAE regime operates within that regime. It does not authorise the transaction under US, UK, or EU law. This distinction is not theoretical. A European financial institution processing a payment for a transaction that is authorised under the UAE regime must separately confirm that the same transaction does not breach OFAC regulations, OFSI rules, or the relevant EU Council regulation.

The extraterritorial reach of OFAC's secondary-sanctions programmes is the most significant cross-border risk in this analysis. Under certain US programmes, non-US persons who conduct transactions with designated parties can themselves be exposed to US measures, even if the transaction is lawful under the law of the jurisdiction in which it takes place. A UAE general licence provides no protection against that exposure.

In our experience, correspondent banking is the practical chokepoint. A UAE entity may hold an authorisation permitting a transaction under the domestic regime. But if that transaction is routed through a US dollar correspondent, the correspondent will apply OFAC's rules, not the UAE's. The transaction may be blocked or rejected at that point regardless of the UAE authorisation's validity.

The practical step here is to map the payment route and identify every jurisdiction whose rules apply at each link in the chain. Where a US dollar leg is involved, OFAC eligibility must be assessed independently. Where a European bank is in the chain, EU and UK rules must be confirmed. The UAE authorisation is one layer of a multi-layer compliance picture, not the whole answer.

See also our related analysis on export-control licensing and frozen account management: frozen account management under BIS/EAR, which addresses the interaction between US export-control licensing and sanctions prohibitions for transactions where both layers are engaged.

Step 5: Document, record, and manage the ongoing conditions

Eligibility for a general licence is not a one-time determination. Most standing authorisations under any regime impose ongoing conditions. Under the UAE regime, these typically include record-keeping obligations, periodic verification that the counterparty remains within the authorised category, and – in some cases – a duty to report specific transactions to the EOCN or to the UAE Central Bank.

Record-keeping is the area where enforcement risk accumulates silently. A business that relies on a general authorisation without maintaining a contemporaneous file of its eligibility determination, the specific authorisation text, and the transaction details is exposed if the EOCN or a correspondent later requests evidence. The inability to produce that documentation is itself a compliance failure, separate from any question about whether the original transaction was authorised.

What records should you hold? At minimum: the text of the general authorisation relied upon as of the date of the transaction; the eligibility memorandum mapping the transaction facts to the authorisation conditions; evidence of the counterparty screening conducted at the time; and a record of any notifications or reports made to the relevant authority. These records should be held for a period consistent with the applicable retention rules of each jurisdiction – under the UAE regime, verify the current period before relying on a fixed number of years.

We have acted for financial institutions and trading companies in circumstances where a general authorisation was validly relied upon at the time of a transaction but where the contemporaneous documentation could not be reconstructed. The cost of that gap – in regulatory time, legal fees, and reputational exposure – consistently exceeds the cost of good record-keeping at the point of the transaction.

Common mistakes and when to involve counsel

Several recurring errors define the risk profile of general licence eligibility work under the UAE regime. First, assuming equivalence with OFAC practice. The UAE regime is not a derivative of OFAC's model, and a compliance professional who approaches it as if it were will miss conditions that are genuinely UAE-specific.

Second, failing to check UN list implementation separately from the domestic list. A standing authorisation covering UAE-listed parties may not extend to UN-listed parties implemented into UAE law through a separate legal instrument. The two populations can overlap, but they are legally distinct.

Third, treating a general authorisation as a substitute for transaction-specific legal analysis. A general authorisation defines a category. Whether a specific transaction falls within that category is a legal question, not a mechanical one. Complex ownership structures, multi-leg transactions, and transactions involving services rather than goods all require careful analysis.

Fourth, neglecting the cross-regime overlay. As described above, UAE eligibility does not substitute for OFAC, OFSI, or EU analysis where those regimes also apply.

When should you involve external counsel? At minimum in four situations: when the transaction involves a party on both the UAE domestic list and a major Western regime's list simultaneously; when the applicable general authorisation is ambiguous about whether the transaction category is covered; when a correspondent bank has rejected a transaction that you believe is authorised; and when the EOCN or another UAE authority has made a direct inquiry. In our practice, early involvement consistently produces better outcomes than late engagement after a transaction has been blocked or a query has escalated.

A common objection we hear is that the UAE regime is less developed than OFAC or OFSI, and therefore the compliance burden is lower. That is a myth worth correcting. The UAE has significantly expanded its sanctions enforcement capacity in recent years, consistent with its commitments to international standard-setting bodies. The reduced volume of published guidance relative to OFAC does not signal a reduced enforcement posture. If anything, the lower volume of published guidance increases the importance of careful eligibility analysis, because there is less public precedent to draw on.

Related practices and further reading

Related practices

Frequently asked questions

What are the steps to rely on a general licence under UAE?
The steps are: confirm which list and legal basis generates the prohibition; identify the specific published standing authorisation covering your transaction category; map each eligibility condition against your transaction facts in writing; assess the cross-regime overlay (OFAC, OFSI, EU) for each jurisdiction in the payment and delivery chain; satisfy and document any reporting and record-keeping obligations; and monitor for changes to the authorisation's conditions for the life of the transaction. Each step requires a documented output, not just a mental check.
What is the most common mistake in general licence eligibility?
The most common mistake is assuming that a general authorisation covers a transaction category without reading and mapping the specific conditions. Practitioners often read the headline description of an authorisation and proceed without working through the end-use restrictions, geographic scope, and reporting requirements. A transaction that satisfies the category test but fails a conditions test is not authorised. The documentation of the mapping exercise is also frequently omitted, which creates a separate enforcement exposure if the transaction is later reviewed.
How does UAE differ from other regimes here?
The UAE regime maintains a shorter list of published standing authorisations than OFAC and applies a dual-list structure (domestic list plus UN implementation) that requires separate analysis. Unlike OFAC, there is no single consolidated public register of general authorisations indexed by programme. Unlike OFSI, the UAE regime does not follow the same specific-licence-heavy model. Practitioners familiar with EU derogation practice will find the UAE's authorisation conditions differently structured. Cross-regime work therefore requires treating the UAE eligibility assessment as a standalone exercise, not an adaptation of another regime's analysis.

Talk to Caldervance

For a scoped view of your exposure, contact info@caldervance.com.

Discuss your matter

This publication is general information and does not constitute legal advice. For advice on your situation, contact info@caldervance.com.