Switzerland adopted the EU's 21st sanctions package against Russia and Belarus on November 4, 2026, effective November 5, 2026. The Swiss Federal Council moved in two stages: the Federal Department of Economic Affairs, Education and Research (EAER) expanded the sanctioned parties list on November 4 at 11 p.m., and the substantive measures followed a day later. While this may seem like EU alignment, it's not an exact copy.
If you manage Name Screening and sanctions controls across Swiss and EU entities, the differences between the two regimes are where errors will accumulate.
Why These Mistakes Keep Happening
Teams often equate "aligned with the EU" to "identical to the EU." This shortcut is understandable. Swiss and EU packages share structure, annex numbering, and political intent, so a control built for one is often reused for the other.
However, Switzerland implements sanctions through its own legal framework, using the Ukraine Ordinance and the Belarus Ordinance, administered by the State Secretariat for Economic Affairs (SECO). Timing and thresholds differ, and Switzerland exercises discretion. The Swiss regime is running about three and a half months behind the EU's measures from July 23, 2026. Compliance programs based on a single sanctions calendar will miss these offsets.
Mistake 1: Assuming Swiss Lists Mirror EU Lists One-for-One
Why it happens: Because Swiss lists closely track the EU, teams stop maintaining a separate Swiss list and rely on the EU list as a proxy.
Consequence: Switzerland has held back on certain measures, like asset freezes on two Russian nationals and stricter export controls on 14 third-country companies, citing insufficient exposure. Applying the EU outcome to a Swiss counterparty may lead to over-blocking a customer you're allowed to serve or applying the wrong control category. Over-blocking creates customer harm and unnecessary escalations; under-blocking creates breach risk.
Fix: Maintain jurisdiction-tagged list data. Every Designated Persons and Entities record in your screening engine should include its issuing authority and effective date. Your Swiss entities should screen against the Swiss annexes, not an EU extract. Document any divergence and decision when a hit exists on the EU list but not the Swiss one.
Mistake 2: Treating Every Listing as an Asset Freeze
Why it happens: Name Screening alerts often collapse into a binary: match or no match. However, the package uses several restriction types, and a single-outcome workflow can't represent them.
Consequence: The package expands asset freezes to 254 individuals, companies, and organizations, with entry and transit bans for individuals. It also introduces transaction bans, covering 33 Russian banks, one third-country bank, 17 financial institutions, and crypto-asset service providers, among others. Applying a full freeze where only a transaction ban applies (or vice versa) is a handling error.
Fix: Build restriction type into your alert disposition. Analysts should see whether a hit triggers Freezing Without Delay, a transaction prohibition, an export restriction, or a vessel ban. Train on the annex structure so analysts know which instrument they're reading.
Mistake 3: Missing Delistings and Wind-Down Windows
Why it happens: Teams focus on additions. Removals and time-limited exemptions generate no urgency, so they linger in a backlog.
Consequence: Six individuals and one company were delisted following EU delistings. Stale entries generate false positives and may lead to wrongly frozen funds. Wind-down authorizations are time-limited: SECO may grant up to three months for withdrawing funds or closing accounts at newly listed institutions, but only for accounts owned or controlled by Swiss or EEA nationals or residence-permit holders. Applications are due within three months of the listing date. Miss that window, and a legitimate exit path closes.
Fix: Run delistings through the same change-control process as additions. For wind-downs, log the listing date at screening and automatically calendar the application deadline. Confirm ownership and destination conditions before filing, as the authorization is conditional.
Mistake 4: Treating Crypto Restrictions as a Wallet-Provider Problem
Why it happens: The earlier rule was narrower, limited to wallet, account, and custody providers. Teams scoped controls to that perimeter and haven't revisited it.
Consequence: The ban on enabling Russian nationals and residents to own, control, or sit on the management bodies of Swiss or EEA crypto companies now covers all crypto service providers, subject to existing exemptions. A trading platform, exchange, or other provider previously outside scope may now have an ownership and governance problem. The same extension applies under the Belarus Ordinance. Customer-facing screening won't catch this, as the exposure is in your cap table and board composition.
Fix: Extend Beneficial Owner Identification and governance reviews to all crypto service provider relationships, including counterparties and, if you're a provider, your own management bodies. Check each case against existing exemptions rather than assuming they apply. Treat this as a Customer Due Diligence trigger event, not a one-time list update.
Mistake 5: Overlooking Dates, Reporting Deadlines, and Belarus Offsets
Why it happens: The package has many staggered dates, and teams focus on the headline effective date of November 5, 2026.
Consequence: Several obligations run on different clocks. LNG operators relying on the new exception must report 2025 volumes by December 7, 2026. The LNG terminal services ban starts on January 1, 2027. Contracts for newly banned imports concluded before November 5, 2026, may be performed until February 6, 2027, under the Ukraine Ordinance. However, the Belarus equivalent applies to contracts concluded before November 4, 2026, and performed by February 5, 2027, one day earlier. Applying the Russia date to a Belarus-linked contract could mean performing after the permitted window.
Fix: Keep a single obligations register with one line per measure: instrument, article, trigger date, end date, and owner. Never share a date across the Ukraine and Belarus Ordinances without checking each. Note that several licensing grounds and transitional exemptions for divestments and wind-downs were extended to December 31, 2027, so confirm which exemption you're relying on.
Prevention Checklist
- Tag every list record with issuing authority and effective date; screen Swiss entities against Swiss annexes.
- Document each Swiss/EU divergence, including the two nationals and 14 third-country companies not yet designated.
- Map alert dispositions to restriction type: asset freeze, transaction ban, export restriction, vessel ban.
- Process delistings with the same rigor as additions.
- Calendar the three-month wind-down application deadline from each listing date.
- Extend crypto ownership and management-body reviews to all crypto service providers.
- Maintain an obligations register with separate Ukraine and Belarus Ordinance dates.
- Escalate to your MLRO any case where a Swiss and EU outcome conflict.
- Re-test your screening configuration against the November 4 and 5, 2026, effective times.
Alignment is a starting assumption, not a conclusion. Verify it measure by measure.





