A payment clears a correspondent bank. Hours later, the funds are frozen by OFAC and the transaction is suspended. The business on the receiving end has no access to its money, no clear timeline for resolution, and an immediate question: what are the legal steps to get those funds released? This is not a hypothetical risk. It is a situation our clients face across sectors – trade finance, energy, professional services, and digital assets alike.
Release of blocked funds under OFAC requires a specific licence (a case-by-case authorisation from the Office of Foreign Assets Control to conduct an otherwise prohibited transaction), or a demonstration that the funds were never properly blocked in the first place. As of July 2026, OFAC administers these requests under authority derived from IEEPA and the relevant programme-specific regulations. The path depends on the reason for the block, the identity of the party whose nexus triggered it, and whether a general licence (a standing authorisation permitting a defined category of transactions without a separate application) already provides relief.
This page sets out the governing authority, the procedure for seeking release, how the OFAC process compares with OFSI and EU mechanisms, the common risk flags that complicate applications, and how Calder & Vance assists clients at this critical stage.
What governs the blocking of funds under OFAC, and when does it apply?
OFAC's authority to require that funds be blocked flows primarily from IEEPA and, for older programmes, the Trading with the Enemy Act. The relevant programme-specific regulations then direct financial institutions to block property in which a designated person – one named on the SDN List (OFAC's list of Specially Designated Nationals and blocked persons) – has any direct or indirect interest.
The trigger is not always obvious. A payment may be frozen because the beneficiary appears on the SDN List, or because OFAC's automated screening flags a name match that has not yet been adjudicated. Alternatively, the block may arise from the 50 percent rule (OFAC's rule treating entities owned 50 percent or more by blocked persons as themselves blocked), where the ultimate beneficial owner of the payee or the payor crosses the ownership threshold even if the immediate counterparty is not listed. In our experience, a significant proportion of initial blocks stem from name-match alerts that, on proper review, do not survive scrutiny – the party is a different person entirely.
A third category involves transactions with specially designated targets whose property in the United States, or property that transits the US financial system, must be blocked and reported. The reporting obligation is real and time-sensitive: institutions must report blocked property to OFAC within a short statutory window. Verify the current deadline before relying on it.
Understanding the precise basis for a block is the first step. The relief route for a false match differs entirely from the route for a true SDN nexus.
How does the OFAC specific-licence process work for releasing blocked funds?
Where funds are correctly blocked – because a designated person does have a genuine interest – the primary mechanism for release is a specific-licence application to OFAC under the applicable programme regulations. The application must demonstrate that releasing or transferring the funds is consistent with US foreign-policy and national-security objectives and falls within a recognised category of authorisable relief.
OFAC evaluates applications against its policy criteria for the relevant programme. For humanitarian categories and certain personal-remittance scenarios, general licences may already authorise the transfer without a case-by-case request. The analysis begins there. If no general licence applies, a specific-licence application sets out:
- the identity of all parties to the transaction and any beneficial owners;
- the nature, origin, and destination of the funds;
- the legal basis for the requested relief;
- a detailed factual statement of why the release is consistent with programme policy; and
- supporting documentation establishing each factual claim.
OFAC's processing time for specific-licence applications varies materially by programme and by the complexity of the ownership-and-identity questions involved. For straightforward applications in less sensitive programmes, a response may come within weeks. For applications touching higher-risk programmes or involving complex beneficial-ownership structures, the process takes considerably longer – sometimes many months. There is no statutory deadline binding OFAC's response on most applications. We regularly advise clients to submit early and to treat the application as a continuing dialogue, not a one-shot filing.
The position above covers the standard case. Your facts – the counterparty, the goods routed through the payment, the route, the programme in play – change the analysis materially. For a first assessment of your application's prospects, contact Calder & Vance at info@caldervance.com.
What if the block was a mistake? Challenging a false match under OFAC
Not every blocked payment reflects a true SDN nexus. Name-match alerts generated by automated screening can incorrectly flag unrelated parties who share a name, a date of birth, or a country of origin with a listed person. In these cases, the correct route is not a licence application – it is a delisting or mistaken-identity request demonstrating that the party whose funds were frozen is not the designated individual or entity.
OFAC's process for resolving mistaken-identity cases is distinct from licensing. The applicant submits evidence – identification documents, corporate records, transactional history – demonstrating that no SDN nexus exists. OFAC reviews the submission and, if satisfied, can instruct the blocking institution to release the funds. In our experience, the quality and completeness of the evidentiary package is the single most important factor in the speed of resolution. An incomplete submission invites requests for further information that extend the timeline significantly.
A parallel question arises when a business believes a designation itself is incorrect – that the named party on the SDN List should not have been listed at all. That is a designation challenge, a distinct procedural route involving a petition to OFAC for reconsideration. Where the designated party is also the party whose funds are blocked, the two questions – licence and challenge – are closely related but must be handled separately. We have acted for clients who needed both tracks run simultaneously, with each coordinated so that concessions in one did not prejudice the other.
How does the OFAC process compare with OFSI and EU blocking mechanisms?
For cross-border businesses, funds may be blocked under more than one regime simultaneously. Understanding where the regimes align – and where they diverge – is essential before filing any application.
Under OFSI (the UK's Office of Financial Sanctions Implementation), ownership and control (the UK test for whether a non-listed entity is caught through a listed person) extends the reach of the block beyond majority ownership. OFSI examines control relationships, not just arithmetic ownership percentages. A party that owns only forty percent of a target company may nonetheless cause it to be caught if it controls the target's decision-making. This diverges sharply from OFAC's 50 percent ownership rule, which is mechanically applied without reference to control. That distinction can mean a payment is blocked under OFSI but not under OFAC, or vice versa.
The EU operates similarly to OFSI on control: the relevant Council regulations use both ownership and control as tests. The EU also maintains its own list under the Common Foreign and Security Policy, which does not mirror the SDN List exactly. A counterparty delisted from the SDN List may remain designated under EU regulations, leaving funds blocked under European law even after US relief is obtained.
For businesses with multi-currency payment flows – particularly those denominated in US dollars and processed through US correspondent banks – the OFAC block will often be the operative one, because the transaction touches the US financial system. But obtaining OFAC relief does not automatically release funds held by a non-US institution acting under its own regime's obligations. A coordinated multi-regime strategy is frequently necessary. Our practice spans all three regimes, and we regularly advise on cross-border release strategies where OFAC, OFSI, and EU licensing tracks must run in parallel. You can read about our release of blocked funds under OFSI service, which sets out the parallel UK process.
If a transaction has already been flagged, or a filing has already been refused, an early review preserves options that narrow with time. Contact us at info@caldervance.com for a confidential preliminary assessment.
What are the common risk flags that complicate release applications?
Several fact patterns consistently cause delays or refusals in OFAC release applications, and recognising them early gives a client the best chance of preparing an effective submission.
Opaque beneficial ownership is the most common complication. If the ownership chain of either the payor or the payee cannot be traced clearly to natural persons, OFAC will request supplemental information. That request pauses the clock. Preparing a complete ownership map – verified to the ultimate beneficial owners – before filing avoids this delay entirely.
A second risk flag is an application that requests release of funds that were initially blocked in connection with an underlying transaction that itself may have been prohibited. Where the blocked payment is the proceeds of a prohibited deal, the licence request implicates the original transaction, not just the transfer of funds. The applicant must be prepared to address both.
Third, prior enforcement history matters. If any party in the chain has a record of apparent violations, OFAC weighs this in its evaluation. A voluntary self-disclosure (VSD – a disclosure to a regulator of a potential violation made before the regulator identifies it) can, depending on the circumstances, form part of a broader strategy. However, the decision to make a VSD requires careful analysis; it is not a step to take without legal advice.
Fourth, the nature of the programme matters. Some programmes carry policy presumptions against licence issuance for the category of transaction in question. Knowing the programme posture before investing in a full application avoids wasted effort.
Fifth, delay itself is a risk flag. Blocked-property reporting obligations run from the date of the block, not from the date of the licence application. Missing a reporting deadline creates an independent exposure. Have you confirmed whether the blocking institution has already reported to OFAC, or whether that obligation falls on your organisation as well?
What parallel BIS or export-control exposure arises alongside a blocked-funds scenario?
An OFAC block does not always exist in isolation from export-control issues. Where blocked funds arose from a transaction involving goods, software, or technology subject to the Export Administration Regulations administered by BIS (the Bureau of Industry and Security), the underlying transaction may carry additional exposure under the EAR.
The Entity List (BIS's list of parties subject to licence requirements for specified items) and the SDN List are not co-extensive. A party may appear on one and not the other, or on both. An exporter whose payment has been blocked under OFAC should simultaneously assess whether the underlying shipment required a BIS licence and whether it was shipped without one. That question is analytically separate from the OFAC release application, but enforcement authorities may consider the two together.
For businesses whose blocked funds relate to technology transactions, we recommend an immediate classification and end-use review alongside the OFAC licensing track. A related service for those facing BIS-related freezes is our frozen account management under the BIS / EAR service.
The intersection of OFAC and BIS is a point where specialist knowledge of both regimes is not a luxury – it is a practical necessity. In our cross-border practice, we routinely see businesses address the OFAC angle competently while inadvertently overlooking a BIS filing obligation that compounds their exposure.
Objection: "Our bank's compliance team said the funds will be released automatically."
This is one of the most persistent myths in this area. The belief is that OFAC blocks are temporary holds that resolve themselves once the screening system clears, or that the correspondent bank will handle the release process as part of its standard compliance procedures.
Neither is reliable. Blocked funds do not self-release. An OFAC block created by a confirmed SDN nexus remains in place until OFAC issues a licence, or until the underlying designation is removed or otherwise resolved. Correspondent banks are not authorised to release blocked funds on their own initiative; doing so would itself constitute a violation. Their obligation is to block and report, not to adjudicate or release.
The bank's compliance team may communicate that a review is under way, or that a matter has been referred to OFAC. That is a procedural step, not a resolution. The applicant – the party whose funds are at stake – has both the right and, in most scenarios, the practical incentive to engage directly with the OFAC process rather than wait passively for institutional processes that do not serve the applicant's timeline. We regularly advise clients who have waited months on the assumption that the bank was managing the matter, only to find that no application had been submitted on their behalf at all.
How Calder & Vance supports release of blocked funds under OFAC
Our approach to a blocked-funds matter begins with a rapid preliminary assessment: we identify the programme, the blocking basis, the ownership and identity questions, and the realistic licence or challenge routes. That assessment – delivered within a defined turnaround – tells the client what they are dealing with before we commit to a course of action.
From there, our work on a specific-licence application includes: assessing eligibility against programme policy, preparing and submitting the licence application with a complete factual record, managing OFAC's queries during review, and advising on the parallel reporting obligations that run concurrently. Where the block reflects a mistaken identity rather than a true SDN nexus, we prepare the evidentiary package and engage OFAC directly to secure a prompt resolution.
For matters with a cross-regime dimension, we coordinate the OFAC track with any parallel OFSI or EU proceedings. Where a BIS or export-control question runs alongside the sanctions issue, our colleagues handle both without the need for external coordination. We also advise on de-risking (the practice by which a financial institution exits a customer relationship to avoid sanctions exposure) where a bank has decided to close an account rather than engage with the OFAC process – a situation that requires a different set of options entirely.
Our engagement model offers a fixed-fee assessment entry point, with the substantive work scoped to the matter. We do not bill by the hour for tasks that can be defined at the outset. That transparency gives compliance teams and boards a clear cost frame before they authorise the engagement.
For an assessment of your exposure and a clear view of the release routes available, contact Calder & Vance at info@caldervance.com.
Related practices
- Frozen account management under the BIS / EAR – parallel export-control licensing and account unfreeze for BIS-related holds
- Release of blocked funds under OFAC (advanced matters) – complex multi-party and cross-programme release applications
- Release of blocked funds under OFSI – UK financial-sanctions licensing for frozen-funds scenarios