A multinational receives notice that its counterparty in a long-running services contract has been added to the SDN List (OFAC's list of Specially Designated Nationals and blocked persons). The contract has six months to run. Payments are mid-cycle. Staff are embedded at the counterparty's site. Does the business simply stop – or is there a lawful route to conclude the relationship without criminal exposure? The answer, almost always, is that a structured wind-down is possible. But it must be authorised, documented, and completed within a defined window.
Wind-down authorisations under OFAC permit businesses to complete pre-existing contractual obligations with a newly designated counterparty, within a bounded time period and under defined conditions, without violating the sanctions prohibitions triggered by a new designation. As of June 2026, such authorisations exist in two forms: general licences (standing authorisations that permit a defined category of transactions without a separate application) and specific licences (case-by-case authorisations granted on application). The applicable authorisation type, its scope, and its duration vary by sanctions programme.
This guide covers how the wind-down mechanism works under OFAC, the procedural steps from designation to completion, the most common compliance failures, and how OFAC's approach compares with those of OFSI and the EU – so that your compliance team can make decisions with the full picture in front of them.
Step 1: Identify whether a general licence already covers your wind-down
The first question is not whether you need a licence – it is whether you already have one. When OFAC adds a party to the SDN List, it frequently publishes a general licence simultaneously, or references a pre-existing programme-level general licence that permits wind-down activity for a fixed period. Before any application is drafted, a compliance adviser should check the relevant programme's general licences in full.
General licences are programme-specific. A general licence authorising wind-down under one sanctions programme does not apply to another. The permitted activities, the counterparties covered, and the time windows differ across programmes. In our experience, the most common early mistake is assuming that a general licence seen in one context applies by analogy elsewhere. It does not. OFAC's authorisations are self-contained.
Where a general licence exists, it will typically define: the category of transactions authorised, the parties eligible to use it, the duration, any payment restrictions (for example, funds may need to flow to a blocked account rather than to the designated party), and any reporting obligations. Read each condition carefully. A wind-down that breaches one condition of a general licence receives no protection from it.
If no general licence applies, or if the general licence does not cover your specific transaction type, the next step is a specific licence application. Do not begin winding down in reliance on a general licence without confirming that your transactions fall squarely within its terms. Where there is genuine doubt about coverage, a specific licence application is the safer route – even if a general licence appears broadly applicable.
Step 2: Map the transactions that need to be completed and assess whether they are within scope
Not every payment or action connected to a contract qualifies as a permissible wind-down transaction. OFAC draws a clear line between completing existing obligations and initiating new business with a designated party. The authorisation covers the former; it does not revive or extend the commercial relationship.
The scope of a wind-down authorisation typically includes: completing delivery of goods or services already in transit or partially performed, receiving payment for work already done, unwinding contractual obligations that cannot legally be left open (such as security interests or joint-property arrangements), and closing accounts in an orderly way. What it does not cover is entering new purchase orders, extending credit, making advance payments, or negotiating revised commercial terms – even where those actions might seem commercially necessary to complete the exit.
Mapping the transaction inventory before the wind-down begins is not optional. List every open obligation: payment legs, delivery milestones, intellectual-property licences, sub-contractor arrangements, and staff-secondment agreements. For each, assess whether it falls within the authorised category. Flag any that do not. Those that do not may require a separate specific licence application or may need to be terminated rather than completed.
The position above covers the standard case. Your facts – the counterparty's ownership structure, the goods or services involved, the route of payment, and the programme in play – change the analysis significantly. For an early assessment of your authorisation scope, contact Calder & Vance at info@caldervance.com.
Step 3: Apply for a specific licence where a general licence is unavailable or insufficient
A specific licence application to OFAC must be precise, well-evidenced, and scoped narrowly to the transactions that genuinely require authorisation. Applications that are vague, overly broad, or unsupported by documentation draw scrutiny and delay. OFAC reviews applications on their merits; the quality of the submission directly affects both the outcome and the timeline.
A well-constructed application includes: a clear description of the pre-existing contractual relationship, the designation event and the date it created the compliance issue, a transaction-by-transaction inventory of what needs to be completed, the proposed duration of the wind-down period, the parties involved (including intermediary banks if payments are involved), a statement of the sanctions programme implicated, and any arguments as to why the proposed transactions present a low risk of sanctions harm. Supporting documents – the contract, invoices, payment records, corporate structure charts – should accompany the submission.
OFAC's processing time for specific licence applications varies. The agency operates a review process that can take weeks to several months, depending on the programme, the volume of concurrent applications, and the complexity of the submission. There is no guaranteed turnaround. This means that a business with a short contractual window should apply promptly and consider whether any interim steps (such as suspending performance pending licence receipt) are commercially and contractually feasible. Sitting on an application while the wind-down period narrows is one of the most avoidable compliance risks we see in practice.
During the review period, the underlying prohibitions remain fully in force. Proceeding with transactions before the licence is granted – even where the outcome seems likely – constitutes a potential violation. The only exception is where a general licence already covers the activity pending the specific licence decision.
What are the cross-regime differences that matter to your wind-down?
OFAC's wind-down mechanism is one of several in play for cross-border businesses. A business with operations in the United Kingdom or within the EU may find that the same counterparty designation triggers concurrent obligations under OFSI and EU Council regulations – and those regimes handle wind-down authorisations differently. Getting one authorisation does not satisfy the others.
Under OFSI (the UK's Office of Financial Sanctions Implementation), the licensing system is similarly structured around general and specific licences, but the governing legislation is SAMLA and the thematic UK sanctions regulations rather than IEEPA. OFSI's general licences for wind-down activity are published separately from OFAC's, cover different programme perimeters, and carry their own conditions. Critically, the UK ownership and control test (the UK and EU test for whether a non-listed entity is caught through a listed person) differs from OFAC's 50 percent rule: OFSI and the EU can catch entities that a listed person controls even without owning 50 percent or more. This means a counterparty that falls outside OFAC's SDN-list aggregation rule may still be caught under OFSI and EU rules, or vice versa.
The EU regime operates through Council regulations. Wind-down authorisations are issued at the national competent authority level of each EU member state, with the conditions set in the applicable Council regulation. This creates a patchwork: a German entity and a French entity with identical contracts with the same designated counterparty will apply to different competent authorities, under the same EU regulation but with potentially different administrative practices.
For a business holding licences from more than one regime simultaneously, the strictest prohibition governs each individual transaction. An OFAC general licence permitting a payment does not override an EU or OFSI prohibition on the same payment if the EU or OFSI licence has not been obtained. The regimes are independent, and the cross-border exposure must be mapped in full before the wind-down begins. Our guide on wind-down authorisations under OFSI covers the UK position in detail.
If a transaction has already been flagged by a bank or a payment processor as potentially impermissible, or if a specific licence application has been refused, the compliance options narrow quickly. An early review can preserve routes that close with time. Contact us at info@caldervance.com to discuss the position.
Step 4: Execute the wind-down with documentary discipline
Holding a licence – whether general or specific – is not the end of the compliance obligation. The wind-down itself must be documented to the standard that OFAC (or, for concurrent programmes, OFSI and the relevant EU competent authority) would expect to see in a review. Gaps in the record are a significant enforcement risk, particularly where the original designation was contentious or where the transactions involved large sums or third-country intermediaries.
Every payment made under a wind-down authorisation should be recorded with: the date, the parties, the amount, the currency, the contractual basis, the licence reference (general or specific) under which it was made, and any relevant communications. Where goods are delivered, the delivery records should be preserved alongside the shipping documents. Where services are completed, the acceptance or sign-off records matter.
Record-keeping periods under the applicable regime should be observed in full. Businesses should treat the wind-down file as a potential evidence set for a future review – whether an internal audit, a bank's correspondent due-diligence request, or an OFAC inquiry. The five-year record-keeping standard that applies across US sanctions and export-control regimes is a useful working floor; some programmes and some jurisdictions impose longer periods.
A practical checkpoint: assign a named compliance officer to the wind-down, set a calendar deadline for completion, and schedule an internal sign-off review before the licence expires. Licence expiry without clean completion is a common source of technical violations. The wind-down is not finished until the last obligation is settled, the records are filed, and – where the licence or programme requires it – the completion report is submitted.
Risk flags: where wind-down authorisations fail in practice
In our cross-border practice, wind-down authorisations encounter predictable failure points. Identifying them in advance is the single most effective compliance action a business can take after a designation event.
Reliance on a general licence without confirming coverage. Programme-specific general licences are not universal. A business that assumes coverage without reading the licence conditions in detail may be proceeding without authorisation. The fact that a general licence was issued at the same time as a designation does not mean it covers every transaction type connected to that designation.
Scope creep during wind-down. Once a wind-down is underway, commercial pressure can push the relationship toward new activity – an updated statement of work, a supplemental payment, an amended delivery schedule. Each of these may fall outside the authorised scope. The licence covers the contract as it existed at the date of designation, not revised versions of it.
Intermediary banks blocking payments. A payment that is within the OFAC wind-down authorisation may be declined by an intermediary bank in a third country that is applying its own sanctions controls. This is a structural tension in cross-border payments. The solution is advance notification and, where possible, an alternative payment route that does not pass through jurisdictions with conflicting prohibitions.
Ignoring concurrent UK or EU designations. A new US designation is frequently mirrored within days or weeks by UK and EU designations of the same party. A business that obtains only the OFAC authorisation and proceeds with payments through EU-based accounts or UK correspondent banks may create exposure under parallel regimes. Always check for concurrent designations and concurrent authorisation requirements.
Missing the reporting obligation. Some specific licences, and some general licences, carry a condition requiring the licensee to report completion of the wind-down or to file periodic transaction reports with OFAC. Failure to file does not retroactively invalidate the licence, but it is an independent violation and can affect how OFAC assesses the business in any future interaction.
Our related service, frozen account management under BIS and the EAR, addresses adjacent issues where export-control holds overlap with sanctions holds on the same counterparty or assets.
A common compliance myth: "If we act in good faith, the wind-down is automatically protected"
The myth in circulation is that good-faith reliance on what appeared to be an authorisation provides complete protection from enforcement. This is not the position OFAC takes. Good faith is a mitigating factor in penalty determination – it can reduce the severity of a civil penalty response and is a component of OFAC's enforcement guidelines – but it is not a legal shield that converts an unlicensed transaction into a licensed one.
Where a business proceeded under a general licence that did not in fact cover the transactions in question, the transactions remain potential violations. OFAC's enforcement guidelines consider good faith and the adequacy of the compliance programme as mitigating factors, alongside the absence of prior violations, the voluntary self-disclosure, and the harm potential of the conduct. But mitigation is not immunity. The distinction matters when advising a board on residual exposure.
The practical corrective: before acting under any general licence, have a qualified sanctions lawyer or compliance counsel confirm that the licence covers the specific transactions. Where genuine doubt exists, apply for a specific licence. The cost of the application is marginal compared with the cost of defending a potential violation. We regularly advise businesses at precisely this decision point – the question is not whether the risk is theoretical but whether it is one the business can accept on documented legal analysis.
See also our companion guide on wind-down authorisations and the OFSI licensing process for a UK-specific view of the same question.
When to involve counsel, and what that looks like in practice
Involve counsel at the designation event, not after the first payment has been made. The window between a designation and the expiry of a general licence wind-down period can be short – measured in days or a small number of weeks in some programmes. If a specific licence is required, that process must be initiated promptly. A counsel-driven response in the first 48 hours after a designation event will almost always produce better outcomes than a reactive engagement weeks later.
In a recent matter, a financial-services business discovered that a long-standing corporate client had been added to the SDN List while three transaction legs were in flight. We assessed the applicable programme-level general licences, confirmed that two of the three legs were covered, and identified that the third required a specific licence application. We prepared and submitted the application, advising the client on interim steps to suspend the uncovered leg without breaching the underlying contract. The matter concluded with a clean wind-down and no enforcement referral.
What counsel provides in this context: a precise analysis of which general licences apply and which do not, drafting and submission of any specific licence application, management of OFAC's queries during review, advice on concurrent OFSI and EU authorisation requirements, and documentary protocols for the wind-down execution phase. We also advise on whether a VSD (voluntary self-disclosure to a regulator) is appropriate where a transaction was completed before the compliance team identified the designation.
Related practices
- Frozen account management under BIS / EAR – managing export-control holds on assets and accounts in parallel with sanctions holds
- Wind-down authorisations under OFSI – the UK licensing process, OFSI's conditions, and how it diverges from OFAC