Phonetic similarity
Catch names that sound alike even when source records use different spellings or local conventions.
Solutions / Screening
Explore screening risk before a decision becomes operational
Give MLROs and compliance teams a controlled portal for exploratory searches across people, companies, vessels, aircraft, passports, IBANs, and counterparties during onboarding, CDD, EDD, investigations, and exception review.
PDF reportMLRO decision and analysis inputs
Source context, notes, search parameters, and timestamps in one downloadable report.
PDFMLRO decision report
Broad inputsSearch names, entities, vessels, passports, and IBANs
MLRO accessSupport senior compliance review
ReviewInspect source-backed sanctions, PEP, wanted, and adverse media results
PDF reportExport MLRO decisions with analysis inputs
Commercial workflow
What this solution is for
Give MLROs and compliance teams a controlled portal for exploratory searches across people, companies, vessels, aircraft, passports, IBANs, and counterparties during onboarding, CDD, EDD, investigations, and exception review.
Search more than customer names
Screen individuals, businesses, vessels, aircraft, passports, IBAN accounts, aliases, nationalities, and related counterparties from one review surface.
Support MLRO judgment
Give the MLRO and compliance reviewers source context, identifiers, match strength, adverse signals, and relationship data before deciding whether to approve, reject, escalate, or monitor.
Generate decision reports
Create a PDF report that captures the MLRO decision, analysis inputs, search parameters, source context, notes, and timestamps for onboarding, CDD refreshes, EDD, and investigations.
Workflow map
How the solution fits into enterprise operations
The page describes the integration point, the operational handoff, and the evidence trail that teams need when screening becomes part of a regulated workflow.
| Stage | Enterprise context | Outcome |
|---|---|---|
| Search subject | Person, company, vessel, aircraft, passport, IBAN, alias, or counterparty | Exploratory screening request. |
| Result review | Source records, aliases, identifiers, list categories, scores, adverse signals | MLRO-ready context. |
| Use case | Onboarding, CDD refresh, EDD, investigation, exception handling | Risk-based review path. |
| PDF decision report | MLRO decision, analysis inputs, notes, timestamps, filters, source context | Downloadable decision evidence. |
Smart matching technology
Match complex names without losing control
PEP screening depends on names that appear in many formats, scripts, and source systems. Checklynx helps handle real-world variation while keeping reviewer decisions separate from the matching step.
Transliteration and spelling
Support non-Latin names, accent differences, reversed word order, and common data-entry variations.
Multiple languages
Represent names and aliases across scripts so reviewers can compare the result against source records.
Nicknames and honorifics
Account for titles, abbreviated names, and short forms while keeping the reviewer in control.
What problem does this solve?
It turns a compliance requirement into an operational workflow: a business event triggers screening or review, the result is routed to the right team, and the evidence is preserved for governance.
Where does it integrate?
Typical integration points include onboarding systems, CRM, payment systems, customer records, case queues, batch operations, webhooks, and audit workflows.
Does this automate the compliance decision?
No. The workflow provides structured screening context and routing support while compliance policy and final review decisions remain under your team's control.