[{"data":1,"prerenderedAt":4},["ShallowReactive",2],{"article-body-the-fifty-percent-rule-countdown":3},"\nTrade compliance rarely gets a deadline this clean. The BIS Affiliates\nRule, which extends Entity List and related export restrictions to\nentities owned 50% or more by listed parties, took effect in September\n2025, was suspended two months later, and returns to force on 10\nNovember 2026. The date is fixed, the mechanics are published, and\nroughly ten weeks remain.\n\nThe rule's logic mirrors OFAC's long-standing 50 percent rule for\nsanctions: restriction follows ownership, directly or indirectly,\nwhether or not the owned entity appears on any list. What changes in\nNovember is scale and consequence on the export side. A customer,\ndistributor or intermediary that is majority-owned by a listed party\ninherits the restriction, and an exporter who ships to it without the\nrequired licence has violated export controls, cleanly named\ncounterparty notwithstanding.\n\n## Why list screening cannot see this\n\nThe standard trade compliance stack matches counterparty names\nagainst restricted party lists. Against the Affiliates Rule this is\nstructurally blind, for the same reason it always was against OFAC's\nrule: the entities the rule captures are, by definition, the ones on\nno list. Their connection to a listed party is an ownership fact,\nburied in corporate registries, holding structures and minority\nstakes that aggregate, sometimes across three or four layers and\nmultiple jurisdictions.\n\nThe enforcement environment gives the gap teeth. BIS penalties now run\nto nine figures ([the enforcement climate, and why screening misses\nit](/insights/95-percent-false-positives-is-a-design-choice)), and both\nBIS and OFAC guidance have converged on the same expectation: a\ncompliance programme is responsible for knowing the ownership behind\nits counterparties, and \"they were not on the list\" is not a defence\nwhen the ownership was knowable.\n\n## The ten-week computation\n\nThe work between now and November is well-defined, and it is a\ncomputation, not a policy rewrite:\n\n1. **Resolve the counterparty file to entities.** Names, aliases and\n   registration numbers collapsed into distinct real-world parties,\n   because ownership attaches to entities, not spellings.\n2. **Assemble the ownership graph** above every active counterparty:\n   parents, holding companies, aggregated stakes, from registry and\n   ownership data, with the gaps honestly marked, because an\n   unknown owner two layers up is itself a risk finding.\n3. **Run the 50 percent arithmetic** as a traversal, aggregating\n   listed party ownership, direct and indirect, per counterparty. The\n   output is an exposure register: entities that will be restricted\n   on 10 November, entities near the threshold, and entities whose\n   structures are too opaque to clear.\n4. **Wire the register to decisions.** Each exposed counterparty\n   gets an owner and a disposition before the deadline: licence\n   application, contract exit, restructured routing, or documented\n   clearance. And because ownership changes weekly, the traversal\n   has to keep running after November; a register computed once is\n   stale by December.\n\n> The difference between October and December is the difference\n> between a planning exercise and an incident response, on the same\n> facts.\n\nFor those who move early, a strategic layer opens up. The same graph\nthat answers \"who is restricted in November?\" answers the questions\nthat follow: what happens to our exposure if this holding company is\nlisted next; which alternative suppliers sit outside restricted\nstructures; where does one listing cascade through our counterparty\nbase? That is scenario capability, and firms that build the graph\nfor the deadline keep it as an instrument.\n\nOwnership traversal, threshold arithmetic and continuous\nre-screening are standing capabilities of the Prophesee Compliance\nSuite's Trade module. Compute your November exposure now.\n[Start here](/contact).\n",1786833838298]