Individual and entity parties
A UBO is screened as a Person against OpenSanctions; a holding company in the ownership chain is screened as an Organization. Both query types run through the same Yente match endpoint.
UBO screening
Screen ultimate beneficial owners the way you screen the named insured.
A corporate insured that screens clean can still carry sanctions exposure through its ownership structure. InsureGuardAI screens individual and entity parties on the same case record, tagged by role, so a UBO, an additional insured, or an assignee gets the same OpenSanctions-backed check as the policyholder.
How UBOs are recorded
Every party added to a case carries a kind (individual or entity), a name, an optional date of birth and country, and a role. Role is a free-text field — UBO, insured, broker, additional insured, assignee, loss payee — so the case record shows who was screened and in what capacity, not just a single named-insured check.
One case, multiple parties
Cases group parties by reference, so a single insurance case can hold the named insured, one or more UBOs, and any other counterparty that needs a documented check, each with its own screening result.
Match evidence per UBO
Each UBO's screen returns its own risk level, match status, top score, and dataset hits, retained separately so a reviewer can see exactly which party in the ownership chain, if any, triggered a hit.
Re-screen as ownership changes
Because parties are recorded against the case rather than baked into a one-time report, adding a newly disclosed UBO or re-running a screen after an ownership change uses the same workflow as the original check.
Where this fits
UBO screening runs on the same Yente-backed matching as party and sanctions screening generally — see sanctions and PEP screening for how a single match call works. InsureGuardAI is bought through the Spot Suite marketplace and runs on the shared tenant identity plane, with customer workspaces on InsureGuardAI hostnames.