Agent StoreLegalRegulatory Compliance
Live

Sanctions Screening Agent

LegalRegulatory Compliance

Screens counterparties, vendors, and transaction parties against global sanctions, export control, and denied-party lists before deal execution.

4
Process steps
5
Integrations
3
Data inputs

Before onboarding a new vendor, customer, or transaction counterparty, companies must confirm the party is not on OFAC, EU, UN, or other sanctions and denied-party lists, but manual screening against dozens of frequently updated lists is slow and easy to skip under deal pressure

A missed match can expose the company to significant civil and criminal penalties and reputational damage

This agent automatically screens every new counterparty name, along with known aliases and affiliated entities, against consolidated global sanctions and export control lists at onboarding and on a recurring basis thereafter, using fuzzy name matching to catch near-matches and transliteration variants that exact-match tools miss

It routes any potential hit to compliance for manual adjudication rather than auto-blocking, keeping deal velocity high while ensuring no genuine match is missed

The agent triggers when a new counterparty is entered into the CRM or procurement system, or on a scheduled rescreening cadence for existing counterparties, and it pulls the party's legal name, known aliases, address, and ownership structure. It queries consolidated sanctions and denied-party list data sources including OFAC SDN, EU consolidated list, UN Security Council list, and BIS Entity List, applying fuzzy matching and transliteration-aware algorithms alongside an LLM-based entity resolution check to identify likely matches versus common-name false positives. Potential hits are scored by confidence and routed to compliance officers with supporting evidence for adjudication, while cleared parties are logged with a screening certificate for the deal file.

1

Capture Counterparty Data

  • Pull legal name, aliases, and address from CRM or procurement record
  • Identify beneficial ownership and affiliated entity structure where available
  • Determine applicable list sets based on transaction geography
  • Queue party for initial and recurring screening
Outcome: Complete counterparty identity data is captured for screening.
2

Screen Against Sanctions Lists

  • Query OFAC, EU, UN, and other applicable denied-party lists
  • Apply fuzzy name matching and transliteration handling
  • Screen known aliases and affiliated entities
  • Score potential matches by confidence level
Outcome: Every counterparty is screened with a confidence-scored match result.
3

Adjudicate Potential Matches

  • Route medium and high-confidence hits to compliance officer
  • Present supporting evidence for match determination
  • Log false positive and confirmed match decisions
  • Escalate confirmed matches for transaction hold and legal review
Outcome: Potential matches are reviewed and resolved by a compliance officer before deal proceeds.
4

Certify and Rescreen

  • Issue a screening clearance certificate for cleared counterparties
  • Attach certificate to the deal or vendor file
  • Schedule recurring rescreening on a defined cadence
  • Alert compliance if a previously cleared party later appears on an updated list
Outcome: Cleared counterparties carry a documented certificate, and ongoing exposure is monitored continuously.
OFAC/Treasury Sanctions List API
pulls current SDN and sectoral sanctions data
Dow Jones Risk & Compliance
sources consolidated global watchlist data
SAP Ariba
triggers screening at vendor onboarding stage
Salesforce
triggers screening at new counterparty CRM entry
Slack
alerts compliance officers to medium and high-confidence matches