A treasury team at a multinational receives instructions to release a payment to a counterparty. A routine screening run returns a match against the UN Consolidated List (the list of individuals and entities subject to measures adopted by the United Nations Security Council). The payment is not large. The goods are not military. Yet the compliance officer knows that releasing funds without authority could constitute a breach of obligations that flow from Security Council resolutions implemented in every major jurisdiction. The question is not whether to pause – that is automatic. The question is how to obtain the authority to proceed, and how quickly that authority can be secured.
Payment authorisations under the UN sanctions regime require a business to work through the implementing authority in its own jurisdiction – typically OFAC, OFSI, or the relevant EU competent authority – because the Security Council itself does not issue individual licences to private parties. The procedural route, the required documentation, and the timing vary considerably depending on which national regime applies. As of June 2026, the UN Consolidated List contains designations across more than a dozen thematic and country-specific committees, each operating under its own resolution and review procedures.
This guide walks through the authorisation process step by step: establishing which committee and which implementing regime governs the payment, building the application, managing the review, and handling the cross-regime considerations that arise when multiple jurisdictions have simultaneously frozen the same funds.
Step 1: Identify the Governing Committee and the Applicable National Regime
The first step is to determine which Security Council committee administers the designation on the Consolidated List, and which national regime has implemented that committee's measures in the jurisdiction where the funds sit. The UN Security Council operates through a series of thematic and situation-specific sanctions committees; each committee corresponds to a distinct resolution and imposes a distinct set of measures – asset freeze, travel ban, arms embargo, or some combination.
Understanding the committee matters because the humanitarian exemption routes and the permitted-payment categories differ between committees. A listed person designated under one committee's resolutions may have access to basic expenses authorisations that a person listed under a different committee's resolutions does not. This distinction is frequently missed in the early stages of a payment hold, and missing it wastes time on the wrong procedural track.
Once the relevant committee is identified, the analysis shifts to the national implementing regime. Security Council resolutions bind member states under Chapter VII of the UN Charter, but they take effect in domestic law through implementing legislation. In the United States, the measures are given effect through OFAC and the relevant programme regulations under IEEPA or TWEA. In the United Kingdom, they are implemented through OFSI under SAMLA and the thematic regulations. In the European Union, they take effect through Council regulations. For Switzerland, SECO administers the measures under the relevant national ordinances. In our cross-border practice, we regularly advise clients who assume the UN route and the domestic route are separate – they are not. The domestic implementing authority is the relevant decision-maker for any payment authorisation.
Practical consequence: if a payment originates in London, the business applies to OFSI. If the funds sit in a US correspondent account, OFAC is the relevant authority. If the counterparty's account is in an EU member state, the competent authority designated under the relevant EU regulation applies. In a genuinely multi-jurisdictional transaction, all three may need to be addressed simultaneously or in sequence.
Step 2: Determine Whether an Exemption or a Licence Is Required
Not every restricted payment requires a bespoke licence application. The second step is to identify whether the proposed payment falls within a standing exemption permitted by the relevant Security Council resolution and reflected in the domestic implementing rules, or whether a specific licence – a case-by-case authorisation – is required.
Security Council resolutions routinely permit member states to authorise payments for basic expenses: food, rent, medicine, legal fees, and other essential needs. Many resolutions also contain exemptions for extraordinary expenses and for payments connected with judicial proceedings. These exemption categories are replicated, with variations, in national implementing law. Under the UK rules administered by OFSI, a specific licence (a case-by-case authorisation to conduct an otherwise prohibited transaction) can authorise payments that fall within categories recognised under the relevant thematic regulations. Under OFAC, general licences (standing authorisations permitting a defined category of transactions without a separate application) can cover some routine payments even where a target is designated.
The practical distinction matters for speed. Where a general licence applies under OFAC – for example, for certain legal services or for payments to meet basic living expenses – no prior approval is required, provided the payment fits squarely within the licence's terms and the conditions are met. Where no general licence covers the payment, a specific licence application is required, and the processing timeline extends accordingly. OFSI and the EU competent authorities do not operate the same general-licence architecture as OFAC; most payment authorisations in those regimes require a positive decision on a specific application.
Does your payment fit an existing exemption, or does it require a new authority? Answering that question early determines the urgency and the shape of everything that follows.
The position above covers the standard case. Your facts – the committee that made the designation, the jurisdiction where funds are held, the nature of the payment, and the identity of all parties in the chain – change the analysis materially. For an initial assessment of the applicable route, contact Calder & Vance at info@caldervance.com.
Step 3: Prepare the Application Package
The application package for a specific-licence authorisation under any of the major implementing regimes must demonstrate three things: that the payment purpose falls within a recognised permitted category, that the listed person or entity is correctly identified, and that no unlisted party in the transaction chain is itself subject to restrictions.
Documentation requirements are broadly similar across OFAC, OFSI, and the EU competent authorities, though the specific form and the required certifications differ. The core components of a well-prepared package are set out below.
- Identification of the designated party: full legal name, date of birth or registration, aliases, address, and the UN reference number appearing on the Consolidated List entry.
- Description of the proposed transaction: amount, currency, payment route, purpose, and the identity of all intermediary institutions.
- Evidence of purpose: for a basic-expenses application, invoices or proof of the underlying obligation; for a legal-fees application, a retainer agreement or court-issued demand; for an extraordinary expenses application, supporting documentation proportionate to the amount.
- Confirmation of the implementing authority's requirements: OFSI requires a completed application form. OFAC takes a written licence request in a prescribed format. EU competent authorities differ by member state, though the substantive assessment is anchored to the Council regulation.
- Ownership and control mapping: a statement confirming that no other party to the transaction is listed or 50 percent or more owned by a listed person.
In our experience, the most common reason for delay at this stage is an incomplete description of the payment purpose. Authorities reviewing applications for basic-expenses authorisations under UN-derived measures apply the exemption narrowly. A generic description of "operational costs" is insufficient. The application must identify the specific obligation – the rent invoice, the utility bill, the medical provider – and connect it to the expenditure requested.
A separate and frequently overlooked requirement is the correspondent-bank position. Where funds must pass through a US correspondent, the US bank may require its own OFAC comfort before processing even a payment that OFSI has already licensed. We regularly advise clients who obtain an OFSI licence and then discover that the payment stalls again at the US correspondent stage. Planning for this in advance, and structuring the application to address both regulators' requirements, avoids a second delay.
Step 4: Submit to the Competent Authority and Manage the Review
Submission triggers the authority's formal review period, and managing that period actively – rather than waiting – is the difference between a payment released in weeks and one that stalls for months.
Under OFSI, the relevant thematic regulations specify the review timelines that apply in the first instance. OFAC processes specific licence applications within timelines that vary with complexity and workload; in our cross-border practice, straightforward humanitarian-purpose applications tend to move faster than complex commercial-payments requests, but no timeline is guaranteed and OFAC does not publish binding processing targets for specific licences. EU competent authorities vary by member state; timelines at some authorities are shorter than at others, and the complexity of the UN-derived measures being applied is a relevant factor.
Active management of the review means several things in practice.
- Acknowledge receipt and confirm the application reference number promptly.
- Monitor for requests for further information; these are common, and a slow response to a query restarts the effective clock.
- If the designated person's circumstances are changing – a medical emergency, a court deadline, an imminent eviction – notify the authority and provide updated documentation.
- Where a US correspondent-bank position is also required, track both applications in parallel rather than sequentially.
One practical point on the UN-level route: it is possible, in certain cases, to request that the relevant Security Council committee itself authorise an exemption through the national implementing authority. This arises where a resolution provides that the committee must approve extraordinary-expenses authorisations rather than delegating approval to the implementing state. In those cases, the domestic authority forwards the application to the committee. The timeline for committee review is distinct from, and in addition to, the domestic review timeline. Identifying at the outset whether the relevant resolution requires committee-level approval – rather than merely state-level approval – is therefore a critical early step. If a transaction has already been flagged or a filing has been refused, an early review can preserve options that narrow with time. Contact us at info@caldervance.com.
Step 5: Understand How Regimes Diverge – and Why It Matters for Your Payment
A payment caught by UN-derived measures in one jurisdiction is almost always simultaneously caught by the implementing rules of every other jurisdiction that has given effect to the same Security Council resolution. The divergence between those implementing regimes is not merely procedural; it can determine whether the payment can be released at all, and under what conditions.
Three divergences are particularly significant for payment authorisations.
First, the ownership and control test – the test for whether a non-listed entity is caught because a listed person controls it – differs between OFAC, OFSI, and the EU. OFAC applies a mechanical threshold: an entity is blocked when listed persons own it 50 percent or more in the aggregate. OFSI and the EU apply a broader test that includes control as well as ownership, meaning an entity with no listed shareholder above 50 percent may still be caught under UK or EU rules if a listed person exercises control through contractual, management, or other arrangements. For payment purposes, this means a counterparty cleared under the OFAC ownership test may not be cleared under OFSI's assessment. The stricter prohibition governs in any jurisdiction where it applies.
Second, the licensing architecture differs. OFAC's general-licence system can provide immediate authority for certain payment categories without a separate application. OFSI and EU competent authorities rely primarily on specific licences, meaning prior approval is almost always required. This asymmetry matters when a payment involves a US and a non-US leg: the US leg may be covered by a general licence while the non-US leg remains held pending a specific authorisation.
Third, the humanitarian-exemption categories are not uniform. The categories of basic expenses recognised in one implementing regime may be narrower or broader than those in another, even though both derive from the same Security Council resolution. The language of the resolution sets a floor; national implementations can be more generous in their permitted categories, but not less restrictive than the resolution requires.
For businesses operating across more than one jurisdiction, the rule is straightforward: map all implementing regimes that apply to the transaction, identify the most restrictive position in each relevant category, and design the authorisation strategy to satisfy all of them.
Step 6: Record-Keeping, Reporting, and Post-Authorisation Obligations
Obtaining a licence does not end the compliance obligation. Businesses authorised to make a restricted payment under a UN-derived sanctions regime have continuing obligations: to make the payment strictly in conformity with the licence terms, to record the transaction, and in some regimes to report to the competent authority once the payment has been made.
Under OFSI, licensed persons are required to maintain records and, where the licensing terms require it, to report to OFSI on the use of the licence. Under OFAC, certain licences contain specific conditions – for example, a requirement to retain documentation for a minimum period or to notify OFAC of the completed transaction. In our experience, post-licence compliance is the part of the process that businesses most often under-resource. The licence is seen as the goal; the conditions attached to it are treated as administrative detail. This is a mistake. A licence used outside its stated terms is not a defence; it is itself a potential violation.
Record-keeping standards apply independently of whether a specific licence was required. Where a business has determined that a payment falls within a general licence or within a basic-expenses exemption without a bespoke authorisation, it should nonetheless document its analysis: the screening result, the basis on which the exemption was assessed to apply, the payment details, and the date of the decision. That documentation is the first line of defence if the transaction is later questioned by a regulator or by a counterparty bank.
Reporting obligations in some regimes also extend to the discovery of listed persons' assets even where no payment is being made. Firms that discover they are holding funds or assets that belong to or are controlled by a listed person may have an obligation to notify the competent authority irrespective of any licence application. The precise scope of this obligation differs between the US, UK, and EU regimes, and between the thematic UN committees whose measures are being applied.
Risk Flags and When to Involve Counsel
Several risk flags indicate that a payment authorisation matter requires specialist input from the outset rather than after a problem has developed.
- A Security Council committee-level approval requirement: where the relevant resolution reserves extraordinary-expenses authorisations to the committee itself, the domestic application is only the first stage. Committee reviews operate on UN institutional timelines that differ from domestic regulatory timelines.
- Multiple implementing jurisdictions: a payment that touches a US correspondent, a UK account holder, and an EU originating institution requires coordinated applications across three regulatory authorities simultaneously. Managing that coordination without specialist support substantially increases the risk of an error in one jurisdiction that voids the authorisation in another.
- An ownership-and-control question under OFSI or EU rules: where a counterparty is not itself listed but may be controlled by a listed person, the domestic authority's assessment of control will determine whether a licence is needed at all. The analysis requires a documented ownership map and a legal assessment of control under the applicable test.
- A legal-fees payment for a designated individual: this is a recognised permitted category in most regimes, but the conditions – including the prohibition on passing the licensed fee proceeds to the listed person or to a blocked entity – are strictly applied. Getting the structure of the legal-fees licence wrong can expose both the paying client and the receiving law firm to enforcement risk.
- A payment that has already been declined by a correspondent bank: a bank's decline of a payment does not resolve the underlying compliance position. If the payment is in fact permissible under the applicable regime – because a licence exists or because an exemption applies – the refusal may be a de-risking (a financial institution exiting a relationship to avoid sanctions exposure) decision rather than a regulatory conclusion. Understanding the difference, and advising the institution on the legal position, is a distinct task from obtaining the licence itself.
A myth that frequently delays action in payment authorisation matters is the belief that UN designations are different in kind from OFAC or EU designations, and that the UN route is therefore simpler or more accessible. In practice, UN-derived measures are implemented through exactly the same domestic licensing authorities as other sanctions programmes. The procedural demands are equivalent. The UN committee layer adds complexity rather than reducing it, because committee-level approvals operate independently of and in addition to domestic authorisation timelines.
Related practices
- Frozen account management under BIS/EAR – managing blocked accounts and licence applications under US export-control rules
- Release of blocked funds: Australia – step-by-step guide to the Australian DFAT process for releasing frozen assets
- Release of blocked funds: Australia (advanced) – further analysis of complex Australian blocking scenarios and review routes