Calder & Vance International Sanctions & Compliance Counsel

Licensing & Authorizations · OFSI

General licence eligibility under OFSI: step by step

A UK-incorporated trading company holds a long-standing commercial relationship with a counterparty whose parent has just been added to the UK financial sanctions list. The compliance team runs a check. The counterparty itself is not designated. But the parent holds a majority stake. Can the trading company continue to pay invoices? Can it access its own receivables held in an account at a UK bank? The answer may turn on a single document: a general licence issued by OFSI.

A general licence (a standing authorisation that permits a defined category of transactions without a separate application) under OFSI covers certain classes of transaction that would otherwise be prohibited by UK financial sanctions. Eligibility is not automatic. A business must identify the correct general licence, confirm that its facts satisfy every condition, comply with any reporting obligation, and keep a complete record. As of June 2026, OFSI administers general licences under the power conferred by the Sanctions and Anti-Money Laundering Act ("SAMLA") and the relevant thematic regulations.

This guide works through eligibility determination in sequence: from the threshold question of whether a prohibition applies, through the conditions of each available general licence, to the reporting and record-keeping duties that follow reliance. It also compares the OFSI model with the OFAC and EU approaches – because for cross-border businesses, the differences are material.

Step 1: Confirm that a UK financial-sanctions prohibition applies to your transaction

Before a general licence becomes relevant, you must confirm that a prohibition actually bites on the transaction in question. Many compliance teams reach for a licence before establishing whether one is needed.

UK financial sanctions prohibit a range of activities involving a designated person or an entity that a designated person owns or controls (the UK and EU test for whether a non-listed entity is caught through a listed person). The core prohibitions typically cover making funds or economic resources available, dealing with funds held to the order of a designated person, and providing financial services that benefit a designated person. The relevant thematic regulations – each implementing a specific sanctions regime by reference to SAMLA – set out the precise prohibitions that apply in that regime context. The prohibitions differ between regimes: the list applicable to one set of thematic regulations is not identical to that in another.

The ownership-and-control question is frequently the harder one. Where a designated person owns 50 percent or more of an entity's shares or voting rights, or otherwise controls it, that entity is treated as subject to the same prohibitions. A transaction with a non-designated subsidiary may still be caught. Run the ownership chain before reaching for a licence.

If the prohibition does not apply – either because the counterparty is not designated, not owned or controlled, and the transaction does not benefit a designated person – no licence is needed. Record that conclusion with a brief analysis. Do not rely on a general licence when a licence is unnecessary; reliance creates a compliance audit trail that can later imply an admission of the underlying risk you did not intend to make.

Step 2: Identify which general licence covers the transaction

Once you have confirmed a prohibition applies, the next step is to locate the general licence – if any exists – that covers your specific transaction type. This is not a free-standing search. Each general licence is issued under a specific regime, covers a defined category of persons, and attaches to a defined purpose.

OFSI publishes general licences on GOV.UK. As of June 2026, general licences in force address purposes that have included, across different regimes: legal expenses, certain payments to maintain ordinary course of business, access to basic personal financial services, pension payments, and specific trade-related activities. The categories, their scope, and the regimes they apply to change. A general licence that was in force last month may have lapsed, been amended, or been superseded.

For each candidate general licence, ask four threshold questions:

  1. Does this licence apply to the relevant thematic regime? A general licence issued under one set of thematic regulations does not automatically extend to another.
  2. Does the transaction purpose match the licence's stated purpose? Purposes are defined narrowly. A "legal expenses" licence covers legal fees in defined proceedings; it does not cover an advisory retainer in an unrelated transaction.
  3. Does the counterparty type match? Some general licences are restricted to natural persons; others apply to corporate entities.
  4. Is the licence currently in force? Check the licence itself for an expiry date and check GOV.UK for any notice of revocation or amendment.

In our experience, the most time-consuming step is matching the transaction purpose to the licence's language. Purpose definitions are read strictly by OFSI. If the transaction sits at the edge of the stated purpose, a specific licence application may be the safer route. A general licence does not protect a relying party whose transaction did not, in fact, fall within its terms.

Step 3: Satisfy every condition of the general licence

A general licence sets out conditions that must all be satisfied for the authorisation to apply. Partial compliance does not create partial protection. An entity that meets nine of ten conditions is not authorised; it is in breach.

Conditions typically include one or more of the following categories:

  • Counterparty conditions: the designated person, the entity through which the benefit flows, or the purpose must fall within the licence's definition. Check each element of the definition individually.
  • Amount or value conditions: some general licences cap the value of transactions permitted. Where a cap applies, verify the cumulative position across all transactions relying on the same licence, not just the single transaction in front of you.
  • Purpose and use conditions: funds or economic resources must be applied only to the permitted purpose. Post-transfer use is a condition, not merely an expectation. Where funds pass through an intermediary, the chain of use matters.
  • Notification conditions: many general licences require the relying party to notify OFSI before, or within a specified period after, the transaction. The notification window is a hard condition; a late notification does not retrospectively cure a breach.
  • Counterpart disclosure: some licences require all parties to the transaction to be informed that the licence is being relied upon and of its terms.

Do you have documented evidence that each condition was satisfied at the time the transaction was executed? OFSI's enforcement guidance makes clear that the burden of demonstrating eligibility rests on the person relying on the licence. That burden is discharged only by contemporaneous evidence, not by reconstruction after the fact.

How does OFSI differ from OFAC and the EU on general authorisations?

The OFSI general licence model operates differently from the standing general-licence system used by OFAC and from the EU's approach, and those differences directly affect a cross-border business that must comply with more than one regime.

Under the US system administered by OFAC, general licences are embedded in the relevant programme regulations and take effect automatically when the conditions are met. Reliance does not require notification to OFAC in most cases, though record-keeping obligations apply. The scope of available general licences under the major US programmes is substantially broader than the number of general licences OFSI has issued under equivalent UK programmes.

The EU regime does not use the term "general licence" in the same sense. Instead, the relevant Council regulations set out exemptions and derogations that function as standing authorisations for defined purposes – for instance, certain humanitarian or legal-expenses payments. The competent authorities of each member state administer these derogations differently. In some member states a prior authorisation is required even where the EU regulation sets out what appears to be a standing permission. A business that has mapped its position under EU rules cannot assume that the same activity is covered by an OFSI general licence.

The practical consequence is that for a transaction that touches the UK, the EU, and the US simultaneously, three separate analyses are required. A transaction that OFAC authorises under a general licence may still require a specific licence from OFSI. A derogation available at EU level may not be reflected in the OFSI regime at all. We regularly advise clients that the strictest prohibition governs: a firm must satisfy the most demanding of the applicable regimes, not merely the regime under which it is domiciled.

Switzerland and Singapore each operate licensing regimes with their own standing permissions, and neither maps cleanly onto the OFSI model. If the transaction involves a Swiss financial institution or a Singapore-connected payment, the local regime must be checked independently.

The position above covers the standard comparison. Your facts – the counterparty's ownership structure, the nature of the goods or services, the jurisdictions of the banks involved – will shift the analysis materially. If the transaction crosses more than one regime, an early review can identify which licences are needed before funds move.

For a cross-regime eligibility assessment, contact Calder & Vance at info@caldervance.com.

Step 4: Comply with notification and record-keeping obligations

General licence reliance is not self-executing. Most OFSI general licences attach reporting and record-keeping conditions that must be followed for the authorisation to remain valid and for the relying party to demonstrate compliance if challenged.

Notification duties vary by licence. Some require the relying party to notify OFSI in advance of the transaction. Others require notification within a specified number of business days after the transaction. A small number require notification only if requested. The notification requirement is stated in the licence text itself; do not assume it is the same across different general licences. Read each licence on its own terms.

Record-keeping is the foundation of a defensible compliance position. OFSI's enforcement guidance indicates that records supporting a claim of general licence reliance should include:

  • the version of the general licence in force at the time of the transaction (downloaded and dated);
  • the analysis confirming that each condition was met, prepared before or contemporaneously with the transaction;
  • transaction documents showing the amount, the parties, the purpose, and the date;
  • any notifications sent to OFSI, with proof of despatch and any acknowledgement received;
  • any consents or disclosures made to counterparties under the licence conditions.

OFSI has statutory powers to request information from persons subject to UK financial sanctions and from those relying on licences. A request for information must be answered within the period specified. Having organised records at the point of reliance – not at the point of a request – is the material distinction between a cooperative, defensible response and a problematic one.

Record-keeping periods under the relevant thematic regulations align with broader financial record-keeping duties. Verify the applicable period for your regime; it is qualitative in most guidance but the duty to retain is not.

Step 5: Recognise the risk flags that displace general licence reliance

A general licence covers a defined category. It does not give a firm blanket protection in the vicinity of sanctions. Several risk patterns displace or limit the protection that reliance would otherwise provide.

Aggregated payments. Where multiple transactions are structured to stay within a value cap, OFSI will look at the pattern as a whole. A series of transactions that would individually fall within the licence but collectively exceed its scope or purpose may constitute a breach. The relevant question is whether the substance of what is being done falls within the licence, not whether individual transactions are individually small.

Changed facts after reliance has begun. If the counterparty's ownership structure changes, if a new designation is issued, or if the purpose of the transaction changes mid-stream, the original eligibility analysis may no longer hold. A general licence does not grandfatherthe right to continue a transaction whose facts have moved out of the licence's scope.

Ownership uncertainty. General licences frequently restrict which types of designated persons or entities are covered. If ownership and control of the relevant counterparty cannot be established with confidence, reliance on a general licence is risky. OFSI has no obligation to accept post-transaction assertions about what the ownership position was at the relevant time.

Licence expiry or revocation. Checking the licence at the start of the transaction and again at the point of execution is basic discipline. Checking it once and treating it as durable for subsequent transactions is a common and avoidable error.

Wrong regime. A general licence issued under one thematic regime does not cross over into another. If the designated person is listed under two separate regimes, each must be addressed separately. In our experience, multi-listed counterparties are the most frequent source of coverage gaps.

If a transaction has already proceeded and a coverage question has emerged, or if a filing has been refused, an early review can identify the options that remain open. Those options narrow with time.

For a confidential review of your exposure, contact Calder & Vance at info@caldervance.com.

When to seek a specific licence instead

A specific licence (a case-by-case authorisation to conduct an otherwise prohibited transaction) is the appropriate route when no general licence covers the transaction or when the facts sit at the boundary of a general licence's conditions.

Specific licences are issued by OFSI on application. The application must set out the factual basis, the legal analysis, the parties, and the grounds on which OFSI should exercise its discretion. OFSI's published guidance identifies the grounds on which a specific licence may be granted: these typically include humanitarian grounds, the administration of justice, the winding-down of a pre-designation contract, and specific grounds in the relevant thematic regulations.

The decision whether to rely on a general licence or to apply for a specific licence is itself a risk decision. Relying on a general licence that does not clearly cover the transaction creates the risk of an unlicensed dealing. Applying for a specific licence takes time; the processing period is not prescribed in days for all transaction types, and complex applications can take substantially longer than straightforward ones. Where business continuity depends on the transaction, the timing of an application must be factored into the decision.

The myth we most commonly encounter at this stage is that applying for a specific licence is an admission of risk. It is not. It is the correct procedural step when a general licence does not clearly apply. OFSI acknowledges that businesses seek licences in good faith for uncertainty as well as for clear prohibitions. The misconception that a licence application signals wrongdoing prevents firms from taking the safer, documented route – and leaves them exposed on a general licence that may not hold.

A related misconception is that the UK and US licensing processes are interchangeable. They are not. An OFAC-issued specific licence does not authorise the UK leg of the same transaction. The applicable regimes must each be addressed in turn.

Related practices

Frequently asked questions

What are the steps to rely on a general licence under OFSI?
Reliance requires five sequential steps: confirm a UK financial-sanctions prohibition applies; locate the relevant general licence and verify it is in force under the correct thematic regime; confirm that your transaction satisfies every stated condition; comply with any notification requirement on time; and retain contemporaneous records demonstrating each of the above. Partial compliance with any step does not protect the transaction. OFSI places the burden of proof on the relying party, and that burden is met only by organised, contemporaneous evidence.
What is the most common mistake in general licence eligibility?
The most common mistake is assuming that a general licence issued under one thematic regime extends to a second regime under which the same counterparty is also designated. It does not. Each thematic regime must be addressed with the general licences issued under it. The second-most common error is failing to comply with the notification condition: a late or absent notification does not retrospectively cure the transaction, and it is itself a breach of the licence conditions that OFSI may consider in an enforcement context.
How does OFSI differ from other regimes here?
OFSI's general licences are issued as discrete instruments, each with its own conditions and expiry dates, rather than being embedded in programme regulations as OFAC's general licences are. The practical difference is that an OFSI general licence can expire or be amended without a regulatory amendment process; monitoring GOV.UK for changes is an ongoing obligation. The EU derogation model differs again: competent authority practice varies by member state, and a standing permission at EU level may require a prior authorisation in certain jurisdictions that does not appear on the face of the Council regulation.

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.