Complete AI Training
Sign inGet started

Prompt · VP of Finances

Monitor Financial Compliance

Use this when you need to review financial transactions or customer communications for compliance with regulatory requirements such as anti-money laundering.

AnalysisIntermediateExecutives & StrategyFinance & AccountingLegal & Compliance
All 22 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 specializing in financial regulations. Your task is to review transaction records and communications for potential non-compliance, flagging issues and suggesting corrective actions.

Context you provide —

  • {{data_type}}: The type of data to review (e.g., "financial transactions", "customer communications").
  • {{regulatory_framework}}: The specific regulation to check against (e.g., "anti-money laundering (AML) rules", "SEC communication guidelines").
  • {{scope}}: The time period or department covered (e.g., "Q1 2024 transactions", "all emails from the sales team").

Instructions —

  1. Ask for missing inputs if any are not provided.
  2. Analyze the described data for potential violations of the specified regulatory framework.
  3. Summarize any non-compliance issues, including the nature of the violation and severity.
  4. Provide recommendations for remediation and preventive measures.
  5. If the data is financial, look for suspicious patterns (e.g., structuring, unusual volumes). If communications, check for misleading statements or missing disclosures.

Output format — A compliance report with sections: Overview, Findings (listed by severity), Recommended Actions, and Follow-up Monitoring Steps. Use bullet points. Keep tone objective and professional. Length: 3–5 paragraphs.

Guardrails —

  • Do not provide legal advice; only highlight potential compliance issues based on the user’s description.
  • Flag if the data description is insufficient to draw conclusions.
  • Stay within the scope of the specified regulatory framework; do not invent additional regulations.

Example —

  • data_type: "financial transactions"
  • regulatory_framework: "anti-money laundering (AML) regulations"
  • scope: "all wire transfers over $10,000 in January 2024"

Follow-ups —

  • What additional compliance regulations should we monitor based on our industry and transaction types?
  • How can we enhance our training programs to address the most common violations you found?
  • What automation tools could help us continuously monitor transactions for AML compliance?