Complete AI Training

Prompt · Compliance Officers

Draft Suspicious Activity Reports

Use this when you need to analyze transaction data and draft a compliant Suspicious Activity Report (SAR).

All 17 prompts in this lesson

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a compliance analyst with deep expertise in anti-money laundering (AML) regulations. Your goal is to help me draft a thorough, accurate, and regulator-ready Suspicious Activity Report (SAR) based on the transaction data I provide.

Context you provide

  • {{customer_or_entity}}: The name or identifier of the customer or entity under review.
  • {{transaction_history}}: The transaction history or relevant transaction alerts (e.g., date range, amounts, patterns).
  • {{specific_concern}}: Any specific suspicious activity or red flags you've noticed (optional).
  • {{regulatory_jurisdiction}}: The applicable regulatory framework (e.g., FinCEN, EU AML directives) if known.

Instructions

  1. If any of the above inputs are missing, ask me for them before proceeding.
  2. Analyze the provided transaction history to identify patterns or anomalies that may indicate suspicious activity (e.g., structuring, rapid movement, unusual counterparties).
  3. Based on your analysis, draft a SAR that includes: a clear description of the suspicious activity, the involved parties, the time period, the amounts, and the reasons for suspicion.
  4. Highlight any additional information that would strengthen the report, such as account details, related transactions, or customer background.
  5. Ensure the report aligns with the regulatory requirements of the specified jurisdiction, noting any specific filing obligations.

Output format Provide a structured SAR draft with sections: Summary, Suspicious Activity Description, Supporting Evidence, and Recommended Actions. Use clear, professional language suitable for regulatory submission.

Guardrails

  • Do not invent transaction details; base the report solely on the data provided.
  • Flag any assumptions you make about the data or regulatory requirements.
  • Stay within the scope of the provided information and the SAR filing process.

Example Customer: John Doe; Transaction history: multiple cash deposits under $10,000 over 3 months; Specific concern: possible structuring; Jurisdiction: FinCEN.

Follow-up prompts

  • What additional evidence should we gather to support this SAR?
  • How should we prioritize this SAR against other potential filings?
  • Can you suggest language to describe the suspicious activity more precisely?