Sanctions Match

Overview

Sanctions Match is a potential or confirmed correspondence between a screened party, address, transaction, or asset and sanctions data or program criteria. Its operational purpose is to identify activity that may require investigation and a legally appropriate disposition before processing continues. It should be considered alongside Sanctions List. The relevant distinction is a confirmed blocked person determination, because an automated alert may be a false positive caused by common names, incomplete identifiers, transliteration, or weak data.

A typical workflow is as follows: The system compares names, aliases, dates, countries, identifiers, addresses, ownership, and other attributes. An analyst then reviews match quality, program applicability, ownership rules, jurisdictional nexus, and transaction context.

Core controls include risk-based thresholds, exact-identifier logic, fuzzy-name governance, secondary attributes, maker-checker review, escalation, documented false-positive rules, and periodic quality testing.

In payment and crypto operations, Processing should pause when required by policy or law while the alert is resolved. The final action may be clear, reject, block, restrict, request information, or seek legal guidance.

Evidence should include input data, list record, matched fields, score, data sources, rule version, reviewer notes, decision, timestamps, and any report or blocked property record. Automatically clearing weak data or automatically blocking every name similarity can both create serious legal and customer harm.

Implementation of Sanctions Match should map a potential or confirmed correspondence between a screened party, address, transaction, or asset and sanctions data or program criteria to the applicable entity, product, customer, transaction, and jurisdictional scope. Evidence for potential, confirmed correspondence between a screened party, and address should preserve the governing requirement, policy version, control execution, exception decision, owner, and review date. Material changes affecting the Sanctions Match context and potential, confirmed correspondence between a screened party, and address should trigger reassessment instead of silent reuse of an outdated conclusion.