sar-filing

Drafts FinCEN Suspicious Activity Reports (Form 111) for BSA/AML regulatory filing. Compiles subject identification, transaction timelines, red-flag analysis, and activity classifications. Use when a financial institution detects suspicious transactions requiring mandatory SAR filing, continuing activity reports, or BSA compliance documentation.

11 stars

Best use case

sar-filing is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Drafts FinCEN Suspicious Activity Reports (Form 111) for BSA/AML regulatory filing. Compiles subject identification, transaction timelines, red-flag analysis, and activity classifications. Use when a financial institution detects suspicious transactions requiring mandatory SAR filing, continuing activity reports, or BSA compliance documentation.

Teams using sar-filing should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/sar-filing/SKILL.md --create-dirs "https://raw.githubusercontent.com/CaseMark/skills/main/skills/legal/sar-filing/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/sar-filing/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How sar-filing Compares

Feature / Agentsar-filingStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Drafts FinCEN Suspicious Activity Reports (Form 111) for BSA/AML regulatory filing. Compiles subject identification, transaction timelines, red-flag analysis, and activity classifications. Use when a financial institution detects suspicious transactions requiring mandatory SAR filing, continuing activity reports, or BSA compliance documentation.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# SAR Filing

Drafts a FinCEN-ready SAR (Form 111) from transaction records, investigation files, and institutional data.

## Prerequisites

Gather before drafting:

1. **Transaction records** — amounts, dates, account numbers, instrument types
2. **CIP/KYC documentation** — government IDs, SSN/TIN, beneficial ownership
3. **Investigation file** — alerts, internal notes, employee observations
4. **Filer details** — institution legal name, EIN, LEI, regulator, SAR contact
5. **Prior SAR history** (continuing filings) — BSA IDs, filing dates

## Quick Start

1. Determine filing type: Initial / Continuing / Corrective
2. Verify thresholds: ≥$5,000 (subject identified) or ≥$25,000 (no subject)
3. Confirm deadline: 30 days from detection (60 if no subject identified)
4. Draft sections in order below
5. Run compliance checklist before submission

## SAR Sections

### 1. Filing Header

| Field | Detail |
|---|---|
| Filing type | Initial / Continuing / Corrective |
| Institution | Legal name, EIN/LEI |
| Regulator | OCC / Fed / FDIC / NCUA / State |
| SAR contact | Name, title, phone, secure email |
| Detection date | When activity first identified |
| Filing deadline | 30 days (60 if no subject) |
| Prior BSA ID | If continuing: reference number + new trigger |

### 2. Subject Identification

Classify each party: Subject, Purchaser/Sender, Payee/Receiver, Other.

**Individuals:** Legal name, aliases, DOB, SSN/ITIN, address, government ID (type/number/jurisdiction/expiration). Foreign nationals: passport, citizenship, visa, high-risk jurisdiction nexus.

**Entities:** Legal name, DBAs, EIN, formation state/date, business nature, beneficial owners (≥25% ownership or substantial control).

**Relationships:** Document familial, business, signatory, nominee, or intermediary connections between parties.

### 3. Account Detail

For each account: number, type, open date, status (active/closed/restricted/frozen), holders/signers, stated purpose, baseline activity profile, and deviations triggering concern.

Include: branch contacts, prior compliance concerns, correspondent/MSB/processor relationships with fund-flow tracing, CIP/CDD/EDD procedures performed, closure details if applicable.

### 4. Activity Classification

Select FinCEN categories:

| Category | Examples |
|---|---|
| Structuring | Below CTR thresholds |
| Money laundering | Layering, integration, funnel accounts |
| Terrorist financing | OFAC/SDN nexus |
| Fraud | Check kiting, wire fraud, elder exploitation |
| Identity crimes | Synthetic ID, stolen credentials |
| Cyber | Account takeover, intrusion-related transfers |
| Sanctions evasion | Sanctioned jurisdictions/persons |
| Other | Unlicensed MSB, trade-based ML, human trafficking |

**Thresholds:** ≥$5,000 (subject identified) / ≥$25,000 (no subject). For blocked/attempted transactions, explain why filing is warranted. Confirm no exemption applies and filing is not duplicative.

State total dollar amount, currency, and complete time period.

### 5. Narrative

Address Who/What/When/Where/Why/How chronologically:

1. **Detection** — How identified (alert, referral, LE inquiry, audit); specific trigger; why not false positive
2. **Timeline** — Each significant transaction: date, type, amount, source→destination, stated purpose, unusual characteristics
3. **Red flags** — Map facts to indicators: reluctance to provide info, no economic purpose, rapid in/out movement, structuring, shell companies, high-risk jurisdictions, profile inconsistencies. Cite FFIEC BSA/AML Manual or FinCEN advisories where applicable.
4. **Investigation** — Customer contact attempts and responses, why insufficient, public records research, prior SARs (BSA IDs and dates)
5. **Conclusion** — Factual basis for filing. Objective tone only — no conclusions about criminal intent.

### 6. Supporting Documentation

Index attachments by category: transaction records, customer ID docs, correspondence, monitoring system output, investigation memos, inter-institution communications. Label each with title and narrative relevance.

## Compliance Checklist

- [ ] Filed within 30-day deadline (60-day if no subject)
- [ ] All mandatory Form 111 fields completed
- [ ] Narrative addresses Who/What/When/Where/Why/How
- [ ] Dollar amounts accurate and aggregated
- [ ] All dates, account numbers, IDs verified
- [ ] Senior management/board notified per policy
- [ ] Legal counsel consulted if civil liability or non-BSA issues
- [ ] Reviewing/approving officers documented
- [ ] Filed via BSA E-Filing; confirmation + BSA ID retained
- [ ] File stored separately, access restricted to need-to-know
- [ ] 5-year retention initiated from filing date
- [ ] **No disclosure** to any subject (31 U.S.C. § 5318(g)(2))
- [ ] No inadvertent tipping via closure letters or communications
- [ ] Immediate LE notification assessed

## Critical Rules

- **Confidentiality is absolute.** SAR disclosure prohibition (31 U.S.C. § 5318(g)(2)) carries criminal penalties. Never reference SAR existence in customer-facing communications.
- **Objectivity only.** State facts and observations. Never conclude criminal guilt or legal violations.
- **Over-include.** FinCEN prefers detailed narratives.
- **Standalone.** Must be comprehensible without access to underlying bank records.
- **Continuing filings** must reference prior BSA IDs and identify what is new.
- **Safe harbor** (31 U.S.C. § 5318(g)(3)) applies to good-faith filings — document investigative process thoroughly.

Related Skills

interpreting-genomic-profiling

11
from CaseMark/skills

Structures comprehensive genomic profiling interpretation with actionable mutations and matched therapies. Use when reviewing genomic test results, identifying targeted therapy options, or interpreting NGS panels.

hsr-filing

11
from CaseMark/skills

Prepares Hart-Scott-Rodino Act premerger notification filings for FTC/DOJ submission under 15 U.S.C. § 18a and 16 C.F.R. Parts 801-803. Covers threshold verification, NAICS revenue breakdowns, Item 4(c)/(d) document collection, competitive overlap analysis, prior acquisitions disclosure, and filing assembly. Use when an M&A deal may meet HSR size thresholds and requires antitrust clearance, premerger notification, or FTC/DOJ merger review.

final-tax-return-filing

11
from CaseMark/skills

Drafts U.S. final tax return filing packets for decedent estates or dissolving entities, covering final-status designation, short-period reporting, liquidation items, schedule selection, and filing mechanics. Use when handling a "final return", "deceased taxpayer", "estate final 1040", "corporate dissolution filing", "short year return", or any closing-phase tax compliance task.

charity-filing-thresholds

11
from CaseMark/skills

Researches state-specific charitable solicitation filing requirements keyed to gross revenue, producing a citation-backed state-by-state compliance matrix of audit thresholds, financial-statement tiers, filing fees, and due dates. Use when building charity compliance matrices, researching nonprofit filing thresholds, charitable solicitation registration renewals, comparing state audit requirements for 501(c)(3) organizations, or when the user mentions audit threshold, review threshold, compilation requirement, charity filing deadline, or multi-state nonprofit compliance.

blue-sky-filings

11
from CaseMark/skills

Produces a practitioner-grade Blue Sky compliance memorandum and execution plan for U.S. securities offerings. Analyzes NSMIA covered securities preemption, classifies offerings under Regulation D/Rule 506 or alternative federal exemptions, maps state jurisdictional nexus distinguishing offers from sales, and generates a state-by-state filing plan with Form D/EFD workflow, fee schedules, amendment triggers, and renewal calendars. Use this skill when advising on private placement Blue Sky compliance, Reg D notice filings, multi-state offering coordination, state securities registration exemptions, Form D filings, EFD submissions, or state fee budgeting. Also trigger when the user mentions covered securities preemption, NSMIA analysis, or asks about state notice filing requirements. Even if the user just says "Blue Sky" or "state filings for our raise," use this skill.

managing-insurance-regulatory-filings

11
from CaseMark/skills

Structures statutory filing preparation with SAP differences, risk-based capital, and annual statement schedules. Use when preparing statutory filings, calculating RBC, or managing regulatory submissions.

tracking-13d-and-13g-filing-patterns

11
from CaseMark/skills

Monitors beneficial ownership filings with accumulation pattern analysis, intent assessment, and historical activist progression. Use when tracking 13D filings, analyzing accumulation patterns, or identifying potential activist situations.

skill-name

11
from CaseMark/skills

Replace with a specific description of what this skill does and when to use it. Include keywords that help agents identify relevant tasks.

writing-surgical-consultation-notes

11
from CaseMark/skills

Creates structured surgical consultation responses with assessment and surgical candidacy determination. Use when responding to surgical consults, evaluating surgical candidates, or documenting surgical recommendations.

writing-operative-reports

11
from CaseMark/skills

Creates structured operative notes with findings, technique, specimens, and estimated blood loss. Use when dictating operative reports, documenting surgical procedures, or recording intraoperative findings.

writing-irb-submissions

11
from CaseMark/skills

Creates IRB submission packages with protocol summaries, consent forms, and risk-benefit analysis. Use when submitting to IRB, preparing ethics applications, or writing consent documents.

writing-grant-applications-research

11
from CaseMark/skills

Structures NIH/foundation grant applications with specific aims, significance, and innovation sections. Use when writing research grants, preparing NIH applications, or structuring grant proposals.