AML sanctions screening is the process of checking people, companies, vessels and aircraft against official sanctions lists to identify potential matches for compliance review. KYCWire screens against OFAC SDN & Consolidated, EU, UK and UN lists, covering 33,381 records with refreshes every 6 hours and reporting a median latency of 66 ms with p95 latency of 142 ms.
A sanctions screening result is not a final decision. It is a signal that a compliance team must review, investigate and resolve using available evidence. The quality of a screening system depends on list coverage, matching logic, explainability and audit records, not only on how many possible matches it returns.
TL;DR: AML sanctions screening facts that matter
- KYCWire covers 5 official sanctions sources: OFAC SDN & Consolidated, EU, UK and UN lists, with 33,381 records available for screening.
- KYCWire refreshes sanctions data every 6 hours, helping teams detect updates without manually tracking multiple publisher changes.
- KYCWire matching performance reaches recall@5 of 0.99 on a public test set, with median response time of 66 ms and p95 cold latency of 142 ms.
- KYCWire supports API checks, batch screening, monitoring webhooks and CSV audit trails, while remaining focused only on sanctions lists rather than PEP or adverse media checks.
Need sanctions list screening without building list ingestion and matching infrastructure? KYCWire lets teams screen names against OFAC, EU, UK and UN lists in one API call with 200 free checks a month and an audit trail included.
What AML sanctions screening actually does
Sanctions screening connects identity data with official restrictions
AML sanctions screening compares customer, partner or transaction-related information against government and international sanctions records. The goal is not to prove that a person or company is sanctioned. The goal is to identify candidates that require human review.
Sanctions lists contain names, aliases, organizations, vessels, aircraft and identifiers. A screening engine must interpret incomplete or inconsistent identity data. A customer name may have different spellings, scripts or transliterations, while an entity may appear under multiple aliases.
KYCWire focuses on official sanctions coverage only. It does not include PEP screening or adverse media screening, which are separate compliance functions that require different data sources and review processes.
| Screening area | KYCWire coverage | Compliance implication |
|---|---|---|
| OFAC SDN & Consolidated | Included | Supports checks against US sanctions records |
| EU sanctions list | Included | Supports EU sanctions screening workflows |
| UK sanctions list | Included | Supports UK sanctions screening workflows |
| UN sanctions list | Included | Supports UN sanctions screening workflows |
| PEP and adverse media | Not included | Requires separate tools and processes |
Teams comparing solutions often confuse sanctions screening with broader AML screening. A practical comparison is available in AML Screening Solutions: A Practitioner’s Review of Top Tools.
Why matching accuracy depends on more than fuzzy search
Name similarity can create both missed risks and unnecessary reviews
A common assumption is that better fuzzy matching automatically creates better sanctions screening. The harder problem is understanding identity signals. A high similarity score without context can increase false positives, while aggressive filtering can hide candidates that deserve review.
KYCWire matching data highlights a practical issue with cross-script names. The name «Владимир Путин» matching “Vladimir Vladimirovich PUTIN” requires name dictionaries and transliteration knowledge, not only fuzzy string similarity. Trigram-only matching approaches can return no result for some Cyrillic queries involving names from other scripts.
Another screening rule is counterintuitive: a conflicting birth year should reduce confidence in a match, not automatically remove the candidate. Removing the record creates an invisible false negative that cannot be audited later. A lower score preserves the investigation trail.
A screening result should remain explainable. A candidate hidden by an aggressive filter cannot be reviewed, challenged or improved later.
KYCWire provides scored sanctions matches with explanations, helping compliance teams review candidates instead of treating every match as an automatic decision.
The data points that separate useful screening from noisy alerts
Identifiers often matter more than names
The strongest non-obvious lesson in sanctions screening is that names are often weaker evidence than identifiers. A passport number, IMO number for a vessel, or registration identifier can provide a clearer link than a similar-looking name.
KYCWire screening logic treats an exact identifier hit as a stronger signal than name similarity. This reflects a broader compliance principle: identity evidence should be weighted according to reliability, not simply according to how closely text strings match.
Sanctions publishers also classify aliases with different strengths. A weak alias should not receive the same treatment as a primary listed name. Treating every alias equally can inflate false positives and increase manual review workload.
Performance data needs context
| Metric | KYCWire value | Why it matters |
|---|---|---|
| Records screened | 33,381 across 5 official lists | Defines the current sanctions data scope |
| Refresh frequency | Every 6 hours | Reduces delays after list updates |
| Recall@5 | 0.99 on a public test set | Measures ability to return relevant candidates within top results |
| Median latency | 66 ms | Supports interactive API workflows |
| p95 cold latency | 142 ms | Shows slower response conditions |
Fast response times do not replace compliance judgment. A 66 ms screening response is useful only if the returned matches include enough explanation for a reviewer to decide the next action.
What we got wrong / What surprised us
The strongest finding: screening quality is about preserving uncertainty
The biggest surprise is that a better system is not always the one that produces fewer alerts. A system that hides difficult candidates may look cleaner while creating harder compliance problems later.
The practical mistake teams make is treating screening as a yes-or-no classifier. Real sanctions workflows operate with incomplete information. The useful output is a ranked set of possible matches with reasons, identifiers and context for review.
Another unexpected issue is overvaluing fuzzy similarity. Similar spelling does not always mean similar identity. Cross-script names, weak aliases and conflicting attributes require structured interpretation rather than a single similarity score.
Practical takeaways for implementing AML sanctions screening
-
Separate sanctions screening from other AML checks.
Time estimate: 1 hour. Difficulty: Low. Expected outcome: Clearer requirements because sanctions lists, PEP data and adverse media are handled as different workflows.
-
Prioritize identifier matching before name-only decisions.
Time estimate: 1-3 days. Difficulty: Medium. Expected outcome: Better review quality by giving stronger evidence more weight.
-
Keep explainable match records.
Time estimate: 1 day. Difficulty: Medium. Expected outcome: Auditors and reviewers can understand why a candidate appeared.
-
Test multilingual and alias scenarios.
Time estimate: 2-5 days. Difficulty: Medium. Expected outcome: Fewer missed candidates caused by script differences and inconsistent names.
-
Connect monitoring events to review workflows.
Time estimate: 1-2 weeks. Difficulty: Higher. Expected outcome: Teams can respond to list changes without repeating every process manually.
For implementation teams, KYCWire provides API screening, batch checks, monitoring with webhooks and CSV audit trails. The free plan includes 200 checks per month for teams evaluating sanctions screening workflows.
Try sanctions screening with an audit trail included
KYCWire gives compliance teams and engineers a direct way to screen names, companies, vessels and aircraft against official sanctions lists. The API returns scored matches with explanations, allowing human reviewers to investigate rather than accept an automated verdict.
Start with 200 free monthly checks and test sanctions screening against OFAC, EU, UK and UN lists before building a larger workflow.
FAQ: AML sanctions screening
What is AML sanctions screening?
AML sanctions screening is a compliance process that checks people, organizations and assets against official sanctions lists. The result identifies possible matches for investigation; it does not automatically determine whether a person or entity is sanctioned.
Which sanctions lists does KYCWire screen?
KYCWire screens OFAC SDN & Consolidated, EU, UK and UN sanctions lists. Coverage details are available through the KYCWire lists documentation at official sanctions lists coverage.
Does sanctions screening replace PEP or adverse media screening?
No. KYCWire covers official sanctions lists only. PEP and adverse media checks require separate data sources and compliance processes.
How fast can an AML sanctions screening API respond?
KYCWire reports median latency of 66 ms and p95 cold latency of 142 ms. Response speed helps applications perform checks quickly, but compliance teams still need human review for potential matches.
Further reference: the OFAC sanctions lists and the UN Security Council consolidated sanctions list provide official source material for sanctions screening programs.
:::
