U.S. flag

An official website of the United States government

SAR Narrative Writing Best Practices

SAR Narrative Writing Best Practices

Table of Contents

  1. Introduction: The Importance of Quality Narratives
  2. The 5 W’s Framework
  3. Structuring the Narrative
  4. Level of Detail Required
  5. What to Include
  6. What to Exclude
  7. Example Narratives by Scenario
  8. Common Mistakes to Avoid
  9. Quality Review Checklist

Introduction: The Importance of Quality Narratives

The narrative section (Part V) of the SAR is the most critical component of the entire report. While the structured data fields provide important information for sorting and categorizing SARs, the narrative tells the story that enables law enforcement to:

  • Understand the suspicious activity quickly and completely
  • Assess the severity and prioritize for investigation
  • Identify patterns across multiple institutions
  • Develop probable cause for further investigative steps
  • Link related cases involving the same subjects or schemes
  • Testify in court using the facts documented contemporaneously

The Law Enforcement Perspective

According to FinCEN and law enforcement feedback, the most common deficiencies in SARs relate to narrative quality:

  • Too vague: Lacks specific facts and details
  • Too brief: Insufficient information to understand the activity
  • Poorly organized: Difficult to follow the sequence of events
  • Missing the “why”: Fails to explain why activity is suspicious
  • Conclusory: States conclusions rather than facts

A well-written narrative can mean the difference between a SAR that leads to a successful investigation and one that cannot be acted upon.

Time Investment

While it may be tempting to rush through the narrative to meet filing deadlines, investing time in a well-crafted narrative serves multiple purposes:

  • Provides maximum value to law enforcement
  • Documents the institution’s reasonable basis for filing
  • Demonstrates thorough investigation and due diligence
  • Supports the institution’s safe harbor protection
  • Facilitates regulatory examination review

Recommended approach: Allocate sufficient time for drafting, reviewing, and refining the narrative before filing.

The 5 W’s Framework

Every effective SAR narrative must answer the five fundamental questions: Who, What, When, Where, and Why. This framework ensures completeness and helps organize information logically.

WHO - Identify All Relevant Parties

The Subject(s)

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

For Individuals:

  • Full legal name (as it appears on identification)
  • All known aliases, nicknames, or AKAs
  • Date of birth
  • Current residential address
  • Previous addresses (if relevant to the activity)
  • Social Security Number or Tax ID Number
  • Driver’s license number and issuing state
  • Passport number and country (for foreign nationals)
  • Phone numbers (home, mobile, work)
  • Email addresses
  • Occupation or employment
  • Employer name and address
  • Role in the suspicious activity

For Entities:

  • Complete legal name
  • DBA (Doing Business As) names
  • Employer Identification Number (EIN)
  • Business address (physical location)
  • Mailing address (if different)
  • Type of business and industry
  • State and date of incorporation
  • Website address
  • Names, titles, and roles of principals, owners, officers, authorized signers
  • Ultimate beneficial owners

Example - WHO: “John Michael Smith (DOB: 05/15/1978, SSN: XXX-XX-1234) is the sole owner and authorized signer on Account #XXXX5678. Mr. Smith opened the account on January 10, 2024, identifying himself as a self-employed consultant. He provided a residential address of 123 Main Street, Anytown, ST 12345, and listed his occupation as ‘Business Consultant.’ According to his account opening documentation, Mr. Smith stated his expected monthly deposits would be $5,000-$8,000 from client payments.”

Other Relevant Parties

  • Co-conspirators or accomplices
  • Recipients of suspicious wire transfers
  • Check payees
  • Counterparties to transactions
  • Victims (if known)
  • Related account holders

WHAT - Describe the Suspicious Activity

Clearly and specifically describe the transactions or conduct that constitute suspicious activity.

Transaction Details:

  • Type of transactions (deposits, withdrawals, wires, checks, ACH, etc.)
  • Dollar amounts (be specific, not vague)
  • Instruments used (cash, official checks, personal checks, wire transfers, etc.)
  • Account numbers involved
  • Reference numbers (wire confirmation numbers, check numbers, etc.)
  • Source of funds (when known)
  • Destination of funds
  • Purpose stated by customer (if any)

Patterns and Behavior:

  • Frequency of transactions
  • Timing patterns
  • Sequencing of activities
  • Unusual characteristics
  • Changes in behavior over time
  • Attempts to avoid scrutiny

Example - WHAT: “Between February 1, 2024, and April 30, 2024, Mr. Smith made 27 cash deposits into Account #XXXX5678, totaling $263,450. Each deposit was structured to be just under $10,000, ranging from $8,500 to $9,900. The deposits occurred at various branch locations across the state. Following each series of cash deposits, Mr. Smith immediately wired funds to offshore accounts. Specifically, he initiated 9 wire transfers totaling $255,000 to accounts at XYZ Bank in the Cayman Islands, account holder ‘ABC Enterprises Ltd.’”

WHEN - Establish the Timeline

Provide specific dates and timeframes to establish when the suspicious activity occurred.

Key Dates:

  • Date account opened
  • Date suspicious activity began
  • Dates of specific transactions (key transactions should have exact dates)
  • Date range of pattern or course of conduct
  • Date activity was detected
  • Date investigation commenced
  • Date of any customer contact or inquiries
  • Date account was restricted or closed (if applicable)

Chronological Narrative: Present information in chronological order when possible to help readers follow the sequence of events.

Example - WHEN: “Mr. Smith opened Account #XXXX5678 on January 10, 2024. Initial activity for the first three weeks appeared consistent with his stated business purpose, with deposits ranging from $3,000 to $6,000. However, on February 1, 2024, the pattern changed dramatically. From February 1 through April 30, 2024 (a 13-week period), Mr. Smith made the following deposits:

  • February 1-28: 9 cash deposits totaling $81,300
  • March 1-31: 10 cash deposits totaling $93,750
  • April 1-30: 8 cash deposits totaling $88,400

The institution’s monitoring system flagged the structuring pattern on March 15, 2024. A formal investigation was initiated on March 18, 2024.”

WHERE - Identify Locations

Document where the suspicious activity occurred.

Geographic Information:

  • Branch locations where transactions occurred
  • ATM locations
  • Cities, states, countries involved
  • Online/mobile banking (IP addresses if available)
  • Wire transfer destination countries
  • Business addresses
  • Residential addresses relevant to the activity

Example - WHERE: “The cash deposits were made at 7 different branch locations:

  • Downtown Branch (123 Main St, Anytown, ST): 8 deposits
  • Westside Branch (456 Oak Ave, Westtown, ST): 6 deposits
  • Northgate Branch (789 Elm St, Northville, ST): 5 deposits
  • Southpoint Branch (321 Maple Dr, Southburg, ST): 3 deposits
  • Eastview Branch (654 Pine Rd, Eastside, ST): 3 deposits
  • Central Branch (987 Cedar Ln, Midtown, ST): 1 deposit
  • Airport Branch (147 Terminal Way, Airportville, ST): 1 deposit

Wire transfers were sent to:

  • XYZ Bank, Georgetown, Cayman Islands (5 wires, $145,000)
  • International Finance Bank, Nassau, Bahamas (3 wires, $75,000)
  • Global Trust Company, Panama City, Panama (1 wire, $35,000)”

WHY - Explain the Suspicion

This is arguably the most important component. Clearly articulate why the activity is suspicious and what red flags or indicators were present.

Red Flags to Address:

  • Deviation from expected account activity
  • Inconsistent with customer profile or stated business
  • Lack of apparent lawful purpose
  • Attempts to evade reporting requirements
  • Unusual for the type of account or customer
  • Involves high-risk jurisdictions
  • Uses of deceptive practices
  • Refusal to provide information
  • Evasive behavior when questioned
  • Rapid movement of funds without economic purpose
  • Inconsistent with customer’s financial capacity

Analytical Framework:

  1. State what activity would be expected based on customer profile
  2. Describe how actual activity deviated from expectations
  3. Explain the significance of the deviation
  4. Identify specific red flag indicators
  5. Describe any additional investigation conducted
  6. Explain why no reasonable legitimate explanation was found

Example - WHY: “This activity is suspicious for the following reasons:

Structuring: Each of the 27 cash deposits was deliberately structured to fall just below the $10,000 Currency Transaction Report threshold. The consistency of amounts between $8,500 and $9,900, combined with the use of multiple branch locations, indicates a deliberate attempt to evade BSA reporting requirements in violation of 31 U.S.C. § 5324.

Inconsistent with Customer Profile: Mr. Smith described himself as a business consultant with expected monthly deposits of $5,000-$8,000. The actual activity of $263,450 in cash deposits over 13 weeks (averaging over $20,000 per week) is grossly inconsistent with his stated business. Additionally, business consultants typically receive payments via check or wire transfer, not large amounts of cash.

Source of Funds Unexplained: When asked during account opening about the source of his funds, Mr. Smith stated ‘consulting fees from various clients.’ However, the volume of cash is inconsistent with consulting services, which typically involve documented contracts and non-cash payments. Mr. Smith has been unable or unwilling to provide documentation supporting the source of the cash.

Immediate Outbound Wires to Offshore Accounts: Immediately following each series of cash deposits, Mr. Smith wired the funds to offshore accounts in high-risk jurisdictions (Cayman Islands, Bahamas, Panama). These transactions lack any apparent business purpose. When asked about the wires during a branch inquiry on March 20, 2024, Mr. Smith stated they were for ‘business investments’ but could not provide details about the nature of the investments or the relationship with the recipient entities.

Pattern Timing: The structured deposits occurred on a regular pattern, typically 2-3 times per week, suggesting an ongoing scheme rather than isolated transactions.

Multi-Branch Activity: Mr. Smith deliberately used seven different branch locations across a wide geographic area, an apparent attempt to avoid detection by conducting smaller amounts at each location.

Based on the totality of these factors, the institution has no reasonable explanation for this activity consistent with legitimate business purposes. The activity is indicative of money laundering, structuring, and potential proceeds from illegal activity.”

Structuring the Narrative

An effective SAR narrative follows a logical structure that guides the reader through the information systematically.

Template Structure

[Opening Summary - 1-2 sentences]

[Subject Background - 1-2 paragraphs]
- Account relationship
- Customer due diligence information
- Expected activity profile

[Description of Suspicious Activity - 2-4 paragraphs]
- Chronological presentation of facts
- Specific transactions and amounts
- Pattern analysis
- Timeline of events

[Red Flags and Indicators - 1-2 paragraphs]
- Specific red flags identified
- Deviation from expected behavior
- Comparison to normal patterns

[Investigation and Analysis - 1-2 paragraphs]
- Steps taken to investigate
- Additional due diligence performed
- Customer responses (if any)
- Internal consultation

[Explanation of Suspicion - 1-2 paragraphs]
- Why activity is suspicious
- Lack of reasonable legitimate explanation
- Assessment of indicators

[Institution Actions - 1 paragraph]
- Detection method
- Account restrictions or closure
- Enhanced monitoring
- Prior SARs filed

[Conclusion - 1-2 sentences]
- Summary of basis for filing
- Ongoing concerns (if applicable)

Opening Summary

Start with a concise summary that immediately communicates the essential information.

Purpose:

  • Quickly orient the reader
  • Provide context for the detailed narrative
  • Highlight the type and significance of the activity

Elements:

  • Type of suspicious activity
  • Subject identification
  • Time period
  • Total amount
  • Primary concern

Strong Opening Examples:

Example 1 - Structuring: “This SAR is filed to report suspected structuring activity conducted by customer John Michael Smith. Between February 1, 2024, and April 30, 2024, Mr. Smith made 27 cash deposits totaling $263,450, each deliberately structured below $10,000, followed by immediate wire transfers to offshore accounts.”

Example 2 - Elder Exploitation: “This SAR is filed to report suspected financial exploitation of vulnerable adult Mary Thompson (DOB: 03/15/1940). Beginning January 2024, Ms. Thompson’s caregiver, Robert Johnson, gained access to her accounts and systematically withdrew $127,000 through unauthorized wire transfers and ATM withdrawals over a six-week period.”

Example 3 - Business Email Compromise: “This SAR is filed to report a business email compromise (BEC) fraud affecting commercial customer ABC Manufacturing Corp. On March 15, 2024, the company’s email system was compromised, resulting in a fraudulent wire transfer of $485,000 to a bank account in Hong Kong based on falsified payment instructions.”

Weak Opening (Avoid): “This SAR is filed to report suspicious activity.” (Too vague, provides no useful information)

Paragraph Organization

Use Focused Paragraphs: Each paragraph should cover one main topic or aspect of the suspicious activity.

Logical Flow:

  • Move from general to specific
  • Follow chronological order for events
  • Group related information together
  • Use transitions between paragraphs

Example Paragraph Progression:

Paragraph 1 - Subject Background: “John Michael Smith opened Account #XXXX5678 on January 10, 2024, as a personal checking account. According to account opening documentation, Mr. Smith is self-employed as a business consultant with an expected monthly income of $5,000-$8,000. He stated the account would be used for receiving client payments and personal expenses.”

Paragraph 2 - Initial Normal Activity: “During the first three weeks following account opening, activity appeared consistent with Mr. Smith’s stated profile. He made 4 mobile deposits of checks ranging from $1,200 to $4,500, totaling $11,300, and used his debit card for typical retail purchases. This initial pattern raised no concerns.”

Paragraph 3 - Change in Pattern: “On February 1, 2024, the account activity changed dramatically. Mr. Smith began making frequent cash deposits in amounts just below $10,000, a significant departure from the initial check deposit pattern and inconsistent with his stated business as a consultant.”

Using Headings and Subheadings (Optional)

For complex cases involving multiple subjects or extensive activity, consider using headings to organize the narrative.

Example:

SUMMARY
This SAR is filed to report...

SUBJECT BACKGROUND
John Smith opened...

SUSPICIOUS ACTIVITY
Cash Structuring Pattern
Between February 1 and April 30, 2024...

Wire Transfers to Offshore Accounts
Following the cash deposits...

RED FLAGS AND INDICATORS
This activity is suspicious for the following reasons...

INSTITUTION INVESTIGATION
Upon detection of the pattern...

Note: Use headings judiciously. They can improve readability for lengthy narratives but may be unnecessary for straightforward cases.

Level of Detail Required

Finding the Right Balance

The narrative should provide sufficient detail to enable law enforcement to understand and act on the suspicious activity, without being so lengthy that key information is buried in irrelevant detail.

When to Include Transaction-Level Detail

Include Specific Transaction Details When:

  • Transactions demonstrate a pattern (show several examples)
  • Specific transactions are highly suspicious
  • Transaction characteristics are unusual
  • Amounts or timing are significant
  • Counterparties are relevant
  • Documentation is questionable

Example - Appropriate Detail: “Representative examples of the structured deposits include:

  • February 3, 2024: $9,800 cash deposit at Downtown Branch
  • February 7, 2024: $9,400 cash deposit at Westside Branch
  • February 10, 2024: $9,950 cash deposit at Northgate Branch
  • February 14, 2024: $9,100 cash deposit at Southpoint Branch

[Full transaction list attached as supporting documentation]”

When to Summarize

Use Summary Information When:

  • There are numerous similar transactions
  • Pattern is more important than individual transactions
  • Transaction details are available in supporting documentation

Example - Appropriate Summary: “Over the 13-week period, Mr. Smith made 27 cash deposits totaling $263,450. The deposits averaged $9,757 per transaction, with a range of $8,500 to $9,900. All deposits occurred between 10:00 AM and 2:00 PM on weekdays. A complete transaction log is maintained in the institution’s supporting documentation.”

Specific vs. Vague Language

Be Specific:

VagueSpecific
“Multiple deposits”“27 deposits over 13 weeks”
“Large amounts”“$263,450 total; $9,757 average per transaction”
“Various branches”“7 different branch locations across the state”
“Shortly after”“Within 24-48 hours of the deposits”
“High-risk countries”“Cayman Islands, Bahamas, and Panama”
“Recently”“Between February 1 and April 30, 2024”
“Several times”“3 times per week on average”

Quantifying Information

Use Numbers:

  • Specific dates (not “early March” but “March 3, 2024”)
  • Exact amounts (not “approximately $10,000” but “$9,847”)
  • Precise counts (not “many transactions” but “27 transactions”)
  • Actual timeframes (not “over several months” but “13 weeks”)
  • Measurable patterns (not “regularly” but “2-3 times per week”)

Level of Detail by Activity Type

High Detail Needed:

  • Insider abuse (document position, access, and breach of duty)
  • Terrorist financing (document all parties, transactions, and connections)
  • Complex fraud schemes (explain the scheme mechanics)
  • Identity theft (document impersonation and unauthorized access)

Moderate Detail Sufficient:

  • Straightforward structuring (pattern is self-evident)
  • Simple check kiting (describe the kite cycle)
  • Unusual wire activity (list wires with key details)

Summary May Be Adequate:

  • Large-volume low-level activity (when pattern is clear)
  • Obvious red flags (but still explain why suspicious)

What to Include

Essential Information Elements

1. All Information That Answers the 5 W’s

Ensure every narrative comprehensively addresses Who, What, When, Where, and Why.

2. Specific Red Flag Indicators

Identify and explain each red flag observed:

  • FinCEN advisory indicators
  • FFIEC BSA/AML Examination Manual red flags
  • Typologies from FinCEN SAR Activity Review
  • Industry-specific indicators
  • Institution-specific risk indicators

3. Customer Statements and Explanations

When relevant, include:

  • Stated purpose of account
  • Explanations provided for activity
  • Responses to inquiries
  • Changes in explanations over time
  • Refusal to provide information
  • Evasive or inconsistent answers

Example: “When questioned by branch staff on March 20, 2024, about the source of cash deposits, Mr. Smith stated the funds came from ‘consulting fees paid by clients in cash.’ When asked to provide documentation of his consulting business, such as business cards, invoices, or contracts, Mr. Smith stated he does not provide written documentation for his services. When asked why clients would pay large amounts in cash, Mr. Smith became evasive and stated ‘some clients prefer cash’ but could not provide further explanation.”

4. Investigation Steps Taken

Document the institution’s due diligence:

  • Review of account history
  • Transaction analysis performed
  • Database searches (LexisNexis, World-Check, etc.)
  • Internet/media research
  • Internal consultations
  • Enhanced due diligence measures
  • Customer contact attempts
  • Additional documentation requested

Example: “Upon detection of the pattern, the BSA Compliance Department conducted the following investigation:

  • Reviewed complete account transaction history
  • Analyzed deposit patterns and timing
  • Conducted LexisNexis search (no criminal history found)
  • Performed internet search on Mr. Smith and business name (no website or business listings found)
  • Reviewed customer identification documents (no issues identified)
  • Consulted with branch manager regarding customer behavior
  • Attempted to contact customer by phone on March 21, 2024 (no answer, voicemail left, no return call)
  • Reviewed account for prior alerts (two prior structuring alerts in February 2024 that were under review)”

5. Comparison to Expected Activity

Explain how the suspicious activity deviates from:

  • Customer’s stated purpose
  • Expected account activity based on profile
  • Typical activity for similar customers
  • Normal business practices for the industry
  • Prior account behavior

6. Pattern Analysis

When applicable, document:

  • Frequency and timing patterns
  • Amount patterns
  • Geographic patterns
  • Relationship patterns (to other accounts or customers)
  • Seasonal patterns
  • Changes over time

7. Connections to Other Activity

Note any connections to:

  • Other accounts at your institution
  • Prior SARs filed
  • Other subjects or entities
  • Known fraud schemes or typologies
  • Media reports or public information
  • Law enforcement inquiries

Example: “This activity is the second SAR filed on Mr. Smith. A previous SAR (BSA ID: XXXXXXXXXX-XXXX-1) was filed on January 15, 2024, reporting similar structuring activity on a different account (Account #XXXX1234) that Mr. Smith closed in December 2023. The prior SAR documented 15 structured cash deposits totaling $138,000 over a two-month period, followed by wires to offshore accounts.”

8. Account Actions Taken

Document steps taken to address the suspicious activity:

  • Enhanced monitoring implemented
  • Transaction restrictions placed
  • Account closure decision and date
  • Funds held or frozen
  • Reporting to account holder (as appropriate)
  • Ongoing review plans

9. Relevant Customer Behavior

Include observations about the customer’s conduct:

  • Evasive or nervous behavior
  • Requests for special treatment
  • Attempts to avoid identification requirements
  • Splitting transactions
  • Multiple branch visits
  • Unusual knowledge of reporting thresholds
  • Threatening or hostile behavior
  • Attempts to develop inappropriate relationships with staff

For cyber-related suspicious activity, include:

  • IP addresses involved
  • Email addresses used
  • Device identifiers
  • Login patterns
  • Geographic anomalies (IP location vs. stated address)
  • User agent information
  • Session data
  • Malware or phishing indicators

Supporting Your Conclusions

Every suspicion statement should be supported by facts.

Weak: “The customer appeared suspicious.”

Strong: “The customer appeared nervous and evasive. When the teller asked routine questions about the source of the cash deposit, the customer avoided eye contact, provided vague answers, and repeatedly asked if the transaction would be reported. When informed of potential CTR requirements, the customer immediately stated he wanted to deposit only $9,500 instead of the $12,000 he initially presented.”

What to Exclude

Information That Should NOT Be Included

1. The Fact That a SAR Is Being Filed

Never include:

  • Statements that a SAR is being filed or has been filed
  • References to SAR in customer communications
  • Any indication to the customer that they are under suspicion

Reason: 31 U.S.C. § 5318(g)(2) strictly prohibits notifying any person involved in the transaction that a SAR has been filed. This prohibition extends to information that might suggest a SAR filing.

Avoid:

  • “This is money laundering”
  • “The customer is guilty of fraud”
  • “This violates 18 U.S.C. § 1956”
  • “The customer is a criminal”

Instead, state facts:

  • “The activity is consistent with money laundering typologies”
  • “The pattern suggests potential fraud”
  • “The activity may violate federal law”
  • “The customer’s conduct raises suspicions”

Reason: The institution’s role is to report suspicious activity and provide facts, not to make legal determinations or accusations. Let law enforcement draw legal conclusions.

3. Irrelevant Personal Information

Exclude:

  • Personal opinions about the customer
  • Speculation about customer’s character
  • Irrelevant personal details (race, religion, political views, etc.)
  • Gossip or rumors
  • Information about the customer’s lifestyle unrelated to the suspicious activity

Include only information directly relevant to the suspicious activity.

4. Information About Ongoing Law Enforcement Investigations

Do not include:

  • Details about active law enforcement investigations
  • Names of law enforcement officers or agencies involved
  • Case numbers or investigation details
  • Information obtained from law enforcement

Reason: Such information is typically confidential and not relevant to documenting the suspicious activity your institution detected.

Exception: You may note that the activity was detected “as a result of a law enforcement inquiry” without providing investigation details.

5. Proprietary Detection Methods

Avoid revealing:

  • Specific algorithm parameters
  • Detailed monitoring system configurations
  • Threshold amounts for internal alerts
  • Specific detection methodologies that could be exploited

Instead:

  • “Detected through automated transaction monitoring”
  • “Identified during routine account review”
  • “Flagged by internal compliance monitoring”

6. Speculation and Assumptions

Do not include:

  • Guesses about the source of funds (unless factual basis)
  • Assumptions about customer motives
  • Speculation about what might happen
  • Theories not supported by facts

Example of speculation to avoid: “The customer is probably involved in drug trafficking and is likely using the funds to purchase narcotics.”

Better approach: “The pattern of cash deposits and immediate wire transfers to high-risk jurisdictions, combined with the lack of legitimate business explanation, is consistent with money laundering typologies. The institution has no information about the ultimate source or use of the funds.”

7. Excessive or Irrelevant Documentation

While supporting documentation is important, avoid attaching:

  • Entire account histories for multi-year accounts (summarize and attach relevant portions)
  • Unrelated transactions
  • Excessive customer correspondence unrelated to the suspicious activity
  • Internal emails beyond what’s necessary to document the investigation

8. Other Customers’ Confidential Information

Protect other customers’ privacy:

  • Redact unrelated account numbers
  • Limit information about counterparties to what’s relevant
  • Do not include other customers’ SSNs unless they are subjects

9. Subjective Character Assessments

Avoid:

  • “The customer seems dishonest”
  • “I don’t trust this person”
  • “The customer gives me a bad feeling”

Instead, describe objective facts:

  • “The customer provided inconsistent explanations”
  • “The customer’s documentation could not be verified”
  • “The customer’s stated income is inconsistent with account activity”

10. Discriminatory Language or Basis

Never include:

  • References to race, ethnicity, national origin, religion as basis for suspicion
  • Stereotypes or biases
  • Profiling based on protected characteristics

SAR decisions must be based on objective suspicious activity, not customer characteristics.

Example Narratives by Scenario

Example 1: Structuring (Cash Deposits)

SUSPICIOUS ACTIVITY REPORT NARRATIVE

This SAR is filed to report suspected structuring activity conducted by customer Robert M. Johnson (DOB: 08/22/1975, SSN: XXX-XX-5678). Between January 15, 2024, and March 30, 2024, Mr. Johnson made 31 cash deposits totaling $294,750 into Account #XXXX9876, each deliberately structured below the $10,000 CTR threshold, in apparent violation of 31 U.S.C. § 5324.

SUBJECT BACKGROUND
Mr. Johnson opened Account #XXXX9876 on December 1, 2023, as a personal checking account. His account opening documentation indicates he is employed as a landscaper with an annual income of $45,000. Mr. Johnson stated the account would be used for receiving his paycheck via direct deposit and for personal expenses. The expected monthly deposits were $3,500-$4,000. He provided a residential address of 456 Oak Street, Springfield, ST 54321, and listed his employer as "Green Lawn Landscaping Services."

INITIAL ACCOUNT ACTIVITY
During December 2023, account activity appeared consistent with Mr. Johnson's stated profile. He received one direct deposit of $3,200 from Green Lawn Landscaping and made typical debit card purchases for gas, groceries, and other retail expenses totaling approximately $2,800. This initial pattern raised no concerns.

SUSPICIOUS CASH DEPOSITS
On January 15, 2024, Mr. Johnson began making frequent cash deposits that deviated significantly from his established pattern:

January 15 - March 30, 2024 Deposit Summary:
- Total deposits: 31 cash deposits
- Total amount: $294,750
- Average deposit: $9,508
- Range: $8,700 - $9,900
- Frequency: 2-3 times per week

Representative examples:
- January 15: $9,850 cash at Downtown Branch
- January 18: $9,200 cash at Westside Branch
- January 22: $9,900 cash at Northgate Branch
- January 25: $9,650 cash at Main Branch
- January 29: $9,400 cash at Eastside Branch

This pattern continued throughout the period, with Mr. Johnson systematically making cash deposits just below the $10,000 threshold at various branch locations across the city.

MULTI-BRANCH PATTERN
Mr. Johnson used seven different branch locations for these deposits:
- Downtown Branch: 9 deposits
- Westside Branch: 7 deposits
- Northgate Branch: 5 deposits
- Main Branch: 4 deposits
- Eastside Branch: 3 deposits
- Southpoint Branch: 2 deposits
- Airport Branch: 1 deposit

The use of multiple branches across a wide geographic area, combined with the consistent sub-$10,000 amounts, indicates deliberate attempts to avoid detection.

RED FLAGS AND INDICATORS
This activity is suspicious for the following reasons:

Deliberate Structuring: Each of the 31 deposits was carefully structured to fall just below the $10,000 CTR threshold. The consistency of amounts between $8,700 and $9,900, the frequency of deposits, and the multi-branch pattern are classic indicators of structuring designed to evade BSA reporting requirements.

Grossly Inconsistent with Income: Mr. Johnson's stated annual income is $45,000 ($3,750 per month). The cash deposits of $294,750 over 11 weeks represent more than 6.5 times his annual stated income, deposited in less than three months. This dramatic inconsistency cannot be explained by his employment as a landscaper.

Cash Intensity Unusual for Occupation: While landscapers may occasionally receive cash payments, the volume of cash ($9,500 average per deposit, 2-3 times per week) is highly unusual and inconsistent with typical landscaping business practices, especially during winter months (January-March) when landscaping activity in this region is minimal.

Source of Funds Unexplained: When asked by a teller on February 10, 2024, about the source of a $9,600 cash deposit, Mr. Johnson stated it was "side job income" but provided no details. When the teller inquired about the nature of the side jobs, Mr. Johnson became evasive, stating only that he does "various projects for cash" and quickly concluded the transaction.

Knowledge of Reporting Thresholds: On March 5, 2024, Mr. Johnson presented $10,400 in cash for deposit. When the teller began preparing the Currency Transaction Report as required, Mr. Johnson asked why paperwork was necessary. After the teller explained the CTR requirement for deposits over $10,000, Mr. Johnson immediately withdrew $500 from the deposit amount and deposited only $9,900. This demonstrates knowledge of the reporting threshold and deliberate action to avoid it.

Timing Pattern: The deposits occurred on a highly regular schedule, typically Monday and Thursday mornings between 9:00 AM and 11:00 AM, suggesting a systematic, ongoing scheme rather than occasional legitimate cash receipts.

INSTITUTION INVESTIGATION
Upon detection of the structuring pattern by the automated monitoring system on February 20, 2024, the BSA Compliance Department conducted the following investigation:

- Reviewed complete account transaction history since opening
- Analyzed deposit patterns, amounts, frequencies, and locations
- Conducted database search (LexisNexis) revealing no criminal history but no business registrations or licenses for any landscaping or contracting business in Mr. Johnson's name
- Performed internet and social media research; found no website, business listings, or advertising for any business operated by Mr. Johnson
- Contacted Green Lawn Landscaping Services (listed employer); confirmed Mr. Johnson worked there part-time during the 2023 season but was laid off in November 2023 for the winter; no current employment
- Reviewed original account opening documentation; found no discrepancies in identification
- Consulted with branch managers at the multiple locations where deposits occurred; all confirmed customer made deposits personally, showed no unusual behavior beyond pattern described above
- Sent letter to Mr. Johnson on March 1, 2024, requesting updated employment and income information; no response received
- Attempted phone contact March 8, 2024; call not answered, voicemail left, no return call

ADDITIONAL CONCERNING FACTORS
During the investigation, the following additional factors were discovered:

- Mr. Johnson's direct deposit from Green Lawn Landscaping stopped in November 2023 (layoff)
- No other identifiable income sources since the November layoff
- No large withdrawals or transfers from the account that would indicate the cash came from another account
- Customer has provided no documentation or credible explanation for the source of the cash
- The total deposited amount ($294,750) significantly exceeds any reasonably expected income for Mr. Johnson's occupation and financial profile

ACCOUNT ACTIONS
Based on the suspicious activity and Mr. Johnson's failure to provide adequate explanations or documentation:
- Enhanced monitoring was implemented on February 25, 2024
- Account was restricted for cash deposits over $5,000 on March 15, 2024
- Decision made to close account on March 28, 2024
- Account closure letter sent to Mr. Johnson on March 28, 2024
- Account will be closed 30 days after notice per account agreement
- All deposits since March 15 have been declined

CONCLUSION
Based on the totality of circumstances—the systematic structuring of 31 cash deposits just below the CTR threshold across multiple branches, the gross inconsistency with the customer's stated income and employment, the lack of credible explanation for the source of funds, the demonstrated knowledge of reporting thresholds, and the timing patterns—the institution has concluded this activity represents deliberate structuring in violation of 31 U.S.C. § 5324 and potential money laundering. The institution has no reasonable legitimate explanation for this activity.

The large volume of unexplained cash, combined with the customer's unemployment status and systematic evasion of reporting requirements, suggests the funds may be proceeds from illegal activity. This SAR is filed to report the suspected structuring and to alert law enforcement to the potential underlying criminal activity generating these funds.

Example 2: Elder Financial Exploitation

SUSPICIOUS ACTIVITY REPORT NARRATIVE

This SAR is filed to report suspected financial exploitation of vulnerable adult Margaret Ellen Davis (DOB: 03/15/1938, SSN: XXX-XX-3456), age 86. Between February 1, 2024, and March 31, 2024, Ms. Davis's caregiver, Patricia Lynn Wilson (DOB: 07/22/1982, SSN: XXX-XX-7890), gained unauthorized access to Ms. Davis's accounts and systematically diverted $147,350 through suspicious wire transfers, ATM withdrawals, and checks made payable to Ms. Wilson, resulting in significant financial harm to this elderly customer.

CUSTOMER BACKGROUND
Margaret Davis has been a customer of our institution since 1987 (37 years). She maintains a checking account (Account #XXXX2345) with an average balance of $125,000 and a savings account (Account #XXXX2346) with a balance of approximately $275,000. Ms. Davis is a widow who receives monthly Social Security and pension deposits totaling approximately $4,200. Her typical account activity consists of:
- Monthly Social Security and pension direct deposits
- Occasional checks for routine living expenses (groceries, utilities, medical)
- Small debit card purchases
- Quarterly dividend deposits from investment accounts
- No wire transfer activity in the prior 10 years

Ms. Davis has never engaged in online banking, ATM transactions, or wire transfers. Her historical pattern showed responsible, conservative financial management consistent with a retired senior on a fixed income.

INTRODUCTION OF CAREGIVER
According to records obtained during our investigation, Patricia Wilson was hired through "HomeHelpers Care Services" in January 2024 to provide in-home care for Ms. Davis, who has been experiencing early-stage dementia and mobility limitations. Ms. Wilson's responsibilities were to include meal preparation, medication reminders, light housekeeping, and companionship. The care arrangement was coordinated by Ms. Davis's daughter, Susan Davis-Miller, who lives out of state.

SUSPICIOUS ACTIVITY DETECTED
On March 15, 2024, Ms. Davis's daughter, Susan Davis-Miller, contacted our Downtown Branch expressing concerns about her mother's account. Ms. Davis-Miller stated she had attempted to pay some of her mother's bills as she typically does and discovered insufficient funds, which was highly unusual. She requested account information and was alarmed to learn of significant recent withdrawals and transfers.

Upon Ms. Davis-Miller's inquiry, the branch manager conducted an immediate review of the account and identified the following suspicious activity that had occurred over the prior six weeks:

WIRE TRANSFERS (Total: $82,000)
February 5, 2024: $25,000 wire to "P. Wilson" at State Federal Bank, Account #XXXX8901
Wire reference: "Financial assistance for niece"

February 19, 2024: $30,000 wire to "Patricia L. Wilson" at Regional Credit Union, Account #XXXX5432
Wire reference: "Family loan"

March 8, 2024: $27,000 wire to "P.L. Wilson" at First Community Bank, Account #XXXX6789
Wire reference: "Gift"

All three wire transfers were initiated through telephone banking using Ms. Davis's customer identification number and date of birth. The wires were sent to accounts in Patricia Wilson's name at three different institutions. Voice recordings were reviewed and confirmed the caller was not Ms. Davis (different voice, no indication of age or speech patterns consistent with an 86-year-old customer).

ATM WITHDRAWALS (Total: $18,350)
Between February 3, 2024, and March 29, 2024, there were 37 ATM withdrawals from Ms. Davis's checking account, totaling $18,350. All withdrawals were for $500-$600 (daily ATM limit), occurring almost daily at ATM locations near Patricia Wilson's residence address (789 Maple Avenue), approximately 15 miles from Ms. Davis's home.

Ms. Davis had never used an ATM in her 37 years as a customer. Her debit card was issued in 2020 but showed no ATM activity until February 2024.

CHECKS PAYABLE TO PATRICIA WILSON (Total: $47,000)
February 12, 2024: Check #1234, $15,000, payee "Patricia Wilson," memo line "Loan"
February 26, 2024: Check #1235, $18,000, payee "Patricia Wilson," memo line "Help with expenses"
March 14, 2024: Check #1236, $14,000, payee "Patricia Wilson," memo line "Gift"

All three checks were deposited via mobile deposit into Ms. Wilson's account at Regional Credit Union. Check images show signatures that appear inconsistent with Ms. Davis's historical signature on file. The handwriting appears shaky and uncertain, and the signature lacks the consistent characteristics of Ms. Davis's signature on file from her account opening and other banking documents.

TOTAL DIVERSIONS TO CAREGIVER
Wire transfers to Wilson: $82,000
ATM withdrawals: $18,350
Checks payable to Wilson: $47,000
TOTAL: $147,350

RED FLAGS AND INDICATORS
This activity is suspicious and indicates likely elder financial exploitation for the following reasons:

Dramatic Change in Pattern: Ms. Davis's account activity was stable and predictable for 37 years. The sudden onset of wire transfers, ATM withdrawals, and large checks—all directed to or benefiting her caregiver—represents a radical and unexplained deviation from lifelong patterns.

Never Used These Services: Ms. Davis had never:
- Initiated a wire transfer in 37 years as a customer
- Used an ATM in 37 years as a customer
- Used telephone banking
- Written checks over $2,000 (her largest prior check was $1,850 for property taxes)

Position of Trust and Access: Patricia Wilson, as Ms. Davis's caregiver, had access to Ms. Davis's home, personal information, financial documents, and presumably her debit card and checkbook. Caregivers are in positions of trust that can be exploited to manipulate vulnerable seniors.

Cognitive Impairment: Ms. Davis has been diagnosed with early-stage dementia (per daughter's report and medical documentation provided). Individuals with cognitive impairment are particularly vulnerable to exploitation and may not fully understand the financial transactions they are being asked to authorize.

All Funds Directed to Caregiver: 100% of the suspicious transactions benefited Patricia Wilson exclusively. There is no indication of any funds being used for Ms. Davis's care, medical needs, or living expenses.

Isolation Tactics: According to Ms. Davis-Miller, when she attempted to speak with her mother by phone in late February and early March, Ms. Wilson answered and stated Ms. Davis was "napping" or "not feeling well enough to talk." Ms. Davis-Miller now suspects Ms. Wilson was deliberately limiting Ms. Davis's contact with family members who might have detected the financial exploitation sooner.

Implausible Explanations: The wire transfer references ("financial assistance for niece," "family loan," "gift") are implausible. Ms. Davis-Miller confirmed that Patricia Wilson is not a niece or family member. Ms. Davis has no history of making loans or large gifts, even to actual family members. The characterization of these transfers as family transactions appears designed to make them seem legitimate.

Questionable Check Signatures: The signatures on the three large checks made payable to Patricia Wilson are inconsistent with Ms. Davis's historical signature. The lack of signature consistency suggests possible forgery or signing under duress, coercion, or incapacity.

Telephone Banking Fraud: The wire transfers initiated via telephone banking were not made by Ms. Davis (voice recordings confirm different voice). This indicates Ms. Wilson used Ms. Davis's personal information to impersonate her and authorize fraudulent transfers.

Rapid Depletion of Funds: In just eight weeks, $147,350 was diverted from Ms. Davis's accounts, representing approximately 37% of her total liquid assets. This rapid depletion caused actual financial harm, leaving Ms. Davis with insufficient funds to pay her bills and threatening her financial security in retirement.

INSTITUTION INVESTIGATION
Upon learning of the suspicious activity from Ms. Davis-Miller on March 15, 2024, the institution immediately:

- Placed holds on both accounts to prevent further unauthorized transactions
- Disabled telephone banking access
- Cancelled Ms. Davis's debit card
- Reviewed all transaction history in detail
- Listened to recorded telephone banking calls for the wire transfers (confirmed caller was not Ms. Davis)
- Examined check images and compared signatures
- Interviewed branch staff (no staff recalled Ms. Davis coming to the branch; all checks were mobile deposits)
- Documented timeline of suspicious activity
- Consulted with BSA/AML and fraud investigation departments
- Advised Ms. Davis-Miller to contact Adult Protective Services and local law enforcement

FAMILY MEMBER STATEMENTS
Susan Davis-Miller provided the following information during multiple conversations with bank staff:

- Her mother has been diagnosed with mild cognitive impairment/early-stage dementia
- Ms. Davis becomes confused easily and has difficulty making decisions
- Patricia Wilson was hired through HomeHelpers Care Services in January 2024
- Ms. Wilson presented good references and background check
- Mother never mentioned making any loans or gifts to Patricia Wilson
- Mother has no history of making large gifts or loans to anyone, including family
- Mother is typically very cautious and conservative with money
- Ms. Davis-Miller typically assists with bill payments and monitors accounts with mother's permission; mother had not mentioned any financial changes
- When she finally spoke with her mother on March 16 (after bank placed holds), Ms. Davis seemed confused about the wire transfers and large checks, stating she "didn't remember" sending money to Patricia
- Ms. Davis stated Ms. Wilson had been "helping" her with banking but seemed uncertain about the details

VICTIM IMPACT
The unauthorized diversions have caused significant harm to Ms. Davis:
- Loss of $147,350 in liquid assets
- Insufficient funds to pay regular bills and living expenses
- Emotional distress and confusion
- Breach of trust by caregiver
- Potential impact on ability to afford future care needs
- Diminished financial security in vulnerable retirement years

REPORTS TO AUTHORITIES
At the institution's recommendation, Susan Davis-Miller has filed reports with:
- Adult Protective Services (APS Case #2024-0456)
- Local Police Department (Case #24-8901)
- HomeHelpers Care Services terminated Patricia Wilson's employment on March 16, 2024

ACCOUNT ACTIONS
The institution has taken the following protective actions:
- Placed immediate holds on accounts on March 15, 2024
- Disabled telephone banking and online banking access
- Cancelled and reissued debit card to daughter's address for safekeeping
- Blocked any transactions or access by Patricia Wilson
- Required in-person branch visit with identification for any future transactions
- Added Susan Davis-Miller as joint account holder with full access (with appropriate POA documentation)
- Provided exception to overdraft fees caused by the unauthorized transactions
- Issued provisional credits for the unauthorized wire transfers pending investigation
- Flagged account for ongoing monitoring

CONCLUSION
The totality of circumstances clearly indicates financial exploitation of a vulnerable elder customer. Patricia Wilson, in her position of trust as Ms. Davis's caregiver, systematically exploited Ms. Davis's cognitive impairment and trust to gain unauthorized access to accounts and divert $147,350 for her personal benefit over an eight-week period. The activity is completely inconsistent with Ms. Davis's 37-year account history and financial profile.

The wire transfers, ATM withdrawals, and checks all benefited the caregiver exclusively, with no apparent benefit to Ms. Davis. The use of telephone banking impersonation, questionable check signatures, and isolation tactics are consistent with elder financial exploitation typologies.

Ms. Davis, at age 86 and with diagnosed cognitive impairment, is a vulnerable adult who has suffered significant financial harm due to this exploitation. This SAR is filed to document the suspected elder financial abuse, support law enforcement investigation, and assist in potential criminal prosecution of Patricia Wilson.

Example 3: Business Email Compromise (BEC) Fraud

SUSPICIOUS ACTIVITY REPORT NARRATIVE

This SAR is filed to report a Business Email Compromise (BEC) fraud affecting commercial customer TechSolutions Inc. On April 10, 2024, TechSolutions' email system was compromised, resulting in a fraudulent wire transfer of $485,000 to a bank account in Hong Kong based on falsified payment instructions, consistent with BEC fraud typologies described in FinCEN Advisory FIN-2016-A005.

CUSTOMER BACKGROUND
TechSolutions Inc. (EIN: XX-XXXXXXX) is a software development company that has maintained commercial accounts with our institution since 2018. The company operates from 555 Innovation Drive, Tech City, ST 67890. TechSolutions maintains a business checking account (Account #XXXX5678) used for payroll, vendor payments, and operating expenses, with an average balance of $750,000.

The company's principal and CEO is Michael Chen. Other authorized signers include Sarah Johnson (CFO) and David Martinez (Controller). TechSolutions typically makes wire transfers 3-5 times per month for vendor payments, ranging from $10,000 to $150,000. All legitimate wire transfers have historically been to domestic recipients for software licensing, contractor payments, and business services.

TYPICAL WIRE TRANSFER PROCEDURES
Based on historical patterns and statements from TechSolutions management, the company's normal wire transfer procedures include:
- CFO (Sarah Johnson) receives invoice from vendor
- Invoice is reviewed and approved
- Controller (David Martinez) prepares wire transfer instructions
- CFO reviews and approves
- Wire instructions submitted to bank via secure online banking
- Wire requests include detailed vendor information and invoice references

FRAUDULENT WIRE TRANSFER
On April 10, 2024, at 2:47 PM, the institution received a wire transfer request through TechSolutions' online banking portal for $485,000. The wire transfer details were:

Amount: $485,000
Beneficiary: Global Tech Partners Limited
Beneficiary Bank: Hong Kong International Bank
Beneficiary Bank Account: XXXXXXXXXX
Bank Address: Central District, Hong Kong
Purpose: "Software licensing payment - Invoice #HTK-2024-089"

The wire transfer request was submitted using David Martinez's (Controller) online banking credentials. The request appeared to have proper dual authorization from Sarah Johnson's (CFO) credentials in accordance with the company's established procedures.

Based on the apparently proper authorization through the company's established online banking credentials and dual approval process, the wire transfer was processed and sent at 3:15 PM on April 10, 2024.

FRAUD DISCOVERY
On April 11, 2024, at 9:30 AM, Sarah Johnson (CFO) contacted the bank's wire transfer department to inquire about the status of a pending wire transfer for $75,000 to a software vendor. During the conversation, she was informed that the most recent wire from the account was the $485,000 wire processed the previous day to Global Tech Partners Limited in Hong Kong.

Ms. Johnson immediately stated that she did not authorize any wire to Hong Kong and that TechSolutions has no vendors or business relationships in Hong Kong. She stated she had not approved any wire transfers the previous day. Ms. Johnson requested immediate details about the wire and asked the bank to attempt to recall it.

INVESTIGATION OF COMPROMISE
The bank's fraud investigation team immediately contacted TechSolutions management and conducted a preliminary investigation. TechSolutions conducted an internal IT investigation and discovered the following:

EMAIL COMPROMISE
On April 9, 2024, the company's email system was compromised through a phishing attack. David Martinez (Controller) had clicked on a phishing email that appeared to be from Microsoft 365 asking him to verify his account credentials. By entering his username and password on the fraudulent website, Mr. Martinez unknowingly provided the attackers with access to his email account.

FRAUDULENT EMAIL COMMUNICATIONS
Between April 9, 2024 (evening) and April 10, 2024 (afternoon), the attackers used the compromised email account to:

1. Create a fraudulent email address that closely resembled the CEO's email: michael.chen@techsolutionsinc.com (legitimate) vs. michael.chen@tech-solutionsinc.com (fraudulent—note the added hyphen)

2. Sent email from fraudulent CEO address to David Martinez at 10:15 AM on April 10, 2024:
"David, We need to process an urgent wire transfer today for a new software licensing agreement with Global Tech Partners in Hong Kong. This is time-sensitive to finalize the deal. Sarah [CFO] is aware and has approved. Please process wire for $485,000 to the account details I'm sending in the next email. Thanks, Michael"

3. Sent follow-up email at 10:18 AM with wire transfer details for Global Tech Partners Limited at Hong Kong International Bank.

4. Sent email from another fraudulent address appearing to be Sarah Johnson (CFO): sarah.johnson@tech-solutionsinc.com (note the hyphen), confirming approval of the wire transfer.

COMPROMISED CREDENTIALS
The attackers, having gained access to David Martinez's email account, also obtained or reset his online banking credentials. The investigation revealed:
- Password reset request for online banking was initiated from David Martinez's email on April 10 at 12:30 PM
- New password was set using the email-based reset process
- Login to online banking occurred at 2:35 PM from IP address 185.220.XXX.XXX (traced to Eastern Europe)
- Wire transfer was initiated at 2:47 PM using Martinez's credentials

The dual authorization requirement was bypassed because the attackers also had access to email communications and were able to impersonate the CFO's approval through the fraudulent email, satisfying the internal approval procedures before the banking credentials were used.

RED FLAGS MISSED (IN RETROSPECT)
Upon review, several red flags were present that, in hindsight, may have indicated fraud:

New Beneficiary: Global Tech Partners Limited was a new beneficiary, with no history of wire transfers to this company or any Hong Kong recipients in the account's history.

High-Risk Jurisdiction: Hong Kong has been identified in FinCEN advisories as a jurisdiction frequently involved in BEC fraud schemes.

Urgency Language: The fraudulent email emphasized urgency ("urgent wire transfer today," "time-sensitive"), a common tactic in BEC fraud to pressure victims to act quickly without thorough verification.

Suspicious Email Address: The fraudulent email addresses contained a subtle variation (added hyphen) that could be easily missed.

IP Address Anomaly: The online banking login occurred from an IP address in Eastern Europe, a significant geographic departure from TechSolutions' normal access from their office location in Tech City, ST. However, this information was not flagged in real-time due to the company's lack of IP address restrictions on their online banking profile.

Large Amount: The $485,000 transfer was significantly larger than typical wire transfers for this customer (normal range: $10,000-$150,000).

ATTEMPTED RECALL
Upon learning of the fraud on April 11, 2024, the institution immediately:
- Contacted Hong Kong International Bank to request a recall of the wire (9:45 AM)
- Sent formal recall request via SWIFT
- Followed up with multiple phone calls to Hong Kong International Bank

Hong Kong International Bank responded on April 12, 2024, indicating:
- The beneficiary account received the funds on April 11, 2024
- Immediately upon receipt, the funds were transferred to multiple other accounts
- The beneficiary account was closed on April 11, 2024
- No funds remain available for return
- They have reported the account activity to Hong Kong authorities

As of the date of this SAR filing (April 18, 2024), no funds have been recovered. The $485,000 loss appears to be total.

LAW ENFORCEMENT REPORTS
TechSolutions Inc. has filed reports with:
- Local Police Department (Case #24-4567, filed April 11, 2024)
- FBI Internet Crime Complaint Center (IC3) (Complaint #24-XXXXX, filed April 11, 2024)
- FBI field office (investigator assigned)

TECHSOLUTIONS' REMEDIAL ACTIONS
Following the incident, TechSolutions has implemented the following enhanced security measures:
- Mandatory cybersecurity training for all employees
- Multi-factor authentication (MFA) required for all email accounts
- Enhanced email filtering and phishing detection
- Mandatory verbal verification (callback to known phone number) required for all wire transfers over $100,000 or to new beneficiaries
- IP address restrictions implemented on online banking profile
- Increased monitoring of email traffic
- Incident response plan developed

INSTITUTION'S ACTIONS
The institution has taken the following actions:
- Reported fraud immediately to internal fraud investigations unit
- Attempted wire recall through all available channels
- Provided TechSolutions with detailed transaction information for law enforcement
- Reviewed online banking access logs and provided to customer and law enforcement
- Temporarily suspended online wire transfer capability pending implementation of enhanced security measures
- Required TechSolutions to reset all online banking credentials
- Implemented additional verification procedures for TechSolutions wires: all wires must now be verified by phone callback to CFO at known number
- Reviewed other commercial customers' wire transfer procedures to identify similar vulnerabilities

CUSTOMER RELATIONSHIP IMPACT
TechSolutions has expressed concerns about the bank's processing of the fraudulent wire transfer without additional verification given the red flags present (new beneficiary, high-risk jurisdiction, large amount). However, TechSolutions acknowledges the wire was authorized using legitimate credentials and their internal approval appeared to be in order at the time of processing.

The institution and TechSolutions are working together to implement enhanced security measures to prevent future incidents. The account remains open with enhanced verification procedures in place.

TYPOLOGY ANALYSIS
This incident is consistent with the Business Email Compromise (BEC) fraud typology described in FinCEN Advisory FIN-2016-A005. Key characteristics present include:

- Compromise of business email account through phishing
- Impersonation of company executives (CEO, CFO)
- Spoofed email addresses with subtle variations
- Urgent language to pressure quick action
- Fraudulent wire transfer instructions to foreign account
- New beneficiary with no established business relationship
- Rapid movement of funds upon receipt (layering)
- Account closure after funds moved
- Use of high-risk jurisdiction (Hong Kong)
- Exploitation of legitimate wire transfer procedures and credentials

BEC fraud has resulted in billions of dollars in losses to businesses worldwide and represents one of the most significant cyber-enabled financial crimes affecting commercial accounts.

FINANCIAL IMPACT
TechSolutions Inc. has suffered a direct loss of $485,000. The company carries cyber insurance with a $100,000 deductible, so the net uninsured loss is $385,000. The company has indicated this loss will have significant impact on their operations and may affect their ability to meet payroll and vendor obligations in the coming months.

CONCLUSION
This SAR is filed to report a Business Email Compromise fraud resulting in a $485,000 fraudulent wire transfer from TechSolutions Inc. to a Hong Kong account controlled by cybercriminals. The fraud was accomplished through a phishing attack that compromised employee email credentials, impersonation of company executives, and use of compromised online banking credentials to initiate the fraudulent wire.

Despite the appearance of proper authorization at the time of processing, the wire was fraudulent and resulted in significant financial harm to the commercial customer. The funds were rapidly moved upon receipt and have not been recovered. This incident highlights the growing threat of BEC fraud targeting commercial accounts and the sophisticated tactics used by cybercriminals to exploit email systems and payment processes.

This SAR is filed to document the fraud, support law enforcement investigation, and contribute to FinCEN's efforts to track and analyze BEC fraud trends. The institution has cooperated fully with TechSolutions and law enforcement and has implemented additional safeguards to reduce the risk of similar incidents in the future.

Common Mistakes to Avoid

The Top 20 SAR Narrative Mistakes

1. Writing a One-Paragraph Narrative

Mistake: Trying to cram all information into a single dense paragraph.

Why It’s Wrong: Makes the narrative difficult to read and key information hard to find.

Solution: Use multiple focused paragraphs, each addressing a specific aspect of the activity.

2. Being Too Vague

Mistake: “The customer made multiple deposits over a period of time and engaged in suspicious activity.”

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

Solution: Be specific: “The customer made 27 cash deposits totaling $263,450 over 13 weeks, each structured between $8,500 and $9,900.”

3. Failing to Explain Why Activity Is Suspicious

Mistake: Describing transactions without explaining what makes them suspicious.

Why It’s Wrong: Law enforcement cannot determine if investigation is warranted.

Solution: Dedicate a section to explaining red flags, deviations from norms, and why suspicion is reasonable.

Mistake: “This is money laundering” or “The customer is guilty of fraud.”

Why It’s Wrong: Financial institutions report suspicions, not guilt. Legal conclusions are for law enforcement and courts.

Solution: “The activity is consistent with money laundering typologies” or “The pattern suggests potential fraud.”

5. Including Too Much Irrelevant Detail

Mistake: Including entire account histories, unrelated transactions, or excessive background information.

Why It’s Wrong: Buries important information and wastes reviewer time.

Solution: Focus on information directly relevant to the suspicious activity. Summarize historical information briefly.

6. Not Providing Subject Identifiers

Mistake: Filing SAR with minimal subject information (only name and partial address).

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

Solution: Include all available identifiers: full name, DOB, SSN/TIN, address, phone, email, driver’s license, etc.

7. Using Only Generic Activity Categories

Mistake: Checking only “Other” or very general categories.

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

Solution: Select the most specific applicable categories that accurately describe the activity.

8. Incorrect Date Ranges

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

Why It’s Wrong: Misrepresents when the activity occurred.

Solution: Part II should reflect when the suspicious activity actually occurred, not when it was discovered or investigated.

9. Wrong Total Amount

Mistake: Reporting only one transaction instead of aggregating all related suspicious activity.

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

Solution: Aggregate all related suspicious transactions during the activity period.

10. No Comparison to Expected Activity

Mistake: Describing activity without explaining how it deviates from the customer’s profile or expected behavior.

Why It’s Wrong: Reviewer cannot determine if the activity is actually unusual for this customer.

Solution: Always include: (1) what was expected based on customer profile, and (2) how actual activity deviated.

11. Relying on Template Language

Mistake: Using boilerplate template language that doesn’t describe the specific case.

Why It’s Wrong: Narratives read as generic and unconvincing; important case-specific details are missing.

Solution: Customize every narrative to the specific facts of the case. Templates can provide structure, but content must be case-specific.

12. Not Documenting Investigation Steps

Mistake: Failing to describe what investigation was conducted.

Why It’s Wrong: No documentation of the institution’s reasonable basis for suspicion and due diligence.

Solution: Describe databases searched, inquiries made, customer contacts attempted, and conclusions reached.

13. Including Speculation

Mistake: “The customer is probably involved in drug trafficking.”

Why It’s Wrong: Speculation without factual basis undermines the SAR’s credibility.

Solution: State only facts. If connecting to known typologies, state: “The pattern is consistent with [typology] as described in FinCEN guidance.”

14. Poor Grammar and Spelling

Mistake: Narratives with typos, grammatical errors, and poor sentence structure.

Why It’s Wrong: Reduces credibility and professionalism; may cause confusion about facts.

Solution: Use spell-check, grammar-check, and have a second person review before filing.

15. No Timeline or Chronology

Mistake: Presenting information in random order without regard to when events occurred.

Why It’s Wrong: Difficult to follow the sequence of events and understand how the activity developed.

Solution: Organize information chronologically or use dates consistently throughout.

16. Burying the Lead

Mistake: Starting with extensive background and account opening details before describing the suspicious activity.

Why It’s Wrong: Reviewer must read through pages of information to understand what the SAR is about.

Solution: Start with a concise summary of the suspicious activity, then provide supporting details.

17. Not Referencing Prior SARs

Mistake: Failing to note that prior SARs have been filed on the same subject or activity.

Why It’s Wrong: Breaks the connection between related SARs, making pattern analysis difficult.

Solution: Always reference prior SAR BSA ID numbers for the same subject or related activity.

18. Inconsistent Information

Mistake: Providing dates or amounts in the narrative that don’t match the structured data fields.

Why It’s Wrong: Creates confusion and raises questions about accuracy.

Solution: Carefully verify that narrative information matches Part II fields.

19. Including Opinions About Guilt

Mistake: “The customer is obviously a criminal” or “This person is guilty.”

Why It’s Wrong: Financial institutions report suspicions, not determinations of guilt.

Solution: Maintain objective tone. Focus on facts and red flags, not judgments about the person’s character or guilt.

20. Not Explaining Technical Terms

Mistake: Using industry jargon, acronyms, or technical terms without explanation.

Why It’s Wrong: Law enforcement reviewers may not be familiar with banking terminology.

Solution: Either use plain language or briefly define technical terms when first used.

Quality Review Checklist

Pre-Filing Quality Review

Before filing any SAR, complete this quality review checklist to ensure the narrative meets best practice standards.

Content Completeness

  • WHO: All subjects fully identified with maximum available identifiers
  • WHAT: Specific description of suspicious transactions or conduct
  • WHEN: Specific dates or date ranges clearly stated
  • WHERE: Locations of activity documented
  • WHY: Clear explanation of why activity is suspicious

Subject Information

  • Full legal name(s) provided
  • All known aliases or AKAs included
  • Date of birth (for individuals)
  • SSN/TIN/EIN provided
  • Complete current address
  • Phone numbers and email addresses
  • Driver’s license or government ID number
  • Occupation or business type
  • All relevant account numbers listed

Transaction Details

  • Specific dates for key transactions
  • Exact dollar amounts (not vague descriptions)
  • Transaction types specified (cash, wire, check, etc.)
  • Instruments described
  • Source of funds documented (when known)
  • Destination of funds documented
  • Total amount correctly aggregated

Narrative Structure

  • Opening summary provides clear overview
  • Organized in logical structure
  • Information presented chronologically when appropriate
  • Focused paragraphs (one topic per paragraph)
  • Appropriate length (sufficient detail without excess)
  • Headings used if helpful for complex cases

Red Flags and Analysis

  • Specific red flags identified and explained
  • Comparison to expected activity provided
  • Deviation from customer profile explained
  • Pattern analysis included (when applicable)
  • Typology references included (when applicable)
  • Clear explanation of why activity lacks legitimate explanation

Investigation Documentation

  • Investigation steps documented
  • Database searches described
  • Customer inquiries noted (if any)
  • Responses or lack of responses documented
  • Enhanced due diligence described
  • Timeline of detection and investigation provided

Institutional Actions

  • Date activity was detected
  • Account actions taken (restrictions, closure, monitoring)
  • Prior SARs referenced by BSA ID number (if applicable)
  • Continuing activity indicated (if applicable)
  • Enhanced monitoring plans noted

Writing Quality

  • Plain language used (no unnecessary jargon)
  • Active voice predominates
  • Specific, not vague language
  • No spelling errors
  • No grammatical errors
  • Professional, objective tone
  • No conclusory legal statements
  • No speculation without factual basis
  • No discriminatory language or profiling

Prohibited Content Avoided

  • No reference to SAR filing or that customer is subject of SAR
  • No statements of guilt or legal conclusions
  • No irrelevant personal information
  • No speculation unsupported by facts
  • No proprietary detection methods revealed
  • No confidential law enforcement information
  • No discriminatory language

Consistency Check

  • Narrative dates match Part II date range
  • Narrative amounts match Part II total amount
  • Subject information consistent between Parts I and V
  • Activity categories match narrative description
  • All statements internally consistent

Supporting Documentation

  • Key transaction records available
  • Investigation work papers complete
  • Customer due diligence documents on file
  • Ready for 5-year retention
  • Organized for easy retrieval

Reviewer Sign-Off

Preparer: _____________________________ Date: _____________

Reviewer: ____________________________ Date: _____________

Reviewer Comments:




Approved for Filing: [ ] Yes [ ] No - Revisions Needed


Document Version: 2.0 Last Updated: February 20, 2024 Next Review Date: February 20, 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 narratives comply with all applicable laws and regulations and meet law enforcement needs.