Testing and tuning
How do you know the filter catches what you think it catches? Testing proves it; tuning changes it — only with evidence and approval.
IN ONE LINE
An everyday analogy: a fire alarm nobody has ever tested is a decoration.
The gate gets drilled the same way: in a controlled test environment, known test posters are sent through to confirm the scanners actually raise the flag; the innocent-lookalike rate is measured to see the cost of the settings; and when someone proposes loosening or tightening a rule, the drill is run first to show what the new setting would catch and what it would miss.
Only then does the change reach the real gate, with approval and a record.
The discipline is uncomfortable on purpose — an untested control is an assumption wearing a uniform, and the drill converts assumptions into evidence.
WHAT IT ACTUALLY IS
Two disciplines share the workbench.
Testing verifies the system does what the documents claim: list ingestion is complete and uncorrupted; every payment path and onboarding flow actually calls the filter — coverage gaps are the classic silent failure; and matching catches the name-variation classes the institution has decided it must catch, proven with constructed test cases (transliteration variants, reordered name parts, missing components) rather than assumed.
Market practice expects this testing to be independent and risk-based — internal audit, a compliance testing team, or a third party validating that alert generation aligns with the stated risk appetite.
Tuning is the other discipline: deliberately adjusting thresholds and rules to balance effectiveness — catching true matches — against the efficiency cost of false-positive volume.
HOW IT WORKS
Practitioner ground rules keep the workbench honest.
Test entries are synthetic and clearly marked, run in test environments — real designations are not toys, and production is not a laboratory.
Effectiveness and efficiency are measured separately, because improving the second at the expense of the first is exactly the failure tuning governance exists to prevent.
Below-the-line sampling gives the crucial early warning: reviewing matches that scored just under the alert threshold estimates what the current setting is already missing, and what any tightening of it would have missed.
And revalidation is event-driven as well as periodic: a list-schema change, a message-standard migration, or a screening-engine upgrade can silently change matching behaviour, so each triggers a fresh drill rather than a hopeful assumption that yesterday's evidence still holds.
THE WORDS
- Below-the-line testing
- Deliberately examining the matches that scored just under the threshold, to find out what the current setting is missing.
READ FIRST
CONNECTED TO
SOURCES
- Wolfsberg Group Sanctions Screening Guidance — The Wolfsberg Group
- Payments Signal editorial teaching models — Payments Signal
Derived from Testing and tuning. Every claim on this card is sourced on that page.