A US-headquartered business is mid-negotiation on a multi-year supply agreement with a distributor whose ultimate beneficial owner was flagged in a recent screening refresh. The deal team wants to proceed. Legal wants protective language. Compliance wants to know whether any clause actually closes the exposure – or whether the whole transaction is already prohibited. Three questions, one contract, and an OFAC prohibition that does not pause for drafting delays.
Sanctions clauses in contracts under OFAC serve two distinct functions: they establish a contractual right to suspend or terminate if a counterparty becomes a blocked person, and they evidence the due diligence that OFAC weighs in any enforcement proceeding. As of August 2026, no standard form is mandated under IEEPA or any applicable OFAC programme; the content and enforceability of any clause depends on the underlying transaction, the counterparty's jurisdictions, and the specific prohibitions in play.
This guide works through the drafting process step by step – from screening the counterparty before the clause is written to the cross-regime checks that matter when the contract has a UK, EU, or multi-national dimension.
Step 1: Understand what OFAC sanctions clauses actually do
A sanctions clause in a contract under OFAC does not itself authorise a prohibited transaction. That is the critical starting point, and it is one many deal teams miss. The clause operates downstream of the prohibition analysis, not in place of it.
OFAC's authority derives from IEEPA and other statutory instruments. When a transaction is prohibited – because a counterparty is on the SDN List (OFAC's list of Specially Designated Nationals and blocked persons), or because the transaction involves a blocked jurisdiction, programme, or commodity – no contractual clause can render it lawful. A well-drafted termination right is irrelevant if you cannot lawfully pay the termination fee. A representation that the counterparty is not a blocked person does not make the underlying facts true.
What the clause does do is create three practical benefits. First, it establishes a clear contractual exit right, avoiding disputes about whether sanctions events constitute force majeure, frustration, or material breach under applicable law. Second, it builds a contemporaneous record of due diligence – one of the factors OFAC expressly weighs when assessing penalty amounts. Third, it allocates risk between the parties where the underlying transaction is lawful but may become restricted as a programme evolves.
In our experience, the most productive framing for a compliance team is to treat the sanctions clause as the last line of contractual defence, not the first line of legal protection. The real protection comes in Step 2.
Step 2: Screen before you draft – the SDN and ownership analysis
Effective sanctions clauses in contracts begin with a screening exercise conducted before any clause language is agreed, because the screening results determine what the clause needs to cover. A clause negotiated on top of an uncleared counterparty creates a paper record of due diligence that OFAC will inspect for substance, not form.
The screening sequence for OFAC purposes involves three layers. The first is a direct search of the SDN List and the relevant programme-specific lists published by OFAC. Most commercial screening tools handle this step, though the quality of name-matching logic and alias coverage varies significantly between platforms. The second layer is the 50 percent rule (OFAC's rule treating entities owned 50 percent or more by one or more blocked persons in the aggregate as themselves blocked, regardless of whether the entity appears on any list). This layer is where manual review is almost always necessary, because beneficial ownership data in many markets is incomplete or delayed. The third layer is an assessment of whether the goods, services, or technology being transacted are themselves subject to a specific programme prohibition, independent of the counterparty's status.
Have you confirmed the full ownership chain, not just the first visible layer? In our cross-border practice, indirect holdings through holding companies in intermediate jurisdictions account for a disproportionate share of the threshold breaches we identify during pre-signing due diligence.
The screening results then directly shape the clause. A counterparty with a clean result warrants a standard representation and compliance undertaking. A counterparty with ambiguous beneficial ownership data warrants enhanced ongoing monitoring provisions and a broader definition of a "sanctions event." A counterparty that cannot clear the ownership analysis warrants a conversation about whether the deal can proceed at all – before the clause drafting begins.
The position above covers the standard case. Your facts – the counterparty structure, the goods or services in scope, the governing programme, and the jurisdictions touched – change the analysis. For a confidential review before a contract is signed, contact Calder & Vance at info@caldervance.com.
Step 3: Draft the four core components of an OFAC-aligned clause
A well-constructed OFAC sanctions clause has four components, each serving a distinct function. Experienced practitioners draft them in sequence, not as a single block of boilerplate.
The first component is the representations and warranties block. Each party represents that it is not a blocked person, is not owned or controlled by a blocked person within the meaning of applicable OFAC rules, and is not located in or organised under the laws of a jurisdiction subject to comprehensive OFAC sanctions. The representation should run as of the date of signing and be capable of being repeated at each payment or delivery milestone. The scope matters: a representation that only addresses the direct contracting entity – and ignores subsidiaries, affiliates used in performance, and beneficial owners – provides limited protection and limited evidence of diligence.
The second component is the ongoing compliance undertaking. This is a positive covenant by each party to maintain compliance with applicable OFAC rules throughout the term, to promptly notify the other party of any change in circumstances that would affect the accuracy of the representations, and – critically – not to use the other party's goods, services, or payments in a manner that would violate OFAC or the other applicable regimes specified in the clause. The "other applicable regimes" language is where the cross-border dimension enters, and it is covered in Step 4.
The third component is the sanctions event definition and termination right. A sanctions event should be defined to capture: a party becoming a blocked person; a party being owned or controlled by a blocked person; performance of the contract becoming prohibited under any applicable sanctions regime; and a required licence being revoked or not renewed. The termination right should be immediate on notice, without penalty, and should address the treatment of payments already in the pipeline. Whether termination fees are themselves subject to a blocking prohibition is a question the drafting must address expressly.
The fourth component is the indemnification and allocation of liability language. This allocates the costs of compliance failure between the parties – legal fees, penalty exposure, and third-party claims – and sets out which party bears responsibility for maintaining the accuracy of representations over time. In transactions involving multiple performance jurisdictions, this component requires careful thought about which regime's enforcement posture creates the highest exposure.
Step 4: Address the cross-border dimension – UK, EU, and multi-regime clauses
OFAC sanctions clauses do not operate in isolation when the contract has a cross-border dimension. A supply agreement between a US parent and a European subsidiary may engage OFAC rules, OFSI rules, and EU Council regulations simultaneously – and the tests under each regime diverge in ways that a clause drafted for OFAC alone will not capture.
The most important divergence is the ownership-and-control test. OFAC applies the 50 percent aggregate ownership rule: the test is mechanical and does not require an assessment of control. OFSI and the EU regulations apply an ownership and control test (the UK and EU standard for whether a non-listed entity is caught through a listed person), which captures entities that a listed person controls even without majority ownership – through board rights, veto rights, or contractual power. A clause that only references OFAC's ownership test will miss entities caught under UK or EU rules, and vice versa.
A second divergence concerns the blocking of funds. Under OFAC, property in which a blocked person has an interest is blocked and must be reported. Under OFSI, the equivalent obligation includes a reporting duty to OFSI – separate from the prohibition itself – and the licensing routes differ from OFAC's. The EU regime adds a further dimension through the asset freeze provisions of each applicable Council regulation, which in some programmes are broader in scope than either the OFAC or OFSI positions.
For contracts with a UK or EU party, the clause should therefore specify each applicable regime by reference and should contain a "stricter prohibition governs" provision – a standard cross-regime drafting device that applies whichever regime imposes the more restrictive obligation in the event of any conflict. We regularly advise clients on how to calibrate this language to avoid over-compliance with one regime creating a breach of another.
A third consideration is the EU Blocking Regulation, which in certain circumstances prohibits EU persons from complying with specific US extraterritorial sanctions requirements. A clause that requires an EU party to comply with the full scope of OFAC secondary-sanctions obligations may create a directly conflicting legal duty for that party. The drafting must be structured to acknowledge this conflict and to establish what each party's obligations are in the event the conflict arises.
If a transaction has already been flagged under one regime, or if a filing has been refused, an early review can preserve options that narrow with time. Contact Calder & Vance at info@caldervance.com to discuss the multi-regime position before the clause is finalised.
Step 5: Build in the monitoring and review mechanism
An OFAC sanctions clause that is not maintained throughout the contract term is a compliance liability, not an asset. Programmes evolve, designation lists are updated, and beneficial ownership structures change – sometimes without notice to the other contracting party.
The monitoring mechanism embedded in the clause should do three things. First, it should require each party to re-screen the other – and its material beneficial owners – at defined intervals throughout the contract term, and to notify the other party promptly if any screening produces a result that was not present at signing. Automated alerts from a commercial screening platform satisfy the technical requirement but do not substitute for a human review of ambiguous or partial matches.
Second, the clause should specify a notification window. What is the period within which a party must notify the other of a sanctions event? The appropriate window depends on the transaction: a long-term supply agreement with monthly payments may justify a short notice period. A framework agreement with sporadic performance may accept a slightly longer window. The key is that the window is defined, not left open-ended.
Third, the clause should address what happens during the period between identification of a potential sanctions event and its resolution. In practice, this is the period of greatest legal risk. A party that becomes aware of a potential SDN hit and continues performance while the position is being assessed may already be in breach of the underlying prohibition. The clause should either suspend performance automatically on identification, or should specify that performance continues at the acting party's risk pending a legal determination – with that determination to be obtained within a defined period.
Record-keeping underpins this entire mechanism. Maintaining documentation of each screening exercise, each ownership-chain review, and each notification under the clause creates the contemporaneous record that OFAC's enforcement framework treats as a mitigating factor in penalty determinations. In our experience, the absence of this record – rather than the breach itself – is often what converts a self-disclosed violation into a more serious enforcement outcome.
Step 6: Identify the risk flags that warrant legal review before signing
Certain fact patterns in a contract negotiation consistently indicate that the sanctions clause needs legal review before it is finalised, rather than after a problem has emerged.
The first flag is a counterparty that declines to provide ownership information beyond the first corporate layer. Beneficial ownership opacity is a known risk indicator across OFAC, OFSI, and EU enforcement programmes. A contracting party cannot satisfy the 50 percent ownership analysis without the underlying data – and a clause agreed in ignorance of ownership facts provides no meaningful protection.
The second flag is performance in or through a jurisdiction subject to a comprehensive OFAC programme. Even where the contracting parties are clean, routing payments, goods, or technology through a jurisdiction under a comprehensive programme can engage the prohibition independently. The clause drafting must address which intermediaries are involved and how their jurisdictions affect the flow of performance.
The third flag is a counterparty that has previously been subject to an OFAC inquiry, a denial of a licence application, or an enforcement action under any sanctions regime. This history does not automatically make the transaction prohibited, but it is material to the due diligence record and to the design of the monitoring mechanism. In our practice, we treat this history as a trigger for enhanced clause provisions and a mandatory pre-signing review.
The fourth flag is a clause submitted by the counterparty that limits the parties' compliance obligations to a single regime only – typically the regime governing the counterparty's home jurisdiction – and expressly excludes OFAC or other programmes. Where a transaction touches US persons, US-origin goods, or the US financial system, this exclusion is not enforceable as a legal matter. The clause, and the negotiating position behind it, warrant close scrutiny.
A common misconception about sanctions clauses – and why it matters
A persistent misconception among in-house teams is that the presence of a well-drafted sanctions clause in a contract provides a substantive legal defence to an OFAC enforcement action. It does not. What the clause provides is evidence of due diligence – one of the factors OFAC considers in the Enforcement Guidelines when assessing whether a violation is egregious and when calculating a penalty.
OFAC does not confer immunity for contractual compliance language. A business that enters a prohibited transaction and relies on its sanctions clause as a defence is misunderstanding the enforcement regime. The defence – to the extent it exists – is built in Steps 1 and 2 of this guide: in the screening, the ownership analysis, and the documented decision to proceed or not proceed. The clause then records that evidence in a form that survives a counterparty dispute and an enforcement inquiry.
We have acted for businesses that presented strong clause language during an enforcement process. In those matters, the quality of the underlying pre-signing analysis – not the clause itself – was what OFAC focused on. Counsel reviewing a potential violation will always ask what due diligence preceded the signing, not what the contract said about it.
Related practices
- Sanctions compliance audit and testing (Australia) – screening-programme review and gap analysis for Australian-nexus transactions
- Sanctions clauses in contracts under OFSI – step-by-step guide to UK financial sanctions clause drafting
- Sanctions clauses under OFSI: advanced guide – ownership, control, and multi-regime clause design for UK-connected transactions