sar-submission

What problem does it solve?

Russian financial institutions and other obligated entities under 115-FZ are legally required to submit suspicious transaction reports (СПО) and control transaction reports (СОО) to Rosfinmonitoring within strict 1 or 3 business day deadlines, with non-compliance resulting in administrative fines of 50,000 to 500,000 rubles for legal entities. Reports also require specific XML formatting and factual, non-accusatory language to be accepted by regulators, creating a high burden for compliance teams to produce accurate, timely submissions.

Core Features & Use Cases

• Report Type Classification: Automatically identifies the correct report type (СОО for mandatory control transactions, СПО for suspicious activity, freeze notices for sanctioned list matches) based on provided transaction context.
• Compliant Report Drafting: Generates structured report content aligned with Rosfinmonitoring specifications, including required XML fields, factual situation descriptions, cross-references to customer risk profiles and prior transaction patterns, and lists of applied control measures.
• Post-Submission Workflow: Includes guided steps for submission tracking, 5-year record retention, strict non-tipping-off confidentiality compliance, and customer relationship management decisions. Use case: A compliance officer at a Russian bank detects a client conducting 5 structured cash transfers of 950,000 rubles each in a single business day (total 4.75M rubles, exceeding the 1M ruble mandatory reporting threshold). This skill guides them to draft a compliant structuring-related СПО report, meet the 1-business-day submission deadline, and avoid accidental disclosure to the client.

Quick Start

Use the sar-submission skill to draft a complete compliant suspicious transaction report for the 4.75M ruble structured cash transfer series detected on client INN 7701234567, including all required transaction details, suspicious activity indicators, and post-submission confidentiality steps.