Monthly customer refresh
ScopeAll active customers
CoverageSanctions, PEP, wanted
CadenceEvery 30 days
Products / Screening Policies
Control every screening workflow
Use screening policies to control what gets checked, when checks run, and how results flow into cases, false-positive suppression, webhooks, and audit evidence.
Review only what changed
Known false positives stay suppressed for the same customer. New or changed matches move into review.
CoverageSet sources and matching behavior
CadenceRun once or on a recurring schedule
ScopeApply to customers, cohorts, or workflows
RoutingSend hits to review, cases, or evidence
Policy engine
One control layer for manual, batch, API, and automated screening
Screening policies make compliance operations repeatable. They let teams standardize coverage and review behavior while still choosing the right implementation path for each workflow.
Standardize screening coverage
Define the lists, source types, entity groups, matching settings, and result behavior that should apply across the business.
Automate periodic screening
Attach policies to customer bases or cohorts so monthly, quarterly, or risk-based screening runs without manual file handling.
Control operational outcomes
Route potential matches into cases, preserve evidence, suppress confirmed false positives, and keep downstream systems updated.
Control screening behavior across every workflow
Screening policies define how Checklynx applies coverage, timing, and operational routing across API checks, CSV batch screening, customer monitoring, and analyst review.
What to screen
Choose sanctions, PEP, wanted, adverse media, customer type, entity type, and any source-specific coverage needed for the workflow.
When to screen
Run a one-off check, screen an imported customer base, or attach a recurring policy for monthly, quarterly, or event-driven screening.
How to route results
Decide whether results clear automatically, create cases, require analyst review, trigger escalation, or preserve evidence for audit.
Use policies for both screening rules and automated runs
Teams can use screening profiles to define coverage and matching behavior, then use monitoring policies to decide which customers or cohorts are screened automatically and how often.
| Policy type | Controls | Used by |
|---|---|---|
| Screening profile | Sources, entity types, matching configuration, and result scope | API checks, CSV runs, portal searches, customer screening |
| Monitoring policy | Customer or cohort scope, recurrence, scheduled runs, and review workflow | Periodic customer screening and ongoing monitoring |
| Review policy | Case routing, false-positive handling, escalation, and evidence retention | Case management, audit trail, and analyst operations |