GLOBAL PAYMENTS KNOWLEDGEISO 20022 / SWIFT / SEPA / MT / MX
SCREENING / THE TUNING DILEMMA

Precision versus recall, on one dial.

Screening teams cannot have it both ways. A looser filter catches more true matches but floods analysts with false positives; a stricter one is lighter to work but lets real matches through. This model makes that trade-off something you can feel — always from the defender’s side.

Tune the match threshold

SYNTHETIC — TRAINING ONLY

Every name on a payment is compared to the watchlist, and the engine returns a similarity score. Anything at or above the threshold becomes an alert an analyst must clear. Drag the threshold and watch what it does to the two numbers that fight each other.

100%REAL MATCHES CAUGHTrecall — 5 of 5
50%ALERTS THAT ARE REALprecision — 5 of 10
10ALERTS TO WORKanalyst workload
0REAL MATCHES MISSEDslipped through

At 60% every real match is caught — but 5 false positives must be cleared by hand to get there. That is the cost of high recall.

See every candidate and how it is classified now
On the paymentWatchlist entrySimilarityTruthNow
Arjun MehtaArjun Mehta98%Listed partyTrue alert
Riya SharmaRiya Sharmaa90%Listed partyTrue alert
M. KabirMohammed Kabir72%Listed partyTrue alert
Asha Traders LtdAsha Trading Limited68%Listed partyTrue alert
Nadia PetrovNadya Petrova63%Listed partyTrue alert
John SmithJohn Smith95%Not listedFalse positive
Maria GarciaMaria Garcia94%Not listedFalse positive
Meridian BankMeridian Capital70%Not listedFalse positive
David CohenDaniel Cohen66%Not listedFalse positive
Li WeiLi Wei60%Not listedFalse positive
Cassia BankAcacia Bank55%Not listedCorrectly cleared
Kabir AhmedKabir Ahmad50%Not listedCorrectly cleared
Priya NairPooja Nair42%Not listedCorrectly cleared
Nordbank ABSudbank AB38%Not listedCorrectly cleared

This is the defender’s tuning problem — how to set controls so real matches are caught without burying analysts. It never shows how to avoid detection.