When OFAC and the EU Spell the Same Name Differently, What Are You Liable For?
It is a question experienced practitioners run into constantly but rarely see answered head-on. A person is designated by both OFAC and the EU. OFAC’s SDN entry romanizes the name one way; the EU’s Official Journal renders it another. Your screening system matches one string cleanly and scores the other below threshold. If a transaction slips through against the spelling you did not catch, what exactly is the liability – and is “we ran a standard edit-distance match” a defense?
The short version: you are liable for the person, not the spelling, and the expectation clearly goes beyond raw edit distance. Here is the reasoning, with the supporting regulatory language.
1. The obligation attaches to the designated person, not to a romanization
OFAC’s prohibitions run against the designated person and that person’s property and interests in property. The name spellings, aliases, and other identifiers published in an SDN entry are aids to identification; they are not the legal definition of the target. That distinction matters because it means a spelling discrepancy between OFAC’s list and another regulator’s list is not, by itself, a shield. You cannot defend a missed match by pointing out that OFAC and the EU transliterated the underlying name differently, because your obligation was never keyed to a specific Latin string in the first place.
This is reinforced by the strict-liability character of most OFAC prohibitions. Civil liability under IEEPA-based programs does not require intent or knowledge, so “the file we screened against spelled it differently” is not a recognized excuse. It goes to mitigation, not to whether an apparent violation occurred.
2. Each list is authoritative in its own jurisdiction – so you screen against each as published
OFAC, the EU, the UN, and OFSI transliterate Arabic, Cyrillic, Farsi, and Chinese names using different conventions. The same human being legitimately produces different Latin strings across the lists – Mohammed / Muhammad / Mohamed; Qadhafi / Gaddafi / Kadafi; hyphenated, spaced, or dropped “Al-” prefixes. Each list is, in its own jurisdiction, the authoritative legal instrument. A firm subject to more than one regime is therefore expected to screen against each list as published and to reconcile the fact that one person maps to several spellings across them. There is no regulator that publishes an explicit “you must reconcile our transliteration against the EU’s” rule – the expectation is inferred from how the obligations are framed and enforced, not from a single on-point statement.
3. Does the expectation go beyond standard edit-distance matching? Yes – and OFAC has said so in substance
Edit distance (Levenshtein, Jaro-Winkler, and similar) is treated as necessary but not sufficient. OFAC does not prescribe an algorithm, but its guidance and enforcement record point squarely at the failure modes that character-level distance handles poorly.
In A Framework for OFAC Compliance Commitments (May 2, 2019), OFAC identifies deficient screening as a recurring root cause of apparent violations, and it specifically calls out the failure to account for alternative spellings of designated parties. Commentators summarizing the Framework note that OFAC warns screening software must, among other things, account for alternative spellings of prohibited firms or people – the Habana / Havana example is OFAC’s own. That is the closest thing to a direct statement that naive string matching is not enough.
Why edit distance alone falls short in the cross-list transliteration scenario:
- Cross-alphabet variance. Two valid romanizations of one name can sit at a large character-level distance from each other. “Qadhafi” versus “Kadafi” is a big edit distance but the same person. A threshold tight enough to suppress false positives will miss these; a threshold loose enough to catch them floods the review queue.
- Phonetic equivalence. Names that sound alike but score as distant (the “Mohammed” / “Muhammad” family) are better bridged by phonetic logic (Soundex, Metaphone) or transliteration-aware normalization than by raw distance.
- Name-order and segmentation. Arabic kunya/nasab structures, Chinese surname-first ordering, and dropped or added particles defeat token-by-token distance scoring.
- Culture and script-specific normalization rather than a single global threshold applied to every population.
4. The enforcement record: tool tuning for name variants is a cited deficiency
Two settlements make the point concretely, and neither turns on willful conduct – both are about how the screening tool was configured.
Apple / SIS (FNKSR, 2023 settlement). As part of resolving apparent violations tied to a designated Slovenian developer, OFAC highlighted remedial measures Apple undertook, including reconfiguring its primary screening tool to fully capture spelling and capitalization variations and to account for country-specific business suffixes, plus annual review of the tool’s logic and configuration. The remediation itself tells you what OFAC viewed as the gap: a tool that did not adequately capture variant spellings.
JPMorgan Chase (FNKSR and Syria, 2018 Finding of Violation). OFAC found that the bank’s screening system, as configured over a multi-year period, failed to identify customer names with hyphens, initials, or additional middle or last names as potential matches to identical or similar names on the SDN List – and that staff did not escalate the red flags despite matching addresses and dates of birth. Again, the deficiency is in the matching logic and the procedures around it, not in the absence of screening.
The through-line: OFAC does not penalize you for the existence of a spelling difference. It looks at whether a reasonable, risk-appropriate program – with fuzzy matching, phonetic and transliteration handling, and periodic tuning and testing – should have caught the target. A tool that “ran” but was mis-tuned to variant spellings is treated as a deficient program.
5. How the liability actually resolves
Put the pieces together and the liability is not “for the spelling” as such. It is for processing a transaction involving a designated person you should reasonably have identified. If your program screens against OFAC’s spelling with matching logic calibrated to catch reasonable variants, and a genuinely divergent EU transliteration was the only version that would have matched, OFAC’s inquiry is whether a reasonable, risk-based program should have caught it anyway. A documented, risk-based methodology – fuzzy plus phonetic and transliteration-aware matching, with periodic tuning and testing – is simultaneously the compliance expectation and, under OFAC’s Economic Sanctions Enforcement Guidelines, a mitigating factor if something still slips through.
Bottom line
No regulator publishes an express “reconcile our transliteration against the EU’s” instruction. But the combination of three things – strict liability, the principle that the obligation runs to the designated person rather than to a designated spelling, and OFAC’s explicit citation of alternate-spelling failures as an enforcement root cause – produces a clear expectation. Screen against each authoritative list as published, and use matching logic that goes beyond raw edit distance to account for transliteration, phonetic, and structural name variation. Edit distance alone, without transliteration and phonetic handling and risk-based tuning, would most likely be viewed as a deficient program.
Source confidence. The Framework‘s treatment of alternate spellings as a screening root cause, and the Apple/SIS and JPMorgan Chase remediation details, are well supported by OFAC’s published materials and settlement summaries. The broader proposition – that this framework requires cross-list transliteration reconciliation – is inference drawn from the Framework, the enforcement record, and the strict-liability structure, rather than from a single on-point OFAC statement, because OFAC has not issued express guidance addressing cross-regulator transliteration divergence directly.
Key references: OFAC, A Framework for OFAC Compliance Commitments (May 2, 2019), Appendix root-cause analysis; OFAC settlement with Apple Inc. under the Foreign Narcotics Kingpin Sanctions Regulations; OFAC Finding of Violation involving JPMorgan Chase (FNKSR and Syrian Sanctions Regulations, 2018).
Category: Burning Questions
-
-
My prompt:
In a practical sense, isn’t freezing the assets in Scenario A a more forceful way to accomplish the goals of sanctions policy, even if the transaction can get accomplished through some other means – by creating immediate real-world economic consequences for the failed attempt that even reporting on attempted transactions just can’t measure up to?
Claude responded:
This is the crux of it, and the sharpest way to answer is: forceful against whom?
Walk through what actually happens to the designated person under each model
In Scenario A, freeze and reject produce the identical outcome for the sanctioned party: they don’t get paid, either way. They’re equally free, either way, to go find the same money — or different money — through Beijing or Istanbul. Freezing the funds doesn’t touch anything the designated person owns, because as established previously, nothing was theirs yet. So the marginal “forcefulness” being described isn’t landing on the sanctions target at all. It’s landing on Customer A — the non-designated party whose money actually gets locked away, indefinitely, based on nothing more than their instruction to pay someone.
That’s a real distinction worth sitting with: freezing in Scenario A is expropriating an unadjudicated third party’s property because of what they attempted, not punishing the person the sanctions regime actually targets.
But there’s something real here too
There is a genuine difference between freeze and reject that survives this reframing, and it’s not nothing: reject hands Customer A their money back, fully unencumbered, free to try the exact same payment again five minutes later through a different bank — the “ammunition” is untouched. Freeze removes that specific pool of liquidity from anyone’s use entirely. If the underlying deal is going to happen at all now, it needs fresh capital, not this capital. That’s a real cost, and it’s the honest, defensible case for the US approach here — it just achieves that cost by seizing the property of someone who hasn’t been found to have done anything wrong, rather than the property of someone who has.
And the EU-family model doesn’t actually leave the attempt costless — it just sequences the cost differently
If Customer A knowingly tried to pay a designated person, that attempt is itself a prosecutable sanctions offense in every jurisdiction covered — participating in or facilitating a breach of the making-available prohibition carries real civil and often criminal penalties, frequently well beyond the value of the blocked transaction itself. So both models are capable of imposing a serious, real cost on Customer A specifically. The difference is procedural: OFAC’s block is automatic and immediate, applied the instant the instruction is given, regardless of whether Customer A knew anything about the designation. The EU-family model waits for an investigation to actually establish knowledge or intent before it converts “you tried this” into a penalty. One bets on speed and volume (freeze everything that touches you, sort out culpability later, if ever); the other bets on accuracy (don’t touch anyone’s property until you can show they did something wrong).
So a gentle pushback on “even reporting can’t measure up” — reporting isn’t the alternative to a real economic consequence, it’s the on-ramp to one. It’s slower and it requires someone to actually build the case. Whether that trade-off is worth it depends on how much you weight “we caught more bystanders along with more real violators, faster” against “we only touched people we could actually show did something wrong.” That’s a genuine values question in sanctions design, not a case of one side simply declining to try.
-
My prompt:
let’s go back to Scenario A: there has to be, in order to effectuate the instruction, an account relationship of some kind, doesn’t there? So why is that case different? You’ve got assets being allocated for a sanctioned party – the only difference is that, in Scenario A, it’s being taken from an existing pooled asset. Or am I missing something?
Claude responded:
You’re not missing something, and it’s a sharp catch — there genuinely is an “account relationship” and something IS being drawn from a pooled asset. But the question is whether that operational fact amounts to a legal interest for the designated person, and here payment law itself already draws the line you’re looking for, independent of sanctions law entirely.
A wire transfer isn’t one asset moving through a pipe — it’s a chain of separate obligations
Under the commercial law that actually governs funds transfers (UCC Article 4A in the US; the EU’s Settlement Finality Directive and the payment-services framework in Europe), a beneficiary acquires zero legal claim against their own bank until that bank “accepts” the payment order — the beneficiary’s bank is only obliged to pay the beneficiary once it accepts the order, and acceptance itself is defined narrowly: the earliest of the bank paying the beneficiary, notifying them of receipt, or receiving settlement for the order. Before that moment, nothing has legally reached the beneficiary — the money belongs to the recipient, free of any strings, only once finality is reached. This isn’t a sanctions-specific fiction. It’s the ordinary rule that governs every wire transfer on earth, sanctions or not — it’s what determines, say, whose money it is if a bank fails mid-transfer, or if a payment gets mis-keyed to the wrong account.
So what is actually happening at your end when you debit Customer A?
Bank A debiting Customer A’s account and sending a payment message isn’t Bank A moving the designated person’s property — it’s Bank A discharging (or beginning to discharge) its own contractual obligation to Customer A, funded out of Bank A’s own balance sheet and correspondent liquidity. That pooled asset is Bank A’s, being drawn down pursuant to A’s instruction; the designated person is a total stranger to that relationship until their own bank actually accepts the order on their behalf. If you refuse at that point, nothing reverses because nothing left — Customer A’s account was never debited (or is simply uncredited if it briefly was), and there’s no moment where the designated person held anything that now has to be “returned.” That’s precisely why refusal doesn’t require a licence the way unwinding a completed freeze does: there’s nothing to unwind.
Why “belonging to/held/controlled by” tracks this, and why OFAC doesn’t
The EU-family test (belonging to, owned, held, or controlled by) is simply importing the ordinary payment-law vesting point rather than inventing its own. OFAC’s blocking regime is the outlier specifically because its “interest of any nature whatsoever, direct or indirect” definition is deliberately written to reach behind that ordinary vesting rule — US commercial law (the same UCC 4A) agrees with the EU-family approach that the beneficiary has no claim pre-acceptance, but OFAC’s sanctions regulations override that for blocking purposes, treating mere intended-beneficiary status as sufficient. So the divergence being described here isn’t a difference in what property law says happens to a payment in flight — both systems’ underlying commercial law agrees on that. It’s that only one of them layers a sanctions-specific rule on top that disregards it.
This also explains the countermand test from the UK “trapped payments” guidance covered previously — asking whether a designated bank still had the right to recall the funds is just asking whether finality/irrevocability had occurred yet. Same doctrinal line, applied to figure out whether the freeze duty travels with the money through a correspondent chain. And it’s why an intermediary bank in the EU-family model typically has nothing of the designated person’s to freeze mid-chain at all: under this same logic, none of the intervening correspondent legs constitute the beneficiary holding anything either, right up until the final beneficiary’s bank accepts.
One thing worth keeping separate: this settles whether the Scenario A/B line is legally real rather than cosmetic — it doesn’t reopen the policy question of whether refuse is a strong enough response on its own. Those are different questions.
-
My prompt:
By refusing or rejecting a transaction, isn’t the regulator copping out? After all, the transaction could be accomplished somewhere else – say, in China or Turkey
Claude responded:
It’s a fair gut reaction, but it conflates two different questions: “does this stop the sanctioned party from ever getting the money” and “what happens to the specific transaction sitting in front of this specific firm.” Those aren’t the same question, and once you separate them, block doesn’t actually beat reject on the first one.
The workaround problem is real, but it’s not a reject-specific problem
If a UK bank refuses to send the payment, sure, the customer can try Beijing, Istanbul, or Dubai. But if a US bank blocks the payment instead, the designated person’s next attempt at financing can just as easily route through those same channels — blocking one wire doesn’t inoculate the rest of their commercial life. This is a well documented, general limitation of unilateral and even coordinated multilateral sanctions: research on sanctions evasion has tracked how Chinese and Russian arms have continued flowing to embargoed destinations for decades through non-dollar channels that sit outside any single regime’s reach. So “they’ll just go elsewhere” is a real critique of sanctions regimes in general — it applies to block just as much as reject. Neither mechanism solves global circumvention; both only capture what happens to already be within a given firm’s grasp at a given moment.
So is releasing that specific transaction really nothing?
Not quite. A rejected payment still comes with a mandatory report to the competent authority in every jurisdiction covered so far — so even though the money moves on, the attempt gets logged: who tried to pay whom, through which counterparties, on what pretext. That’s raw material for future listings, for identifying facilitators, and for building the kind of evidentiary record these regimes’ own courts increasingly demand. It’s a much thinner form of “action” than seizing the money, and it isn’t honest to pretend otherwise — but it isn’t nothing either.
The real reason isn’t laziness, it’s legal exposure
Here’s the part that actually answers the question. The EU, UK, Switzerland, Canada, and Australia are all legal systems where courts have been genuinely aggressive about policing sanctions listings on due-process and property-rights grounds — and the cleanest illustration is that the same person, Mr. Kadi, brought parallel challenges in EU and US courts over the same asset freeze, and the EU courts ruled the listing process lacked fundamental protections while the US courts rejected the equivalent constitutional claims. If that’s how exacting these courts are about freezing a person who has actually been designated, extending that seizure power further — to a non-designated customer’s own money, based solely on their stated intent to pay someone else — would be a considerably bigger and more legally exposed step, one these systems have chosen not to take. The US, operating under IEEPA’s far more executive-deferential tradition, doesn’t face the same internal constraint, which is a large part of why it’s comfortable blocking property whose ownership hasn’t fully vested yet.
There’s a structural reason layered on top of the legal one. The US can afford to cast that wide a net because so much of world trade has no way to avoid touching dollar clearing — roughly 88 percent of foreign-exchange transactions involve the dollar, and the correspondent banking system that actually moves the money concentrates through a small number of banks in New York and London. Blocking a dollar payment captures real marginal value precisely because rerouting around the dollar is genuinely hard. A rejected euro, pound, franc, Canadian, or Australian dollar payment is comparatively easy to complete elsewhere without touching that currency’s clearing system at all, so the deterrent value of seizing a non-designated customer’s funds is lower relative to the legal and political cost of doing it — this half of the explanation is an original synthesis of the two facts above, not something any regulator has stated as its rationale.
And this isn’t a “the EU goes soft” story — the freeze side still bites, hard
Worth remembering: none of this caution applies once a resource actually belongs to the designated party. The clearest proof is sitting in Belgium right now — roughly €210 billion of Russian Central Bank reserves are frozen in Europe, most of it at the Euroclear depository, and that’s a Scenario B freeze, not a reject outcome, because those securities already belonged to the CBR the moment it was designated. And the EU’s own hesitation about going one step further — from freezing that money to actually using it for a reparations loan — is itself a live demonstration of the exact caution just described: Belgium has resisted precisely on expropriation grounds, warning other reserve holders might flee European custody, and Russia’s central bank has already sued Euroclear for roughly $230 billion over the freeze itself. That’s not a regime being casual about property rights; if anything it’s the same instinct that keeps the reject rule in place for in-flight payments, now playing out at nation-state scale.
Self-check
- Kadi I/II outcomes and the EU/US divergence: confirmed across multiple sources including a direct comparison piece and the CJEU’s own case summary.
- Dollar/FX and correspondent-concentration figures: from a 2026 explainer drawing on the Farrell & Newman “weaponized interdependence” literature — solid secondary sourcing, not a primary BIS/Fed data pull.
- Euroclear/CBR figures (~€210bn, ~€193bn at Euroclear, Belgium’s objections, the Russian lawsuit): converging figures across CFR, CEPR, Squire Patton Boggs, and AP reporting from November 2025–January 2026 — figures move slightly by source and date, so treat the exact number as “roughly €200–210bn” rather than a fixed figure if publishing this.
- The causal argument connecting legal-rights culture and dollar centrality to the reject/block design choice is original synthesis — no regulator has published that rationale in those terms.
-
My prompt:
ok… let’s open the aperture a bit. Explain what a compliant firm is supposed to do, for the US, UK, EU, Canada, Australia and Switzerland, in the following 2 scenarios – assuming we’re talking blocking/freezing sanctions only: Scenario A: You receive instructions to make a payment that involved a sanctioned party. Scenario B: You receive funds that involve a sanctioned party. For each scenario, also denote whether the answer is different in the case you are the beneficiary bank or an intermediary bank. Phrase this for a sanctions novice, but feel free to quote text (not full regulatory sections) – like “make economic resources available”, for example. Assume that my goal is to eventually, once I refine the response, make a “Burning Questions” post out of this
Claude responded:
This is exactly the kind of question that makes a good Burning Questions piece, because the honest answer isn’t “six jurisdictions, six rules” — it’s one rule almost everyone agrees on, and one narrow but consequential place where the US breaks from the rest.
Two moves, and two roles, defined simply
A compliant firm facing a sanctioned party has two different levers available, and confusing them is the single most common mistake:
- Freeze/block: take the resource into your own custody, lock it away from everyone — including the customer who originally owned it — and report it. Nobody gets it until a regulator says otherwise.
- Refuse/reject: simply decline to carry out the instruction. The money never leaves the paying customer’s account, so there’s nothing to freeze.
And two roles matter for how this plays out:
- Beneficiary bank: the bank holding the account of the person or entity who’s supposed to end up with the money.
- Intermediary (correspondent) bank: a bank in the middle of the chain, routing the payment onward, with no account relationship to either the sender or the ultimate recipient.
Scenario A: you receive instructions to make a payment that involves a sanctioned party
Picture a customer who isn’t sanctioned asking you to send money to someone who is.
Jurisdiction What you do Beneficiary vs. intermediary bank US (OFAC) Block. Take the funds into a blocked, interest-bearing account. Don’t send them, and don’t hand them back to the customer either. No difference in principle — blocking applies regardless of whether it is the originating or intermediary bank in the chain. A purely blind intermediary with no account relationship to a non-listed related party gets a narrow pass on investigating what it has no way of knowing, but the moment it knows or should know a designated person is involved, it blocks too. UK (OFSI) Refuse. Don’t execute the payment; the customer’s own funds are untouched. Same principle for any bank in the chain — but correspondent banks caught mid-chain have created a genuine practical headache here (see below). EU Refuse — going ahead would mean making economic resources available to the designated person, which every EU regulation prohibits directly or indirectly. Same in principle for whoever in the chain is asked to move the money. Switzerland (SECO) Refuse, for the same reason — Swiss ordinances closely mirror the EU wording, prohibiting third parties from making economic resources available to a listed person. Same in principle. Canada Refuse — completing the payment would breach the ban on making any goods available to a designated person, or providing services to their benefit. Same in principle, though published Canadian guidance addressing intermediary banks specifically the way the US and UK have could not be located. Australia (DFAT/ASO) Refuse — a person commits an offence if they make assets available to a designated person or entity. Same in principle. The one country that flips the answer is the US, and it’s worth pausing on why. OFAC treats a designated person’s status as intended beneficiary of a payment as itself an “interest” in the funds, so the moment the firm has possession or control of the money for the purpose of sending it their way, it’s already blockable property — even though it started out as the customer’s own money and never actually reached anyone. Everyone else in this table requires the resource to actually belong to, or be held or controlled by, the designated person before the freeze duty exists — and a payment instruction that hasn’t been executed yet doesn’t meet that bar. So the divergence isn’t really about freeze versus reject as competing philosophies; it’s about how early each regime decides a sanctioned party has acquired an interest in money that hasn’t arrived yet.
Scenario B: you receive funds that involve a sanctioned party
Now flip it: money has actually arrived, or is already sitting in an account, where a designated person has a real, present interest — as the account holder, or as the completed beneficiary of an inbound transfer.
Jurisdiction What you do Beneficiary vs. intermediary bank US (OFAC) Block, and report within 10 business days. No difference — whoever’s possession or control the funds come within, blocks, subject to the same narrow intermediary safe harbor as above. UK (OFSI) Freeze, and report. The beneficiary bank freezes without question. An intermediary bank is generally fine to keep routing a payment onward provided the funds aren’t owned, held, or controlled by a designated person at the point it’s dealing with them — which gets complicated fast if a designated bank sat somewhere upstream (see below). EU Freeze, and report to the national competent authority. Notably, a bank is explicitly permitted to credit an incoming third-party payment into a frozen account without needing prior authorization for that specific act — the funds simply join the frozen pool once they land. Same logic as the UK: a true intermediary that never holds the designated person’s resources has nothing to freeze; a beneficiary bank freezes on receipt. Switzerland Freeze, and report to SECO. Same principle as the EU. Canada Freeze (functionally, by disclosing the property to the RCMP and being barred from dealing with it) — firms must report property in their possession or control that is owned or controlled by designated persons and freeze such property. Same principle, applied to whoever holds it. Australia Freeze, and notify the Australian Federal Police. Same principle for whoever is holding the asset. This is really the headline finding: on receipt, all six jurisdictions land in the same place. The freeze duty is nearly universal once a designated person actually has a stake in the resource — the interesting divergence lives entirely in Scenario A, where the US alone extends that duty backward to cover an unexecuted instruction.
Two wrinkles worth knowing for intermediary banks specifically
US: OFAC’s own guidance draws the safe-harbor line precisely. An intermediary bank with no account relationship to a non-listed party referenced in a wire, and no actual or constructive knowledge of a blocking issue, isn’t expected to go digging — but the instant it has information suggesting blocked status, the duty to block attaches regardless of its position in the chain.
UK: because the UK (unlike the EU generally) has designated entire banks, correspondent banks kept finding themselves holding payments that had passed through a now-designated bank somewhere upstream, with no clean way to either complete or return them — the industry calls these “trapped payments.” OFSI’s analysis turned on whether the designated bank still had a right of countermand over the funds at that point in the chain: if it had already discharged its role and lost any right to pull the funds back, the funds were no longer considered owned, held, or controlled by that designated bank, so the freeze duty didn’t travel downstream with it. That general licence has since been superseded by later amendments, so it’s an illustration of the reasoning rather than current operative guidance — worth pulling OFSI’s live Russia guidance before citing the mechanism itself.
Self-check
- US: OFAC FAQ 36 (reject example), FAQ 116 (intermediary safe harbor), and 31 CFR 501.603 (blocked-property reporting) pulled directly from ofac.treasury.gov.
- EU: Regulation 36/2012 Article 14 template and the Council’s July 2024 Best Practices document, both previously verified.
- UK: OFSI’s general guidance and reporting pages (gov.uk, ofsi.blog.gov.uk) plus the Trapped Payments general licence publication notice — flagged above as superseded, useful for the reasoning, not for current citation.
- Canada: Global Affairs Canada’s own “Dealings prohibition and asset freeze” and disclosure pages — solid primary sourcing, but nothing found specific to intermediary-bank treatment; that’s a gap in published guidance, not a claim made by extension.
- Australia: DFAT/Australian Sanctions Office guidance notes, all primary and current (2024–2025 dated).
- Switzerland: sourced mainly through a Swiss press account describing the ordinance language rather than a direct ordinance or SECO FAQ pull — worth swapping in the exact ordinance article, and worth checking whether SECO’s FAQs address this reject/freeze point directly before publishing.
- The “when does an interest attach” framing that ties the whole piece together is an original synthesis of the sourced material above, not a line any one source states outright.
-
My prompt:
I knew you were going to add a caveat… it – the second I entered the question, I realized I didn’t include the exceptions, like the NS-PLC list, etc. Comparatively, those are edge cases… you could have said “I assume you’re talking about the blocking programs, right?” and be done with it
Claude responded:
Fair, and that’s the better version of it. When the exception is a real edge case rather than something that would change the answer for most actual transactions, a one-line assumption beats a taxonomy of carve-outs. Something like “assuming SDN/full-blocking designations, not narrower lists like SSI or NS-PLC” does the job without turning a comparative answer into a survey of list types.
Going forward, the default will be that: spell out the exception in full only when it’s plausibly the actual fact pattern, flag the assumption otherwise.
My next prompt:
or if i ask for a more comprehensive survey of options, OK?
Claude responded:
Of course — that’s the trigger for the full breakdown. Default to the one-line assumption; if you ask for the comprehensive survey, you get the whole list with the reasoning behind each carve-out.
-
My prompt:
so, let’s assume my customer A is neither listed nor implicated by ownership and control sanctions. It’s my understanding, therefore, if he instructs me to transfer some funds to a sanctioned part, in the EU, I can refuse the instruction. However, in the US, I am obligated to take the funds and freeze them. Am I mistaken?
Claude responded:
You’re not mistaken about the pattern, but the accurate version of it hinges on which US list the counterparty is on, so let’s walk through both sides properly.
EU: refuse, don’t freeze A’s funds
This is the “making available” half of the earlier discussion. Customer A isn’t designated and the money is still A’s property, so it never meets Article 2(1)’s trigger (belonging to, owned, held, or controlled by a designated person). Executing A’s instruction would be the firm making resources available to the designated person, which Article 2(2) flatly prohibits absent a derogation. So the firm declines to execute, and A’s account is untouched, not frozen. There is one obligation people miss here: the Council’s Best Practices guidance is explicit that firms must report attempted transactions, including customer attempts to make funds or economic resources available to a designated person without authorization, to their national competent authority. So “refuse” is the transaction-level answer, but it comes bundled with a reporting duty, not a freeze.
US: block, don’t reject, don’t return to A
This is where the mechanics genuinely diverge, and the reason is definitional. OFAC’s blocking obligation attaches to property or interests in property that are within the United States or come within the possession or control of a U.S. person, and “interest” is defined expansively as an interest of any nature whatsoever, direct or indirect, present, future, or contingent. A designated person named as the intended beneficiary of a payment has exactly that kind of interest in the funds the moment the firm, a U.S. person, has possession or control of them for the purpose of completing the transfer, even though the money started out as A’s and A was never designated. OFAC’s own FAQ on this is unambiguous: once property is blocked, title remains with the blocked person, and the exercise of ownership powers is suspended absent OFAC authorization; the funds must be frozen, not seized, and reported. And the obligation to block, rather than reject, applies regardless of whether the designated person is the originator or the intended recipient of the funds. So the firm takes custody of A’s payment, places it in a blocked, interest-bearing account, files the initial blocked-property report within 10 business days under 31 CFR 501.603, and then includes it in the comprehensive Annual Report of Blocked Property due every September 30 for anything still blocked as of the prior June 30. The money does not go back to A.
The contrast, side by side
EU (Art. 2(1)/(2) template) US (OFAC blocking programs) Trigger Resource already belongs to/owned/held/controlled by the designated person Any interest of any nature — including a contingent interest as intended beneficiary — once the property is within a U.S. person’s possession or control What happens to A’s funds Nothing; instruction is simply not executed, funds stay in A’s ordinary account Removed from A’s ordinary account and placed in a blocked, interest-bearing account; A no longer has free use of them Ownership A retains full ownership throughout Title is treated as passing to/vesting in the blocked person once blocked Reporting Attempted “making available” reported to the national competent authority Initial blocked-property report within 10 business days (31 CFR 501.603), then annual reporting each September 30 while still blocked Where this framing needs a caveat
This only holds for a US counterparty that’s a blocked person, meaning someone on the SDN list or otherwise subject to OFAC’s blocking authority (including via the 50 percent rule). If the “sanctioned party” is instead someone subject only to OFAC’s narrower sectoral-style restrictions, such as the Sectoral Sanctions Identifications List under the Russia/Ukraine directives, there’s no blockable interest at all: OFAC’s own FAQ 36 example is exactly this case, an underlying dealing that’s prohibited but has no SDN or blocked-government interest in it, and the answer there is reject, or don’t process and return to the originator, reported under the separate rejected-transaction regime at 31 CFR 501.604. So the real dividing line isn’t “EU versus US” as such, it’s whether the applicable regime treats the counterparty as subject to a full asset freeze/blocking designation (EU Annex listing, OFAC SDN) or a narrower restriction on specific dealings (OFAC SSI, and arguably the EU’s own sectoral trade and financial restrictions on Russia that don’t run through personal designation). Matched apples to apples, both EU and OFAC would tell you to reject; it’s specifically the blocked-person case where OFAC’s answer flips to block while the EU’s stays at refuse.
Self-check
- OFAC FAQ 9 (blocking definition, title/possession language) and FAQ 36 (reject vs. block, with the Iran third-country example) pulled directly from ofac.treasury.gov.
- 31 CFR 501.603 (blocked-property reports, 10-business-day initial report, September 30 annual report) and 501.604 (rejected-transaction reports) confirmed against Cornell/GovInfo CFR text and a recent OFAC annual-report reminder.
- The “regardless of originator or recipient” framing and the broad “interest of any nature whatsoever” phrasing came from secondary sources (a law-firm compliance blog and a client alert) rather than a direct CFR pull of that exact clause — both are standard, uncontroversial restatements of OFAC’s general definitions section, but if citing the definition itself for publication, pull the exact text from the specific program’s CFR part (the phrasing is boilerplate but repeated part by part, e.g. 31 CFR 594.311, 515.312, etc., rather than centralized in one place).
- The claim that a blocked person’s title is treated as attaching to an unexecuted, in-process payment is a synthesis of FAQ 9’s title language plus the broad interest definition, not something one source states in that combined form — flagged as inference, not a verified single-source claim.
-
The prompt:
Speak to the following: The Federal Register vs. the OFAC website: which one is legally operative, and what about time gaps between the two?
The response:
The Federal Register is legally operative for OFAC actions that require notice-and-publication; the OFAC website is not a legal instrument.
The distinction turns on the type of action. For designations under most sanctions programs, OFAC’s legal authority to add a party to the SDN List derives from the underlying statute and executive order, and the designation becomes effective when the Director (or Secretary) signs the determination, not when it appears anywhere. OFAC then publishes the SDN List update on its website, typically the same day, and follows with a Federal Register notice, sometimes days or weeks later.
For rules that carry legal force in their own right, the Federal Register is authoritative. Amendments to the sanctions regulations in Title 31 CFR, general licenses that OFAC chooses to codify, and formal rulemakings take legal effect on the date and terms stated in the Federal Register. The Federal Register text is the official version; if the website and the published notice ever diverged, the Federal Register controls.
On the time gaps: the practical answer for compliance purposes is that OFAC treats a designation as effective from the moment of the action, and the SDN List posting on the website is the operational trigger the industry screens against. The Federal Register notice is a legal formality that documents the action and satisfies publication requirements, but the absence of a same-day Federal Register notice does not delay the legal effect of a designation. A party added to the SDN List on Tuesday is blocked as of Tuesday, even if the corresponding Federal Register notice does not run until the following week. The prohibition attaches to the U.S. person’s dealings with blocked property, and OFAC’s position is that the obligation exists once the property interest is blocked, independent of publication timing.
Two nuances worth flagging. First, some due-process and constructive-notice questions have been litigated, and courts have generally accepted that public availability of the SDN List provides adequate notice, which is why the website posting matters practically even though it is not the legal instrument. Second, the effective date stated in a Federal Register notice may differ from the website posting date; where a specific legal deadline or wind-down period runs from an effective date, read that date from the Federal Register text rather than inferring it from when the website was updated.
If you want, I can pull the specific statutory publication requirements (for example, the IEEPA and APA provisions and any program-specific notice language) to tighten the citations.
-
My prompt:
EU sanctions say you can’t make economic resources available to a Designated Person. Does that mean you freeze the resources, or do you refuse the transaction? Show your work
Claude responded:
Neither, cleanly — and the question itself flags where people go wrong, because EU sanctions regulations don’t treat “freeze” and “make available” as two labels for the same act. They’re two separate obligations, and which one governs a given fact pattern turns on a single question: do you already have the resource in your possession, custody, or control, or would you be the one handing it over?
The architecture
Nearly every EU sanctions regulation runs the identical two-paragraph template. Regulation 36/2012 (Syria) is a clean illustration: Article 14(1) freezes all funds and economic resources belonging to, owned, held, or controlled by listed persons, while Article 14(2) separately prohibits making funds or economic resources available, directly or indirectly, to or for the benefit of those persons. The Council’s own compliance guidance confirms this isn’t a Syria quirk: financial restrictive measures under EU regulations consist of freezing the funds and economic resources of designated persons, plus a separate prohibition on making funds and economic resources available to them. Regulation 269/2014 (Russia/Ukraine) uses the same two-limb split at Article 2(1)-(2), just with different article numbering.
Freeze applies to what’s already theirs and already in your hands
“Freezing” is defined as a status, not a transaction. For funds, the operative CJEU language is that freezing prevents any move, transfer, alteration, use of, access to, or dealing with funds in any way that would change their volume, amount, location, ownership, possession, character, or destination — and a March 2026 CJEU ruling on Regulation 269/2014 reads that as applying absolutely and unconditionally, extending even to ancillary rights like voting attached to frozen securities. Economic resources get the parallel treatment: freezing prevents their use to obtain funds, goods, or services. Critically, freezing doesn’t change who owns the thing and doesn’t require you to divest yourself of it: financial restrictive measures do not involve a change in ownership of frozen funds and economic resources and are not punitive, and a person who already holds or controls a designated person’s funds or economic resources is not required to give them up or seek authorization merely to continue holding them. What requires authorization is any new dealing with them.
Making available applies to what would newly become theirs
This is where “refuse the transaction” comes in. The CJEU (Möllendorf, C-117/06) reads “making available” broadly: rather than a specific legal category of act, it covers whatever acts are necessary under the applicable national law for a person to obtain full power of disposal over the resource, and it applies regardless of whether adequate consideration is paid. There’s nothing to freeze here, because you’re not yet holding anything that belongs to the designated person — you’re holding your own funds, goods, or services and about to transfer disposal of them. So the compliance action isn’t a freezing decision, it’s a straight refusal: don’t complete the transaction absent a derogation from the competent authority.
Why the same wire can trigger both obligations at once
A frozen account receiving an incoming payment shows both rules operating on a single transaction from opposite sides. On the receiving end, a financial institution that receives funds transferred by a third party into a customer’s frozen account is permitted to credit those funds without prior authorization — Regulation 269/2014 builds this in explicitly, stating the making-available prohibition does not prevent crediting of frozen accounts by institutions that receive funds transferred by third parties onto a listed person’s account. But on the sending end, the remitting party needed authorization before initiating that transfer, because from their side, routing funds to a designated person’s account is exactly the act Article 2(2) prohibits. The receiving bank freezes (accepts the credit, then locks it down as part of the frozen balance); the remitter should have refused to send it in the first place.
The trap worth flagging: indirect making available
The refusal duty doesn’t stop at the listed name. Making resources available to a non-listed entity that is owned or controlled by a listed person is, in principle, treated as indirectly making them available to the listed person, unless a case-by-case assessment shows the resources won’t be used by or for that person’s benefit — this is the same ownership/control test (50%+ or the control indicators) that comes up again and again in this area.
Self-check
- Reg 36/2012 Art 14 and the Reg 269/2014 Art 2 language are confirmed against primary/near-primary text (Wikisource reproduction cross-checked against a March 2026 CJEU judgment quoting the operative articles directly).
- The two-limb “freeze plus prohibition on making available” framing and the paragraph 30/44/57/59/68 content come from the Council’s July 2024 “EU Best Practices for the effective implementation of restrictive measures” (doc 11623/24) — non-binding Council guidance, not itself the law, and originally LIMITE-marked but retrievable from the public Consilium document register.
- The CJEU case cited on “absolutely and unconditionally” (C-465/24, judgment of 12 March 2026) postdates my reliable knowledge and was pulled from a secondary reproduction (financialcrime.lu), not EUR-Lex/InfoCuria directly — worth a direct EUR-Lex pull before citing the CELEX number anywhere public.
- Article numbering (2(1)-(2) vs. 14(1)-(2), etc.) varies by regulation even though the substantive template is uniform; derogation categories and exact definitions also live in each regulation’s own Article 1 and derogation articles, so don’t assume identical wording across regimes without checking.
-
The prompt:
Summarize UK sanctions regulations and exemptions regarding Basic Needs Allowance, including any relevant definitions, in light of today’s FAQs, attached here. plesse provide your response for an audience of non-UK sanctions professonals who are not lawyers.
The final response:
The legal architecture beneath BNA
Primary legislation. The Sanctions and Anti-Money Laundering Act 2018 (SAMLA, 2018 c.13) is the enabling statute for essentially all post-Brexit UK sanctions. It doesn’t itself list licensing grounds – it authorises Treasury/the Secretary of State to make regime-specific secondary legislation.
Regime-specific regulations. Each sanctions regime (Russia, Iran, Syria, Belarus, Chemical Weapons, and so on) has its own statutory instrument made under SAMLA – for example the Russia (Sanctions) (EU Exit) Regulations 2019 (SI 2019/855). Each of these includes a schedule titled “Treasury licences: purposes,” which is the actual legal source of each licensing ground. I confirmed this schedule structure directly: in the Chemical Weapons (Sanctions) (EU Exit) Regulations 2019 (SI 2019/618), Schedule 2, paragraph 2, “Basic needs” reads almost exactly as you’d expect:
To enable the basic needs of a designated person, or (in the case of an individual) any dependent family member of such a person, to be met.
For individuals, it lists medical needs, food, insurance premiums, tax, rent or mortgage, and utility payments as included needs. The Russia Regulations carry the equivalent ground at Schedule 5, paragraph 2, though I wasn’t able to pull the exact Russia-specific wording (only confirmed its existence and paragraph position via secondary indices) – the substance is consistent across regimes but the schedule number and paragraph numbering differ regime to regime, so it’s worth checking the specific regulation rather than assuming identical numbering.
Where basic needs sits among the other grounds. Per OFSI’s own “How to apply for a financial sanctions licence” guidance, the generally available licensing grounds are:
- basic needs
- legal fees and expenses
- prior obligations (pre-designation contracts)
- routine holding or maintenance of frozen funds/economic resources
- implementation of a judicial, administrative, or arbitral decision or lien
- post-designation judicial decisions (non-UN designations only)
- extraordinary expenses
- extraordinary situations (non-UN designations only)
- humanitarian assistance
- diplomatic missions
- insolvency
- divestment
That page also confirms the general/specific licence mechanics I described earlier: general licences are issued by OFSI at its own initiative for a defined class of activity, and OFSI does not accept applications for them – you either fall within one or you apply for a specific licence.
The direct throughline to BNA
This is the most useful find. OFSI’s “Designated Individuals Licensing Principles” (a policy document sitting under the General Guidance, last updated 2 February 2026) already contained a formal benchmark for basic needs, at Principle 4:
Licensing should permit basic needs, which OFSI considers to include the reasonable standard of living as compared to a person receiving the net UK median wage.
And Principle 4(a): “Ordinarily, Principle 4 will be generally satisfied by granting a designated individual the net UK median wage.”
That’s a striking match to today’s BNA FAQs, with one difference worth flagging as a genuine shift rather than a restatement: the February principle benchmarks to the net UK median wage (an individual figure), while today’s FAQ benchmarks to a median income household. A household benchmark is not the same number as an individual wage benchmark – it implicitly accounts for household composition and dependents in a way a flat wage figure doesn’t. I can’t tell you from the FAQ text alone whether that’s a deliberate policy refinement or just looser drafting, but it’s the kind of distinction worth watching for in OFSI’s next General Guidance update, since it would change the actual capped amount a DP receives.
Historical background, clearly caveated as background rather than confirmed lineage: In 2023, litigation against OFSI (Fridman v HMT, the first challenge to an OFSI licensing decision under the Russia Regulations) resulted in disclosure of a previously secret internal “Basic Needs Framework,” which split basic needs into “core needs” (proposed to be met by a flat monthly sum pegged to median wage) versus needs beyond that. The High Court dismissed the claim and confirmed OFSI retains “residual discretion to refuse to grant a licence, even if the conditions for the grant of a licence are met” – a principle that reappears in today’s FAQ as “compliance with those conditions does not guarantee that a licence will be renewed or varied.” Commentators at the time (Law Gazette, November 2023) explicitly called for OFSI to formalise exactly this kind of standing monthly allowance rather than handling it case by case. I can’t point to a document that explicitly says “BNA is the formalisation of the Basic Needs Framework” – but the throughline from the 2023 disclosure, to the February 2026 Designated Individuals Licensing Principles, to today’s FAQ is consistent enough that I think it’s a fair inference, not a stretch.
A limitation worth being upfront about
I tried to independently verify FAQs 197-202 on OFSI’s live FAQ page. The version I could retrieve carries a “last updated” stamp of 29 May 2026, predating your attachment’s 21 July 2026 date – so I couldn’t cross-check the exact text against a live, independently-fetched copy; I’m relying on your attachment as the primary source for the BNA-specific content itself. What I can confirm independently is that the FAQ numbering, format, and “Added on:” convention in your document are consistent with OFSI’s genuine, ongoing FAQ series (which runs to at least FAQ 186 in the version I retrieved), so the document is stylistically and structurally what it claims to be – I just can’t yet corroborate the specific new entries from a second, independent live source.
Source list
Primary legislation and regulations
- Sanctions and Anti-Money Laundering Act 2018 (c.13) – legislation.gov.uk/ukpga/2018/13
- Chemical Weapons (Sanctions) (EU Exit) Regulations 2019 (SI 2019/618), Schedule 2, para 2 (“Basic needs”) – legislation.gov.uk/uksi/2019/618/schedule/2/paragraph/2/data.html
- Russia (Sanctions) (EU Exit) Regulations 2019 (SI 2019/855), regulation 64 and Schedule 5 – legislation.gov.uk/uksi/2019/855/regulation/64
OFSI guidance and policy
- OFSI, “How to apply for a financial sanctions licence” (last updated 1 September 2025) – gov.uk/guidance/licences-that-allow-activity-prohibited-by-financial-sanctions
- OFSI, “UK Financial Sanctions FAQs” (updated 29 May 2026 as retrieved) – gov.uk/government/publications/uk-financial-sanctions-faqs/uk-financial-sanctions-faqs
- OFSI, “Designated Individuals Licensing Principles” (updated 2 February 2026) – gov.uk/government/publications/financial-sanctions-licensing/ofsi-licensing-designated-individuals-licensing-principles–2
- OFSI, “UK financial sanctions general guidance” (updated 28 January 2026) – gov.uk/government/publications/financial-sanctions-general-guidance/uk-financial-sanctions-general-guidance
- OFSI Blog, “OFSI successfully defends first court review” (Fridman v HMT) – ofsi.blog.gov.uk/2023/11/28/ofsi-successfully-defends-first-court-review
Commentary (context on the pre-BNA “Basic Needs Framework”)
- Law Gazette, “Sanctions: Time for a general licence to cover basic needs” (13 November 2023) – lawgazette.co.uk/practice-points/time-for-a-general-licence-to-cover-basic-needs/5117856.article
- Corker Binning, same title/content (23 September 2024 mirror) – corkerbinning.com/time-for-a-general-licence-to-cover-basic-needs