08:14 / Account activity
Regular incoming transfer recorded.
The amount and source are consistent with this fictional account’s recent pattern.
NORMAL CONTEXTAML operations / evidence before escalation
See the reason
behind the signal.
AMLSentry brings transaction monitoring, sanctions screening and regulatory reporting into an evidence-led workspace for banks and payment companies.
Inspect a sample transaction ↓Signals support investigation. They are not conclusions on their own.
02 / Transaction narrative
Follow the behaviour, not just the alert count.
This fictional timeline demonstrates how monitoring reasons can stay attached to a transaction story.
CASEAML–0137Sample record
Investigator note
No review reason at this event.
03 / Screening layers
Different checks. Different reasons. One review record.
Screen names with traceable matching context.
Present potential matches, aliases and confidence cues for trained reviewers rather than hiding them behind a single colour.
NAME + LIST CONTEXTConnect rules to the behaviour that triggered them.
Keep amounts, timing, counterparties and the relevant scenario together for investigation.
EVENT + REASONKeep ownership and decisions reviewable.
Record hand-offs, evidence requests and closure rationale in the same case narrative.
OWNER + DECISION04 / Regulatory reporting
Assemble the record without rewriting the investigation.
- 01Bring verified case facts forward
Reuse reviewed information while keeping its source visible.
- 02Complete required reporting fields
Separate incomplete information from information that does not apply.
- 03Preserve submission history
Keep preparation, review and reporting events in an accountable trail.
05 / Operations conversation