Entity Connections
Relationships the lists don't document. Detected automatically.
Beta version. Sanctions lists are subject to change by their issuing authorities.
The Gap in Sanctions Lists
Ten authorities. Ten independent lists. Zero cross-references between them.
Sanctions lists document who is designated. They do not document how designated actors are connected. The EU does not reference OFAC entries. OFAC does not cross-reference the UN. Each authority publishes its own list independently — with no links to other jurisdictions.
The connections exist. They are simply invisible to anyone screening one list at a time.
Connection Types
Three classes of connection. Each structurally distinct. Each impossible to surface at scale without automation.
Connections are detected — not inferred. Each connection type is grounded in a specific data point that appears on at least two separate list entries.
The Three Connection Types
- Shared Addresses: Two persons or organisations registered at the same address — across different sanctions programmes. Neither list documents the connection. The registry detects it by comparing normalised address fields across all entity cards. A sanctioned person and a sanctioned company sharing a registered address is a connection worth knowing about.
- Shared Identity Documents: The same passport number, LEI, or IMO number appearing on separate list entries. Definitive proof of a relationship — or a data quality issue requiring review. Either way, it surfaces automatically.
- Shared Alias Identities: A name appears as an alias of one actor on one list, and simultaneously as an alias of a different actor on another list. Virtually impossible to detect manually across tens of thousands of entries. The registry cross-indexes all aliases against all entity cards after every import cycle.
Detection Mechanism
Every night after all imports complete. Three targeted steps. Only affected entities re-evaluated.
Connection detection does not re-evaluate the entire dataset nightly. It identifies what changed and re-evaluates only the affected entities. This keeps the detection cycle fast and ensures every change is acted on immediately.
The Three Detection Steps
- Change Detection: Which entries changed since the last cycle, and in which data category? Changes to identity data (names, aliases), documents (passport, LEI, IMO), and geographic data (addresses) each trigger different connection checks.
- Targeted Re-Evaluation: Only entities affected by the detected changes are re-evaluated — not the entire dataset. Existing connections that are unaffected by the change set are not rechecked.
- Connection Update: New connections created, existing ones confirmed or invalidated. Every change is documented with source evidence and an audit trail. A connection that existed yesterday and does not exist today is preserved in history — not silently removed.
As soon as a sanctions list adds a new alias, address, or identifier, all resulting connections are detected within the next daily cycle.
How Connections Appear
In the screening result — where you need them. Not buried in a separate search.
Connections are displayed as badges directly in screening results. When a matched entity has known connections to other sanctioned actors, the reviewer sees this immediately — not after a separate search.
The connection badge links to the full connection detail with source evidence: which data field triggered the connection, which list it appeared on, and when it was detected. Everything needed to document the finding is in one place.
Sanctions Screening Built to Be Audited.
Beta access is free and includes full screening functionality across all official sources, the complete review workflow, and audit-ready exports.
Login / Register