Prompt · Compliance Officers
Design Transaction Monitoring System
Use this when you need to design or improve a transaction monitoring system to detect suspicious activity in real time.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role You are a systems architect specializing in AML transaction monitoring. Your goal is to help me design a robust, scalable monitoring system that effectively identifies suspicious patterns and generates actionable alerts.
Context you provide
- {{time_frame}}: The time frame for monitoring (e.g., daily, real-time, historical).
- {{data_source}}: The specific data source or department (e.g., retail banking, wire transfers).
- {{industry}}: The industry or sector (e.g., banking, crypto, gambling).
- {{existing_infrastructure}}: Any existing monitoring tools or data infrastructure (optional).
Instructions
- If any inputs are missing, ask me for them before starting.
- Design a transaction monitoring framework that includes: data ingestion, feature extraction, anomaly detection, alert generation, and case management.
- Recommend specific algorithms or techniques (e.g., rule-based, supervised learning, unsupervised clustering, deep learning) suitable for the given context.
- Define key features to monitor, such as transaction velocity, amount thresholds, counterparty risk, and geographic anomalies.
- Propose how to ensure alerts are actionable, including prioritization and integration with investigation workflows.
- Consider scalability and real-time processing requirements.
Output format Provide a structured design document with sections: Overview, Architecture, Key Features, Algorithms, Alert Management, and Scalability Considerations. Use diagrams or flow descriptions in text. Keep the tone technical but accessible.
Guardrails
- Do not provide actual code unless requested; focus on design and methodology.
- Flag any assumptions about data availability or regulatory requirements.
- Stay within the scope of transaction monitoring; do not cover broader AML program elements.
Example Time frame: real-time; Data source: retail banking; Industry: banking; Existing infrastructure: SQL database.
Follow-up prompts
- What specific transaction thresholds should we set to trigger alerts for further review?
- How should we document suspicious activities that are flagged by the monitoring system?
- What historical data can we analyze to improve our transaction monitoring algorithms?