SAR Thresholds and Triggers: When SARs Are Required
SAR Thresholds and Triggers: When SARs Are Required
Table of Contents
- Overview of SAR Thresholds
- The Four Primary Filing Scenarios
- Understanding the $5,000 Threshold
- Understanding the $25,000 Threshold
- Aggregation Requirements
- No Minimum Thresholds for Certain Violations
- Timeline Requirements
- Continuing Activity Provisions
- Regulatory Expectations and Examination Standards
- Special Considerations by Institution Type
- Practical Examples
- Common Questions and Misconceptions
Overview of SAR Thresholds
Understanding when a Suspicious Activity Report (SAR) must be filed is fundamental to BSA/AML compliance. While many compliance professionals focus on dollar thresholds, SAR filing requirements are more nuanced and involve multiple factors including the type of violation, whether a subject can be identified, and the nature of the suspicious activity.
Key Principle
Not all suspicious activity requires a SAR filing. The Bank Secrecy Act establishes specific thresholds and conditions that must be met before a SAR filing is mandatory. However, institutions may file SARs below these thresholds when appropriate as part of a comprehensive AML program.
Regulatory Authority
SAR thresholds are established in:
- 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
While specific requirements vary slightly by institution type, the core threshold concepts remain consistent across all financial institutions.
The Four Primary Filing Scenarios
Financial institutions must file a SAR when they detect any of the following four scenarios. Each scenario has different threshold requirements and conditions.
Scenario 1: Insider Abuse Involving Any Amount
Filing Requirement: File a SAR when the financial institution detects any known or suspected federal criminal violation, or pattern of criminal violations, committed or attempted against the financial institution or involving a transaction or transactions conducted through the financial institution, where the institution believes it was either:
- Committed by an insider, OR
- Involved an insider as an accomplice
Dollar Threshold: NONE - Any amount triggers filing requirement
Identification Requirement: Subject must be identified (the insider)
Who Qualifies as an “Insider”?
“Insider” includes any of the following affiliated with the financial institution:
- Director
- Officer
- Employee
- Agent
- Other institution-affiliated party
This broad definition encompasses:
- Board members
- Executive management
- Branch staff
- Compliance personnel
- IT staff
- Third-party agents acting on behalf of the institution
- Independent contractors performing institution functions
- Consultants with access to institution systems or information
Why No Dollar Threshold?
Insider abuse poses unique risks to financial institutions:
- Insiders have privileged access to accounts, systems, and confidential information
- Insider fraud can undermine institutional integrity
- Regulatory expectation of zero tolerance for insider misconduct
- Insider involvement in customer crimes facilitates broader criminal activity
Examples of Insider Abuse Requiring SAR (Any Amount)
Example 1 - Employee Embezzlement: A teller steals $500 from the cash drawer. SAR required (no dollar threshold).
Example 2 - Officer Facilitating Money Laundering: A loan officer knowingly processes fictitious loans to layer proceeds for a money laundering customer involving $3,000. SAR required (no dollar threshold).
Example 3 - IT Employee Data Theft: An IT employee steals customer account information for 25 customers and sells it to identity thieves for $1,000. SAR required (no dollar threshold for insider involvement; also requires SAR for identity theft victims if losses exceed thresholds).
Example 4 - Director Conflict of Interest: A board member approves a $4,000 loan to a family member without disclosure, violating conflict of interest policies. SAR required (no dollar threshold; violation of fiduciary duty by insider).
Scenario 2: Federal Criminal Violation Aggregating $5,000 or More (Subject Identified)
Filing Requirement: File a SAR when the institution knows, suspects, or has reason to suspect that a transaction or pattern of transactions:
- Involves funds derived from illegal activity, OR
- Is designed to evade BSA requirements, OR
- Has no business or apparent lawful purpose and the institution knows of no reasonable explanation after examining the available facts, including background and purpose of the transaction
Dollar Threshold: $5,000 (in aggregate)
Identification Requirement: Subject must be identified
Transaction Involvement: Transaction or pattern must involve or aggregate at least $5,000
What Constitutes “Identification” of Subject?
A subject is “identified” when the institution can provide:
- A name (even if possibly false)
- Some additional identifying information (address, date of birth, SSN, account number, physical description, etc.)
Note: The subject does not need to be identified with certainty. If you have a name and some additional information, the subject is “identified” for threshold purposes, even if the name might be an alias.
Examples Requiring SAR Under $5,000 Threshold (Subject Identified)
Example 1 - Structuring: Customer John Doe makes three cash deposits of $3,500, $3,200, and $2,800 (total $9,500) over five days, each deliberately under $10,000 to avoid CTR filing. SAR required (exceeds $5,000 threshold; structuring to evade BSA requirements; subject identified).
Example 2 - Check Fraud: Customer Jane Smith deposits five counterfeit checks totaling $7,200. SAR required (exceeds $5,000 threshold; illegal activity; subject identified).
Example 3 - No Apparent Lawful Purpose: Customer Robert Johnson receives wire transfers totaling $12,000 from multiple foreign senders, with no apparent business purpose and unable to explain the source or purpose of funds. SAR required (exceeds $5,000 threshold; no apparent lawful purpose; subject identified).
Example 4 - Identity Theft: Customer account is taken over by identity thief who steals $6,500 through unauthorized wire transfers. SAR required (exceeds $5,000 threshold; illegal activity; subject can be identified by account and transaction details even if true identity unknown).
Scenario 3: Federal Criminal Violation Aggregating $25,000 or More (Subject Unidentified)
Filing Requirement: File a SAR when the institution detects transactions aggregating $25,000 or more involving known or suspected federal criminal violations, and the institution cannot identify a subject involved in the suspicious activity.
Dollar Threshold: $25,000 (in aggregate)
Identification Requirement: Subject cannot be identified
Why Higher Threshold When Subject Unknown?
The higher threshold for unidentified subjects balances:
- Law enforcement’s limited ability to investigate without subject identification
- Institutional burden of investigating and filing SARs on unidentified activity
- Focus resources on cases where subject identification enables investigation
However, institutions should make reasonable efforts to identify subjects before applying the higher threshold.
Examples Requiring SAR Under $25,000 Threshold (Subject Unidentified)
Example 1 - Anonymous Wire Transfers: Account receives five anonymous wire transfers from overseas sources totaling $32,000. Sender information is generic or false, and institution cannot identify who is actually sending the funds. SAR required (exceeds $25,000 threshold; illegal activity suspected; subject cannot be identified despite reasonable efforts).
Example 2 - ATM Fraud by Unknown Perpetrator: Institution’s ATM is compromised with skimming device, resulting in fraudulent withdrawals totaling $28,000 by various unknown persons using cloned cards. SAR required (exceeds $25,000 threshold; illegal activity; subjects cannot be identified).
Example 3 - Cyber Attack: Institution suffers cyber attack resulting in unauthorized transactions totaling $50,000. Despite investigation, perpetrators cannot be identified. SAR required (exceeds $25,000 threshold; illegal activity; subjects unidentified).
Scenario 4: Transactions Aggregating $5,000 or More - BSA/AML Violations or Suspicious Transactions
Filing Requirement: File a SAR when the institution knows, suspects, or has reason to suspect that a transaction or pattern of transactions aggregating $5,000 or more:
- Involves funds derived from illegal activity, OR
- Is designed to evade any BSA requirement, OR
- Has no business or apparent lawful purpose, OR
- Involves use of the financial institution to facilitate criminal activity
Dollar Threshold: $5,000 (in aggregate)
Identification Requirement: Subject should be identified if possible (use $25,000 threshold if subject cannot be identified)
This is the “catch-all” category for suspicious transactions that don’t fit neatly into other categories but exceed the $5,000 threshold.
Understanding the $5,000 Threshold
How to Calculate the $5,000 Threshold
The $5,000 threshold is based on the aggregate of all suspicious transactions or activity related to the same subject, violation, or pattern.
Aggregation Period
Key Principle: There is no fixed time period for aggregation. Aggregate transactions over any reasonable period during which the suspicious activity occurred.
Factors to Consider:
- Nature of the activity
- Pattern of transactions
- Relationship between transactions
- Logical connection to the same scheme or subject
Common Aggregation Periods:
- Same day
- Multiple days or weeks (for patterns)
- Duration of scheme or pattern
- Account lifecycle (for account takeover or fraud)
What to Aggregate
Aggregate transactions that are:
- Part of the same pattern or scheme
- Conducted by the same subject
- Related to the same suspicious activity
- Connected by common characteristics
Do NOT Aggregate:
- Unrelated transactions
- Different types of suspicious activity (unless connected)
- Activity involving different unrelated subjects
Examples of $5,000 Threshold Calculations
Example 1 - Clear Aggregation: Customer makes four cash deposits: $1,500 (Monday), $2,000 (Wednesday), $1,800 (Friday), $2,200 (following Monday). Total = $7,500. All deposits are part of the same structuring pattern. Aggregate = $7,500. SAR required (exceeds $5,000 threshold).
Example 2 - Aggregation Over Longer Period: Customer conducts check kiting scheme involving 12 checks deposited and withdrawn over three weeks. Total value of kite = $18,000. All checks are part of the same kiting scheme. Aggregate = $18,000. SAR required (exceeds $5,000 threshold).
Example 3 - Partial Aggregation: Customer makes three suspicious wire transfers: $2,000 to offshore account (March 1), $1,800 to different offshore account (March 5), $2,500 to third offshore account (March 10). All three appear to be part of money laundering pattern. Total = $6,300. Aggregate = $6,300. SAR required (exceeds $5,000 threshold; part of same pattern).
Example 4 - Do NOT Aggregate: Customer makes one $3,000 cash deposit that appears to be structuring (March 1) and later commits check fraud involving $2,500 check (April 15). These are two separate types of suspicious activity not connected to a common scheme. Do not aggregate. Each activity is below $5,000 individually. No SAR required for either (unless insider involvement or other threshold exception applies).
However, if investigation reveals both activities are part of a larger scheme, aggregation may be appropriate. Use professional judgment based on facts.
When Activity Falls Below $5,000
If suspicious activity is detected but the total aggregate is below $5,000, a SAR is generally not required unless:
- Insider involvement (no dollar threshold)
- Certain violations with no minimum threshold (see section below)
- Institution chooses to file voluntarily as part of risk-based approach
Voluntary Filing: Institutions may file SARs for activity below thresholds when it serves AML program objectives, risk management, or law enforcement support goals. However, voluntary filings should be based on risk assessment, not routine practice for all sub-threshold activity.
Understanding the $25,000 Threshold
When the $25,000 Threshold Applies
The higher $25,000 threshold applies only when:
- There is suspected federal criminal activity, AND
- The institution cannot identify a subject involved in the activity
Reasonable Efforts to Identify Subject
Before applying the $25,000 threshold, institutions must make reasonable efforts to identify a subject.
Reasonable Efforts Include:
- Reviewing transaction records for customer information
- Checking account records and customer identification documents
- Analyzing IP addresses or electronic access logs
- Reviewing surveillance footage (if available and relevant)
- Conducting database searches
- Reviewing related accounts or transactions
- Interviewing staff who interacted with the subject
Document Your Efforts: Maintain records of steps taken to identify the subject. If a SAR is filed using the $25,000 threshold, document in the narrative why the subject could not be identified despite reasonable efforts.
Subject Identification: Certainty Not Required
A subject is considered “identified” even if:
- The name provided may be false
- The subject cannot be located
- The true identity is uncertain
- Only partial identifying information is available
If you have a name and some additional information (address, DOB, account number, etc.), the subject is “identified” for threshold purposes, even if you suspect the information may be false or incomplete.
Examples: $25,000 Threshold Analysis
Example 1 - Subject Cannot Be Identified: Institution’s ATM network is compromised by unknown hackers who steal $30,000 through unauthorized transactions. Despite investigation, reviewing IP logs, and working with law enforcement, the perpetrators cannot be identified. Use $25,000 threshold. SAR required (exceeds $25,000; subject unidentified despite reasonable efforts).
Example 2 - Subject Is Identified (Even with False Information): Account opened with likely false identification documents shows suspicious wire transfer activity totaling $18,000. While the institution suspects the identification is fraudulent, there is a name, address, DOB, and SSN on file. Use $5,000 threshold, not $25,000 threshold. Subject is “identified” even if information is false. SAR required (exceeds $5,000 threshold; subject identified).
Example 3 - Reasonable Efforts Lead to Identification: Account receives $22,000 in suspicious deposits. Initial review shows limited customer information, but investigation reveals IP address used for online banking, security camera footage of deposits, and vehicle license plate. These details allow subject identification. Use $5,000 threshold. Subject has been identified through reasonable investigative efforts. SAR required (exceeds $5,000 threshold; subject identified).
Aggregation Requirements
Principles of Aggregation
Aggregation is the process of combining related transactions to determine if a SAR threshold is met.
What is a “Transaction”?
For SAR purposes, a “transaction” includes:
- Deposits (cash, check, wire, ACH, mobile deposit, etc.)
- Withdrawals (cash, check, wire, ACH, ATM, etc.)
- Transfers (between accounts, wire transfers, etc.)
- Payments (loan payments, credit card payments, etc.)
- Account openings or closings (when relevant to the suspicious activity)
- Any other financial service or product activity
Aggregation Rules
Rule 1: Aggregate Related Suspicious Transactions Combine all transactions that are part of the same pattern, scheme, or suspicious activity.
Rule 2: Same Subject Across Multiple Accounts Aggregate activity by the same subject across multiple accounts when part of the same suspicious activity.
Rule 3: No Fixed Time Period Aggregate over whatever time period the suspicious activity occurred. This could be:
- Single day
- Multiple days or weeks
- Several months
- Duration of pattern or scheme
Rule 4: Use Professional Judgment Aggregation requires analysis of whether transactions are truly related as part of a common suspicious activity or pattern.
Aggregation Scenarios
Scenario 1: Structuring Pattern
Customer makes the following deposits at various branches:
- Monday: $9,000 cash at Branch A
- Tuesday: $8,500 cash at Branch B
- Thursday: $9,200 cash at Branch C
- Friday: $9,800 cash at Branch D
Analysis: All deposits are part of a single structuring pattern (sub-$10,000 deposits to avoid CTR). Aggregate all transactions: $36,500. SAR required.
Scenario 2: Multiple Account Structuring
Customer has two accounts and makes the following deposits:
- Account 1: $6,000 cash (Monday)
- Account 2: $5,500 cash (Monday)
- Account 1: $7,000 cash (Wednesday)
- Account 2: $6,200 cash (Wednesday)
Analysis: Activity across both accounts appears designed to structure deposits below $10,000 per account. Aggregate across both accounts: $24,700. SAR required.
Scenario 3: Fraud Scheme Over Time
Customer engages in check fraud:
- Week 1: Deposits two counterfeit checks totaling $3,200
- Week 2: Deposits one counterfeit check for $1,800
- Week 4: Deposits three counterfeit checks totaling $4,500
Analysis: All checks are part of same check fraud scheme by same subject. Aggregate over entire fraud period: $9,500. SAR required.
Scenario 4: Separate Unrelated Activity - Do NOT Aggregate
Customer conducts the following:
- January: Possible structuring with cash deposits totaling $4,000
- April: Separate check fraud incident involving $3,500
Analysis: These are two separate, unrelated suspicious activities separated by time and type. Do not aggregate. Each incident is below $5,000 individually. No SAR required (unless subsequent investigation reveals a connection, making aggregation appropriate).
Aggregation Across Multiple Subjects
General Rule: Do not aggregate transactions by different unrelated subjects.
Exception: Aggregate when multiple subjects are working together in a common scheme.
Example - Aggregate Multiple Subjects: Three customers (Smith, Jones, and Williams) are working together in a conspiracy to structure cash deposits to avoid CTRs:
- Smith deposits $9,000 on Monday
- Jones deposits $8,500 on Tuesday
- Williams deposits $9,300 on Thursday
- All deposited into accounts that rapidly wire funds to the same offshore entity
Analysis: The three customers are working in concert as part of a single money laundering conspiracy. Aggregate all transactions: $26,800. File one SAR listing all three as subjects.
Aggregation Documentation
Best Practice: Document the aggregation methodology in:
- Internal SAR review and decision documentation
- SAR narrative (briefly explain the aggregation)
- Supporting documentation
Example Narrative Statement: “Between February 1 and February 28, 2024, the customer made 12 cash deposits totaling $112,450. These deposits are aggregated as they are all part of the same pattern of structuring to evade CTR requirements.”
No Minimum Thresholds for Certain Violations
While most SAR filings are subject to the $5,000/$25,000 thresholds, certain violations have no dollar threshold requirement. For these violations, a SAR must be filed regardless of the amount involved.
Violations With No Dollar Threshold
1. Insider Abuse (Any Amount)
As discussed above, any insider involvement in criminal activity requires SAR filing regardless of amount.
Examples:
- Teller embezzles $200
- Officer falsifies $500 transaction
- Director misuses $100 in customer funds
2. Structuring and BSA Evasion (Any Amount)
Regulatory Position: While regulations state a $5,000 threshold for SARs, FinCEN and regulators expect institutions to file SARs for structuring and BSA evasion regardless of the amount when the deliberate evasion is clear.
Rationale:
- Structuring itself (31 U.S.C. § 5324) is a federal crime regardless of amount
- BSA evasion undermines the reporting system
- Regulatory expectations established in examination guidance
Example: Customer makes two cash deposits of $4,000 each on the same day at different branches, clearly attempting to avoid the $10,000 CTR threshold. Total = $8,000. While this exceeds the $5,000 threshold anyway, even if it were $4,500 total, examiners would expect a SAR given the clear evasion attempt.
Best Practice: File SARs for clear, deliberate structuring even if below $5,000 when the evasive intent is obvious.
3. Terrorist Financing (Any Amount)
Regulatory Expectation: Terrorist financing should be reported regardless of amount.
Rationale:
- National security priority
- Even small amounts can finance terrorist operations
- 18 U.S.C. § 2339A and § 2339B criminalize material support to terrorism regardless of amount
- FinCEN guidance emphasizes reporting all suspected terrorist financing
Example: Customer wires $1,200 to an entity on OFAC’s Specially Designated Nationals (SDN) list. SAR required immediately regardless of amount.
4. Violations of OFAC Sanctions (Any Amount)
Regulatory Expectation: Transactions involving OFAC sanctions violations should be reported regardless of amount.
Example: Wire transfer of $500 to an individual in a sanctioned country or to a blocked entity. SAR required regardless of amount.
5. Elder Financial Exploitation
Regulatory Emphasis: While technically subject to dollar thresholds, FinCEN guidance (FIN-2014-A003 and updates) strongly encourages filing SARs for elder financial exploitation even when below thresholds, given the vulnerability of victims and the prevalence of this crime.
Best Practice: Consider filing SARs for elder exploitation even below $5,000 when the exploitation is clear and the victim is vulnerable.
6. Human Trafficking
Regulatory Emphasis: FinCEN guidance (FIN-2020-A006) encourages reporting suspected human trafficking regardless of amount due to the severity of the crime and national priority.
Best Practice: File SARs for suspected human trafficking activity regardless of dollar amounts involved.
Risk-Based Approach to Below-Threshold Filing
Institutions should adopt a risk-based approach to filing SARs for activity below thresholds:
Factors to Consider:
- Severity and type of suspected crime
- Vulnerability of victims
- National security implications
- Law enforcement intelligence value
- Pattern of activity (even if individual transactions are small)
- Regulatory emphasis areas (terrorist financing, human trafficking, elder exploitation, etc.)
Document Your Risk-Based Decisions: When choosing to file (or not file) below-threshold SARs, document the risk-based rationale in compliance files.
Timeline Requirements
SAR filing timelines are strict and non-negotiable. Understanding when the clock starts and when filing is due is critical to compliance.
The 30-Day Rule (Subject Identified)
Requirement: File SAR within 30 calendar days after the date of initial detection of facts that may constitute a basis for filing a SAR.
Applies When: A subject can be identified
What is “Initial Detection”?
“Initial detection” is the date when the institution first becomes aware of facts that may constitute a basis for filing a SAR, not when the investigation is complete.
Triggering Events for Initial Detection:
- Automated monitoring system generates alert
- Employee reports suspicious activity to compliance
- Discovery during account review or audit
- Customer complaint reveals suspicious activity
- Law enforcement inquiry provides information suggesting suspicious activity
- Receipt of notification from another financial institution
- Media report identifies customer in suspicious activity
Important: Initial detection is when the institution has facts suggesting a possible basis for a SAR, not when the institution has conclusively determined a SAR will be filed.
The 30-Day Timeline
Day 0: Initial detection of facts that may constitute basis for filing
Days 1-30: Investigation, analysis, documentation, narrative preparation
Day 30 (deadline): SAR must be filed
Calendar Days: The 30 days are calendar days, not business days. If Day 30 falls on a weekend or federal holiday, the deadline extends to the next business day.
The 60-Day Rule (Subject Unidentified)
Requirement: If unable to identify a subject, file SAR within 60 calendar days after the date of initial detection.
Applies When: Subject cannot be identified despite reasonable efforts
The 60-Day Timeline
Day 0: Initial detection of facts that may constitute basis for filing
Days 1-30: Investigation to identify subject; no SAR required yet
Day 30: If subject still unidentified, continue investigation
Days 31-60: Continue efforts to identify subject; prepare SAR with unidentified subject
Day 60 (deadline): SAR must be filed even without identified subject (if activity exceeds $25,000 threshold)
No Extensions
Critical Rule: There are no provisions for extensions of SAR filing deadlines. Institutions must file within the prescribed timeframe.
If Deadline Is Missed:
- File the SAR as soon as possible (late filing is better than no filing)
- Document internally why the deadline was missed
- Include explanation in internal documentation (not in the SAR narrative)
- Implement corrective actions to prevent future late filings
- Be prepared to explain to examiners
Timeline Best Practices
Best Practice 1: Start Early Begin investigation immediately upon detection. Waiting until Day 20 or Day 50 leaves insufficient time for thorough investigation and quality narrative preparation.
Best Practice 2: Set Internal Deadlines Establish internal deadlines earlier than regulatory deadlines (e.g., Day 25 for 30-day deadline, Day 50 for 60-day deadline) to allow for quality review and unexpected delays.
Best Practice 3: Track Timelines Use case management system to track:
- Date of initial detection
- Filing deadline date
- Current status
- Days remaining
Best Practice 4: Escalation Procedures Implement escalation procedures when investigations approach deadlines without resolution. Designate authority to make filing decisions when time is short.
Best Practice 5: Document Initial Detection Clearly document the date of initial detection in case files. This establishes the filing deadline and demonstrates timely compliance.
Continuing Activity Provisions
When suspicious activity previously reported in a SAR continues, special rules apply for ongoing reporting.
When to File Continuing Activity SARs
File a continuing activity SAR when:
- The suspicious activity was previously reported in a SAR, AND
- The same or similar suspicious activity by the same subject continues, AND
- At least 90 calendar days have passed since the prior SAR
The 90-Day Review Cycle
Requirement: After filing an initial SAR, review the activity every 90 calendar days to determine if the suspicious activity is continuing.
90-Day Review Process:
- Day 90 after prior SAR: Review account/subject activity
- Determine: Has the suspicious activity continued?
- If Yes: File continuing activity SAR
- If No: Continue monitoring; reassess in another 90 days or when appropriate
Filing Continuing Activity SARs
How to File:
- Check the “Continuing Activity” box in Part II of the SAR form
- Reference the prior SAR(s) by BSA Identification Number
- Describe the continued suspicious activity in the narrative
- Include dates of continued activity
- Note total cumulative amount (original SAR + new activity)
Narrative Content:
- Reference prior SAR(s) by BSA ID and date
- Briefly summarize previously reported activity
- Describe the continuing activity since the last SAR
- Provide specific transactions/dates for the continuing period
- Explain why activity remains suspicious
- Note any changes in pattern or new developments
- Describe any account actions taken
Example Continuing Activity Narrative Opening: “This is a continuing activity SAR related to previously filed SAR (BSA ID: XXXXXXXXXX-XXXX-1, filed 01/15/2024). The prior SAR reported suspected structuring activity by John Doe totaling $127,000 between October 1, 2023, and January 10, 2024. The structuring activity has continued. Between January 11, 2024, and April 10, 2024, Mr. Doe made an additional 18 cash deposits totaling $165,000, each deliberately structured below $10,000…”
When to Stop Filing Continuing Activity SARs
Stop filing continuing activity SARs when:
- The suspicious activity has ceased
- The account is closed and no further activity is occurring
- The subject is no longer conducting transactions with the institution
- Law enforcement has specifically requested no further SARs
Continue Monitoring: Even after the suspicious activity stops, maintain enhanced monitoring of the subject/account for a reasonable period to detect resumption of activity.
Aggregating Amounts in Continuing Activity SARs
Two Approaches:
Approach 1 - New Activity Only: Report only the new activity since the last SAR. This is acceptable and commonly used.
Approach 2 - Cumulative Total: Report the cumulative total including all prior SARs. This gives law enforcement the complete picture in one SAR.
Best Practice: Use the new activity amount in Part II, but state the cumulative total in the narrative for context.
Example: “Part II Total: $165,000 (new activity since last SAR) Narrative Statement: Combined with the $127,000 reported in the January 15, 2024 SAR, the total cumulative suspicious activity is $292,000.”
Detailed guidance on continuing activity SARs is provided in the separate “Continuing Activity SARs” resource document.
Regulatory Expectations and Examination Standards
What Examiners Look For
During BSA/AML examinations, regulators assess whether institutions are:
- Timely identifying suspicious activity
- Appropriately applying SAR thresholds
- Filing SARs when required
- Maintaining adequate documentation supporting SAR decisions
- Not over- or under-filing SARs
Common Examination Findings
Finding 1: Failure to File Required SARs
Examiners identify suspicious activity that met thresholds but was not reported.
Causes:
- Inadequate monitoring systems
- Poor understanding of thresholds
- Incomplete investigations
- Failure to aggregate related transactions
- Not recognizing red flags
Prevention: Robust monitoring, training, and quality assurance processes
Finding 2: Late SAR Filings
SARs filed after the 30-day or 60-day deadline.
Causes:
- Delayed investigation start
- Insufficient resources
- Poor case management
- Lack of timeline tracking
Prevention: Immediate investigation upon detection, internal deadlines, case tracking systems
Finding 3: Incorrect Threshold Application
Misapplication of $5,000 vs. $25,000 thresholds or failure to recognize no-threshold situations.
Causes:
- Insufficient training
- Misunderstanding of “identified subject”
- Inadequate subject identification efforts
Prevention: Clear policies, training, documented decision-making
Finding 4: Improper Aggregation
Failure to aggregate related transactions or improper aggregation of unrelated activity.
Causes:
- Lack of clear aggregation policies
- Inadequate pattern analysis
- Siloed account reviews (not looking at customer holistically)
Prevention: Clear aggregation policies, training, customer-level analysis
Finding 5: Inadequate Documentation
Insufficient documentation of SAR decisions and investigations.
Causes:
- Lack of documentation standards
- Time pressures
- Inadequate case management systems
Prevention: Documentation standards, templates, quality review
Examiner Expectations by Area
Transaction Monitoring
- Monitoring systems calibrated to detect activity approaching and exceeding thresholds
- Aggregation logic in automated systems
- Timely alert review and investigation
SAR Decision-Making
- Clear, documented decision-making process
- Threshold analysis in case documentation
- Aggregation methodology documented
- Supervisor review and approval
Timeliness
- Initial detection date clearly documented
- Timeline tracking for all cases
- Adherence to 30-day/60-day deadlines
- Escalation procedures for approaching deadlines
Quality
- Complete and accurate SAR forms
- Detailed narratives explaining activity
- All subjects identified when possible
- Appropriate activity categories selected
Special Considerations by Institution Type
While threshold concepts are generally consistent across institution types, there are some differences and special considerations.
Banks and Credit Unions (31 CFR § 1020.320)
Standard Thresholds Apply:
- $5,000 (subject identified)
- $25,000 (subject unidentified)
- No dollar threshold for insider abuse
Special Considerations:
- Wide variety of products and services increases complexity
- Must monitor deposits, withdrawals, wires, ACH, loans, safe deposit boxes, etc.
- Enhanced scrutiny on cash-intensive businesses
- Complex aggregation across multiple accounts and products
Money Services Businesses (31 CFR § 1022.320)
Standard Thresholds Apply:
- $2,000 for money transmitters (lower than other institution types)
- $5,000 for currency dealers/exchangers
- No dollar threshold for insider abuse
Special Considerations:
- $2,000 threshold for money transmitters (lower due to transaction volume and risk profile)
- High volume of cash transactions requires robust monitoring
- Cross-border transactions common (wire transfers, remittances)
- Structuring particularly common in this sector
Key Difference: The $2,000 threshold for money transmitters is the lowest SAR threshold across all financial institution types, reflecting the higher risk profile and regulatory expectations for this sector.
Securities Broker-Dealers (31 CFR § 1023.320)
Standard Thresholds Apply:
- $5,000 (subject identified)
- $25,000 (subject unidentified)
- No dollar threshold for insider abuse or market manipulation
Special Considerations:
- Must report market manipulation regardless of amount
- Insider trading red flags (often no direct dollar threshold)
- Microcap fraud schemes
- Complex products (options, derivatives) require specialized monitoring
- Focus on trading patterns, not just account transactions
Casinos (31 CFR § 1021.320)
Standard Thresholds Apply:
- $5,000 (subject identified)
- $25,000 (subject unidentified)
- No dollar threshold for insider abuse
Special Considerations:
- Must aggregate gaming and non-gaming transactions
- Chip purchases, redemptions, cage transactions
- Slot machine activity
- Marker (credit) activity
- Suspicious gaming patterns (minimal play, chip passing, etc.)
Insurance Companies (31 CFR § 1025.320)
Standard Thresholds Apply:
- $5,000 (subject identified)
- $25,000 (subject unidentified)
- No dollar threshold for insider abuse
Special Considerations:
- Focus on products with cash value (annuities, life insurance)
- Rapid liquidation of policies
- Premium financing structures
- Beneficiary changes
- Borrowing against cash value
Mutual Funds (31 CFR § 1024.320)
Standard Thresholds Apply:
- $5,000 (subject identified)
- $25,000 (subject unidentified)
- No dollar threshold for insider abuse
Special Considerations:
- Late trading
- Market timing schemes
- Rapid trading patterns
- Complex ownership structures
- Use of fund shares to layer illicit proceeds
Practical Examples
Example 1: Structuring - Threshold Met
Scenario: Customer Sarah Johnson makes the following cash deposits at various branches over two weeks:
- Day 1: $9,500 at Branch A
- Day 3: $9,000 at Branch B
- Day 7: $9,800 at Branch C
- Day 10: $8,900 at Branch D
- Day 14: $9,200 at Branch A
Analysis:
- Total aggregate: $46,400
- Pattern: All deposits just under $10,000 CTR threshold
- Subject identified: Yes (Sarah Johnson, account holder)
- Type of violation: Structuring to evade BSA requirements (31 U.S.C. § 5324)
- Applicable threshold: $5,000 (subject identified)
Conclusion: SAR Required
- Exceeds $5,000 threshold
- Clear structuring pattern
- Subject identified
- File within 30 days of initial detection
Example 2: Check Fraud - Below Threshold
Scenario: Customer deposits two counterfeit checks:
- Check 1: $2,000 (deposited March 1)
- Check 2: $1,800 (deposited March 8) Both checks were returned as counterfeit.
Analysis:
- Total aggregate: $3,800
- Subject identified: Yes (customer who deposited)
- Type of violation: Check fraud (illegal activity)
- Applicable threshold: $5,000 (subject identified)
Conclusion: SAR Not Required (Below Threshold)
- Activity totals $3,800, below $5,000 threshold
- No insider involvement
- Not a no-threshold violation type
However: Institution may choose to file voluntarily given fraud occurred, especially if pattern of similar activity by same customer or if amount approaches $5,000. Use risk-based judgment.
Example 3: Wire Fraud - Threshold Met, Subject Unidentified
Scenario: Business customer receives fraudulent wire transfer for $30,000 based on Business Email Compromise (BEC) scheme. Wire comes from domestic account in another customer’s name (victim’s account was compromised). The actual perpetrator’s identity is unknown. Despite investigation, perpetrator cannot be identified.
Analysis:
- Total amount: $30,000
- Subject identified: No (actual perpetrator unknown; the sending account holder is a victim, not the subject)
- Type of violation: Wire fraud, BEC fraud
- Applicable threshold: $25,000 (subject unidentified)
Conclusion: SAR Required
- Exceeds $25,000 threshold
- Subject cannot be identified despite reasonable efforts
- File within 60 days of initial detection
- Report on the receiving account customer; note in narrative that actual perpetrator unknown
Also: The institution holding the victim’s account (the sending bank) should also file a SAR on the unauthorized transaction from their customer’s account.
Example 4: Insider Embezzlement - No Dollar Threshold
Scenario: Branch manager Michael Davis steals $800 from the vault by manipulating cash count records.
Analysis:
- Amount: $800
- Subject identified: Yes (Michael Davis, branch manager)
- Type of violation: Embezzlement by insider
- Applicable threshold: None (insider involvement)
Conclusion: SAR Required
- Insider involvement = no dollar threshold
- File within 30 days of initial detection
- Report any amount of insider abuse
Example 5: Elder Exploitation - Risk-Based Filing
Scenario: Customer Mary Thompson, age 82, has her account taken over by a caregiver who makes unauthorized withdrawals totaling $3,200 over two weeks.
Analysis:
- Amount: $3,200
- Subject identified: Yes (caregiver)
- Type of violation: Elder financial exploitation, theft
- Applicable threshold: Technically $5,000 (subject identified)
- Below $5,000: $3,200 < $5,000
Conclusion: SAR Not Technically Required (Below Threshold), BUT Strongly Consider Filing
- Activity is below $5,000 threshold
- However, elder financial exploitation is a priority area emphasized in FinCEN guidance
- Victim is vulnerable
- Exploitation may continue if not reported
Best Practice: File SAR Voluntarily
- FinCEN guidance encourages reporting elder exploitation
- Protects vulnerable victim
- May prevent continued exploitation
- Demonstrates strong risk-based AML program
Example 6: Structuring with Multiple Subjects - Aggregate Conspiracy
Scenario: Three customers (related family members) coordinate to structure cash deposits:
- Customer A: Deposits $4,500 cash on Monday
- Customer B: Deposits $3,800 cash on Monday
- Customer C: Deposits $4,200 cash on Tuesday
- All three immediately wire funds to the same offshore entity
- Pattern repeats weekly for four weeks
- Total over four weeks: Customer A ($18,000), Customer B ($15,200), Customer C ($16,800)
Analysis:
- Individually: Each customer’s weekly activity is below $10,000
- Combined weekly: Exceeds $10,000 ($12,500 first week)
- Total aggregate: $50,000 over four weeks
- Pattern: Coordinated to evade CTRs by splitting across multiple people
- Subjects identified: Yes (all three customers)
Conclusion: SAR Required
- File ONE SAR listing all three customers as subjects
- Aggregate all activity: $50,000
- Exceeds $5,000 threshold
- Coordinated structuring conspiracy
- Describe coordination in narrative
Example 7: Terrorist Financing - No Dollar Threshold
Scenario: Customer initiates $1,500 wire transfer to entity listed on OFAC SDN list or otherwise connected to known terrorist organization.
Analysis:
- Amount: $1,500
- Below $5,000: Yes
- Type of violation: Material support to terrorism (18 U.S.C. § 2339A, § 2339B)
- Regulatory expectation: Report all terrorist financing regardless of amount
Conclusion: SAR Required Immediately
- National security priority
- File SAR regardless of amount
- Also block transaction (OFAC compliance) if SDN listed
- Contact appropriate authorities (OFAC, law enforcement)
- Terrorist financing has no practical dollar threshold
Example 8: Two Separate Activities - Do Not Aggregate
Scenario: Customer engages in two separate suspicious activities:
- February: Check kiting involving $3,500
- May: Suspected structuring with cash deposits totaling $4,200
Analysis:
- Activity 1: $3,500 (check kiting)
- Activity 2: $4,200 (structuring)
- Each individually below $5,000
- Three months apart
- Different types of suspicious activity
- No apparent connection
Conclusion: Generally No SAR Required (Each Below Threshold)
- Do not aggregate unrelated activities
- Each is below $5,000 threshold
- Unless investigation reveals activities are connected to a broader scheme, no aggregation is appropriate
However: Monitor customer closely. Two separate suspicious activities by the same customer may indicate a pattern of illicit activity. Consider filing voluntarily or aggregate if subsequent investigation reveals a connection.
Common Questions and Misconceptions
Q1: Can we file SARs below the thresholds?
Answer: Yes. The thresholds establish when SARs are required, not when they are permitted. Institutions may file SARs below thresholds when appropriate as part of a risk-based AML program.
Considerations:
- Is there law enforcement value?
- Does it fit within the institution’s risk-based approach?
- Is it a priority area (elder exploitation, human trafficking, etc.)?
- Will it establish a record for potential escalation?
Caution: Avoid routinely filing SARs far below thresholds on marginal activity, as this can overwhelm law enforcement and reduce the value of SARs generally.
Q2: Do we need to file a SAR every time a customer makes a $10,000 cash deposit?
Answer: No. A $10,000 cash deposit requires a Currency Transaction Report (CTR), not a SAR. A SAR is only required if the transaction is suspicious (e.g., structured to evade the CTR, lacks business purpose, etc.).
Key Distinction:
- CTR: Required for currency transactions over $10,000 (not suspicious, just large)
- SAR: Required when activity is suspicious and meets threshold requirements
Q3: If we file a SAR, do we also need to file a CTR?
Answer: Yes, if the transaction meets CTR requirements ($10,000+ in currency), file both.
Key Points:
- SAR and CTR serve different purposes
- Both may be required for the same transaction
- Example: Customer deposits $12,000 in cash (file CTR for large currency transaction). If deposit is part of a pattern of suspicious activity totaling $15,000, also file SAR.
- File both independently; don’t assume one replaces the other
Q4: Is there a maximum dollar threshold above which we don’t need to file SARs?
Answer: No. There is no upper limit. Institutions must file SARs for all suspicious activity that meets the minimum thresholds, regardless of how large the amount.
Examples:
- $5,000 suspicious transaction: File SAR
- $5,000,000 suspicious transaction: File SAR
- Both require reporting; no upper limit
Q5: Can we aggregate activity over a year or longer?
Answer: Yes, if the suspicious activity continued over that period and represents a related pattern or ongoing scheme.
Considerations:
- Is the activity part of a continuous pattern?
- Are the transactions related to the same scheme?
- Use professional judgment about what constitutes a reasonable aggregation period
- Very long periods may be more appropriate for continuing activity SARs
Best Practice: For initial SARs, aggregate over the period of the specific pattern or scheme. For ongoing activity, use continuing activity SARs every 90 days.
Q6: What if we’re not sure if the activity is suspicious but it’s close to the threshold?
Answer: If in doubt and activity is approaching or exceeding thresholds, investigate thoroughly. If investigation does not resolve the suspicion and activity exceeds thresholds, file the SAR.
Key Principle: “Knows, suspects, or has reason to suspect” is a relatively low standard. Certainty is not required.
Factors to Consider:
- Red flags present
- Ability to explain the activity
- Customer’s response to inquiries
- Risk profile of customer
- Type of activity
Best Practice: Document the decision-making process. If you decide not to file, document why the activity was deemed not suspicious despite initial concern.
Q7: Do thresholds apply differently for continuing activity SARs?
Answer: No. The same thresholds apply, but the 90-day review cycle determines when continuing activity SARs are filed (not the dollar thresholds alone).
Process:
- File initial SAR when thresholds are met
- Review every 90 days
- If activity continues, file continuing activity SAR every 90 days regardless of new activity amount (as long as activity continues and exceeds thresholds cumulatively)
Q8: If we close the account, do we still need to file a SAR?
Answer: Yes. Account closure does not eliminate the SAR filing obligation for suspicious activity that already occurred and meets thresholds.
Process:
- Detect suspicious activity
- Investigate
- Determine SAR filing required
- May close account as risk mitigation
- Still must file SAR within required timeframe
Note in Narrative: Describe account closure as part of institution’s response to the suspicious activity.
Q9: Does the threshold apply to losses or to the transaction amounts?
Answer: Apply thresholds to transaction amounts, not losses.
Example: Customer attempts to cash a counterfeit $8,000 check. Teller detects the fraud and does not cash the check. Loss to institution = $0.
Threshold Analysis: Use the $8,000 transaction amount, not the $0 loss. SAR required (exceeds $5,000 threshold, illegal activity, subject identified).
Rationale: SARs report suspicious activity, not just completed crimes or actual losses.
Q10: What if the suspicious activity involves multiple institutions?
Answer: Each institution files a SAR based on the activity they observed.
Scenario: Customer structures deposits across three banks:
- Bank A: $12,000 in structured deposits
- Bank B: $9,000 in structured deposits
- Bank C: $11,000 in structured deposits
Each bank files separately:
- Bank A files SAR for $12,000 observed at Bank A
- Bank B files SAR for $9,000 observed at Bank B
- Bank C files SAR for $11,000 observed at Bank C
Do Not Aggregate Across Institutions: Each institution reports only what they observed, not the total across all institutions (unless they have direct knowledge through information sharing arrangements).
Law Enforcement’s Role: Law enforcement aggregates SARs from multiple institutions to see the full picture.
Exception: Joint SARs may be filed when institutions coordinate (see separate guidance on Joint SARs).
Summary of Key Thresholds
| Scenario | Dollar Threshold | Subject Identification | Filing Deadline |
|---|---|---|---|
| Insider Abuse | None (any amount) | Must identify insider | 30 days |
| Federal Crime - Subject Identified | $5,000 | Must identify | 30 days |
| Federal Crime - Subject Unidentified | $25,000 | Cannot identify | 60 days |
| BSA Evasion | $5,000 (though often filed regardless of amount) | Should identify if possible | 30 days if identified; 60 days if not |
| Terrorist Financing | None (any amount) | Should identify if possible | Immediately |
| OFAC Violations | None (any amount) | Should identify if possible | Immediately |
Regulatory Citations
Primary Regulations:
- 31 U.S.C. § 5318(g) - SAR Requirements
- 31 CFR § 1020.320 - Banks
- 31 CFR § 1021.320 - Casinos
- 31 CFR § 1022.320 - Money Services Businesses
- 31 CFR § 1023.320 - Broker-Dealers
- 31 CFR § 1024.320 - Mutual Funds
- 31 CFR § 1025.320 - Insurance Companies
- 31 CFR § 1026.320 - Futures Commission Merchants
Related Guidance:
- FFIEC BSA/AML Examination Manual
- FinCEN Advisories and Guidance Documents
- Federal Reserve SR Letters
- OCC Bulletins
- FDIC Financial Institution Letters
Document Version: 1.0 Last Updated: January 18, 2024 Next Review Date: January 18, 2025
This guidance is for informational purposes only and does not constitute legal advice. Financial institutions should consult with legal counsel and compliance professionals regarding SAR threshold application for their specific circumstances.
