Home/Resources/Guides/From alert to report

From alert to report

Most alerts close. Some become cases, and a few become reports. This guide follows one all the way, and shows where each person signs.

ForAnalyst, Compliance officer, MLROSteps6Reading time5 min
01

Read the alert, not just the score

Every alert leads with its reason in a full sentence, then the score, the customer and the time left. Your queue is ordered by what matters and how long remains.

My open work
87

Funds reached an exchange whose inflows are 31% darknet-traced, four times the customer’s declared ceilingALT-2291 · corporate customer

4.6h left
02

Work through the evidence

Evidence is sorted into adverse, inconclusive, context and clearing. A quick closure is locked until you have read what could change your mind.

TipThe lock is deliberate. It is what lets a closure stand up in QA months later.

Evidence summary
2adverse
0inconclusive
1context
1clearing

Close as false positive · read 3 remaining items first

03

Open a case and test the story

When one alert is not enough, open a case. The agent drafts a narrative, marked as machine-written, and you test hypotheses as open, supported, weakened or refuted.

Hypotheses
H1

The mandate expansion explains the higher outflowSigned letter on file

supported
H2

Part of the outflow goes outside the mandateCounterparties not yet reconciled

open
04

Escalate through the chain

Suspicion goes from the analyst to the compliance officer, who adds a view, and then to the MLRO, who decides whether to file. Each step is signed with a name, a time and a reason.

Escalation
  1. 1Report to the MLROAnalyst
  2. 2Compliance officer’s viewCompliance officer
  3. 3Filing decisionMLRO
05

Draft and check the report

The report drafts itself from the case, and each field shows where it came from. Checks run before submission, and anything blocking is shown first.

STR · draft1 issue blocks submission
  • Subject and beneficial owners listed
  • Transactions with hash, asset and value
  • Every attribution names its provider
06

File, and keep the record

The MLRO signs and exports to goAML. The report joins the filing register, any follow-up from the FIU is tracked with its deadline, and contact with the customer is restricted to prevent tipping off.

Filing register
STR-2026-0194Reported
FIU request31h left
Customer contactRestricted

See it on your own cases.

We will walk through this with your team, on a scenario you choose.