Screening
Introduction
In this use case, we’ll cover how to utilize Sayari API endpoints to conduct a compliance screening workflow to mitigate risks, including financial, legal, and reputational damages.
Conduct a screening workflow in three key steps:
- Resolution: Accurately identify and resolve the entity of interest against the Sayari Knowledge Graph.
- Entity: Access the detailed profile of the entity, including attributes, risk factors, and relationships.
- Traversal: Explore and filter specific relationships and risks to understand the entity’s network and associated risks.
Step 1: Resolution Match
The Resolution endpoint uses advanced search capabilities, such as elastic search and natural language processing (NLP), for accurate entity matching based on a query. This step is crucial for screening and validating entities.
Making a Resolution Request
To initiate a resolution request, at a minimum, provide the entity’s name. For optimal results, we recommended including name, address, country, and type. For example, to screen a potential supplier named RE-X PRODUCTS LTD. in Thailand, use:
Parameters:
name
: RE-X PRODUCTS LTD.address
: 2 Soi Nonthaburi 20 Sec 1 Meung Nonthaburi 11000country
: THAtype
: company
Include additional parameters like identifier
, contact
, and date_of_birth
to further refine the resolution and improve matching accuracy.
Response Review
The response provides a summary of the matched entity, highlighting key attributes such as the entity’s name, unique identifier, and match rationale. Understanding the match_strength
value helps gauge the confidence level in the match.
Step 2: Entity Profile Review
After a successful match, use the Entity endpoint to review the entity’s full profile, which includes comprehensive attributes, risk factors, and relationship types. Use the entity_id
from /resolution
for this request.
Entity Request Example
Response Review
Examine key elements, such as risk factors (sanctioned_adjacent
, export_to_sanctioned
), to assess potential risks. These factors are crucial for understanding the entity’s risk profile.
Note: At this stage, a screening workflow could conclude. The entity has been validated and risk has been identified. To further understand the entity’s relationship to risk, proceed to the Traverals endpoint.
Step 3: Traversal Exploration
The Traversal endpoint identifies paths from a target entity to related entities within the Sayari Knowledge Graph. Use filters like sanctioned
and regulatory_action
to refine searches. This requires a target entity id
.
Making a Traversal Request
To explore entities related to RE-X PRODUCTS LTD. that might be on a sanctions watchlist:
Parameters:
entity_id
: hYPJlqax9a6I45lnSvgQhQ | RE-X PRODUCTS LTD.limit
: 5 | limits the result set to 5sanctioned
: true | set to filter paths to entities based on sanctions risk
This request identifies relationships leading to entities on a sanctions watchlist, which is crucial for risk assessment.
Response Review
Here, we suggest focusing on the paths and risk objects related to the entity. The response includes underlying records, aiding in comprehensive risk analysis.
Congratulations! This concludes our Screening Use Case.