The officer's view.
Everything that needs your signature.
The MLRO Console shapes the whole workspace around the person who signs: escalations, dual-control approvals, committee reviews, workflow rules, supervisory reporting and one unfiltered audit log. Analysts investigate; the officer decides; the ledger remembers.
Built for the person who signs
Every screen is shaped for the officer's decision — nothing buried in an analyst queue, nothing assembled by hand at quarter end.
Everything that lands on you, ranked
Cases escalated by analysts arrive with the reason, the risk band, the evidence and the regulatory clock. Nothing waits in an inbox.
- Risk-ranked, filterable, searchable
- Regulatory due-date tracking
- Analyst notes inline with the trace
Two named approvers, enforced
STR filings, freeze orders and watchlist changes require two signatures. The console shows who approved first, what they signed against, and who is waiting.
- Enforced by the system, not by etiquette
- Evidence attached to every signature
- Approver identities in the audit log
The full file, on one screen
Open any escalation and see what the officer needs to decide: score dial, factor-by-factor breakdown, behavioural signals, the agent's reasoning trace, the transaction timeline and the analyst's disposition note. Then decide — approve, request more information, route to committee, or dismiss with a recorded reason.
TRACE name similarity 0.94 · alias 2 · engine v1.0
NEXT decision required: approve STR · freeze · dismiss
When one signature isn't enough
Route high-stakes cases to a review committee: assign reviewers, collect opinions, record the majority. The committee record becomes part of the case file.
Policy in the officer's hands
Auto-clear thresholds, band boundaries, override rules, human-review mandates. Every change is versioned and attributed.
- Thresholds & bands, configurable
- Policy overrides, itemised
- Versioned, in the audit log
The numbers the board and supervisor ask for
STR volumes, filing timeliness, freeze orders, escalation backlogs — derived live from the case ledger. No more assembling five exports every quarter.
Escalations pending 3 · oldest 2h 12m
Freeze orders 2 · dual control ✓
EXPORT goAML XML · quarterly summary · audit bundle
Every signature, timestamped, immutable
The console appends every decision to the shared event log: who approved, who rejected, who reassigned, who changed a rule — with the reason and the exact version of the engine and policy that applied. The examiner's favourite question has a page, and the page is searchable.
[A. AL-RASHID] ESCALATED_TO_MLRO · reason: SDN alias + structuring
[MLRO M. KRISHNAN] RULE_UPDATED · auto-clear 20 → 25 · v4.2
[T. JASSIM] APPROVED_FREEZE_ORDER · MZ-FRZ-2026-003
mizan.agent REPORT_EXPORTED · goAML XML · audit ref attached
The dual-control enforcement alone is worth the migration. No more chasing second signatures by email — the console holds the case until the second approver signs, and the examiner can see it.
Supervisory reporting used to be a two-day scramble before every board meeting. Now it's one screen — STR volumes, timeliness, backlog, live from the case ledger.
I approve or reject with the full reasoning trace on the same screen. I stopped opening three tabs to make one decision.
Take the officer's seat.
An interactive preview of the console is running right now — escalations, approvals, rules, reports, audit log. Sign in with the demo account and make a few decisions.