Transaction monitoring
that shows the rule

DetectX® measures every transaction against the customer’s own history and the rules your compliance team writes, using thresholds, country risk and any table you add. Every alert names the rule that raised it, and opens in AlertViewer ready to investigate, escalate or report to your Financial Intelligence Unit.

  1. 1Detect
  2. 2Investigate
  3. 3Report
  4. 4Record
  5. 5Platform tour
One monitoring alert from the rule that fired to the record: the alert opened on its rule and score, the investigation opened from it, the MROS filing form, and the audit trail of every action taken on it.
DetectX - One Platform. Total Compliance (FINAL CAPTIONS)

One Platform. Total Compliance.

The DetectX® Approach

Every transaction, against its own past.

DetectX® loads your customers, accounts and transactions into its datamart, adds each customer’s history to every record, and tests it against your rules in an end-of-day run. A broken rule becomes an alert.

Your data, checked at the end of each day. Transactions are loaded into the DetectX® datamart and processed in an end-of-day batch. Each one is measured against its history and your rules, and a violation becomes an alert.

Your systemsCore Banking System
Data inDetectX® Datamart
Customers
Transactions
Addresses
Accounts
End-of-day batchAnalytical EngineEvery transaction in the configured time range, one record at a time.
  • Values and statistics from the base model
  • Your business rules
  • Alert filtering
Rule violatedAn Alert Is RaisedFor review in AlertViewer.
Your analystWorks the AlertConfigurable workflows, reports and link analysis.

Key Benefits & Impact

One transaction rarely tells the story. Its history does.

DetectX® Transaction Monitoring measures each transaction against what that customer normally does, raises one alert where one is enough, and gives every alert its reason. Your analysts spend their time on the customers whose behaviour has changed, not on the ones who are simply large.

Catches Change, Not Size

The small client who changed, not the large one who didn’t.

A rule can compare this month’s outflows with the customer’s own twelve-month average, so a private client sending 2.4 times their usual amount stands out, and a trading company moving millions as normal does not.

Spotting structuring and layering
Alerts Worth Opening

A shorter queue, with nothing missed.

With alert filtering on, a customer who keeps breaking the same rule raises one alert for the interval you set. The first breach still reaches an analyst, and the repeats don’t bury the next case.

What a False Positive costs
Your Policy, Your Rules

The people accountable for the policy write the rules.

Your compliance team builds rules from customer history, your own tables and the thresholds you set, combines them into rule sets and activates them. When your risk appetite changes, the rules change with it.

How rules are built
Every Alert Explained

An answer ready for “why did this alert?”

Each alert opens on the transaction, the rule that raised it and its score. Your analyst starts from the reason, and so does anyone who reviews the decision later.

Investigating an alert
From Alert to Report

One record, from rule to report.

An investigation opens from the alert, a suspicious activity report for your Financial Intelligence Unit can be prepared from the same data, and every action is recorded with who took it and when.

Reporting to your Financial Intelligence Unit
Two Results from One Load

Load your data once. Monitor and score from it.

The same datamart and analytical engine run Client Risk Scoring. Monitoring raises alerts on transactions, scoring assigns each customer a risk class, and that class goes back to your core system.

Scoring every customer from the same data

Why DetectX®

Most monitoring flags the biggest clients. DetectX® flags the ones that changed.

  • Measured against their own pastOne threshold for every customerA rule can compare each customer with their own twelve monthsHistory in every check
  • Big is not suspiciousYour largest clients flagged every monthA steady large client stays out of the queueHow it works
  • Change is caughtA smaller customer whose behaviour changed slips underA customer whose activity jumps is flagged, whatever their sizeKey benefits
  • One alert per intervalThree breaches, three alertsRepeat breaches within the interval you set raise one alertAlert filtering
  • Your rules, your multiplesOne number, set once for everyoneYour team sets the comparison period, the multiple and the tables behind itBusiness Rules Design & Engine
  • One platform, not another systemA separate system with its own dataShares its datamart and engine with Client Risk Scoring and its rule designer with Transaction FilteringThe DetectX® platform

How Transaction Monitoring Works

Try it yourself: four steps, from the rule that fired to the record of what was done.

DetectX® checks every transaction against its history and your rules in an end-of-day run. A violation becomes an alert, and the alert becomes an investigation, a report and an audit trail in the same AlertViewer. Every step is yours to drive.

Illustrative exampleInvented Names & Data

Explore the DetectX® Platform

Start with Transaction Monitoring. Add what you need next.

Every DetectX® solution runs on the same underlying platform, sharing its capabilities, AlertViewer and audit trail. Pick one to see what it adds to Transaction Monitoring.

All solutions

Transaction Monitoring FAQs

What compliance teams usually ask before they choose Transaction Monitoring.

Something we have not covered?Talk to our team

Transaction monitoring is the ongoing review of customers’ transactions to find activity that is unusual for that customer and may point to money laundering or terrorist financing. Unusual activity is investigated and, where the suspicion remains, reported to the Financial Intelligence Unit. DetectX® does this in an end-of-day run: every transaction is checked against the customer’s history and your rules, and a broken rule opens an alert.

No. It runs at the end of each day over every transaction in the configured time range. To stop a payment before it is released, use Transaction Filtering or Instant Payment. For fraud checks while a payment is in flight, see Real-time Transaction Monitoring.

Yes. Rules are built from three kinds of input: parameters from the base model or your dictionaries, such as country risk; variables you set, such as a multiple or a threshold; and expressions calculated from the data. Inputs are compared with operators such as equal or greater, and conditions are joined with AND and OR. Rules are grouped into rule sets and activated there.

Yes. Before the rules run, values from each customer’s history, such as the sum of outflows over the last twelve months, are calculated and added to every record. A rule can then ask whether this month is unusual for this customer, not only whether it is above a fixed amount. Which history values you use, and over what period, is part of your configuration.

In two ways. First, rules can measure each customer against their own history, so large but steady customers do not raise alerts every month. Second, with alert filtering on, a customer who keeps breaking the same rule raises one alert for the interval you set, not one per run.

It needs your customers, accounts, transactions and addresses in the DetectX® datamart. You fill the datamart from your core system directly, or through a data warehouse or operational data store. The same datamart is also used for regulatory reporting.

Yes. When an investigation confirms the suspicion, the report is prepared in AlertViewer from the alert and the data in the datamart. For Switzerland, DetectX® produces payment, transaction history and activity reports to the goAML XML schema, and created reports can be searched in the reports inventory.

They share the datamart and the analytical engine. Transaction Monitoring works on one record per transaction and raises alerts. Client Risk Scoring works on one record per customer and assigns a risk score and class, which go back to your core system. Loading the data once serves both.

Transaction Monitoring · DetectX®

See Transaction Monitoring in a demo

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.