Phonetic similarity
Show likely sound-alike variants alongside the candidate and customer record instead of leaving the reviewer to reconstruct them.
Solutions / Case Management
AML Case Management Software for Screening and Monitoring Alerts
Turn onboarding and monitoring signals into assigned cases with hit review, evidence, escalation, timeline history, and report-ready outcomes.
Review queue4 reviews
HighPotential sanctions matchNeeds review
MedPEP review neededAssigned
LowKnown false-positive checkSaved view
Screening decisionIn review
Match reviewPotential match
Source evidence attachedRationale addedCompliance escalation
Audit evidence5 actions recorded
Screening, review, note, escalation, and outcome.
QueuesTabs, filters, saved views
ReviewHit decisions with rationale
ControlEscalation, checklist, saved views
EvidenceTimeline, attachments, reports
Compliance operations
Built for ongoing compliance operations
Case management gives compliance teams a governed way to handle potential matches after screening. Each case carries ownership, status, priority, source context, notes, attachments, and the decision history needed to explain how the alert was handled.
Prioritize the daily queue
Use tabs, filters, pagination, saved views, queue ownership, assignee, and review state to keep analyst work visible and manageable.
Standardize the investigation
Review one or many hits with a decision and rationale, add notes and attachments, follow required checklist items, and keep related case context in view.
Govern exceptions and outcomes
Move cases through open, in review, awaiting information, resolved, and closed states with audited transitions, escalation controls, and report artifacts.
Investigation journey
From signal to case decision
A screening or monitoring signal becomes owned work, analysts review the underlying hits, managers can escalate or monitor review bottlenecks, and the final outcome remains tied to the evidence that supported it.
| Stage | Case context | Business outcome |
|---|---|---|
| Signal raised | Onboarding, customer screening, monitoring run, or manual review trigger | Potential risk becomes visible work instead of an informal task. |
| Case routed | Blueprint defaults, queue, assignment mode, checklist state, and escalation context | The right team owns the case from the start. |
| Hits reviewed | Match profiles, source results, adverse outcomes, rationale, reviewer, and timestamps | Analysts decide true positive, false positive, or potential match with context. |
| Investigation completed | Notes, events, related cases, attachments, checklist items, and optional financial context | Evidence is gathered in the same place as the decision. |
| Outcome recorded | Resolution outcome, reason where used, resolver, timestamp, and immutable timeline | The business can prove who decided what and why. |
| Systems updated | Webhook events | Downstream teams and systems stay aligned with compliance work. |
Review efficiency
Reduce repeated review work
Case management should not make analysts rebuild the same review packet every time. Checklynx keeps hit decisions, rationale, attachments, and timeline activity tied to the customer and case so future work starts from a clearer record.
Keep the queue current
Saved views, filters, tabs, and escalation visibility help leads see what is unassigned, in review, or waiting on information.
Make decisions reusable
False-positive reviews can be tied to the customer and exact screening result, reducing the chance that the same non-risk hit returns as fresh work in later checks.
Support second-line review
Escalation targets, optional transition reasons, checklist status, related cases, and full timeline history give senior reviewers the context needed for oversight.
Prepare the evidence pack
Report artifacts can draw from the case summary, reviewed hits, rationale, attachments, and action timeline instead of scattered screenshots and notes.
| Trigger | Handoff | Business outcome |
|---|---|---|
| Unassigned or aging work | Queue filters and queue visibility | Leads can rebalance work before review bottlenecks grow. |
| Known false positive | Customer-scoped hit decision | Analysts avoid repeating the same non-risk review. |
| Case needs oversight | Escalation and timeline context | Senior reviewers can act without reconstructing the case. |
| Governance request | Report artifact and immutable audit trail | Compliance can explain the decision record. |
Design case handling around investigation and evidence
Use these guides to connect alert review to the wider AML operating model and reduce repeated false-positive work without losing reviewer context.
Candidate review context
Bring name variants and identifiers into a clearer case review
Cases often begin with names that appear differently across records, languages, aliases, and writing systems. Checklynx groups the available matching context for review while keeping the analyst's case decision separate from the matching step.
Aliases and transliteration
Keep aliases, spelling variants, and transliterations visible with the source context used in the case.
Identifiers and relationships
Compare available identifiers, dates, countries, and related-party context before recording a case outcome.
Human confirmation
Use matching signals to prepare the review while leaving the true-positive, false-positive, or potential-match decision with the authorised reviewer.
Prepare the evidence before the reviewer makes the case decision
Bring names, identifiers, risk categories, source context, prior outcomes, and relevant case evidence into one review. AI can help organise the available information; the authorised reviewer confirms the outcome and records the rationale.
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
Bring compliance signals into one controlled review process
Create governed case work from onboarding, screening, monitoring, customer-risk, or manual triggers while keeping the originating context and final outcome connected.
01Screening portal
Move a potential customer or counterparty match from direct investigation into an owned case.
Explore 02Real-time screening APIRoute selected event-driven screening results into the configured review workflow.
Explore 03Ongoing monitoringTurn relevant post-onboarding changes into assigned work with prior decisions attached.
Explore 04Customer risk assessmentEscalate exceptions or higher-risk outcomes under the organisation's review policy.
ExploreSee how an AML alert becomes a documented outcome
01Signal and source context
Keep the screening, monitoring, onboarding, or customer-risk event that created the work.
02Queue and ownership
03Investigation and decisionAssign priority, reviewer, status, checklist, and escalation route under the configured process.
Review candidates, add notes and evidence, record rationale, and complete authorised actions.
04Audit evidence and handoffPreserve the timeline and provide controlled outcomes to connected systems.
Measured impact in AML case 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 AML case management software?
AML case management software turns screening, monitoring, onboarding, and manually raised compliance signals into assigned investigation work. It keeps the alert context, ownership, status, review activity, evidence, rationale, escalation, and final outcome together so teams can operate and explain the process consistently.
How does case management reduce review bottlenecks?
It turns potential matches into owned work with queue visibility, assignment, status, priority, hit context, notes, attachments, and escalation history. Leads can see what is aging or unassigned, while analysts start from a structured case instead of rebuilding context from searches, screenshots, and messages.
What makes a case decision easier to defend later?
The case keeps the reviewed hits, source context, analyst rationale, notes, attachments, checklist progress, related cases, timestamps, and final outcome together. That creates a decision packet that QA, management, audit, or banking partners can review without asking the analyst to reconstruct the story.
Can case outcomes still update business systems?
Yes. Case events can support downstream handoff when a case is created, assigned, escalated, updated, resolved, closed, or when a hit is reviewed. The important boundary is that business systems receive controlled outcomes while the compliance decision and supporting evidence remain in the governed case record.
Which alerts can become AML cases?
Cases can begin from customer or counterparty screening, ongoing monitoring, onboarding exceptions, reviewed sanctions or PEP candidates, adverse-media findings, customer-risk escalation, or a manual compliance trigger. The organisation decides which signals require a case and which can follow a lighter review route.
What case statuses and ownership controls are available?
Teams can use queues, assignment, priority, saved views, checklist state, escalation context, and controlled status transitions such as open, in review, awaiting information, resolved, and closed. The configured workflow should reflect the organisation's review authority and operating model.
Is a screening match the same as a case decision?
No. Screening returns potential candidates that require review. A case gives an authorised reviewer the context and workflow to evaluate those candidates, gather supporting evidence, document rationale, escalate where required, and record the outcome. The candidate is an input to the decision, not the decision itself.
What remains available after a case is closed?
The retained record can include the originating signal, reviewed hits, source context, notes, attachments, checklist activity, assignments, escalations, related cases, status history, reviewer rationale, outcome, timestamps, and report artifacts, subject to the customer's retention and access policies.
How are AML cases assigned to reviewers?
Cases can enter a queue with priority, assignment context, status, and checklist requirements. Teams use filters and saved views to identify unassigned, active, aging, or escalated work, then apply their own operating model for analyst and senior-review ownership.
Can an AML case be escalated for second-line review?
Yes. A case can retain its escalation target, status movement, transition reason where configured, checklist progress, notes, attachments, and timeline. That gives a senior reviewer the existing investigation context without requiring the first reviewer to rebuild it elsewhere.
Can supporting documents and notes be attached to a case?
Yes. Notes and supporting attachments can remain connected to the case alongside reviewed hits, source context, checklist activity, related cases, rationale, and outcome. Access and retention remain subject to the customer's governance policy.
Can case information support management or audit reporting?
Case records and report artifacts can bring together the case summary, reviewed hits, rationale, attachments, outcome, and action timeline. This supports internal QA, management oversight, partner reviews, and audit preparation without turning the software into the authority responsible for regulatory reporting decisions.