KYC screening tools evaluation guide
A screening API is only one part of the control. Buyers also need to know which sources are covered, how names and entities are matched, how alerts are resolved, when checks rerun, and whether the resulting evidence survives review.
KYC screening sources
Map required sanctions, PEP, enforcement, adverse-media, and internal sources to entities, countries, products, and policy.
Name-matching behavior
Test transliteration, aliases, dates, identifiers, entities, ownership, thresholds, and explainable reason codes.
Screening decision evidence
Measure analyst workload while retaining the source version, candidate, rationale, reviewer, and monitoring history.
Screening stack
What a KYC screening stack must keep separate
| Layer | Purpose | Buyer evidence |
|---|---|---|
| Risk sources | Define the official, commercial, public, and internal data that policy requires. | Source catalog, jurisdiction, entity types, update frequency, provenance, and licensing. |
| Matching | Generate candidates across names, aliases, scripts, dates, locations, identifiers, and ownership. | Configurable thresholds, field weighting, reason codes, change history, and reproducible tests. |
| Resolution | Confirm, reject, escalate, or defer a candidate under controlled authority. | Source snapshot, analyst rationale, reviewer, evidence attachment, service level, and override record. |
| Monitoring | Rerun or alert when sources, customer data, ownership, or policy changes. | Trigger, timestamp, deduplication, affected population, queue routing, and historical reconstruction. |
Replay set
Test screening misses and false alerts together
- Known true matches across exact, transliterated, reordered, aliased, and misspelled names
- Known non-matches that resemble listed people or entities and create operational noise
- Sparse records, conflicting dates of birth, missing nationality, and common-name populations
- Entity, beneficial-owner, director, representative, and counterparty screening paths
- Source-list additions, customer-data changes, rescreening latency, and alert deduplication
- Analyst disposition, four-eyes review, override, reopening, export, and audit reconstruction
Report confirmed-match recall on the controlled set, false-candidate rate, alerts per customer, analyst handling time, backlog age, reopened cases, and the percentage of decisions whose source and rationale can be reconstructed.
Cost
Screening price includes the queue it creates
Add screening unit charges and platform fees to analyst handling time for initial and ongoing alerts. A lower API price can cost more when weak source details or noisy matching expands the manual-review queue.
Model screening and review costDirect answers
KYC screening questions
Next decision