U.S. flag

An official website of the United States government

Comprehensive SAR Filing Guide for Financial Institutions

Comprehensive SAR Filing Guide for Financial Institutions

Table of Contents

  1. Overview of SAR Requirements
  2. When to File a SAR
  3. SAR Filing Timeline and Deadlines
  4. FinCEN Form 111 Instructions
  5. Critical Data Elements
  6. Narrative Writing Best Practices
  7. Common Filing Errors
  8. Documentation Requirements
  9. Regulatory Citations

Overview of SAR Requirements

The Suspicious Activity Report (SAR) is one of the most critical tools in the fight against money laundering, terrorist financing, and other financial crimes. Financial institutions are required to file SARs with the Financial Crimes Enforcement Network (FinCEN) when they detect known or suspected violations of federal law or suspicious transactions.

SAR filing requirements are established under:

  • 31 U.S.C. § 5318(g) - Bank Secrecy Act provisions
  • 31 CFR § 1020.320 - Banks and credit unions
  • 31 CFR § 1021.320 - Casinos
  • 31 CFR § 1022.320 - Money services businesses
  • 31 CFR § 1023.320 - Brokers or dealers in securities
  • 31 CFR § 1024.320 - Mutual funds
  • 31 CFR § 1025.320 - Insurance companies
  • 31 CFR § 1026.320 - Futures commission merchants and introducing brokers

Purpose of SAR Filing

SARs serve multiple critical functions:

  • Alert law enforcement to potential criminal activity
  • Provide intelligence for ongoing investigations
  • Identify emerging financial crime trends
  • Document the institution’s compliance with BSA/AML obligations
  • Establish the institution’s safe harbor from civil liability

When to File a SAR

Four Primary Scenarios

A financial institution must file a SAR when it detects any of the following:

1. Insider Abuse Involving Any Amount

File a SAR when an insider (director, officer, employee, agent, or other institution-affiliated party) is involved in potentially criminal activity, regardless of the dollar amount.

Examples:

  • Employee embezzlement
  • Officer facilitating money laundering
  • Insider fraud schemes
  • Abuse of position for personal gain

Key Point: No dollar threshold applies to insider abuse.

2. Federal Criminal Violations Aggregating $5,000 or More

File when you detect a known or suspected federal criminal violation where:

  • A subject can be identified
  • The violation involves or aggregates at least $5,000
  • The violation involves funds derived from illegal activity

Examples:

  • Check fraud totaling $7,500
  • Wire fraud scheme of $10,000
  • Identity theft involving $8,000
  • Structuring deposits to avoid CTR reporting

3. Federal Criminal Violations Aggregating $25,000 or More (No Subject)

File when you detect a known or suspected federal criminal violation where:

  • No subject can be identified
  • The violation aggregates at least $25,000

Examples:

  • Anonymous wire transfers showing money laundering patterns
  • Unidentified persons conducting suspicious transactions
  • Account takeover with unknown perpetrator

4. Transactions Aggregating $5,000 or More with BSA Violation Indicators

File when a transaction or pattern of transactions:

  • Aggregates at least $5,000
  • The institution knows, suspects, or has reason to suspect:
    • The transaction lacks business or apparent lawful purpose
    • The transaction is not the sort the customer would normally be expected to engage in
    • The institution has no reasonable explanation after examination
    • The transaction is designed to evade BSA requirements

Examples:

  • Rapid movement of funds without economic purpose
  • Unusual transaction patterns inconsistent with business
  • Structuring to avoid reporting thresholds
  • Transactions with known high-risk jurisdictions without clear purpose

Aggregation Rules

Time Period for Aggregation:

  • Aggregate related transactions over any reasonable period
  • Consider patterns over days, weeks, or months
  • Document the aggregation methodology

Related Transactions:

  • Multiple transactions involving the same subject
  • Transactions that appear coordinated
  • Transactions with common characteristics or patterns
  • Transactions conducted to evade thresholds

SAR Filing Timeline and Deadlines

Standard Filing Deadlines

The timeline for filing a SAR depends on whether a subject can be identified:

Identified Subject: 30 Days

Initial Detection → Day 30: File SAR within 30 calendar days of initial detection of facts that constitute a basis for filing.

Example Timeline:

  • Day 0: Compliance officer identifies suspicious structuring pattern
  • Days 1-29: Investigation, documentation, narrative preparation
  • Day 30: SAR filed via FinCEN’s BSA E-Filing System

Unidentified Subject: 60 Days

Initial Detection → Day 30: No SAR required yet; conduct investigation to identify subject

Day 30 → Day 60: If unable to identify subject, file SAR within 60 calendar days of initial detection.

Example Timeline:

  • Day 0: Suspicious wire transfers detected, subject unknown
  • Days 1-30: Investigation attempts to identify subject
  • Day 30: Subject still unidentified, investigation continues
  • Days 31-60: Complete investigation and documentation
  • Day 60: SAR filed without identified subject

Critical Timeline Considerations

What is “Initial Detection”?

Initial detection occurs when the institution first identifies facts that may constitute a basis for filing a SAR, not when the investigation is complete.

Triggering Events:

  • Automated monitoring system generates alert
  • Employee reports suspicious activity
  • Discovery during account review
  • Receipt of law enforcement inquiry
  • Customer complaint reveals suspicious activity
  • External notification (e.g., from another institution)

Extensions and Delays

No Extensions Permitted: There is no provision for extending SAR filing deadlines. Institutions must file within the prescribed timeframe.

Mitigating Circumstances:

  • Document any delays beyond your control
  • File as soon as possible even if past deadline
  • Include explanation in internal documentation
  • Consider filing a late SAR rather than not filing at all

Weekends and Holidays

Filing deadlines fall on calendar days, not business days. If the deadline falls on a weekend or federal holiday, file by the next business day.

Continuing Activity Deadlines

For continuing suspicious activity previously reported:

  • Review activity every 90 calendar days
  • File a continuing activity SAR if activity continues
  • Reference the prior SAR(s) in the continuing activity report
  • See separate guidance on continuing activity SARs

FinCEN Form 111 Instructions

Overview of FinCEN SAR Form

The current SAR form is FinCEN Form 111 (revised April 2013). All SARs must be filed electronically through the BSA E-Filing System at https://bsaefiling.fincen.treas.gov.

Form Structure

The SAR form consists of five main parts:

Part I: Subject Information

Documents information about the person(s) or entity(ies) conducting the suspicious activity.

Key Fields:

  • Subject type (individual or entity)
  • Name, address, identification numbers
  • Date of birth (individuals)
  • Occupation or type of business
  • Account numbers involved
  • Relationship to institution

Important: You can report up to 999 subjects on a single SAR.

Part II: Suspicious Activity Information

Describes the suspicious activity itself.

Key Fields:

  • Date or date range of suspicious activity
  • Total dollar amount involved
  • Category of suspicious activity (from checkbox list)
  • Instruments involved (cash, wire, check, etc.)

Activity Categories Include:

  • BSA/Structuring/Money laundering
  • Check fraud
  • Commercial loan fraud
  • Consumer loan fraud
  • Credit card fraud
  • Counterfeit instruments
  • Defalcation/Embezzlement
  • Elder financial exploitation
  • Identity theft
  • Market manipulation
  • Mortgage fraud
  • Securities fraud
  • Terrorist financing
  • Wire transfer fraud
  • Other

Part III: Information About Financial Institution

Documents the filing institution’s information.

Key Fields:

  • Institution name and TIN
  • Type of financial institution
  • Primary federal regulator
  • Institution contact information
  • Filing institution’s role

Part IV: Filing Institution Contact Information

Provides point of contact for law enforcement.

Key Fields:

  • Contact office name
  • Contact phone number
  • Date SAR prepared
  • Alternate contact information (if applicable)

Part V: Suspicious Activity Information - Narrative

The detailed description of the suspicious activity. This is the most important section of the SAR.

Required Elements:

  • Who: Subject(s) involved
  • What: Type of suspicious activity
  • When: Timeframe of activity
  • Where: Location(s) of activity
  • Why: Why the activity is suspicious
  • How: Methods used to conduct activity

Electronic Filing Requirements

BSA E-Filing System:

File Formats:

  • Complete form online through BSA E-Filing
  • Upload batch files (for larger institutions)
  • Receive immediate acknowledgment
  • Download acknowledgment for records

Technical Requirements:

  • Secure internet connection
  • Compatible web browser
  • PDF capability for acknowledgments
  • Secure credential storage

Critical Data Elements

Mandatory vs. Critical vs. Optional Fields

Mandatory Fields: Required for all SARs (form will not accept submission without these)

Critical Fields: Not mandatory for submission but critical for law enforcement usefulness

Optional Fields: Provide if available and relevant

Essential Subject Information

For Individual Subjects

Critical Elements:

  • Full legal name (first, middle, last)
  • All known aliases or AKAs
  • Complete current address
  • Date of birth (DOB)
  • Taxpayer Identification Number (TIN) or Social Security Number (SSN)
  • Driver’s license or state ID number and issuing state
  • Passport number and country (if foreign national)
  • Phone numbers (all available)
  • Email addresses (all available)
  • Occupation or profession

Why These Matter: Each additional identifier significantly increases the likelihood law enforcement can:

  • Locate the subject
  • Link activity to other investigations
  • Establish patterns across institutions
  • Take appropriate enforcement action

For Entity Subjects

Critical Elements:

  • Complete legal name of entity
  • DBA (Doing Business As) names
  • Employer Identification Number (EIN)
  • Business address (physical location)
  • Mailing address (if different)
  • Type of business/industry
  • State and date of incorporation
  • Phone numbers and email addresses
  • Website address
  • Names of principals/owners/authorized signers

Account Information

Critical Account Details:

  • All account numbers involved
  • Account type (checking, savings, loan, etc.)
  • Date account opened
  • Date account closed (if applicable)
  • Branch location
  • Account purpose as stated by customer
  • Authorized signers and controllers
  • Beneficiaries (if applicable)

Transaction Information

Critical Transaction Details:

  • Specific dates of each significant transaction
  • Exact dollar amounts
  • Transaction types (deposit, withdrawal, wire, etc.)
  • Instruments used (cash, check, wire, ACH, etc.)
  • Source of funds (when known)
  • Destination of funds
  • Geographic locations involved
  • Counterparties to transactions
  • Reference numbers (wire references, check numbers, etc.)

Amount Fields

Key Amount Information:

  • Cumulative amount of all suspicious activity
  • Amounts by transaction type (if multiple types)
  • Known losses (actual losses to victims)
  • Recovery amounts (if any funds recovered)

Aggregation Considerations:

  • Aggregate related transactions over the suspicious activity period
  • Include all related deposits, withdrawals, and transfers
  • Document aggregation methodology in narrative

IP Addresses and Cyber Information

For cyber-related suspicious activity, critical elements include:

  • IP addresses (all involved)
  • Email addresses (all involved)
  • Device identifiers
  • Login credentials (usernames, not passwords)
  • Session identifiers
  • URL addresses
  • Cryptocurrency wallet addresses
  • Blockchain transaction identifiers

Narrative Writing Best Practices

The Purpose of the Narrative

The narrative is the most important part of the SAR. Law enforcement relies on well-written narratives to:

  • Understand the suspicious activity quickly
  • Determine investigation priority
  • Identify patterns across institutions
  • Link related cases
  • Establish probable cause for further action

Key Principles

1. Be Clear and Concise

  • Use plain English, avoid jargon
  • Write in active voice
  • Use short sentences and paragraphs
  • Organize information logically

2. Be Complete

  • Answer all the 5 W’s (Who, What, When, Where, Why)
  • Include all relevant facts
  • Provide sufficient detail for understanding
  • Include specific dates and amounts

3. Be Factual

  • State facts, not conclusions
  • Avoid speculation
  • Distinguish between facts and suspicions
  • Let the facts speak for themselves

4. Be Objective

  • Maintain professional tone
  • Avoid emotional language
  • Present information neutrally
  • Do not make accusations

Essential Narrative Components

Opening Summary (1-2 sentences)

Provide a concise overview of the suspicious activity.

Example: “This SAR is being filed to report suspected structuring activity conducted by John Doe. Between January 15, 2024, and March 10, 2024, Mr. Doe made 23 cash deposits, each under $10,000, totaling $227,500, in apparent attempt to evade Currency Transaction Report requirements.”

Subject Background

Describe the subject’s relationship with the institution.

Include:

  • Account opening date and circumstances
  • Stated purpose of account
  • Expected account activity based on customer profile
  • Subject’s occupation and income sources
  • Prior account history or alerts

Description of Suspicious Activity

Detail the specific transactions or patterns that are suspicious.

Include:

  • Chronological sequence of events
  • Specific transaction dates and amounts
  • Method of transactions (cash, wire, check, etc.)
  • Geographic locations
  • Counterparties involved
  • Pattern analysis

Why the Activity is Suspicious

Explain clearly why the activity raised suspicion.

Include:

  • Deviation from expected activity
  • Lack of apparent business purpose
  • Inconsistency with customer profile
  • Evasive behavior or structuring
  • Connections to known criminal activity
  • Red flag indicators present

Institution’s Actions

Describe steps taken by the institution.

Include:

  • When activity was detected
  • Investigation conducted
  • Additional monitoring implemented
  • Account actions taken (restrictions, closure)
  • Prior SARs filed on subject
  • Enhanced due diligence performed

Additional Relevant Information

Include any other pertinent facts.

May Include:

  • Law enforcement contacts
  • Media reports
  • Information from other sources
  • Related accounts or subjects
  • Ongoing monitoring plans

Writing Style Guidelines

DO:

  • Use specific dates and amounts
  • Provide transaction-level detail when relevant
  • Describe patterns clearly
  • Include subject statements when relevant
  • Note evasive behavior or red flags
  • Reference prior SARs by BSA ID number

DON’T:

  • Use vague terms like “various” or “multiple” without specifics
  • Include irrelevant personal information
  • Make legal conclusions (“This is money laundering”)
  • Include opinions about subject’s guilt
  • Disclose SAR filing to the subject
  • Include information about ongoing law enforcement investigations

Common Filing Errors

Critical Errors That Reduce SAR Value

1. Vague or Incomplete Narratives

Error: “Customer conducted suspicious activity on account.”

Why It’s Wrong: Provides no useful information for law enforcement.

Correct Approach: Provide specific dates, amounts, transaction types, and explanation of why activity is suspicious.

2. Missing Subject Identifiers

Error: Filing SAR with only name and partial address.

Why It’s Wrong: Law enforcement cannot locate or identify subject without sufficient identifiers.

Correct Approach: Include all available identifiers: DOB, SSN, TIN, driver’s license, phone, email, etc.

3. Incorrect Activity Date Range

Error: Using the investigation date range instead of the actual suspicious activity date range.

Why It’s Wrong: Misrepresents when the suspicious activity occurred, affecting statute of limitations and case development.

Correct Approach: Part II should reflect the date or date range when the suspicious activity actually occurred, not when it was discovered or investigated.

4. Wrong Dollar Amount

Error: Reporting only one transaction amount instead of cumulative suspicious activity amount.

Why It’s Wrong: Understates the scope and seriousness of the activity.

Correct Approach: Aggregate all related suspicious transactions during the activity period.

5. Selecting Wrong Activity Categories

Error: Checking every possible box or only generic categories.

Why It’s Wrong: Makes it difficult for law enforcement to prioritize and categorize the SAR.

Correct Approach: Select the most specific applicable categories that accurately describe the suspicious activity.

6. Continuing Activity Errors

Error: Filing a new initial SAR for ongoing previously reported activity instead of a continuing activity SAR.

Why It’s Wrong: Breaks the link between related SARs, making it harder for law enforcement to track patterns.

Correct Approach: Check “Continuing Activity” box and reference prior SAR BSA ID number(s).

7. Missing Critical Checkbox Indicators

Error: Not checking boxes like “Subject is insider” or “Law enforcement request.”

Why It’s Wrong: These flags help law enforcement prioritize review.

Correct Approach: Review all checkbox options carefully and select all that apply.

8. No Explanation of “Why” Suspicious

Error: Describing transactions without explaining why they’re suspicious.

Why It’s Wrong: Law enforcement cannot determine if activity warrants investigation.

Correct Approach: Clearly articulate the red flags, deviations from expected behavior, and reasons for suspicion.

Technical Filing Errors

1. Duplicate SARs

Issue: Filing multiple SARs on the same activity.

Solution: Before filing, check if activity has already been reported. If continuing, file a continuing activity SAR.

2. Wrong Filing Institution Type

Issue: Selecting incorrect institution type in Part III.

Solution: Verify your institution’s regulatory classification and select the correct type.

3. Invalid Date Ranges

Issue: End date before start date, or future dates.

Solution: Carefully verify date logic before submission.

4. Missing Contact Information

Issue: Incomplete or incorrect contact information in Part IV.

Solution: Provide a reliable point of contact who can respond to law enforcement inquiries.

5. Attachment Issues

Issue: Not attaching supporting documentation when available and relevant.

Solution: Use the attachment feature for relevant supporting documents (not excessive or irrelevant documents).

Quality Control Measures

Pre-Filing Checklist:

  • All critical subject identifiers included
  • Activity dates accurately reflect suspicious activity period
  • Total amount correctly calculated and aggregated
  • Appropriate activity categories selected
  • Narrative is complete, clear, and explains why suspicious
  • All relevant checkboxes marked
  • Contact information current and correct
  • Continuing activity properly indicated if applicable
  • Prior SAR BSA ID numbers referenced if applicable

Post-Filing Review:

  • Download and review acknowledgment
  • Save acknowledgment with case file
  • Verify BSA ID number recorded correctly
  • Confirm all required documentation maintained
  • Update case management system

Documentation Requirements

SAR Supporting Documentation

Financial institutions must maintain adequate supporting documentation for each SAR filed.

Required Documentation Elements

Transaction Records:

  • Account statements showing suspicious transactions
  • Deposit and withdrawal tickets
  • Wire transfer records and instructions
  • Check images (front and back)
  • ACH transaction records
  • Debit/credit card transaction records
  • Loan documentation (if applicable)

Customer Due Diligence Records:

  • Account opening documentation
  • Customer identification verification
  • Beneficial ownership information (for entities)
  • Expected activity documentation
  • Source of funds documentation
  • Customer statements about account purpose

Investigation Records:

  • Alert or detection record
  • Investigation notes and findings
  • Interview notes (if customer interviewed)
  • Enhanced due diligence performed
  • Database searches conducted
  • Internet/media searches
  • Prior history review

Decision Documentation:

  • Analysis of why activity is suspicious
  • Supervisor review and approval
  • Decision rationale
  • Escalation records
  • Quality review documentation

Filing Records:

  • Copy of filed SAR
  • BSA E-Filing acknowledgment
  • BSA ID number
  • Filing date
  • Preparer and reviewer identification

Retention Requirements

5-Year Retention Period: Under 31 CFR § 1020.320(d), financial institutions must maintain a copy of any SAR filed and the original or business record equivalent of supporting documentation for five years from the date of filing.

What Must Be Retained:

  • Complete copy of the SAR as filed
  • BSA E-Filing acknowledgment
  • All supporting documentation
  • Investigation work papers
  • Internal communications about the SAR
  • Management approval documentation

Retention Format:

  • Paper or electronic format acceptable
  • Must be readily accessible
  • Must be producible upon request by regulators or law enforcement
  • Recommend organized filing system by BSA ID number or subject

Segregating SAR Files

Confidentiality Requirements: SAR information is confidential and must be maintained securely with limited access.

Access Controls:

  • Restrict access to personnel with legitimate need to know
  • Implement role-based access for electronic records
  • Secure physical files in locked, access-controlled areas
  • Maintain access logs
  • Train staff on confidentiality requirements

Prohibited Access:

  • Subject of the SAR must never know a SAR was filed
  • Account officers or branch staff not involved in BSA compliance generally should not have access
  • Do not disclose SAR information in response to customer requests or discovery requests without legal consultation

Regulatory Access

Examiner Access: Regulators and law enforcement have the right to review SARs and supporting documentation during examinations and investigations.

Be Prepared to Provide:

  • Complete SAR files upon request
  • Ability to search and retrieve SARs by various criteria
  • Documentation of SAR decision-making process
  • Evidence of timely filing
  • Quality control documentation

Regulatory Citations

Primary Regulations

31 U.S.C. § 5318(g) - Suspicious Activity Reports Establishes the statutory authority for SAR requirements under the Bank Secrecy Act.

31 CFR § 1020.320 - Reports by banks SAR filing requirements for banks, savings associations, credit unions, and trust companies.

31 CFR § 1021.320 - Reports by casinos SAR filing requirements for casinos and card clubs.

31 CFR § 1022.320 - Reports by money services businesses SAR filing requirements for money transmitters, check cashers, currency dealers or exchangers, and issuers or sellers of money orders or stored value.

31 CFR § 1023.320 - Reports by brokers or dealers in securities SAR filing requirements for securities broker-dealers.

31 CFR § 1024.320 - Reports by mutual funds SAR filing requirements for mutual funds.

31 CFR § 1025.320 - Reports by insurance companies SAR filing requirements for insurance companies.

31 CFR § 1026.320 - Reports by futures commission merchants and introducing brokers SAR filing requirements for futures commission merchants and introducing brokers in commodities.

Key Guidance and Advisory Documents

FinCEN Guidance:

  • FIN-2012-G001: Filing Trends in Mortgage Loan Fraud SARs
  • FIN-2014-A003: Advisory to Financial Institutions on Filing SARs regarding Elder Financial Exploitation
  • FIN-2016-A005: Advisory on Email Compromise Fraud Schemes
  • FIN-2017-A006: Advisory on Human Trafficking and Related Activity
  • FIN-2019-A003: Advisory on Illicit Activity Involving Convertible Virtual Currency
  • FIN-2020-A006: Advisory on Identifying and Reporting Human Trafficking
  • FIN-2022-A003: Advisory on Cybercrime and Cyber-Enabled Crime Exploiting the Ongoing Coronavirus Disease 2019 (COVID-19) Pandemic

FFIEC BSA/AML Examination Manual: The Federal Financial Institutions Examination Council’s BSA/AML Examination Manual provides detailed guidance on SAR filing expectations and examination procedures.

Safe Harbor Protection

31 U.S.C. § 5318(g)(3) - Safe Harbor Provides immunity from civil liability for financial institutions and their employees who file SARs in good faith.

Key Points:

  • Protects institutions from civil liability
  • Applies to SARs filed with reasonable basis
  • Protects employees involved in SAR process
  • Does not protect against intentional false filing
  • Does not protect gross negligence

Confidentiality Requirements

31 U.S.C. § 5318(g)(2) - Confidentiality of SARs Prohibits institutions and their employees from notifying any person involved in the transaction that a SAR has been filed.

31 CFR § 1020.320(e) - Confidentiality of SARs Implements the confidentiality requirements and specifies limited exceptions for information sharing.

Violations:

  • Civil penalties up to $100,000 per violation
  • Criminal penalties for willful violations
  • Removal or prohibition orders against individuals
  • Regulatory enforcement actions

Additional Resources

FinCEN:

Regulators:

  • Federal Financial Institutions Examination Council (FFIEC) BSA/AML Examination Manual
  • Federal Reserve BSA/AML resources
  • OCC Bank Secrecy Act resources
  • FDIC BSA/AML resources
  • NCUA BSA resources

Training:

  • ACAMS (Association of Certified Anti-Money Laundering Specialists)
  • ABA (American Bankers Association) BSA/AML training
  • Regional AML working groups

Document Version: 2.0 Last Updated: March 15, 2024 Next Review Date: March 15, 2025

This guidance is for informational purposes only and does not constitute legal advice. Financial institutions should consult with legal counsel and compliance professionals to ensure their SAR filing procedures comply with all applicable laws and regulations.