A trading company operating across multiple jurisdictions discovers that its intended transaction touches a counterparty connected to the UN Consolidated List. The compliance team asks the right question immediately: does a general licence authorise this, or does the firm need to stop? Getting that answer wrong – in either direction – carries serious consequences.
Under the UN sanctions regime, general licences (standing authorisations that permit a defined category of transactions without a separate application) are not issued by the UN Security Council itself. Instead, member states implement Security Council resolutions through national legislation, and it is those national implementing regimes – OFAC in the United States, OFSI in the United Kingdom, the EU Council regulations, and their equivalents elsewhere – that grant general licences. As of June 2026, eligibility for any such authorisation therefore depends on which national regime governs the transaction, what category of licence that regime has published, and whether the specific facts satisfy every condition of that authorisation.
This guide walks through the eligibility process step by step: from identifying the correct implementing regime to self-certifying reliance, managing record-keeping obligations, and knowing when the analysis exceeds what internal teams can safely handle alone.
Step 1: Identify which implementing regime governs your transaction
The governing regime is the national or supranational instrument that has converted the relevant Security Council resolution into binding domestic law – and that determination comes first, before any licence question can be answered.
The UN Security Council adopts resolutions under Chapter VII of the UN Charter. Those resolutions are not self-executing in most legal systems. They require domestic implementation. A US person looks to OFAC regulations issued under IEEPA or the relevant thematic authority. A UK person looks to OFSI and the statutory instruments made under the Sanctions and Anti-Money Laundering Act ("SAMLA"). An EU entity looks to the relevant Council Regulation and Decision. A Swiss firm looks to SECO ordinances. An Australian business looks to the autonomous sanctions regime administered by DFAT.
The critical point is this: a transaction may sit within the scope of more than one implementing regime simultaneously. A UK bank processing a payment for a US exporter to a counterparty listed on the UN Consolidated List is potentially subject to both OFSI and OFAC rules. A general licence issued by OFSI does not authorise the transaction under OFAC, and vice versa. In our experience, the single most damaging assumption compliance teams make at this stage is treating one regime's authorisation as though it covers all others.
Practical step: map every jurisdiction that touches the transaction – the nationality or location of each party, the currency of the payment, the routing of funds, and the destination of goods or services. Each jurisdiction that appears on that map is a potential source of obligation. Only once the full jurisdictional picture is drawn can eligibility analysis begin.
Step 2: Locate the applicable published general licences under each regime
Each implementing authority publishes its general licences – whether called general licences, general authorisations, or exemptions – in a defined location, and the current version controls reliance.
OFAC publishes general licences under each sanctions programme on its dedicated website pages. OFSI publishes general licences on the GOV.UK platform. The EU publishes general authorisations in the relevant Council Regulation or in amending regulations. SECO, DFAT, and the other national authorities publish their equivalent instruments through their own regulatory portals.
An important structural point: the UN itself does not publish general licences. The Security Council Committee administering a particular regime may publish humanitarian exceptions or carve-outs for specific programmes – such as the humanitarian exemptions within certain thematic regimes – but those committee-level determinations are implemented through the national regime, not applied directly by private actors. The UN Consolidated List is the reference tool for identifying listed persons; it is not itself a licensing instrument.
At this step the task is purely cataloguing. Pull every general licence published by each relevant implementing authority that appears to cover the subject matter of the transaction – for example, humanitarian transactions, personal remittances, legal services, or wind-down authorisations. The list of potentially applicable licences is the input for Step 3.
The position above covers the standard case. Your facts – the counterparty's precise ownership structure, the goods or services involved, the intermediaries in the payment chain, and the regimes in play – change the analysis materially.
For an assessment of your exposure under the UN-implementing regimes, contact Calder & Vance at info@caldervance.com.
Step 3: Test whether your transaction satisfies every eligibility condition
Eligibility is not a single question but a sequence of tests, and failure at any one test means the general licence does not authorise the transaction.
General licences in the major implementing regimes typically impose conditions across several dimensions. First, the category of transaction must match: a general licence for humanitarian assistance does not cover commercial goods shipments. Second, the relevant persons must qualify: some general licences are limited to US persons, UK persons, or EU operators; others extend to third-country persons transacting through the regime's jurisdiction. Third, there may be a counterparty condition: the listed person must be the specific type of entity the licence addresses (a government entity, a designated individual, an entity in a specified sector). Fourth, there may be a geographic condition: the authorised activity must be for the benefit of individuals in a specified territory, or goods must move to or from a particular destination.
The condition that most frequently catches businesses out is the exclusion for transactions that benefit a listed person in a way not contemplated by the licence. Consider a humanitarian general licence that permits the export of food to a particular territory. If the recipient entity – a distributor – is itself listed on the UN Consolidated List and the transaction would result in a payment to that entity, many general licences will not authorise the transaction even if the end-beneficiaries are civilians. The licensing architecture here differs by regime. OFAC's humanitarian general licences under some programmes explicitly address this. OFSI's general licences may impose narrower conditions. EU general authorisations within Council regulations often track a similar structure but may differ in the precise definition of who benefits.
Practical step: write out each condition of each potentially applicable general licence as a checklist item. Answer each item with a specific factual finding drawn from verified information about the transaction. Where a condition cannot be answered with certainty – typically because ownership or control of a counterparty is unclear – Step 3 cannot be completed, and Step 4 (ownership analysis) is required before continuing.
Step 4: Apply the ownership and control analysis to every counterparty
A general licence that authorises transactions with non-listed persons does not authorise a transaction where the counterparty is effectively a listed person under the applicable ownership and control rules.
The 50 percent rule (OFAC's rule treating entities owned 50 percent or more in the aggregate by blocked persons as themselves blocked, whether or not they appear on any list) operates independently of the general licence analysis. Under OFAC's interpretation, an entity that meets the 50 percent threshold is treated as blocked by operation of law. A general licence that does not expressly authorise dealings with such entities will not cover the transaction.
Under OFSI and the EU, the test is ownership and control: a non-listed entity may be subject to the restrictions if a listed person owns or controls it. The control element is broader than the mechanical ownership threshold under OFAC. It can capture an entity where a listed person holds less than 50 percent but exercises decisive influence over commercial decisions, governance, or finances. In our practice, clients frequently present a counterparty that falls below the OFAC 50 percent threshold but is still caught under the OFSI or EU control test – meaning that a US general licence might appear to authorise the transaction while OFSI's position differs.
Practical step: obtain the beneficial ownership register entry, the corporate registry filings, and any available UBO (ultimate beneficial owner) disclosure for each counterparty. Map ownership through every intermediate layer. Where the chain is opaque – particularly in jurisdictions with limited public disclosure requirements – seek a representation and warranty from the counterparty accompanied by supporting documentation. Document the analysis. The record of how the ownership and control conclusion was reached is itself a compliance asset.
Step 5: Satisfy any procedural conditions attached to the general licence
Many general licences are conditional not only on the substantive eligibility criteria but also on the party taking specific procedural steps before or at the time of the transaction.
Common procedural conditions across the major implementing regimes include: prior notification to the relevant authority (not approval, but notice); reporting of the transaction within a defined window after it takes place; end-use assurances from the recipient; and the maintenance of specified documentation for a prescribed record-keeping period. Under OFSI's published guidance, reporting obligations for relevant institutions handling transactions authorised under a general licence are taken seriously at enforcement stage; failure to report a transaction that the firm knew fell within scope of a general licence has been treated as a breach of the licence conditions in practice.
The OFAC record-keeping standard under IEEPA requires records to be kept for five years from the date of the transaction. OFSI's guidance similarly requires records to be retained to support any subsequent compliance review. EU regulations impose equivalent record-keeping requirements. These periods matter: an enforcement inquiry may arise long after the transaction, and the absence of contemporaneous records shifts the burden of proof onto the firm.
Practical step: before executing the transaction, prepare a compliance memorandum. It should set out: (a) the general licence relied upon, (b) the eligibility analysis for each condition, (c) the ownership and control analysis, (d) any procedural steps taken, and (e) the date the analysis was completed. File it with the transaction documentation. Attach copies of the published general licence as it appeared at the date of reliance – this matters because general licences can be revoked or amended without notice.
If a transaction has already been flagged, or a filing has been refused, an early review can preserve options that narrow with time. Reach us at info@caldervance.com.
Step 6: Handle divergence across regimes and decide whether a specific licence is needed
Where a transaction appears eligible under one regime's general licence but not under another, the stricter prohibition governs for each regime independently – and that conclusion may mean a specific licence application is the only lawful route.
This is the point in the analysis where multi-regime transactions require a decision. Suppose a UK entity determines that its proposed humanitarian transaction qualifies under OFSI's published general licence but cannot satisfy OFAC's conditions for the equivalent general licence under the applicable US programme. The UK entity cannot proceed with the US leg of the transaction on the strength of OFSI's authorisation alone. It must either restructure the transaction to remove the US nexus – currency, routing, US person involvement – or seek a specific licence from OFAC.
A specific licence (a case-by-case authorisation to conduct an otherwise prohibited transaction) is available from OFAC, OFSI, and under EU member-state procedures. The application process differs materially by regime. OFAC processes applications on its own platform; OFSI accepts applications through its published guidance route; EU member-state competent authorities operate their own procedures. Timelines are not guaranteed and vary. In our experience, applications that are incomplete or that do not clearly demonstrate why the general licence does not apply take considerably longer to resolve.
The decision matrix is as follows. If the transaction is clearly within a published general licence across all relevant regimes, document and proceed. If the transaction falls within a general licence under one regime but not another, identify whether restructuring removes the second regime's jurisdiction or whether a specific licence is necessary. If the transaction does not qualify under any published general licence, a specific licence application is the only authorised route – and operating without one while that application is pending may itself constitute a violation. Do not assume that good intent covers the gap.
Step 7: Monitor for changes and review the authorisation position at each transaction stage
A general licence that authorises a transaction today may not authorise the same transaction next month: the licensing environment under UN-implementing regimes is subject to change without the notice periods that other regulatory instruments carry.
Security Council committees can tighten or relax humanitarian carve-outs. OFAC can amend, narrow, or revoke general licences. OFSI can issue updated or superseding general licences with immediate effect. EU Council regulations can be amended as the Council's position evolves. In our cross-border practice, we regularly advise clients who have relied on a general licence for an extended transaction – a supply agreement spanning several months, a humanitarian delivery programme, a phased construction project – and discovered mid-transaction that the underlying authorisation has changed.
The practical obligation is to designate a member of the compliance function who monitors the relevant implementing authority's publication feed for each regime in scope. The monitoring cadence should match the transaction cadence: for single transactions, a check at commitment and at execution is the minimum; for ongoing programmes, a monthly check with a standing review trigger for any significant development is reasonable. Automated alert services exist for each major regime. They are a useful supplement but not a substitute for adviser-level review of whether an amendment affects a specific authorisation.
What happens if a general licence is revoked after a transaction has been authorised but before it completes? The answer differs by regime and by the specific revocation terms. Some revocations include a wind-down period; others are immediate. Understanding that distinction before it arises – rather than after – is the purpose of the monitoring step.
Related practices
- Frozen account management under BIS/EAR – managing blocked assets and navigating release procedures across US export-control programmes
- General licence eligibility – supplementary analysis – deeper treatment of specific eligibility scenarios and procedural edge cases
- Humanitarian authorisation under Australia's regime – a step-by-step guide to DFAT licensing for humanitarian transactions
A common misconception: the UN list is a licensing instrument
Many compliance teams treat the UN Consolidated List as though relying on it – verifying that a counterparty does not appear – is itself a form of authorisation. It is not.
The UN Consolidated List is a reference tool. It aggregates the designations made by Security Council committees across all active UN sanctions regimes. It does not issue licences, authorise transactions, or provide a legal basis for proceeding. A counterparty's absence from the Consolidated List does not mean the counterparty is free of sanctions exposure: national implementing regimes may list additional persons (autonomous sanctions), and the ownership and control tests can capture unlisted entities.
Conversely, a counterparty's presence on the Consolidated List does not necessarily mean that every transaction with that counterparty is prohibited: the applicable implementing regime may have published a general licence that covers the specific category of transaction you are considering. Screening and licensing are complementary tools, not alternatives. Both must be applied.
In a recent matter, a manufacturing business had been relying on a clean screening result against the UN Consolidated List as its primary compliance step. The counterparty's parent entity – which held a controlling interest but did not appear on any published list – fell within the EU Council regulation's ownership and control test. The transaction was prohibited regardless of the Consolidated List result. We assisted the client in restructuring the commercial arrangement, preparing the compliance record, and submitting a notification under the applicable regime. The matter was resolved within the compliance window available to the client. No outcome is guaranteed, but early engagement consistently preserves more options than late engagement.