Monthly customer refresh
ScopeAll active customers
CoverageSanctions, PEP, wanted
CadenceEvery 30 days
Products / Screening Policies
AML screening policy management software
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.
Policy control
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.
Policy builderCustomer risk refresh
Active01Coverage
SanctionsPEPWantedAdverse media
02Cadence
One-offMonthlyEvent-driven
03Routing
ClearLow-risk records
ReviewPotential matches
EvidenceAudit trail
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 |
Keep policy-driven results connected to reviewer decisions
Carry the policy, screening result and source records into the same review. Resolved outcomes remain attached so later runs can distinguish unchanged results from new or changed matches.
Explore case managementApply approved policies to recurring screening runs
Use customer or cohort scope and an approved cadence to run screening automatically. Changed results return to review with the policy and earlier decision history attached.
Explore ongoing monitoringUse the same screening policy across portal, API, CSV and monitoring
Keep coverage, matching and result routing consistent while each workflow uses the access method suited to the job.
01Portal investigations
Apply approved coverage and review behavior to analyst searches.
Explore 02Real-time API checksUse consistent source, matching and routing rules in product events.
Explore 03CSV population screeningApply the same controls to migrations and periodic population reviews.
Explore 04Monitoring and casesSchedule recurring runs and route changed results into the right review path.
ExploreSee where screening policies fit in the wider Checklynx platform
01Customer and workflow scope
Define which customers, cohorts and business events require screening.
02Screening policies
03Screening executionSet coverage, cadence, matching behavior and result routing once.
Apply approved controls through portal, API, CSV and monitoring workflows.
04Review and auditKeep reviewer outcomes, escalation and retained evidence connected to the policy.
Trusted by teams at
What is AML screening policy management software?
It is the control layer used to define which risk sources and matching settings apply, when screening runs, which population is in scope, and how potential matches move into review and evidence workflows.
What can a Checklynx screening policy control?
A policy can control enabled sanctions, PEP, wanted-list, and adverse-media sources, entity scope, matching configuration, screening cadence, result routing, and supported false-positive handling.
Can the same policy support API, CSV, portal, and monitoring workflows?
The same screening profile can provide consistent coverage and matching rules across access methods, while separate monitoring and review settings control cadence, population scope, and operational routing.
Do screening policies automatically clear every repeated false positive?
No. Supported prior decisions can be reused when the customer and relevant result context remain unchanged. New or materially changed signals return for review according to the configured workflow.
Who remains responsible for the final screening decision?
Your authorised reviewers remain responsible for validating candidate matches, recording rationale, applying escalation rules, and making the final compliance decision.