Four windows
for every alert
List entry, customer file, alert detail, and a translator, opened again for each one.
By role
Every alert, one customer record: built for FinCrime analysts
The screening results, the transaction alerts, the adverse media and the risk changes all relate to the same customer. The noise is eliminated before the queue is processed. Each match is accompanied by the evidence.
What you switch on
What the analyst works with
Each alert has one record associated with it. There's no need to check anywhere else.
Why this matters here
Most alerts turn out to be false positives
Industry estimates suggest that most screening alerts are false positives. To verify each alert, one has to check the list, the customer's file, the alert details, and obtain a translation. Screening alerts, monitoring alerts, and media alerts are each in their own queues. The actual case is located behind these.
One pattern
cleared again and again
Each clearance applies to one row, and the same false match will occur tomorrow.
Score only
with no reason
A number is given without a corresponding field. The decision begins with a guess.
−66%
Fewer alerts after entity resolution
Single
Screen for every decision
5
Writing systems supported
Zero
Extra tabs per alert
Week · Sideways
Scroll to advance
From queue to decision
-
Step 01
The queue you start with
The overnight deltas have already been cleared and what is left is sorted according to risk, divided by customer, with the reason given on each row.
-
Step 02
One screen per alert
The matched field, source list, original text and translation are displayed together alongside the transaction and media history on the same record.
-
Step 03
Clear the pattern, not the row
A false match that occurs repeatedly is adjusted once and then clears completely. The cleared state remains valid through the following list update.
-
Step 04
Escalate in one action
The case begins by including the evidence attached, and it is the MLRO who looks at it rather than reconstructing it.
complead / alerts
- Open34
- Auto-cleared overnight211
- Unassigned2
complead / alerts / detail
- Matched fieldname + DOB
- ListEU consolidated
- Sourceoriginal retained
complead / alerts / bulk
- Pattern cleared84 alerts
- Survives updatesyes
- Reason coderecorded
complead / cases / new
- Escalated3
- Evidence attachedautomatic
- Time to escalate40 s
Queue
Read
Clear
Escalate
What you answer to
What every decision must carry
What matters is not speed, but a decision another reviewer can follow three years later.
Read the compliance guides
Supervisor
A recorded reason for every disposition
Per alert
MLRO
Escalation inside the internal SLA
Per case
Auditor
Evidence kept with the decision
5 to 10 years
Policy
Second approval on every clearance
Per clearance
Case study · Banking
Read the case study
An analyst team that stopped growing with volume
Entity resolution removed most of the queue, pattern clearing removed most of what remained, and the team handled twice the customer base with the same five people.
−66%
Alerts per month
2x
Customers per analyst
40 s
Median escalation
Cross-family links
Where teams like yours go next
FAQ
Before you ask us
Will I see why something matched?
Yes. Each match shows the matched field, the source list, the score band and the source text in its original language. You start from the reason for the match, not from a number you have to work backwards from.
Can I clear a false match once instead of every day?
Once a pattern is tuned, yes. The clearance attaches to the name and its evidence, not to the row, so the same false match does not come back after the next list update. A genuine change to that list entry still raises a new alert.
How are Arabic, Cyrillic or Chinese names shown?
The original script and its translation appear side by side, across five writing systems. Nothing is normalised away before you see it, so you can check a transliterated match against what the list or the article actually says.
How many windows do I need per alert?
One. Match detail, source list, translation, transaction history and media history sit on the same record. The list entry, customer file, alert detail and translator that usually take four windows are already in one view.
How is the queue sorted?
By risk and by customer, with the reason given on each row. Three alerts on the same customer appear together as one piece of work, so you decide once with the full picture instead of three times with part of it.
What has been cleared before my shift starts?
Routine overnight deltas are auto-cleared, so the queue holds work that needs a decision. Every auto-clearance is logged with its reason, so it can be reviewed like any other decision.
How do I escalate to the MLRO?
One action. The case opens with the evidence already attached and goes to the MLRO, who reviews it rather than reconstructing it. Escalation stays inside the internal SLA because nothing has to be gathered twice.
Do I see screening, transaction and media alerts together?
Yes. Screening, transaction and media alerts on the same customer appear on one record, not in separate queues. A sanctions near-match and an unusual transfer on the same person are seen together, which is often where the real case is.
What must my decision record carry?
A recorded reason, so another reviewer can follow the decision years later. What matters is not how fast the alert was closed but whether the reasoning holds up in an audit three years on. Where your policy requires it, a second approval is recorded on the same decision.
Can we try it on the kind of alerts we handle?
Yes. We load sample alerts from your sector and you work the queue for twenty minutes. You judge the screen, the evidence and the clearing workflow on the kind of alerts you handle every day.
Work a real queue for twenty minutes
We will load sample alerts from your sector and let you clear them. That is the whole demo.
3,000+
Data sources checked
220+
Countries covered
15 min
Always real-time data