Independent advisory · Banking · Public sector · Defence · AI
Client portalJoin the expert network
PiR2-IT Start an engagement
Product & project · Agentic AI for AML compliance

Agentic AI that triages alerts, builds cases and drafts reports — with compliance officers in control.

An agentic AI and hyperautomation platform for anti-money laundering. Specialised agents enrich alerts, evaluate typologies, resolve beneficial ownership and draft investigation and SAR narratives, while every consequential decision stays with a human. Implemented in 16 financial institutions.

Start an engagement →Open the live demo ↗
Status
In production & support · continuously refined
Implementations
16 financial institutions
Scope
KYC / CDD · Transaction monitoring · Investigations · Regulatory reporting
Control
Human-in-the-loop · confidence gate · immutable audit log
Integration
Core banking · SWIFT / SEPA · existing TMS (Actimize, Mantas, NetReveal)
Agentic AML Hyperautomation — concept illustration
Results

Measured outcomes.

16
financial institutions
4
AML domains covered
≥95%
confidence required for auto-closure
100%
agent steps logged for audit
Architecture

Core design themes.

01

Event & data layer

Alerts and transactions from core banking, SWIFT/SEPA and the existing monitoring system are streamed through an event bus and normalised into one standard payload.

02

Agentic orchestration

A supervisor agent routes each case to specialised agents — enrichment, typology and risk, narrative and case packaging — with short-term state and a vector memory of past resolutions.

03

Tool bus

Agents call governed tools over APIs / MCP: customer profile, transaction ledger, sanctions and PEP screening, counterparty graph and adverse media.

04

Output & governance

High-confidence false positives are closed with a full rationale; everything else goes to an L2 analyst as a pre-filled case file. Every step is logged and explainable.

Customisation

What can be tailored.

Customisation workflow

From scoping to continuous improvement.

01

Alert ingestion

An alert from the monitoring system is normalised into a standard payload: alert ID, rule, entity, transaction and timestamp.

02

Context enrichment

The enrichment agent pulls the KYC profile, 30/60/90-day ledger history and the counterparty graph in parallel.

03

Intent & typology evaluation

The typology agent checks the business rationale, re-screens sanctions and PEPs and scores known laundering typologies.

04

Narrative synthesis

The narrative agent writes an audit-proof summary: trigger, findings, risk factors and recommended disposition.

05

Confidence gate

Auto-close only at ≥95% confidence and low risk; otherwise escalate to an L2 analyst with the full case file.

06

Human decision

Analysts and the MLRO take the decisions that matter — escalations, SARs and high-risk customers.

07

Audit & evaluation

Immutable logs of every step; regular benchmark tests on precision and recall.

08

Continuous improvement

Baselines, typologies and rules are updated as behaviour and regulation change.

Capabilities

What it delivers.

Implementation note · Product · in production & support

Agentic AML Hyperautomation is a PiR2-IT product in production and support, implemented in 16 financial institutions and continuously refined. Agents prepare evidence and recommendations; suspicious activity reports, high-risk escalations and model changes are approved by people.

References, case studies and demonstrations are available on request, under NDA.

AMLKYC / CDDUBOTransaction monitoringAlert triageSAR / STRAgentic AIHyperautomationHITL
Questions

About this project.

Does it replace our transaction monitoring system?

No. It works on top of the existing system (for example Actimize, Oracle Mantas or NetReveal): alerts are streamed in, and agents do the enrichment, triage and case preparation.

Can an agent close an alert on its own?

Only when confidence is at least 95% and the risk score is below the institution’s threshold. Everything else is escalated to an L2 analyst with a pre-filled case file. If a tool fails or times out, the case is escalated by default.

Who files the SAR / STR?

A compliance officer. Agents draft the narrative, citing transaction IDs, rules triggered and typologies; a person reviews, signs off and submits.

How is it audited?

Every agent reasoning step, tool call and model prompt/response is written to an immutable audit log, and the models are tested regularly against historical false positives and confirmed SARs.

Where has it been implemented?

In 16 financial institutions. Client names are confidential; references are available on request, under NDA.

Can I try it?

Yes. An interactive demo on synthetic data runs at aml.pir2-it.com: alert triage by agents, L2 case files, SAR drafting with MLRO approval, UBO resolution and a hash-chained audit log. A demonstration on your own data runs under NDA.

Related

Explore further.

Ready to discuss
your programme?

Start an engagement → office@pir2-it.com