You run dual-regime name screening because you have to. But if you're treating OFAC and OFSI lists as interchangeable, you're building compliance gaps into your program.
The myth problem stems from proximity. OFAC and OFSI coordinate closely through their Enhanced Partnership, meeting annually and publishing joint guidance. Your screening vendor probably bundles both lists into the same workflow, making it easy to assume the regimes work the same way.
They don't. The differences change how you identify hits, calculate ownership thresholds, and what you're required to report. Here's what sanctions analysts get wrong most often.
Myth 1: The 50% ownership rule works the same in both regimes
Reality: OFAC aggregates ownership across multiple blocked persons under its 50 Percent Rule. If three designated individuals each own 20% of an entity, OFAC treats that entity as blocked because the combined ownership exceeds 50%.
OFSI doesn't aggregate. Under UK sanctions, you apply an ownership test separately for each designated person. That same entity with three 20% shareholders wouldn't automatically trigger a freeze under OFSI's ownership threshold alone.
OFSI also applies a separate control test. An entity can be subject to UK sanctions even if no single designated person owns 50% or more, if a designated person exercises control through board seats, voting arrangements, or operational influence. Your screening logic needs to account for both tests independently. A single global "50% rule" filter won't catch everything.
Myth 2: General licenses operate the same way across jurisdictions
Reality: OFAC general licenses typically authorize specific activities without requiring you to notify the agency or submit periodic reports. You confirm your transaction fits within the authorization, document your analysis, and proceed.
OFSI general licenses often include notification or reporting requirements. You might need to inform OFSI that you're relying on a specific license, or submit regular reports on the activities conducted under that authorization.
This difference matters for operational design. If your sanctions team treats a UK general license the same way it treats a US general license, you may be out of compliance with OFSI's procedural conditions. Your license management system needs jurisdiction-specific checklists.
Myth 3: Recordkeeping obligations are basically the same
Reality: Both regimes require you to maintain records of blocked property and authorized transactions, but the retention periods and reporting deadlines differ.
OFAC requires financial institutions to file annual reports of blocked property by September 30 each year. OFSI uses a different annual reporting deadline and different data fields in its reporting templates.
If you're using a single consolidated recordkeeping system for both regimes, make sure your compliance calendar flags the correct deadline for each jurisdiction. Missing an OFSI annual report because your team is keyed to OFAC's September 30 deadline creates an unnecessary enforcement risk.
Myth 4: Jurisdictional reach is comparable between the two regimes
Reality: US sanctions have significant extraterritorial reach. OFAC can penalize non-US persons for conduct that causes a US person to violate sanctions, or for transactions that facilitate or evade US sanctions even if no US person is directly involved. Secondary sanctions programs extend US enforcement authority to foreign entities that engage in specified activities with sanctioned jurisdictions or sectors.
UK sanctions rely primarily on territorial and nationality-based jurisdiction. OFSI generally asserts authority over UK persons, entities incorporated or operating in the UK, and conduct occurring in UK territory. While OFSI has taken a broad interpretation of these jurisdictional concepts in recent enforcement cases, the legal framework differs structurally from OFAC's approach.
For a multinational institution, this means your risk assessment has to account for asymmetric exposure. A transaction involving a non-US subsidiary and a non-UK counterparty may still create US sanctions risk if it touches the US financial system or involves US-origin goods. That same transaction may not create UK sanctions risk unless it involves a UK person or UK territory.
Your training materials and escalation protocols should make this distinction explicit. Sanctions analysts need to understand that "no US nexus" doesn't mean "no OFAC risk," and that UK jurisdiction doesn't automatically extend to your offshore branches in the same way US jurisdiction might.
Myth 5: Enforcement approaches align because the agencies coordinate policy
Reality: Both agencies consider voluntary disclosures when calculating penalties, but they apply different mitigation frameworks and penalty calculations.
OFSI's civil enforcement regime now operates on a strict liability basis. You can be penalized for a sanctions breach even if you had no knowledge of the violation and took reasonable care to prevent it. This shift brings OFSI closer to OFAC's enforcement model in some respects, but the penalty calculation methodologies still differ.
OFAC applies the Economic Sanctions Enforcement Guidelines, which use a base penalty amount adjusted by aggravating and mitigating factors. OFSI applies its own penalty framework under UK regulations. The weight given to specific factors, like compliance program quality or management involvement, may differ between the two agencies.
If you're preparing a voluntary disclosure, don't assume that a submission to OFAC will satisfy OFSI's expectations, or vice versa. Each agency has its own disclosure process, criteria for evaluating cooperation, and settlement practices. You need jurisdiction-specific legal counsel for each disclosure.
What to do instead
Stop treating OFAC and OFSI as plug-and-play equivalents. Build jurisdiction-specific controls into your screening, interdiction, and reporting workflows.
Start with your screening rules. Make sure your system can apply OFAC's aggregation logic and OFSI's separate ownership and control tests independently. If your vendor's platform doesn't support parallel logic paths, you need manual review procedures that fill the gap.
Review your general license procedures. Create jurisdiction-specific checklists that capture notification and reporting requirements for UK licenses. Train your team to check procedural conditions, not just substantive authorizations.
Audit your compliance calendar. Confirm that your recordkeeping and reporting deadlines reflect the correct dates for each jurisdiction. If you're using a single global deadline, you're probably missing one of them.
Update your jurisdictional risk assessments. Map out which entities, branches, and transaction types create exposure under each regime. Don't assume that avoiding US nexus eliminates OFAC risk, and don't assume UK jurisdiction mirrors US jurisdiction.
Finally, if you're relying on the Enhanced Partnership as evidence that the regimes are converging, read the joint guidance they published in June 2026 following their January exchange in London. It's a side-by-side comparison that highlights differences as much as similarities. Use it as a gap analysis tool, not a reassurance document.
The agencies coordinate policy. Your compliance program still needs to comply with two different legal frameworks.
