Monitoring that shows which rule fired and why

DetectX® continuously monitors financial transactions to spot unusual patterns and suspicious activity. Your compliance team decides what counts as unusual, and no alert arrives without naming the rule that raised it.

  1. 1Ingest
  2. 2Detect
  3. 3Review
Stylised mockupA stylised representation of the DetectX® interface: the dashboard view of the workload, how much is open and how much is in process, and which sources the alerts arrived from. Every figure and label in it is synthetic, and it awaits ground truth from the canonical deployment.Not a screenshot: a simplified drawing of the DetectX® interface carrying fictional data. It awaits a capture of the deployment it represents, so no value, label or arrangement in it is a measured one.

The DetectX® Approach

Transaction Monitoring is one module of the DetectX® platform. What is watched, what counts as unusual and where the result goes are three separate decisions, and your compliance team holds all three.

Continuous monitoring

Three kinds of signal are read together: what moved on the account, how that account normally behaves, and what the wider dataset shows around it.

Transaction signals

Volume

Volume, velocity and counterparty behaviour are assessed continuously rather than at a review date.

Behavioural analysis

Behaviour

Analyses patterns and anomalies in user behaviour to detect potential fraud and AML risks, enhancing the precision of risk assessments.

Pattern recognition

Patterns

Identifies trends, anomalies and clusters in complex datasets, so a pattern running across many accounts is visible where a single transaction is not.

Key Benefits and Impact

A monitoring system that alerts generously is easy to build.
The cost of monitoring is not the detection, it is the review queue behind it. What makes that queue workable is not how many alerts the engine can raise, but what each one arrives holding and who set the threshold that raised it.

Stylised mockupA stylised representation of the DetectX® interface: one alert opened, with a similarity score, a status, the tabs across it and the fields that identify the case. Every name, reference and date in it is synthetic, and it awaits ground truth from the canonical deployment.Not a screenshot: a simplified drawing of the DetectX® interface carrying fictional data. It awaits a capture of the deployment it represents, so no value, label or arrangement in it is a measured one.

WHAT MAKES THE QUEUE WORKABLE

Fewer alerts that were never casesAdaptive filters and AI-driven algorithms, including evolutionary learning, maximise true detections whilst minimising false alerts.
Thresholds you controlYour compliance team maintains the thresholds it answers for, against the customers, volumes and typologies you actually carry.
The reason on the alertThe rule that fired and the behaviour that tripped it travel with the alert, so a review starts from the evidence rather than from a search.
Regulatory complianceComplies with GAFI/FATF standards; meets FINMA, MiFID and regional requirements.

Why DetectX®

A pattern is a question.
The record is the answer.

One monitoring alert, as the record holds it

Transaction Monitoring shares the AlertViewer, the lists and the reporting with Name Screening, Client Risk Scoring and every other DetectX® module. Monitoring signals are also an input to the client risk score, so a worked alert changes the client's picture.

Step 1 of 4 · Ingest

The transaction arrives with its context

The transaction is assessed against the customer's own behaviour as well as against the rule set, so an unusual amount is unusual for them.

Recorded: the transaction, and the behavioural signals around it.

Step 2 of 4 · Detect

The alert names the rule

The rule identifier, the threshold and the score are written onto the alert as it is raised, so the trigger is part of the record rather than a lookup made afterwards.

Recorded: the rule, the threshold and the score.

Step 3 of 4 · Assign

Who may work it is a matter of record

Who the alert was assigned to is recorded, and so is who else could have claimed it.

Recorded: who it was assigned to, and when.

Step 4 of 4 · Decide

A decision, with the reason it was reached

The disposition attaches to the alert with its justification, its author and its timestamp, and can be forwarded for four-eyes review.

Recorded: the disposition, the justification and the author.

Common questions

Transaction Monitoring · DetectX®

See a monitoring alert
from rule to disposition.

Book a session on your own transaction types. Bring your questions about rule tuning, thresholds and the four-eyes review workflow.

98% fewer false alerts
Observed at a Swiss retail bank running DetectX®.
Rules you own
Written, tested and activated by your own compliance team.
One platform
Monitoring, screening and risk scoring on the same AlertViewer.