An international NGO prepares to deliver medical supplies into a conflict-affected area. Its legal team identifies that the destination falls within the scope of at least three separate sanctions regimes – one imposed by the United States under IEEPA, one by the European Union by Council regulation, and one by the United Kingdom under the Sanctions and Anti-Money Laundering Act. Each regime carries its own humanitarian authorisation pathway. Each has its own application form, its own competent authority, and its own conditions. Miss one, and the shipment stops at the border or the payment is blocked by the correspondent bank.
Humanitarian and NGO authorisations across borders require a parallel-track application process: one submission per relevant regime, timed to align approvals before operational deadlines. No single "global humanitarian licence" exists. As of June 2026, the three principal regimes – OFAC in the United States, OFSI in the United Kingdom, and the EU Council regime – each maintain standing general licences or general authorisations for defined categories of humanitarian activity, but the scope, conditions, and reporting obligations differ materially.
This guide sets out, step by step, how to identify which regimes apply, how to build and submit the authorisation package for each, how to manage the parallel timelines, and where the risk of non-compliance is highest for organisations operating across jurisdictions.
Step 1: Identify which regimes are triggered before you apply
The first step is a jurisdiction map: a structured analysis of every regulatory regime that has a legal claim over the proposed activity, based on the organisation's nationality, its personnel, its banking relationships, and the destination of goods or funds. Getting this map wrong at the outset means either missing a required authorisation entirely or duplicating effort on regimes that do not bite.
OFAC's rules apply to US persons and to transactions that touch the US financial system – including US dollar clearing through a US correspondent bank, even where neither the payer nor the payee is in the United States. A European NGO moving US dollars through a New York correspondent to fund humanitarian operations is a US-person transaction for OFAC purposes. That connection is frequently overlooked.
OFSI's rules apply to UK persons – individuals ordinarily resident in the UK, UK-incorporated entities, and persons in the UK – and to conduct that takes place in the UK. A UK-based charity with international field offices must map every transaction that passes through its UK accounts or is authorised by a UK-based signatory.
The EU regime applies to all persons within EU territory, to EU nationals wherever they are, and to EU-registered entities. A German-incorporated relief organisation operating in a non-EU country with a subsidiary registered in the United States must consider both the EU and OFAC layers for the same payment run.
For organisations with a footprint in Switzerland, Canada, or Australia, SECO, Global Affairs Canada, and DFAT each maintain their own humanitarian licensing mechanisms under their respective national instruments. In our experience, smaller NGOs with limited legal resource routinely analyse only the jurisdiction in which their headquarters sits, missing the secondary triggers entirely. That is where enforcement exposure begins.
Practical checklist for the jurisdiction map:
- Nationality and registration of the legal entity funding the operation
- Currency of all transactions – US dollar flows trigger OFAC regardless of entity nationality
- Location of the bank accounts and the correspondent banks used
- Nationality of key personnel authorising or executing the transactions
- Destination country and whether it falls within a country-specific or thematic regime
- Whether the goods or services to be delivered are subject to export-control rules as well as financial-sanctions rules
Export controls sit alongside sanctions and are frequently underweighted by humanitarian actors. Medical devices, certain communications equipment, and dual-use items may require a separate export licence under the EAR (BIS, United States), the Export Control Order (ECJU, United Kingdom), or the EU dual-use rules. A sanctions authorisation does not substitute for an export licence. Both are needed.
Step 2: Determine whether a general authorisation covers your activity
Before filing a specific-licence application, determine whether a standing general authorisation – one that covers your activity without a separate submission – already exists under each relevant regime. All three principal regimes maintain some form of general humanitarian authorisation, but the scope is not identical and the conditions attached to each differ significantly.
Under OFAC, general licences (standing authorisations that permit a defined category of transactions without a separate application) for humanitarian activity are programme-specific. They are published as part of each sanctions programme's regulations. Some programmes carry broad humanitarian general licences. Others do not. Whether a general licence covers the activity depends on the specific programme triggered by the destination or the counterparty – not on a universal humanitarian carve-out that applies across all OFAC programmes. Check each programme separately.
Under OFSI, general licences for humanitarian activity have been issued under certain thematic regimes. OFSI's published guidance sets out the conditions attached to each general licence: which activities fall within scope, which entities can rely on it without prior registration, and whether a reporting obligation attaches. In our experience, organisations assume that a general licence issued under one OFSI regime will cover activity under a neighbouring regime. That assumption is frequently wrong.
Under the EU regime, Council regulations for certain programmes contain humanitarian exemptions that operate as general authorisations. These permit member state competent authorities (national ministries or central banks, depending on the member state) to authorise certain activities, or they permit the activity directly without prior approval subject to conditions and reporting. The key distinction is between activities that are self-executing under the exemption and those that require prior notification or authorisation from the national competent authority. The text of the relevant regulation must be read carefully for each programme.
Where a general authorisation covers your activity, document your reliance on it. Keep a record of the analysis showing why the activity falls within the scope of the general licence or exemption, the date of the analysis, and the personnel who carried it out. General licences can be amended or withdrawn. Build a monitoring calendar to track changes to every general authorisation you rely on.
Step 3: Prepare a specific-licence application for each regime where no general authorisation applies
Where no general authorisation covers the planned activity, a specific licence (a case-by-case authorisation to conduct an otherwise prohibited transaction) must be sought from each competent authority. Each regime has its own submission format, evidentiary standards, and decision timeline.
For an OFAC specific licence, the application is submitted through OFAC's online licensing portal. The application must identify the statutory basis, the specific parties, the amounts and transaction types, the duration requested, and the humanitarian purpose. OFAC will consider whether the applicant has an adequate compliance programme in place. Where OFAC issues a specific licence, it will typically carry conditions – reporting of transactions conducted, end-use monitoring, due diligence on sub-grantees. Failure to comply with licence conditions is itself a sanctions violation. The decision timeline is not fixed by statute and can vary considerably; plan around this uncertainty when scheduling operations.
For an OFSI specific licence in the United Kingdom, the application is submitted to OFSI by email with supporting documentation. OFSI applies the test set out in the relevant thematic regulations: the activity must fall within a permitted purpose category, and OFSI must be satisfied that the licence is consistent with the objectives of the relevant sanctions regime. OFSI's published guidance on the licensing process describes the information required and the standard conditions attached to humanitarian licences. Plan for OFSI's processing times, which are published periodically in its annual report and may be subject to revision.
For an EU authorisation, the application goes to the competent authority of the relevant member state, not to the Council of the EU directly. Each member state's competent authority applies the Council regulation's criteria, but administrative practice varies. A German NGO applying through the German competent authority and a French branch of the same organisation applying through a French authority may receive decisions at different times and under slightly different conditions, even though both apply the same Council regulation. Coordinating these timelines is a practical challenge for multi-jurisdiction operations.
Common documentation required across all three regimes:
- Description of the humanitarian programme – beneficiaries, geography, type of activity
- Identification of all parties to the transactions (including sub-grantees and local delivery partners)
- Due diligence records on counterparties, including ownership and control information
- Banking and payment channels to be used
- Proposed amounts, transaction types, and duration of the authorised activity
- Existing compliance policies and screening procedures
- Prior sanctions licences or enforcement history, if any
The quality of the counterparty due diligence is the single element that most frequently causes OFAC to return an application for supplemental information, extending the timeline. Build the due diligence file before you submit, not after.
How does cross-border differ from single-regime applications?
A cross-border authorisation structure differs from a single-regime application in three material respects: parallel timelines that do not synchronise, conditions that conflict between regimes, and reporting obligations that aggregate into a significant administrative burden if not managed centrally.
On timelines: OFAC, OFSI, and the relevant EU member state authorities each run their own review clocks. OFAC's processing times for humanitarian licences are not statutory and can extend over several months for complex applications. OFSI publishes indicative timescales and aims to process straightforward applications within a defined period, but complex applications take longer. EU member state authorities are subject to their own administrative law requirements and may have statutory decision deadlines under national law. The result is that a three-regime authorisation package will rarely be approved simultaneously. Operations planning must accommodate a gap between the first approval and the last.
On conflicting conditions: one regime's licence may permit a category of payments to a local delivery partner that another regime's licence conditions restrict. OFAC, for example, may permit the transfer of funds to an entity in the destination country subject to enhanced due diligence, while an OFSI licence for the same activity may require prior notification of each transaction over a defined threshold. Where conditions conflict, the stricter prohibition governs – you may not use one regime's licence to justify conduct that another regime's licence conditions prohibit.
On reporting: OFAC licence conditions typically require periodic reporting of transactions conducted under the licence. OFSI may require notification of transactions and annual compliance reports. EU authorisations may carry their own notification requirements under national administrative law. For an organisation managing a multi-year humanitarian programme across all three regimes, the reporting calendar can generate a substantial volume of concurrent obligations. Centralise the compliance function and maintain a master obligations register from the date each licence is issued.
What about secondary sanctions? Where OFAC's programme carries secondary-sanctions provisions – rules that can affect non-US entities that conduct certain activity with designated persons – a non-US NGO that obtains only an EU or UK authorisation remains exposed to OFAC's secondary-sanctions risk if it engages US persons or US-dollar transactions at any point in the transaction chain. In our practice, we regularly advise European and international NGOs on this secondary layer, which often requires either an OFAC licence or a restructured payment route that avoids the US-dollar clearing system entirely.
Step 4: Manage conditions, reporting, and renewals after approval
An authorisation obtained is not a problem solved. Each licence or authorisation carries ongoing conditions, and the failure to comply with them is treated by every competent authority as a new violation – separate from, and potentially more serious than, the underlying sanctions question.
Condition management begins on the day the licence is issued. Assign a named compliance officer to each licence. Extract every condition into a structured log: what must be done, by when, in what format, to which authority. Cross-reference the conditions of all concurrent licences to identify any points of tension between regimes.
Reporting is the most commonly missed condition in our experience. OFAC licences for humanitarian activity frequently require the licensee to file periodic reports – quarterly or annually – covering all transactions conducted under the licence. The report must include counterparty names, amounts, dates, and a certification of compliance with end-use monitoring conditions. Late or defective reports undermine the firm's ability to rely on the licence as a defence and can result in OFAC declining to renew.
Renewals require forward planning. Licence terms are finite. A specific licence issued for a defined period will expire, and operations authorised under it will become impermissible on expiry unless a renewal is in place. Build a renewal trigger into the compliance calendar at least ninety days before expiry. OFAC, OFSI, and EU member state authorities do not automatically renew licences; a fresh application – or at minimum a formal renewal request – is required. Renewed licences may carry updated conditions that differ from those in the original.
For general licences, monitor the relevant regulator's website and official publications for amendments. OFAC, OFSI, and the EU Council amend and revoke general licences and general authorisations without advance notice in some cases. An organisation whose operational model rests on a general licence must treat any amendment as a potential operational disruption requiring immediate legal review.
Risk flags: where cross-border humanitarian authorisations go wrong
In our cross-border practice, the following are the most common failure points in multi-regime humanitarian authorisation work. They recur across sectors – relief organisations, development banks, and commercial partners supplying humanitarian programmes.
Assumption that one authorisation covers all regimes. It does not. Each regime requires its own analysis. A US general licence for a specific programme does not authorise the same activity under an EU or UK regime.
Sub-grantee and downstream partner screening. A humanitarian licence typically authorises transactions with the named recipient only. If that recipient passes funds or goods to a sub-grantee who turns out to be a designated person or an entity owned 50 percent or more by a designated person under the applicable ownership and control test, the licence condition requiring end-use monitoring has been breached. Due diligence must extend to every tier of the delivery chain, not just the direct counterparty.
Banking-channel disruption. Even a validly licensed humanitarian payment can be blocked by a correspondent bank whose own sanctions policy is stricter than the regulatory minimum. De-risking (a financial institution exiting a relationship to avoid sanctions exposure) affects humanitarian organisations acutely because their payment routes often pass through jurisdictions or currencies that trigger automated screening alerts. The licence does not compel the bank to process the payment. Engage your banking partners early – before the licence is issued, not after.
Export controls forgotten. A humanitarian licence for financial sanctions purposes does not resolve the export-licence requirement for controlled goods. Medical equipment, certain ICT goods, and dual-use items may require an export licence under the EAR or the ECJU's export control regime in addition to the sanctions authorisation. Treating the sanctions licence as the whole answer is a category error. Our practice on export controls and dual-use goods is addressed at licensing and authorisations for BIS/EAR matters.
Delayed voluntary self-disclosure. Where an organisation discovers that a transaction was conducted outside the scope of an authorisation – for example, a payment to a sub-grantee later found to be on a designated list – the question of whether to make a VSD (voluntary self-disclosure to a regulator) arises immediately. All three principal regimes treat prompt, co-operative disclosure as a significant mitigating factor. Delay narrows options and, in some regimes, transforms a civil matter into one with criminal dimensions. Take legal advice before deciding.
The position above covers the standard case. Your facts – the counterparty, the programme geography, the funding source, the banking route, and the regimes in play – change the analysis.
For a confidential review of your organisation's authorisation requirements, contact Calder & Vance at info@caldervance.com.
When does your situation require specialist counsel?
Not every humanitarian authorisation question requires outside counsel. A well-resourced compliance team with access to current regulatory guidance can manage straightforward general-licence reliance under a single regime. The calculus changes when any of the following apply.
First: the activity crosses three or more regimes simultaneously and involves non-US dollar payment routes as well as US dollar flows. The combination of OFAC secondary-sanctions risk, OFSI licensing conditions, and EU national competent authority practice creates an interaction that requires coordinated legal advice, not sequential analysis.
Second: the organisation or a key delivery partner has appeared on a screening alert, even if subsequently cleared. A cleared hit still generates a record in OFAC's, OFSI's, or the EU member state authority's file. Future licence applications will be assessed against that background. Managing the record requires deliberate steps.
Third: a previous licence application was refused or returned for supplemental information. Refusal is not final in most regimes, but the route to reconsideration differs. Under OFAC, the applicant may request reconsideration and submit additional information. Under OFSI, there is an internal reconsideration process and, ultimately, judicial review in the High Court. Under the EU Council regime, an annulment action before the EU General Court is available in certain circumstances. Each route requires a different evidentiary and procedural strategy.
Fourth: the organisation is considering a programme structure that relies on a novel interpretation of a general licence's scope. OFAC's guidance warns against reliance on general licences for activities that are not clearly within their scope. OFSI's published guidance sets out similar cautions. Where the activity sits at the edge of a general authorisation's language, a specific-licence application is the safer route – but it adds time. Counsel can advise on whether the general licence interpretation is defensible and what documentation to put in place to support it.
If a transaction has already been flagged, or a filing has been refused, an early review can preserve options that narrow with time. Write to us at info@caldervance.com.
A common misconception: "humanitarian work is automatically exempt"
We regularly correct a widely held belief in the NGO and relief sector: that humanitarian intent creates a blanket exemption from sanctions prohibitions. It does not. The humanitarian exemptions and general licences that exist in the major regimes are specific, limited, and conditional. They do not create a freestanding carve-out for any activity with a charitable purpose.
OFAC's humanitarian general licences are programme-specific and do not extend to all OFAC-administered programmes. An NGO conducting operations in a country subject to a programme with no humanitarian general licence must apply for a specific licence, however clear the humanitarian purpose. Intent is relevant to mitigation of penalties if a violation occurs – it is not a substitute for authorisation.
OFSI's approach is similar. The UK regime requires either a general licence covering the activity or a specific licence issued by OFSI. A humanitarian purpose supports the licence application; it does not make the application unnecessary.
Under the EU regime, the humanitarian exemptions in Council regulations are narrower than many practitioners assume. Some apply only to activities of certain designated international organisations. Others require prior authorisation from the national competent authority rather than permitting self-executing reliance. Reading the relevant regulation carefully – and not assuming that a favourable interpretation of one programme's exemption extends to another – is essential.
In a recent matter, a development-sector organisation operating under what it understood to be a general licence later discovered that the specific activities it was conducting – providing certain technical assistance in addition to financial aid – fell outside the general licence's scope and required a specific licence under two of the three applicable regimes. We assessed the apparent violation, advised on the VSD question, and structured the remediation with the relevant authorities. The matter resolved without formal enforcement action, but the cost in management time, operational disruption, and legal fees significantly exceeded what a pre-programme authorisation review would have required.
Related practices
- Licensing and authorisations – BIS/EAR and frozen-account management – export-licence and EAR authorisation support for controlled goods in humanitarian programmes
- EU humanitarian authorisation guide – Council regulation exemptions, national competent authority procedure, and reporting obligations
- EU humanitarian authorisation: advanced considerations – annulment routes, general-authorisation scope questions, and multi-programme EU compliance