AML transaction monitoring alert triage
Alerts arrive enriched with a draft narrative; the analyst always decides and the filing goes out in minutes.
AML transaction monitoring alert triage is an agent scenario in the Fintech & Payments sector running on the api, batch channels. Trigger: Rule alert from the monitoring engine (structuring / rapid pass-through). The AML Supervisor coordinates 4 specialist agents (Enrichment Agent, Screening Agent, Narrative Agent, Filing Agent) across 4 systems (Core Ledger, Sanctions Screening, Case Management, MASAK Reporting Portal); of 10 steps, 2 write to systems and 2 are checks or approvals. Outcome: Alert decided, case closed or STR filed with MASAK, narrative and evidence trail stored. Approval rule: Every alert → compliance analyst decision mandatory; the agent never files an STR or closes a case alone.
AML transaction monitoring alert triage
- Alert #TM-51290: 9 cash deposits in 6 days totalling 1,140,000, rule R-14
- Customer profile and 90-day history pulled: 47 transactions, 3 counterparties
- Plan: counterparty screening → typology → draft narrative → analyst decision → filing
- 3 counterparties screened: no sanctions hit, 1 PEP link (relative)
- Prior cases: 1 alert on the same customer closed in 2024 (false positive)
- Typology: sub-threshold splitting, 4× declared income → suspicion score 0.82
- Draft narrative prepared with 5 evidence references, MASAK format check passed
- Mandatory analyst decision: compliance analyst edited the narrative, chose "file STR"
- STR filed on the MASAK portal, reference #STR-2026-08812
- Case #AML-7734 set to "filed", evidence pack and decision trail attached
- ■completed
Simulation · derived from real agent definitions · every agent can be built by dialogue with the Autonomous Agent and validated with a test corpus
Rule alert from the monitoring engine (structuring / rapid pass-through)
Alert decided, case closed or STR filed with MASAK, narrative and evidence trail stored
Agents
AML Supervisor
Decomposes the objective, delegates to agents, manages approval points, merges the result.
Enrichment Agent
Gathers customer profile, 90-day transactions and counterparty data
get_alertget_customer_profileget_transactionsget_counterpartiesScreening Agent
Screens counterparties against sanctions/PEP lists, finds prior cases
screen_sanctionsscreen_pepsearch_prior_casesNarrative Agent
Assesses the typology, drafts the STR narrative
score_typologydraft_narrativesummarise_evidenceFiling Agent
Updates the case, files the report with MASAK
update_casefile_strnotify_analystSteps
| # | Kind | Agent | What happens | System | ms | tok |
|---|---|---|---|---|---|---|
| 01 | ingest | AML Supervisor | Alert #TM-51290: 9 cash deposits in 6 days totalling 1,140,000, rule R-14 | — | 180 | — |
| 02 | tool | Enrichment Agent | Customer profile and 90-day history pulled: 47 transactions, 3 counterparties | Core Ledger | 520 | — |
| 03 | plan | AML Supervisor | Plan: counterparty screening → typology → draft narrative → analyst decision → filing | — | 300 | 220 |
| 04 | tool | Screening Agent | 3 counterparties screened: no sanctions hit, 1 PEP link (relative) | Sanctions Screening | 560 | — |
| 05 | retrieve | Screening Agent | Prior cases: 1 alert on the same customer closed in 2024 (false positive) | Case Management | 410 | — |
| 06 | reason | Narrative Agent | Typology: sub-threshold splitting, 4× declared income → suspicion score 0.82 | — | 1,200 | 1,600 |
| 07 | verify | Narrative Agent | Draft narrative prepared with 5 evidence references, MASAK format check passed | — | 900 | 1,100 |
| 08 | approval | AML Supervisor | Mandatory analyst decision: compliance analyst edited the narrative, chose "file STR" | — | 3,800 | — |
| 09 | write | Filing Agent | STR filed on the MASAK portal, reference #STR-2026-08812 | MASAK Reporting Portal | 740 | — |
| 10 | write | Filing Agent | Case #AML-7734 set to "filed", evidence pack and decision trail attached | Case Management | 460 | — |
Merchant operations assistant: POS, settlement, refund and limit
The merchant writes on WhatsApp; POS fault, settlement query, refund and limit increase are resolved in one dialogue.
Merchant KYB onboarding
Registry, UBO and sanctions checks in one flow; low-risk merchants start accepting payments the same day.
BNPL instant instalment decision
Checkout instalment decision in seconds from bureau and open-banking data; large tickets go to underwriting.
Time to move from experimenting with AI to transforming with it.
In a 30-minute discovery session we take your 2–3 priority business problems, show a live demo of a similar scenario, and draft a roadmap that starts with the Value layer.
- Your 2–3 priority problems
- Live demo of a similar scenario
- Roadmap starting with value analysis