Phonetic similarity
Catch names that sound alike even when source records use different spellings or local conventions.
Solutions / Screening
AML Screening Portal for Customer and Counterparty Checks
Run browser-based sanctions, PEP, watchlist, wanted-list, and adverse-media checks without building an integration. Review people, companies, vessels, aircraft, passports, IBANs, and counterparties with the source context attached.
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
Browser-based AML screening
Screen and review a subject without building an integration
The Checklynx screening portal gives compliance teams a direct workspace for one-off customer and counterparty checks. Search a subject, compare possible matches, inspect source evidence, record the outcome, and retain a report for onboarding, CDD, EDD, or investigation work.
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.
Portal screening workflow
From exploratory search to documented reviewer outcome
Search the party and available identifiers, review grouped results across the selected risk sources, record the MLRO or analyst decision, and retain the inputs and evidence behind it.
| 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.
Move from portal results to a prepared human review
AI can organise the names, identifiers, risk categories, and source context already available in the result. The reviewer confirms the outcome and keeps the rationale attached to the case.
Checklynx
Source context
Structured signals, not raw noise.Name and aliasesIdentifiersRisk categoriesAI assistance
Review summary✦Potential high-risk match. Name signals and birth year align. Review source evidence before deciding.
- Name
- aligned
- Birth year
- consistent
- Context
- source-backed
Reviewer decision
Human confirmation requiredFalse positivePotential matchAuthorised AI agentUnderstand · select · call
→Governed connectionMCP→Permitted Checklynx toolsScreen · research · retrieve
Choose the screening access method that fits the job
Use the portal for direct human-led searches, then move to API, CSV or monitoring when the screening population or operating cadence requires it.
01Screening portal
Run a direct customer, counterparty or investigation check in the browser.
Explore 02Real-time APIEmbed screening into onboarding, payments and other product events.
Explore 03CSV batch screeningUpload a defined population for migration, remediation or periodic review.
Explore 04Ongoing monitoringRe-screen approved records when sources, customer data or review cadence changes.
ExploreSee where portal screening fits in the wider Checklynx workflow
01Customer and party context
Identify the person, company, UBO or counterparty that needs review.
02Portal screening
03Result assessmentSearch enabled risk sources and inspect grouped candidate profiles.
Compare source evidence and record the human reviewer outcome.
04Monitoring and casesReturn meaningful changes for review and retain the decision history.
Measured impact in screening review
30–40%Less compliance review time
CashDirector reports that clustered profiles and fewer false positives help its compliance officers review cases faster.
20%Less time spent on monthly reviews
Shopware connects retained false-positive decisions, customer screening and ongoing monitoring.
What is an AML screening portal?
An AML screening portal is a browser-based workspace where authorised compliance users can screen customers and counterparties, inspect possible sanctions, PEP, watchlist, wanted-list, and adverse-media matches, and record the reviewer outcome without first building an API integration.
Who can be checked in the screening portal?
Teams can search people, companies, counterparties, vessels, aircraft, passports, IBANs, aliases, nationalities, and other available identifiers. The appropriate subjects and sources depend on the organisation’s risk-based screening policy.
Can the portal be used for customer onboarding and EDD?
Yes. Compliance teams can use it for onboarding checks, CDD refreshes, enhanced due diligence, investigations, exception handling, and other controlled one-off reviews where a human needs to inspect and document the result.
Does portal screening replace ongoing monitoring?
No. Portal screening supports direct and exploratory checks at a point in time. Ongoing monitoring re-screens approved records when source data, customer information, or a configured review cadence changes.
What evidence can be retained after a portal check?
A review can retain the search inputs, selected sources, possible matches, source context, reviewer notes, outcome, timestamps, and a decision report so the organisation can explain how the result was handled.