Demo · Internal SAR end-to-end

One suspicion.
Six steps. One confidential chain.

A colleague on the operations desk notices something odd. Follow that single suspicion from the Staff Hub through the Money Laundering Reporting Officer (MLRO) substrate — with three statutory SLA clocks armed at submission, tipping-off safeguards on every screen, and an aggregate-only line at the end for the board.

Confidentiality firewall
Separate RLS from every other tenant surface. Never indexed into Compass or any AI context. Tipping-off banner on every screen. Board pack receives counts only — never names, subjects or case content.
IntakeSLA armedAcknowledgeTriageDecideFIU · Board
01

Intake — the colleague submits from the Staff Hub

/intake/saltire · Internal SARNo operator seat consumed
Unusual third-party payment pattern — Client file C-48212026-06-28 09:42
"Three payments in one week from unrelated corporate accounts, all rounded to the nearest £5k, all narrated as loan repayments. Client hasn't previously used these counterparties."
submitter: ops-desk (seat-less)channel: internal-sar

Why this matters: Anyone in the firm can raise a suspicion — no seat, no licence cost. The Staff Hub is per-tenant branded, so it looks and feels like the firm's own channel, not a third-party form.

Ownershipwhole-firm reach
02

SLA armed — three statutory clocks start

/mlro-case · Triage queueSubstrate: mlro_internal_sar
acknowledged_atdue +24h (2026-06-29 09:42)
initial_fiu_consideration_due_at+3 business days
external_report_due_at+10 calendar days
mlro_internal_sar · On insert · refreshed just now

Why this matters: The three JFSC clocks (acknowledge · initial FIU consideration · external report) arm the moment the row lands. Queue tiles count overdue items against these clocks — nothing to configure.

Evidencestatutory clocks recorded
03

Acknowledge — the 24h leg closes automatically

sar-ack email templateTipping-off safe
To: ops-desk · Subject: Your report has been received

"Thank you for raising this. It has been received and logged. Please do not discuss the substance with anyone else, including the subject or your line manager. The MLRO will handle any next steps."

acknowledged_at = 2026-06-28 09:47 · clock closed

Why this matters: The acknowledgement is a compliance obligation, not a courtesy. Copy is tipping-off safe by design — no confirmation of what happens next, no mention of the FIU.

Trusttipping-off safe
04

Triage — MLRO promotes the SAR into a case

/mlro-case · SAR-DEMO-005 → CASE-DEMO-005MLRO only
Drafted by Compass · awaiting review
Compass suggestionTypology: layering

Rationale: pattern matches previously closed CASE-DEMO-002 (rounded-value structuring, unrelated corporate senders). MLRO reviews before accepting the tag.

suspicion_arose_at = 2026-06-28 09:42 · MLRO: S. Henderson

Why this matters: Compass suggests a typology tag — the MLRO decides. The moment triage completes, the "initial FIU consideration overdue" tile drops this row: the decision has been made, on the record.

JudgementMLRO decides, Compass suggests
05

Decide — decision is hash-chained into the log

/mlro-case · Decision logSubstrate: mlro_decision_log

Trust filterWould you sign this yourself? If not, hold.

Append-only chain (SHA-256):
#1 prev 0000…0000 · hash 6d21…be04 — "Case opened from SAR-DEMO-005."
#2 prev 6d21…be04 · hash a917…33f8 — "Reasonable grounds present. External report to FIU authorised."

Why this matters: Every MLRO decision writes an entry whose hash is derived from the previous entry. Nothing can be silently amended after the fact — the chain would break and the tampered link would be visible.

Evidencehash-chained decisions
06

FIU marker + board — aggregate only, never PII

/governance/board-pack · Q3 2026 draftAggregate-only feed
Financial crime · this quarter
Internal SARs raised: 14
Triaged to case: 9
External reports filed with FIU: 3
Median acknowledge time: 4h 12m
no subject names · no case content · verify counts at /verify

Why this matters: The board sees the shape of the risk — volumes, medians, throughput — never the names or the narrative. The FIU report existence is marked; the report content stays in the MLRO substrate.

Trustaggregate to the board, always
Try it live
See a regulatory change end-to-end Back to the demo hub
Ready when you are

Seen enough to talk?

Every demo on RegAlign is open — no form wall, no sales chase. When you're ready, request pilot access and we'll book a working session.