sar-submission

Classify and draft Rosfinmonitoring AML reports with XML formatting.

17|4|Updated May 25, 2026
One-click install
npx skills add https://github.com/AlsKozlov/ru-legal --skill sar-submission
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sar-submission
Source: https://github.com/AlsKozlov/ru-legal/tree/main/packs/compliance-aml/skills/sar-submission
Command: npx skills add https://github.com/AlsKozlov/ru-legal --skill sar-submission

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about sar-submission

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I draft a suspicious transaction report for Rosfinmonitoring under 115-FZ?▼

To draft a suspicious transaction report under 115-FZ, provide transaction details and client risk profiles to generate structured content with required XML fields, factual descriptions, and applied control measures compliant with Rosfinmonitoring specifications.

What is the difference between a СПО and СОО report for AML compliance in Russia?▼

An AML СОО report is for mandatory control transactions, while a СПО report covers suspicious activity. The skill classifies the correct report type based on provided transaction context to ensure proper regulatory adherence.

How do I format Rosfinmonitoring XML reports for suspicious transactions?▼

Formatting Rosfinmonitoring XML reports requires specific fields and factual, non-accusatory language. This skill generates structured report content aligned with official specifications, including cross-references to customer risk profiles and prior transaction patterns.

What are the post-submission requirements for 115-FZ suspicious transaction reports?▼

Post-submission requirements for 115-FZ reports include submission tracking, strict non-tipping-off confidentiality compliance, customer relationship management decisions, and maintaining 5-year record retention. This skill provides guided steps for these workflows.

When do I need to submit a suspicious transaction report to avoid Russian AML fines?▼

You must submit suspicious transaction reports to Rosfinmonitoring within strict 1 or 3 business day deadlines to avoid administrative fines ranging from 50,000 to 500,000 rubles for legal entities under 115-FZ.

Can I use this skill for freeze notices matching sanctioned list entities?▼

Yes, this skill supports freeze notices for sanctioned list matches alongside control transaction reports and suspicious activity reports. It automatically identifies the required report type based on the provided transaction context.