OFAC's 50 Percent Rule: Trace Indirect Ownership Beyond a Business-Name Search

Executive Summary: OFAC's 50 Percent Rule determines whether an entity is treated as blocked property even though its name never appears on a sanctions list, because ownership by one or more blocked persons can reach 50 percent or more in the aggregate^[1], directly or through one or more intermediate entities^[2]. This article walks a compliance lead through a documented ownership-chain review, contrasts it with a name-only screen, and provides a worked illustration, a decision table, and a reviewer worksheet built from OFAC's own published examples^[2]. None of the material below substitutes for a legal determination on an actual file; it is a structured way to organize the questions a reviewer needs answered before escalating.

What Problem Does A Name-Only Screen Leave Unresolved?

A name-based sanctions screen answers one question: does the applicant's submitted name, or a submitted owner's name, produce a potential match against a current sanctions list entry that then has to be evaluated for quality^[3]. That is a necessary check, but OFAC's own guidance describes a second category of risk that a name match will never surface: an entity that is not itself listed anywhere, yet is still considered blocked property because one or more blocked persons own it, directly or indirectly, 50 percent or more in the aggregate^[1].

Why Does A Clean Screen Not Mean A Clean Ownership Chain?

The 50 Percent Rule is stated in terms of aggregate ownership, not name presence. OFAC's FAQ 399 gives a simple illustration: if Blocked Person X owns 25 percent of Entity A and Blocked Person Y owns another 25 percent of Entity A, Entity A is considered blocked, because the two blocked owners' stakes are added together to reach 50 percent^[1]. Entity A's own name may never have been designated. A reviewer who only screens the entity's name will get a clean result and never learn that the underlying ownership arithmetic already crossed the threshold.

What Does OFAC Say About Non-Blocked Entities That Fall Short Of The Threshold?

FAQ 398 is equally important on the other side. Control by a blocked person is not the same as ownership. An entity that a blocked person controls, but does not own 50 percent or more of in the aggregate, is not automatically blocked under the 50 Percent Rule^[4]. OFAC may still designate that entity separately under other sanctions criteria, and it explicitly urges caution when a significant, sub-50-percent ownership interest or a control relationship exists, because such an entity could become the subject of a future designation^[4]. The same FAQ adds a practical warning that matters at closing: a person dealing with a non-blocked entity should make sure it is not, for example, entering into a contract signed by a blocked person who represents that entity^[4]. FAQ 400 answers the follow-on question directly: transactions involving a blocked individual are generally prohibited absent OFAC authorization even when that individual is acting on behalf of a non-blocked entity, so a U.S. person may not, for example, enter into a contract signed by a blocked individual^[5]. For a lender, "controlled by, ownership unresolved" is not the same file disposition as "owned 50 percent or more, automatically blocked," and neither disposition settles who may sign the loan documents.

A workable starting posture is to treat a clean name screen as answering the direct-match question only, and to treat any file with a multi-layer or fund-like ownership structure as needing a separate, documented ownership review before the file is closed out. That second review is a manual, evidence-gathering exercise, not something a name-matching API performs.

How Does Aggregate Ownership Actually Work Across A Chain?

OFAC's guidance defines "indirectly" to mean one or more blocked persons' ownership of shares of an entity through another entity or entities that are 50 percent or more owned in the aggregate by those blocked persons^[2]. This is a chain test applied entity by entity, not a single multiplication carried down through every layer of a structure.

Does OFAC Multiply Ownership Percentages Down A Chain?

This is the point where a reasonable-looking shortcut produces the wrong answer. A reviewer might assume that if Blocked Person X owns 50 percent of Entity A, and Entity A owns 50 percent of Entity B, then X's "effective" economic interest in B is 25 percent, calculated as 0.5 times 0.5. OFAC's own Example 1 rejects that math. OFAC states that Entity B is considered blocked because Blocked Person X owns, indirectly, 50 percent of Entity B, and it adds that X's 50 percent ownership of Entity A makes Entity A a blocked person, whose 50 percent ownership of Entity B in turn makes Entity B a blocked person^[2]. The chain therefore does not decay the way a percentage-of-percentage calculation would suggest.

What Do OFAC's Own Five Examples Establish?

OFAC publishes five worked examples in FAQ 401 that a reviewer can use as a direct template. Example 2 shows aggregation across two intermediate entities: Blocked Person X owns 50 percent of Entity A and 50 percent of Entity B; A and B each own 25 percent of Entity C; because X is considered to indirectly own 25 percent of C through A and another 25 percent through B, the totals equal 50 percent and Entity C is blocked^[2]. Example 3 combines a direct and an indirect stake: X owns 50 percent of Entity A and 10 percent of Entity B, and A owns 40 percent of B, so X's indirect 40 percent plus direct 10 percent equals 50 percent and B is blocked^[2]. Examples 4 and 5 show the negative cases. In Example 4, X owns 50 percent of A but only 25 percent of B; A and B each own 25 percent of C; X is considered to indirectly own 25 percent of C through A, but because B is not 50 percent or more owned by X, nothing passes through B, so X's total stays at 25 percent and C is not blocked, even though A itself is a blocked person^[2]. In Example 5, X owns only 25 percent of each of A and B, so neither A nor B is blocked and X is not considered to indirectly own any of C through them, even though A and B each own 50 percent of C^[2]. The reviewer's job is to identify, for each entity in the chain, whether that entity itself meets or exceeds 50 percent blocked-person ownership in the aggregate; only entities that clear that bar carry ownership forward to the next layer.

What Does A Worked Ownership-Chain Review Look Like?

The following is an illustrative worked case built to mirror OFAC's own structure of examples. It does not describe an actual applicant, borrower, or transaction.

Borrower A applies for financing. Borrower A's stated owner on the application is Entity B, a holding company, at a 60 percent equity stake. During file review, the reviewer learns from borrower-supplied documents that Entity B is itself partly owned by two other holding entities, Entity C and Entity D, each holding 50 percent of Entity B. A name screen on Borrower A and on Entity B both return no potential match against current sanctions list data^[3]. Separately, in the course of document review, the reviewer notes that an individual identified in Entity C's ownership records shares a name with a listed individual on a public sanctions list.

What Facts Would Need To Be Confirmed Before Any Escalation?

At this point the file contains an unresolved fact pattern, not a conclusion. The reviewer would need to confirm, using borrower-provided ownership documents and a full review of the sanctions list entry, whether the named individual in Entity C's records is in fact the listed blocked person, and if so, what percentage of Entity C that person owns^[3]. If that individual is confirmed to own 50 percent or more of Entity C, and Entity C owns 50 percent of Entity B, then under OFAC's Example 1 logic Entity C would be a blocked person and Entity B would be considered indirectly owned 50 percent by the blocked individual, making Entity B a blocked person as well^[2]. Following the same chain one step further, Entity B's 60 percent stake in Borrower A would mean Borrower A is owned 50 percent or more by a blocked person, which is the fact pattern the rule describes as blocked^[2]. If instead the individual's stake in Entity C is confirmed at only, say, 30 percent, with no other blocked person holding an interest in C or D, then Entity C is not itself blocked. Example 4 applies that reasoning to a single intermediate: where an entity is not owned 50 percent or more by the blocked person, the blocked person is not considered to indirectly own any of the entity beneath it through that part ownership, so nothing passes through Entity C to Entity B^[2].

Why Does This Case Stop Short Of A Legal Conclusion?

This illustration deliberately stops at the fact-gathering stage. Confirming identity between a name in an ownership document and a listed individual, confirming a percentage stake, and applying the aggregation rule correctly across every entity in the chain are all steps that call for a documented review and, in ambiguous cases, escalation to a supervisor or compliance officer, consistent with OFAC's own recommended step of escalating a potential match or a 50 Percent Rule nexus rather than resolving it informally^[3].

What Should A Decision Table For Ownership Findings Contain?

A structured table helps a reviewer separate the fact pattern from the disposition, and helps a second reviewer audit the same file later. The table below reflects OFAC's own examples, FAQ 398's control distinction, and FAQ 400's signatory point; it is a proposed internal reference, not a Cobalt output.

How Should A Reviewer Use This Table In Practice?

The table is meant to be filled in row by row as facts are confirmed, not applied all at once from an assumption. A reviewer should record which row applies, what document or source supported that row, and the date of the finding. Where the facts do not cleanly match a row, for example when a percentage stake cannot be confirmed from available paperwork, the honest disposition is to mark the row as unresolved and escalate, rather than guessing at a percentage.

What Happens When A Blocked Person Later Divests?

A separate wrinkle applies once an entity has already been treated as blocked. OFAC's FAQ 402 explains that if blocked persons divest so that their combined stake falls below 50 percent in a transaction that occurs entirely outside U.S. jurisdiction and does not involve U.S. persons, the entity is no longer automatically considered blocked going forward, but property that was already blocked while in the possession or control of a U.S. person remains blocked, and OFAC does not recognize unlicensed transfers of that interest^[6]. OFAC also says sufficient due diligence should be conducted to determine that a purported divestment in fact occurred and was not merely a sham transaction^[6]. An earlier "blocked" entry therefore cannot be flipped to "clear" on a divestment claim until that confirmation is documented.

Which Alternative Approaches Can A Reviewer Use Before Any Product Bridge?

Before reaching for any screening tool, a reviewer has at least three manual paths available, each with different strengths.

• Direct authority lookup. A reviewer can review the complete sanctions list entry through OFAC's Sanctions List Search Tool or Sanctions List Service for any name that surfaces in ownership documents, comparing full names, former names, aliases, addresses, nationalities, and identification numbers listed against the party in the file^[3].

• Borrower-supplied ownership documents. Cap tables, operating agreements, stock ledgers, or organizational charts provided by the borrower can establish the percentage stakes needed to apply the aggregation logic in FAQ 401, though these documents reflect what the borrower discloses and are not independently verified by that act alone^[2].

• Internal escalation and second review. OFAC's own recommended workflow calls for escalating an ambiguous match to a supervisor or compliance department rather than resolving it at the first reviewer's desk, particularly where the alert implicates an unlisted entity potentially blocked by operation of the 50 Percent Rule^[3].

• Weak-alias and match-quality review. Some listed aliases are classified by OFAC as weak, and a reviewer's own screening tool may exclude those aliases as part of a risk-based decision, which affects how a name in an ownership document should be weighed^[3].

• Jurisdictional and U.S.-person scoping. OFAC sanctions obligations apply to all U.S. persons, including U.S. citizens and permanent residents wherever located, all individuals and entities within the United States, and U.S.-incorporated entities and their foreign branches, and in certain programs foreign subsidiaries owned or controlled by U.S. persons, which affects who on a lending team actually carries the compliance obligation for a given file^[7].

Where Does A Name-Screening API Fit Into This Process?

A name-screening API, including Cobalt's OFAC endpoint, accepts a required search query for a business or an individual, optional filters such as search type, selected list sources, a match score, and address fields, and returns scored matches with the fields that contributed to each match for the reviewer to evaluate^[8]. That is the direct-authority-lookup task above, run at production speed: it answers whether a submitted name matches a listed name or alias at a chosen score. Nothing in the documented request or response describes discovering who owns an entity, calculating aggregate percentages across a chain, or determining whether the 50 Percent Rule applies to an unlisted entity^[8]; those remain the reviewer's separate work. Related background on pairing entity screening with separate owner-level review is discussed in existing coverage of OFAC screening alongside beneficial ownership practices^[9].

What Should A Lender Expect The API To Return, And What Is Documented Scope?

The documented response includes the screened name, a match count, a per-match score, matched fields marked as strong or weak similarity with a note on whether the match was against a primary name or an alias, and sanction record detail such as the source list, source identifier, programs, aliases, addresses, and identification data^[8]. Fields in that response can be incomplete depending on what the underlying list source publishes for a given entry, and the documentation notes that identification types are not normalized across lists, so a reviewer should not treat an empty field as a negative finding^[8]. The documented endpoint returns its result in the response to the request, with no callback parameter, so it is a lookup rather than an ownership-discovery process^[8].

What Belongs In A Reviewer Worksheet And Escalation Checklist?

A worksheet documents each entity in a chain; a short checklist decides when a file must move beyond a routine name screen. Both are proposed customer-owned controls, not a Cobalt deliverable.

Which Fields Should The Worksheet Capture For Each Entity?

The fields below are an illustrative customer-owned template. Fields marked "not yet confirmed" or "not specified" are expected during an active review and must not be filled in with an assumed value; every unresolved field should appear in the distinct list shown, so a second reviewer can see what remains open.

{
  "recordType": "illustrative customer-owned ownership review record",
  "applicationId": "application-example-1",
  "borrowerName": "Borrower A",
  "reviewDate": "not specified",
  "entitiesReviewed": [
    {
      "entityLabel": "Entity B",
      "role": "stated owner of Borrower A",
      "statedOwnershipPercent": 60,
      "nameScreenResult": "no match against selected sources as of review date",
      "ownershipDocumentSource": "borrower-supplied cap table",
      "notes": "owners of Entity B not yet confirmed against sanctions list"
    },
    {
      "entityLabel": "Entity C",
      "role": "partial owner of Entity B",
      "statedOwnershipPercent": 50,
      "nameScreenResult": "individual name flagged for manual review",
      "ownershipDocumentSource": "borrower-supplied operating agreement",
      "notes": "percentage stake of flagged individual not yet confirmed"
    }
  ],
  "signatoryScreened": "not yet confirmed",
  "unresolvedFields": [
    "confirmed identity match for flagged individual",
    "confirmed percentage stake of flagged individual in Entity C",
    "sanctions screen of the individual signing for Borrower A"
  ],
  "reviewerDisposition": "escalated, pending confirmation",
  "escalatedTo": "not specified"
}

When Should A File Be Escalated Rather Than Closed?

Beyond the worksheet's data fields, the following checklist items each justify moving a file beyond a routine name screen:

• Multi-layer ownership disclosed. The applicant's ownership documents show one or more intermediate holding entities rather than a single direct owner.

• A name in ownership documents resembles a listed name. Any resemblance, even a partial one, to a name or alias on a current sanctions list should trigger the match-quality review described in OFAC's guidance^[3].

• A control relationship exists without a confirmed ownership percentage. The FAQ 398 row above applies only once the percentage is confirmed; until then the 50 Percent Rule cannot be ruled out^[4].

• A blocked individual may be acting for the applicant. Screen every signatory separately from the entity, on the FAQ 400 row above^[5].

• A prior divestment is asserted. Document the FAQ 402 confirmations described earlier before moving any entity off a blocked disposition^[6].

• Aggregation math has not been walked entity by entity. Any shortcut that multiplies percentages down a chain instead of testing each entity against the 50 percent threshold should be flagged and redone using OFAC's example structure^[2].

A file should be escalated whenever any item above is unresolved after document review, not only when a name screen itself returns a positive match. OFAC's own guidance frames escalation as the appropriate response when an alert implicates a nexus to the 50 Percent Rule rather than a straightforward listed-name match^[3].

Who Should Make The Final Ownership Determination?

A workable operating principle is to keep name screening, document-based ownership review, and the final blocked-property determination as three separate, separately dated steps in the same file, so that no single automated result is mistaken for the legal conclusion.

The final determination on whether an entity is blocked under the 50 Percent Rule is a legal judgment that OFAC's guidance ties to due diligence on ownership stakes^[2] and, once property is actually blocked, to authorization requests through OFAC's Licensing Division rather than to any single tool's output^[6]. Because documents and escalation responses arrive at different times, mark the worksheet final only once every unresolved field is addressed or formally waived by policy.

What Is A Contrasting Case Where The Rule Does Not Apply?

Contrast the worked case above with a shorter, narrower fact pattern. Entity B, a borrower's stated owner, discloses that a named individual holds a 25 percent stake, and that same individual separately holds a 25 percent stake in an unrelated Entity D, which in turn owns 50 percent of Entity B alongside another unrelated owner.

Why Does This Structure Not Trigger The 50 Percent Rule?

This fact pattern is not one of OFAC's five published examples, so it has to be worked through in two parts. Entity D is 25 percent owned by the individual, short of 50 percent, so Entity D is not itself a blocked person and, on Example 4's reasoning, no ownership of Entity B is considered to pass through it^[2]. That leaves the individual's direct 25 percent stake in Entity B. OFAC totals direct and indirect ownership when applying the threshold, as Example 3 shows by adding a direct 10 percent stake to a 40 percent indirect stake to reach 50 percent^[2]. Here the same addition produces 25 percent plus nothing, so the threshold is not met on the disclosed facts. Even if the individual were confirmed as a listed blocked person, the aggregation test stops at each entity that does not itself clear 50 percent. The reviewer's disposition here, assuming the 25 percent figures are confirmed accurately, would document that the rule's threshold is not met on the facts as disclosed, while still noting OFAC's caution that any confirmed sub-50-percent ownership by a blocked person warrants continued attention for future designations^[4].

What Should The File Record Regardless Of Outcome?

Whether the finding is that an entity is blocked, not blocked, or unresolved, OFAC's own guidance calls for keeping complete, accurate records of the steps taken to investigate a potential match and the information relied on to determine whether the match was valid, since OFAC may request those records under its recordkeeping regulation^[3]. That discipline applies equally to a simple name match and to a multi-entity ownership chain, whatever tool or manual method produced the alert.

How Does This Fit Into A Lender's Broader Screening Workflow?

Ownership-chain review is one component of a wider file review process that also includes name screening at intake and at renewal, borrower entity verification against state records, and periodic re-screening as ownership or control changes over time.

How Does Ownership Review Relate To Borrower Entity Verification?

Verifying that a borrower is the entity it claims to be, using state registry data, is a separate step from screening that entity's name or its owners against sanctions lists. A borrower's submitted trade name may differ from its registered legal entity name, and resolving that identity question correctly affects which name gets screened in the first place^[10]. Existing coverage of cross-entity verification discusses using the officer and agent names returned during standard entity verification as a starting point for finding other entities connected to the same principals, which can help a reviewer decide where an ownership chain needs more documents^[11]. Neither step replaces the ownership percentages that the 50 Percent Rule actually turns on.

What Is A Reasonable Cadence For Revisiting Ownership Findings?

Ownership structures and sanctions lists both change, so a file reviewed as clear at origination is not guaranteed to stay clear. A workable policy re-runs name screens at defined intervals or on material events such as a change in stated ownership, and re-opens the ownership worksheet whenever new intermediate entities are disclosed. This is a proposed internal control, not a product feature.

For a compliance lead who wants to see how Cobalt's OFAC name-screening endpoint behaves against your own applicant and ownership data, bring a concrete scenario, including the layered entities you actually encounter, to a live walkthrough on the Cobalt Intelligence demo page so the discussion can center on your file structure rather than a general overview.