Skip to main content

Configuring Monitoring Worklists

Fine-tune sanctions and adverse media screening by configuring worklists based on profile type, risk level, and your risk sensitivity

T
Written by TJ Sangam
Updated over 3 weeks ago

1. What’s New with Acuris V3

SILO’s integration with Acuris V3 allows precise monitoring configuration per profile type:

  • Create custom worklists for Individuals, Entities, and Trusts

  • Tune match thresholds and modes to reduce false positives

  • Target screening by risk score, profile data quality, or other criteria

All licensees with screening enabled should review and update their configuration.


2. Default Worklist Settings (New Licensees)

Profile Type

Threshold

Frequency

Matching Mode

Individual

85

Daily

Fuzzy

Entity

85

Daily

Fuzzy

Trust

85

Daily

Fuzzy

These defaults are a starting point. Adjust based on your data quality and risk model.


3. Worklist Setting Options Explained

Setting

Description

Name

Assign a clear label (e.g., "Individual – High Risk")

Type

Select profile type: Individual, Entity, or Trust

Threshold

Set match score from 1–100 (higher = stricter)

Matching Mode

Choose Fuzzy for flexibility or Strict for exact matching

Frequency

Recommended: Daily screening

DOB Required

Only returns matches with a DOB (Individuals only). Not recommended.

DOB Match Mode

Optionally allow match within ±1–5 years

Country Required

Only includes profiles with a country tag (does not compare countries)

Datasets

Select relevant Acuris datasets (see below)

Updated Guidance:
Requiring DOB can significantly reduce false positives for common names, but may exclude valid matches if data is incomplete.


4. Acuris Datasets Explained

PEP Datasets

  • PEP – All PEPs

  • PEP-CURRENT – Active PEPs only

  • PEP-FORMER – Former PEPs

  • PEP-LINKED – Associates of PEPs

Sanctions Datasets

  • SAN – All sanctions

  • SAN-CURRENT – Currently sanctioned

  • SAN-FORMER – Previously sanctioned

Other Risk Datasets

  • RRE – Reputational Risk

  • DD – Disqualified Directors

  • POI – Profiles of Interest

  • REL – Regulatory Enforcement

  • SOE – State-Owned Enterprises

  • INS – Insolvency (UK/Ireland only; can generate many false positives)

Remove irrelevant datasets (e.g., INS) to reduce screening noise.

5. When to Use Multiple Worklists

Using multiple worklists allows you to tailor screening behaviour to different types of profiles.

Common scenarios include:

  • Profiles with common names generating high volumes of matches

  • Profiles requiring enhanced due diligence

  • Differences in jurisdiction or regulatory exposure

  • Variations in data quality (e.g. verified vs unverified profiles)


6. Recommended Approach: Standard vs Precision Worklists

A practical and widely used setup is to maintain two types of worklists:

Standard Screening Worklist

  • Default for most profiles

  • Balanced Threshold and Fuzzy matching

  • Designed for broad, efficient monitoring

Precision Screening Worklist

  • Higher Threshold

  • Strict matching or tighter rules

  • Used for profiles with common names or excessive false positives

💡 This approach helps reduce noise while maintaining effective coverage.


7. Example: Worklist for Verified Low-Risk Individuals

Setting

Value

Name

Individual – Verified

Type

Individual

Threshold

92

Matching Mode

Strict

Frequency

Daily

DOB Required

No

Country Required

No

Datasets

PEP, SAN, RRE

Best for profiles sourced via eID or verified intake methods.


8. Moving Profiles Between Worklists

Profiles can be reassigned between worklists when screening behaviour needs to change.

Typical use cases:

  • Reducing false positives for common names

  • Applying stricter monitoring for higher-risk profiles

  • Aligning screening with updated risk assessments

Key points:

  • Only users with Senior Compliance permissions can move profiles

  • Changes typically take effect by the next working day

  • New worklists may take several hours (or overnight) to appear


9. Configuration Tips & Governance Requirements

Best Practices

  • Separate worklists by profile type

  • Use stricter settings for verified data

  • Use Fuzzy matching where name inconsistency is common

  • Use Precision worklists to manage high-volume match profiles

Governance Reminder

  • Worklist changes must be reviewed and approved internally

Ensure policies and procedures reflect:

  • When different worklists are used

  • When profiles should be moved between them

  • Who is authorised to perform these actions

  • SILO Support requires written sign-off from a Director or Senior Manager for configuration changes


10. Support & Optimization

Need help optimizing worklist accuracy?

  • Request sample hit reports

  • Get assistance tuning thresholds and dataset combinations

  • SILO can support bulk configuration requests

Contact: [email protected]

Did this answer your question?