A risk class for every client,
and the reason for it

DetectX® scores every client in real time and in batch runs, from the risk factors and weights your compliance team sets. Each factor’s class and weight is on the client’s profile, a rise in risk class opens an alert, and every change, calculated or set by hand, is kept with its reason.

Request a demoTalk to us
  1. 1Aggregate
  2. 2Record
  3. 3Alert
  4. 4Review
  5. 5Platform tour
DetectX - One Platform. Total Compliance (FINAL CAPTIONS)

One Platform. Total Compliance.

The DetectX® Approach

Every client, scored on factors you set.

Client risk scoring is the assessment of each customer’s money laundering and terrorist financing risk, so that the depth of due diligence and monitoring matches the risk. DetectX® scores clients in real time and in batch runs: your rules give each risk factor a class, the classes are weighted into one score, and the score sets the client’s risk class.

Scored in real time and in batch, returned to your core system. Client data is loaded into the DetectX® datamart. A client can be scored in real time, and every client is covered in the scheduled batch run. The score and risk class go back to your core system, and any alert opens in AlertViewer.

Your systemsCore Banking SystemDirectly, or through a data warehouse or operational data store.
Data inDetectX® Datamart
CustomersAccountsAddressesTransactions
Real time · one client, when it mattersTrigger TBC
Batch run · every client, one record each
ResultRisk Score and Risk ClassSent back to your core system, for use across the bank.
Your analystsClient Risk ProfileIn AlertViewer, with any alert ready to review.How client data reaches the datamart

Routes and data sets vary by bank.All data shown is synthetic.

Key Benefits & Impact

A risk class is only as good as the reason behind it.

A class set at onboarding records who a client was. DetectX® keeps every client’s class current, shows the factors behind it, counts the people they are connected to, and keeps every change your analysts make on the record.

A Class You Can Defend

Ask why, and the answer is on the profile.

Every client’s profile shows the factors behind their class and how much each one weighs. When an auditor asks why a client is Medium, your analyst opens the profile and shows them.

How each factor is written as a rule
Why is customer 418.230 Medium?2.05 · Medium
0Score 2.05
Adverse media0.60
Transaction Monitoring alerts0.40
Complex structure0.30
Documents and contracts0.30
3 more factors0.45
The answer for the auditorTwo factors carry half the score: adverse media and Transaction Monitoring alerts. Each one names the rule that set it.

Example data. Factors and weights are set for your bank.

Risk That Keeps Up

A class that moves when the client does.

Clients are rescored in real time and in scheduled runs, so a client whose behaviour changes does not keep the class they were given at onboarding. When the class rises, an alert opens for review.

Monitoring results as a risk factor
Customer 418.230 · risk scoreReal time and batch
Medium from 1.75High from 2.50MarAprMayJunJulAugSepAlert raised
LowClass at onboarding
MediumClass today, reviewed

Example data. The alert opens when the class rises.

Connections Counted

No client scored as if they stood alone.

Clients carry risk from their riskiest connection, such as a joint account holder or a signatory. A client who looks Medium alone can be High once the people they bank with are counted.

Following connections between clients
Customer 418.230 · two scoresJoint account with 418.236
Scored alone2.05Medium

From the client’s own factors.

+ risk from 418.236
3.40 · weight 50%
With connections2.73High

Their riskiest connection counted.

What changesOn their own, this client would stay Medium. Counted with the joint account they share, they cross into High and get the review that comes with it.

Example data and weights. Spillover can raise a score, never lower it.

Judgement on the Record

Your analysts decide. The record shows why.

An analyst can raise, lower or approve a client’s score. A written comment is mandatory, and every version stays on the profile, so a manual decision is as traceable as a calculated one.

Working client risk alerts
Update risk score · customer 418.230Calculated 2.05
New risk score
2.80 · High
Relationship approved · Generate alert
Y · No alert
Comment (mandatory)
Adverse media confirmed by the relationship manager. Raised to High pending review.
Revert to calculated riskUpdate with comment

Example data. No comment, no change. Every version stays on the client’s profile.

Back in Your Core System

One class, wherever the client is handled.

Calculated, updated and approved classes go back to your core system, so onboarding, review cycles and due diligence all work from the same current class.

How client data moves in and out
Core system · client recordUpdated by DetectX®
Client418.230
CategoryPrivate
DetectX® risk classHigh was Medium
Risk score2.80
SetManually, approved
Last update19.09.2026
Used across the bank forReview cycleDue diligence depthOnboarding decisions

Example data. Which fields are written back depends on your core system.

The Whole Book, Current

No client waiting for their next review.

Every client is scored in each scheduled run, not only the ones due for periodic review. The changes surface on their own, and the rises arrive as alerts.

How client profiles are scored
Client book · today2,313 clients scored
Low1,840
Medium412
High61
14Classes changed since the last run
9Rises, each opened as an alert

Example data.

Why DetectX®

Most risk classes are set once at onboarding. DetectX® keeps them current.

Request a demoTalk to our team
  • Rated as they are todayA class set at onboarding, kept until the next reviewEvery client rescored in scheduled batch runs and in real timeHow scoring runs
  • A rise reaches your teamA higher risk waits for the review dateA rise in class opens an alertWorkflows
  • Counted with their connectionsA joint account holder’s risk goes unseenRisk Spillover passes risk from the riskiest connection, and never lowers a scoreLink Analysis
  • Fed by what you already knowMonitoring alerts and media hits kept elsewhereAdverse media and monitoring alerts can count as factorsKey benefits
  • Your factors, on the recordA class with no trace of how it was reachedFactors and weights set by your team, and every class shows how it was reachedProfiling & Scoring
  • One platform, not another systemA separate scoring tool with its own dataShares its datamart with Transaction MonitoringThe DetectX® platform

In production

Factor Explained

The answer to “why this class?” is on the profile, not in a model no one can open.

Every Factor shown with its class and weight

Each factor’s class, weight and share of the score sit on the client’s profile.

Writing the rules behind each factor

Your Next Step

Three ways in, depending on where you are.

Each one is a conversation with the people who build DetectX®, with no obligation.

Start Here

Request a Demo

Watch Client Risk Scoring work through real alerts with a product specialist.

  • Alerts explained, field by field
  • Thresholds tuned in front of you
  • Your questions answered on the call
30 min · Video callRequest

Talk to Our Team

Bring your data, volumes and core banking system. We map where DetectX® fits.

  • How DetectX® connects to your systems
  • Which data you would use
  • A realistic plan for going live
45 min · Video callBook a call

Ask for a Reference

Speak with a compliance team already running DetectX®.

  • A peer with a set-up close to yours
  • Their experience, in their words
  • Arranged with their agreement
By arrangement · CallAsk us

How Client Risk Scoring Works

Try it yourself: four steps, from a nightly score to a decision on file.

DetectX® scores every customer each night from your risk factors and weights. A change in class raises an alert, your analyst decides, and every version of the risk is kept. Every step is yours to drive.

Illustrative exampleInvented Names & Data

Explore the DetectX® Platform

Start with Client Risk Scoring. Add what you need next.

Every DetectX® solution runs on the same underlying platform and shares its capabilities, AlertViewer and audit trail. Pick a solution to see what it adds to Client Risk Scoring.

All solutions
Business IntelligenceWorkflowsRegulatory Reporting

Client Risk Scoring FAQs

What compliance teams ask before choosing DetectX®.

Something we have not covered?Talk to our team

Client risk scoring is the assessment of each customer’s money laundering and terrorist financing risk, so that the depth of due diligence and monitoring matches the risk. A risk-based approach requires it under FATF Recommendation 1, and every major AML regime builds on that requirement. In DetectX®, your rules give each risk factor a class, the classes are weighted into one score, and the score sets the client’s risk class.

PlatformProfiling & Scoring

The score is built from the risk factors your compliance team defines. Typical factors include domicile, PEP and sanctions status, adverse media, complex ownership structures, domiciliary companies, and missing documents or contracts. Your rules give each factor a class, and the calculation works in three steps:

  • Each factor’s weight is divided by the sum of all weights.
  • That share is multiplied by the factor’s class.
  • The results add up to the client’s score, which falls into a risk class using thresholds your bank sets.

Every factor’s class and weight is shown on the client’s profile.

PlatformBusiness Rule Engine

Clients are scored in real time and in scheduled batch runs. Every client is rescored on each run, not only those due for periodic review. When a client’s risk class rises, an alert opens in AlertViewer with the old and new risk side by side.

SolutionWorkflows

Risk spillover is risk a client takes on from the people they are connected to, such as a joint account holder or a signatory. Each client has two scores: an independent score from their own factors, and a spillover risk once their riskiest direct connection is counted. That connection is weighted by its type and direction, for up to five levels. Spillover can raise a score but never lowers it.

PlatformLink Analysis

Yes. An analyst can update, approve or revert a client’s score, and every change needs a written comment. Each version, calculated or manual, stays on the client’s profile with who made it, when and why. The result is then sent back to your core system.

The two modules read the same datamart and run on the same analytical engine, so the data is loaded once and used twice. Transaction Monitoring works with one record per transaction and raises alerts on unusual activity. Client Risk Scoring works with one record per client and assigns a risk score and class.

SolutionTransaction Monitoring

Go Deeper

All resources
InsightExpert Guide: AML Risk Scoring, How to Build a Smarter Compliance Framework

How to build an AML risk scoring model from the ground up: which risk factors to assess, how to weight them, and how the score sets the depth of due diligence for each customer.

Read the articleInsightTop Customer Risk Profiling Techniques to Enhance Compliance Accuracy

The techniques institutions use to find their higher-risk customers, from customer and enhanced due diligence to automated profiling, and how each one supports what regulators expect.

Read the articleInsightBest Practices for Real-Time Risk Profiling and Personalised Risk Scoring

Why a risk class set at onboarding goes out of date, and how rescoring customers as their behaviour and circumstances change keeps each class current.

Read the article

Client Risk Scoring · DetectX®

See Client Risk Scoring in a demo

Book a session on your own client base. Bring your questions about which signals should weigh most, and how your supervisors want the score taken apart.

Request a demoTalk to us
360° client risk visibility
Name screening, transaction monitoring, profiling and NLP signals unified in one score.
Drill-down, not a black box
From the dashboard to the underlying data and the audit trail.
One platform
Every module you run is an input to the score.