AML Monitoring
Rule-based detection
Build, simulate and tune your own scenarios with no-code, and see the impact before anything goes live.
AI-powered detection
Advanced machine learning reads behaviour across transactions, accounts and the network behind them. Every score comes with the factors that drove it.
Case management
A workspace for alerts, customer profiles and reporting, with a full audit trail. Use ours, or keep the case manager your investigators work in today.
Explainable and traceable
Explainability was a condition from the start. For every alert, your team sees what drove the score, down to a single transaction. You set your own risk appetite. Every new version of the AI is tested against the current one before it goes live, and your bank validates the results. Every decision can be traced and explained, even years later.
Nothing has to be replaced for this to work
Discai can run as an add-on to the transaction monitoring you have today, or you can replace it. It can check transactions ex ante, before they are executed, and ex post, depending on what you need. You can start by adding our AI solution to the rule-based scenarios you already run. Later you can move your rules onto our platform, and your investigations into ours. You decide how far you go and what you leave to us.
The cost of AML is mostly time
Discai brings false positives down by 40 to 60%. That means fewer alerts reach your team that never needed to be looked at. Every alert that does arrive shows the customer, the transactions and the factors behind the score. So investigators can judge within minutes whether an alert needs a full investigation or a short note. Your team is always in control and reaches a decision on each case faster.
The other part of the cost is keeping the solution running. One subscription covers the licence, the cloud, maintenance and the retraining of the AI. You do not pay separately for servers, updates or data scientists to keep the AI accurate.
Build and manage scenarios with full transparency over how alerts are generated. Our dynamic scenario management enables teams to simulate and tune scenarios before deployment, adjust thresholds and continuously improve performance.
- Design and manage scenarios Align detection logic with the institution’s risk framework.
- Simulate changes before deployment Simulate a change to a rule and see its impact before it goes live. A lookback runs a new or changed rule over past transactions and shows which alerts it would have raised.
- Continuously improve Evaluate scenario performance and tune thresholds using actual results.
- No-code rule design Create, manage and adapt rules with an intuitive drag-and-drop interface.
Discai uses machine learning to identify behavioural patterns, relationships and risks that predefined scenarios cannot capture. Depending on the institution’s needs and targets, different models are trained and combined to provide the most effective detection coverage.
By learning from your historical investigations or looking at anomalous behaviour within peer groups, the solution brings together behavioural, transactional and network insights into a holistic risk score. This way, investigators can focus their attention on customers that warrant closer investigation.
- Broader detection Identify suspicious behaviour that remains invisible to predefined scenarios.
- Behavioural insights Detect unusual customer behaviour and transaction patterns.
- Network intelligence Reveal relevant relationships and transactional connections.
- Risk prioritisation Focus investigative capacity on higher-risk behaviour for target typologies.
- Explainable risk scoring Understand the drivers behind each risk score and document your decision-making.
AI is becoming increasingly important in AML detection, uncovering suspicious behaviour that traditional scenarios may not identify. At the same time, scenario-based monitoring remains an established approach, providing the transparency, explainability and control regulators expect.
Combining rule-based monitoring with machine learning brings both together: broader detection without giving up regulatory control, with investigators remaining firmly in the decision-making process.
The customer demonstrates frequent inbound transfers from transport-related counterparties and regularly sends funds internationally to high-risk countries. This activity is accompanied by high-value payment flows and recurring outgoing cash transactions at night, indicating a high level of transactional activity across multiple channels.
- Number of transfers received from transport companies (last 3 months) 25 +0.763% ↑
- Average amount of point-of-sale payments received (last month) 20,237.29 +0.574% ↑
- Number of days since the customer registered 549 +0.522% ↑
- Number of transfers sent to high-risk countries (last 3 months) 36 +0.337% ↑
- Total amount of outgoing cash transactions at night (last 12 months) 2,740.09 +0.235% ↑
- Number of transfers received from transport companies (last 3 months) 25 +0.763% ↑
- Number of days since the customer registered 549 +0.522% ↑
- Percentage of outgoing cash transactions (last 3 months) 68.75 +0.513% ↑
- Proportion of transfer amounts received from European countries (last 3 months) 55.83 +0.211% ↑
- Age of the customer 80 +0.143% ↑
- Average amount of point-of-sale payments received (last month) 20,237.29 +0.574% ↑
- Number of transfers sent to high-risk countries (last 3 months) 36 +0.337% ↑
- Total amount of outgoing cash transactions at night (last 12 months) 2,740.09 +0.235% ↑
- Number of incoming transfers on shared accounts (last month) 128 +0.222% ↑
- Lowest cheque amount received (last month) 2,282.24 +0.219% ↑
- Deployment stage
- Champion
- Model version
- 5
- Version date
- 2 June 2026 at 11:23
- Model creator
- Discai nv
- Business purpose
- Discai foundation models
- Primary use
- Generating better alerts
- Explainability available
- Yes
- Explainability approach
- SHAP values combined with LLM explainability
- Validation guidelines
- Bank XYZ model management framework policy, version 2.3
- Time scope
- 2023 to 2026
- Upstream systems
- AML API
- Downstream systems
- Payment rail, case manager
- Training data
- Investigations history 2024 to 2026
- Change log
- 14 July 2026 at 17:34: Model retraining default cycle
- Related models
- Model 123 · sibling
- Champion v5 in production
- Archived v4
- Archived v3
- Archived v2
- Archived v1
The model owner updated Intended Use, Ethics & Compliance, Model Data and Lineage. 18 Sept 2026
Do we have to take the whole platform?
No. AML Monitoring stands on its own, and within it you choose rules, AI or both. Investigations stay in your own case manager or move into ours. Everything runs on one platform, so once you are connected, adding more later takes little extra effort.
Has this been used in a real bank?
Yes, it has. What’s more: Discai was built inside KBC, a leading European banking group, by people who then had to defend it to a regulator. AML Monitoring has been running there for years, across several countries and >13M customers.
Does it work ex ante, in real time?
Yes. Discai can check transactions ex ante, in real time, before they are executed, and flag the ones that look suspicious. Your bank decides what happens next. Ex post, Discai looks back over time to find patterns that only show up across many transactions. You choose what is checked ex ante and what ex post.
Do we need data scientists to run this? And who keeps the AI accurate?
You do not need data scientists to run Discai. Our team takes care of the AI and your compliance team manages the rules. During the implementation, it helps to have someone on your side who knows your data and how it is structured.
For the AI, our team does the data science work. Criminals keep changing their methods, so the AI has to keep up. We monitor it every day and counter drift. When something changes, we retrain it on your own data, several times a year if needed, always in agreement with you. Every new version is tested against the current one before it goes live. Your bank validates the results and decides.
For the rules, your compliance team works self-service. You can start from our rules library or use your own. Scenarios are designed, simulated and tuned with no-code. You decide how much of the configuration you keep in house and how much you leave with us.
Can we try it first?
Yes. We understand this is not a decision taken lightly, and that you want to see it work on your own data first. For the AI, we start with a pilot on your own data, live in eight weeks. For the rules, you can build and test your own scenarios in a sandbox before anything goes live.