← The Embargo Brief
Issue 11 · 9 July 2026

5,802 Removals, Thousands of Additions: The July 3 Consolidated List Reset

A single-day sweep on 3 July touched every major screening list simultaneously — 5,802 removals and thousands of new additions across nine jurisdictions. Here is what moved and why it matters.

Reported by Argus, Embargo’s analyst engine · Checked against primary sources · 5 min

The number 5,802 appears in the removal column of every alert dated 3 July — US BIS, US OFAC, US State, US DHS, EU, UK OFSI, Switzerland, Australia, Canada. The same count, across nine separate sync events. That uniformity is the tell: this is not a wave of individual delistings driven by policy. It is a bulk database reconciliation, a moment where the Consolidated Screening List (CSL) infrastructure pruned duplicate or legacy entries that had accumulated across source lists. The removals include names as varied as Tehrik-I-Taliban Pakistan and JSC Zelenograd Nanotechnology Center — entities on opposite ends of the sanctions universe. What they share is presence in a list architecture that was apparently carrying redundant records.

Compliance teams should not read 5,802 removals as 5,802 delistings. The underlying designations — SDN entries, BIS Entity List entries, UN consolidated entries — are almost certainly intact. What changed is the CSL's internal record count, not the legal exposure. If your screening system queries the CSL directly and you saw a mass-clear event on 3 July, verify against the authoritative source lists before concluding any counterparty is clean. The CSL is a convenience aggregation. OFAC's SDN list, BIS's Entity List, and OFSI's consolidated list are the instruments of record.

The Addition Side: Breadth Across Lists

The addition counts on 3 July vary sharply by jurisdiction — from 89 at US BIS to 5,539 at Switzerland — and that variance reflects how each jurisdiction's sync window captures cross-list overlaps rather than the number of genuinely new designations. Switzerland's 5,539 additions span thirteen source lists including the EU Financial Sanctions, Swiss SECO, BIS Entity List, and the Denied Persons List. Canada's 4,135 additions include the UFLPA Entity List, which is notable: Canadian operators screening against the CSL will now surface Uyghur Forced Labor Prevention Act entities in their results, a practical expansion of supply-chain exposure for any firm with dual US-Canada compliance obligations.

Enjoying this free preview?

Enter your email to keep reading and get future issues delivered.

The US State alert adds 11 entities spanning Nonproliferation Sanctions, OFAC SDN, and UN Consolidated Sanctions — a tight cluster that signals proliferation-related designations rather than Russia-Ukraine or narcotics action. US BIS added 89 across the BIS Entity List, Denied Persons List, and Non-SDN MBS List. The Denied Persons List additions are worth isolating: a Denied Persons List entry carries a flat export prohibition regardless of license availability, a harder stop than most Entity List entries, which typically trigger a presumption of denial reviewable case by case.

Regulatory activity by jurisdiction
Count of source updates
BAFA
5
Australia
2
Canada
2
EU Official Journal
2
UN
2
EU
1
Fig. 1Published alerts by jurisdiction, week of Jul 2.

EU Corrigenda: The June 15 Russia Package Gets Corrected

Two corrigenda landed in the EU Official Journal this week — OJ:L_202690561 and OJ:L_202690562 — correcting Council Implementing Regulation (EU) 2026/1362 and Council Decision (CFSP) 2026/1363, both dated 15 June 2026, both implementing Russia restrictive measures under the (EU) 2024/1485 and (CFSP) 2024/1484 frameworks. Corrigenda to Russia sanctions instruments are not unusual — the June package was the latest in a sequence of rolling EU Russia measures — but they are operationally significant. A corrigendum can fix a name spelling, an entity identifier, a date, or a geographic qualifier; any of those changes can flip a screening hit from a false positive to a true match or vice versa. Until the corrected text is reviewed against your entity records, any screening conducted solely against the original 15 June text is potentially stale.

BAFA, the German export control authority, separately published an update to the annexes of the EU Dual-Use Regulation this week — advance publication of amended control list annexes. For exporters classifying items under the EU's dual-use framework, this is the moment to pull the updated annexes and re-examine any classification opinions issued against the prior version. BAFA also flagged a reinstatement of sanctions against Iran, consistent with the snapback mechanism that re-engaged UN and EU measures. The Iran item is brief in the briefing material and carries no entity-level detail, but the direction of travel — more designations, not fewer — is consistent with the trajectory of Iran-related controls since late 2025.

The Late-Week Additions: Ryzhkov Off, One Entity On

On 7 July, both Australia DFAT and Canada SEMA removed Nikolai Ivanovich Ryzhkov — and a truncated variant entry, "k RYZHKOV" — while adding one new entity across both lists. Ryzhkov, the former Soviet Prime Minister who died in February 2024, had been designated under Russia-related measures. His removal is administrative housekeeping following death, not a political softening. The single addition, appearing simultaneously on Canada SEMA and Australia DFAT, suggests coordinated Five Eyes-adjacent list maintenance rather than unilateral action. The addition's identity is not named in the briefing material; the difftable would carry the detail.

On 9 July, the UN Consolidated Sanctions list recorded one further addition. Single-entity UN additions outside a full Security Council sanctions committee session sometimes reflect technical list corrections — a name variant brought into the main entry — rather than a fresh designation. Watch the relevant committee's public statements for confirmation.

BAFA
17th Export Control Information Day – Registration Open
BAFA
17th Export Control Information Day – Postponement of Registration Start
BAFA
Aktuelle Information zum Iran-Embargo
BAFA
Aktualisierung der Anhänge der EU-Dual-Use-Verordnung
BAFA
Aktualisierung des Merkblatts „Optimierte Antragstellung“
EU
Screening list update — 1594 entities added (EU Financial Sanctions, Swiss SECO Sanctions, OFAC SDN List, UK Financial Sanctions, UN Consolidated Sanctions, Australia DFAT Sanctions, Canada SEMA Sanctions, Nonproliferation Sanctions, BIS Entity List, PLC List, Denied Persons List, Sectoral Sanctions (SSI), UFLPA Entity List), 5802 removed
Fig. 2Regulatory chronology, week of Jul 2. Dates are publication dates from the primary sources.
· · ·

The Diff — This Week

No registry list changes are recorded this week. The action is entirely in the screening list sync layer — additions and removals processed through the CSL rather than through direct registry amendments. The chart above shows the addition volume by jurisdiction; the scale difference between Switzerland and US BIS is a function of list-overlap counting methodology, not of enforcement intensity. The single most operationally material item in the diff is the EU corrigenda pair: corrections to a Russia package less than four weeks old suggest the original publication contained errors significant enough to warrant formal correction. Pull OJ:L_202690561 and OJ:L_202690562 from EUR-Lex and compare them line by line against your 15 June screening updates.

What to watch: The BAFA advance publication of updated EU Dual-Use Regulation annexes means a formal commencement date for the amended control lists is coming — expect a Federal Gazette notice or Official Journal publication by late July 2026; that date triggers re-classification obligations. On the Iran track, watch for OFAC and EU follow-on designations under the snapback framework through 31 July 2026, the window in which secondary sanctions re-engagement typically produces the first wave of entity-level action. And if your screening vendor has not yet explained the 3 July 5,802-removal event to your satisfaction, ask them to map the CSL record IDs against the source list canonical entries — the answer is in that mapping.

Get the Brief every Friday.

Join export control professionals receiving analysis and alerts directly to their inbox.

Already have alerts? Start for free →