Suspicious transaction monitoring
Suspicion is risk- and context-based and can exist regardless of amount. Monitoring should combine customer profile, typologies, linked transactions and hu
Finin2min summary
Suspicion is risk- and context-based and can exist regardless of amount. Monitoring should combine customer profile, typologies, linked transactions and human review.
Legal anchors
- PML Rules definition and reporting obligations
- FIU sector guidelines
How to analyse it
- Create sector-specific scenarios.
- Aggregate linked activity.
- Document alert closure rationale.
- Escalate promptly to principal officer.
Practical illustration
A dormant account receives rapid third-party credits followed by overseas transfers. Even if individual transactions are below cash thresholds, pattern and purpose can be suspicious.
What can go wrong?
- Rule-based alerts with no review
- Backlog without governance
- Customer contacted about STR decision
Evidence pack
- Alert file
- Customer profile
- Transaction graph
- STR decision note
Decision workflow
- Freeze the facts and effective date.
- Identify the controlling Act, rule, notification, circular and jurisdictional overlay.
- Prepare a calculation or exposure note.
- Collect the evidence pack before filing, payment, signing or response.
- Record reviewer conclusion and assumptions.
Quick Q&A
Is the result automatic?
No. Create sector-specific scenarios.
What is the most important control?
Escalate promptly to principal officer.
What should be escalated?
Rule-based alerts with no review, especially where money, deadlines, enforcement, personal liability or irreversible transaction steps are involved.
Official source trail
- PMLA, 2002 — FIU-IND
- PMLA, 2002 PDF — FIU-IND
- PML Maintenance of Records Rules, 2005 — FIU-IND
- FIU-IND FAQs
Secondary commentary may help interpretation, but it is not the source of law.