Match Score Thresholds
Guidance on choosing the right match score threshold for your compliance program.
What is the default threshold?
TradeLasso defaults to displaying results with a match score of 80 or above. This threshold was chosen as a practical balance between catching real matches and avoiding an unmanageable volume of false positives for most use cases.
Why does the threshold matter?
The threshold determines which results are shown to you:
- Lower threshold (e.g., 70) — Shows more results, catches more potential matches, but increases the number of false positives you need to manually review
- Higher threshold (e.g., 90) — Shows fewer results, reduces review workload, but carries a higher risk of missing a near-match that falls just below the cutoff
Note
There is no universally "correct" threshold. The right choice depends on your risk tolerance, transaction volume, and the nature of your counterparties.
Recommended thresholds by use case
| Use case | Recommended threshold | Rationale |
|---|---|---|
| General compliance screening | 80 | Default. Catches most real matches with manageable false positives. |
| High-risk transactions (large value, sensitive technology) | 70 | Wider net reduces the risk of missing a near-match. Expect more false positives to review. |
| High-volume batch screening | 85+ | Reduces review workload for large files while still catching high-confidence hits. |
| Audit verification (confirming a specific known entity) | 90+ | High confidence only. Use when verifying a suspected match, not for general screening. |
How to adjust the threshold
In the single-entity RPS tool, the threshold is set to 80 by default. Use Advanced Filters to adjust it for a specific search.
In Batch Screening, the screening is run at the default threshold. After results are returned, use the fuzzy score slider on the results page to filter the view by a higher threshold without re-running the job.
Documenting your threshold choice
If your compliance program requires it, document the threshold used for each screening event. The search history (Pro) records the parameters of every search, and exported batch results include match scores for every row, making threshold decisions auditable.