The OFAC 50 Percent Rule is an ownership-graph problem, not a list-screening feature
OFAC's 50 Percent Rule can extend blocking consequences beyond a named list entry. Learn why this is an ownership-analysis problem, not simply a name-screening feature.
A sanctions list is deceptively reassuring. It gives a team a set of names and identifiers to screen. But some of the most consequential decisions sit one step away from the list: a company is not named, yet is owned—directly or indirectly—by a blocked person.
That is why OFAC’s 50 Percent Rule should not be treated as a checkbox in a screening vendor comparison. It is an ownership-analysis problem. A list-search result can tell you whether a name retrieved a candidate. It cannot, on its own, demonstrate that you have understood the relevant ownership chain or documented the conclusion.
This article explains the operational model. It does not determine whether a particular transaction is prohibited; teams need qualified legal advice for their facts and jurisdictions.
Short answer
Under OFAC guidance, an entity that is owned, directly or indirectly, 50 percent or more in the aggregate by one or more blocked persons is itself treated as blocked, even if it does not appear by name on OFAC’s list. Ownership must therefore be analysed across the relevant chain and at the relevant time. Control alone is not the same test under this specific rule, but it can still create risk, obligations or reasons for escalation under other authorities, policies and facts.
The operational implication is simple: screen the named counterparty, then maintain a documented path from the counterparty through ownership data to the conclusion. Do not call a list result a 50 Percent Rule conclusion.
Why list screening alone has a hard boundary
Consider a distributor called Northbridge Medical Trading. Its legal name is not on a sanctions list. A conventional API call might return no candidate and therefore no alert. That result is useful, but it only answers a narrow question: was the named distributor itself retrieved as a candidate from the sources searched?
It does not answer these questions:
- Who owns Northbridge, directly and indirectly?
- Is the ownership information current enough for the relationship and risk level?
- Are blocked persons’ ownership interests aggregated correctly?
- Did a corporate change occur after the previous review?
- Did the analyst distinguish ownership from management influence, beneficial interest and control?
Those questions form a graph: entities and people are nodes; shares, beneficial interests and corporate relationships are edges; dates and sources qualify every edge. A flat “sanctions hit / no hit” field cannot carry that model honestly.
The practical decision path
| Step | Question | Evidence to retain |
|---|---|---|
| 1. Resolve the counterparty | Which legal entity is actually entering the relationship? | Legal name, registration data, identifier, jurisdiction, retrieval time |
| 2. Screen relevant parties | Did the entity, known owners, directors or other policy-relevant parties return candidates? | Query input, normalisation, source state, candidates and disposition |
| 3. Build the ownership path | What direct and indirect ownership relationships are evidenced? | Source for each relationship, effective date, percentage, exceptions |
| 4. Apply the rule | Do blocked persons own 50% or more in aggregate, directly or indirectly? | Calculation, assumptions, analyst/legal reviewer, decision timestamp |
| 5. Preserve and monitor | What changes would reopen the conclusion? | Monitoring trigger, re-screening event, historical record |
The quality of this process depends on its limitations being visible. If the ownership data cannot establish a chain, the correct output may be “insufficient evidence—escalate” rather than a false all-clear.
Two errors teams make repeatedly
Error 1: treating the named list as exhaustive
OFAC’s guidance is explicit that the rule can apply even where the entity is not separately named on the Specially Designated Nationals and Blocked Persons List. A workflow that only searches the legal entity name will necessarily miss that class of risk. That is not an API bug. It is a mismatch between the control being claimed and the control actually performed.
Error 2: turning “control” into an automatic percentage calculation
The opposite mistake is also dangerous. OFAC distinguishes its 50 Percent Rule from a blanket proposition that any entity merely controlled by a blocked person is automatically blocked. Control may still be highly relevant: a bank’s policy, another sanctions authority, a contractual obligation, fraud indicators or the wider risk context can all require escalation. But a system should not silently substitute its own legal conclusion for a documented review.
Good product language makes the distinction plain: ownership calculation, control context and sanctions-list retrieval are related signals with different meanings.
What an audit-ready output looks like
The output should be a decision record, not a colour. For every material entity in the chain, keep the stable identity, source of relationship data, observed date, percentage, screening outcome, source status and reviewer note. The final calculation should be reproducible: another reviewer should be able to see why interests were included, excluded or treated as unresolved.
That record matters when an ownership structure changes. Instead of starting from a spreadsheet with no provenance, the team can compare the new graph to the prior graph, re-run relevant screening and attach the new conclusion without overwriting history.
Where Verifex fits
Verifex can help bring entity resolution, UBO analysis, screening evidence and the review trail into the same workflow. It should never claim that an ownership graph by itself delivers a legal determination. The product promise is narrower and more useful: preserve the data, source context, calculations and human decision needed for a team to explain its process. Confirm current source availability and product scope against Sources & Freshness before relying on any workflow.
Sources
This is educational material about screening operations. Verifex provides screening infrastructure and evidence records, not legal advice, transaction approval, or a replacement for your risk-based compliance program.
Continue reading
- Blog · ComplianceDaily sanctions screening under the Instant Payments Regulation is an evidence problem before it is a latency problem
- Blog · ComplianceA false positive is not a screening failure. An unexplained clearance is.
- Blog · ComplianceAn LEI is not KYB: what a company identifier can tell you, and what it cannot
Run a screening and inspect the decision record.
The free plan includes OFAC and UN screening. Coverage stays explicit when a required source is unavailable.