AML Reporting Essentials: STR, CTR and SAR Made Simple

What makes a transaction suspicious? Who is responsible for reporting it? And what happens after suspicious activity is identified?

This lecture introduces the fundamentals of Suspicious Transaction Reports (STRs) and explains how financial institutions identify, investigate, document, and report potentially suspicious activity linked to money laundering, terrorist financing, and other financial crimes.

In This Lecture, You Will:

▸ Understand the meaning of a suspicious transaction and the types of activity that may raise concern

▸ Identify common suspicious transaction indicators, including activity inconsistent with a customer's profile, transactions without an apparent economic or lawful purpose, unusual cash activity, complex transaction patterns, and high-risk jurisdictions or individuals

▸ Understand the purpose of a Suspicious Transaction Report (STR) and how it helps alert authorities to potential financial crime

▸ Follow the typical STR filing process, from identification and investigation through documentation, reporting, follow-up, and ongoing monitoring

▸ Understand what information an STR generally contains, including details about the reporting entity, parties involved, suspicious activity, and supporting information

▸ Identify the role of the Financial Intelligence Unit (FIU) in receiving and analyzing suspicious transaction reports

▸ Understand who is responsible for filing an STR and how compliance, AML, and financial crime departments support the reporting process

▸ Recognize the role of frontline employees, including tellers and relationship managers, in identifying and escalating suspicious activity

▸ Explore a sample STR form and understand the key information required when reporting suspicious activity

▸ Understand why effective AML/CFT policies, procedures, employee training, systems, and controls are essential for detecting and reporting suspicious transactions

Resources Covered

• Financial Intelligence Unit (FIU) reporting framework

• Sample Suspicious Transaction Report (STR) form

• STR form available through the lecture resources

Who This Lecture Is For

• AML and compliance professionals

• Compliance and financial crime analysts

• Banking and financial services professionals

• Tellers and relationship managers

• Employees involved in AML/CFT controls and suspicious activity escalation

• Business users who need to understand suspicious transaction reporting

Why This Matters

Suspicious activity can be identified at different points across a financial institution. Frontline and business teams may be the first to notice unusual customer behavior or transaction patterns.

Understanding STR reporting helps business users:

• Recognize common suspicious transaction red flags

• Understand when activity should be escalated to AML/compliance teams

• Follow the institution's suspicious activity reporting process

• Understand the information required for an STR

• Support effective AML and counter-terrorist financing (CFT) controls

• Understand how suspicious activity moves from detection and investigation to regulatory reporting

Stop Confusing CTRs With Suspicious Transaction Reports

What exactly triggers a Currency Transaction Report (CTR)? Does every large transaction require suspicion? How do multiple cash transactions on the same day affect the reporting threshold? And when can a CTR and a SAR/STR apply to the same activity?

This lecture breaks down CTR reporting in practical terms — covering cash thresholds, aggregation, structuring, reporting obligations, and the critical difference between a CTR and SAR/STR. It also compares the reporting frameworks used in the United States and India, making the concepts easier to apply in real-world AML compliance situations.

In This Lecture, You Will:

▸ Understand what a Currency Transaction Report (CTR) is and why mandatory cash transaction reporting exists

▸ Identify when a CTR filing obligation is triggered, including the US$10,000 threshold in the United States and ₹10 lakh threshold in India

▸ Distinguish physical cash transactions from wire transfers, card payments, checks, and other non-cash transactions

▸ Apply the cash aggregation rule by combining multiple cash transactions conducted by the same customer within a single business day

▸ Recognize the difference between aggregation and structuring, including how deliberate transaction splitting can be used to avoid reporting requirements

▸ Understand how structuring can become relevant to suspicious transaction reporting when patterns emerge across days, weeks, or months

▸ Compare a threshold-based CTR with a suspicion-based SAR/STR, including their different purposes and reporting triggers

▸ Determine when a CTR and SAR/STR can apply independently or simultaneously to the same transaction or activity

▸ Understand who is responsible for CTR reporting, including financial institutions and relevant reporting entities

▸ Explore the US and Indian reporting frameworks, including BSA, FinCEN, Form 112, BSA e-filing, PMLA, and FIU India

Why This Lecture Matters

Large cash transactions can create mandatory reporting obligations even when there is no suspicion of wrongdoing. At the same time, deliberately structured transactions may require a completely different compliance response.

Understanding the difference helps business and financial services teams:

• Recognize CTR reporting triggers

• Apply cash aggregation rules correctly

• Distinguish legitimate large cash activity from potential structuring

• Understand when SAR/STR reporting may also be required

• Avoid treating CTR and SAR/STR as interchangeable reports

Who This Lecture Is For

• AML and compliance professionals

• Compliance analysts and financial crime teams

• Banking and financial services professionals

• Business users involved in cash transaction processing

• Professionals who need to understand CTR, SAR/STR, cash reporting, aggregation, and structuring

No separate technology is required to understand the core concepts. The lecture also introduces the relevant reporting systems and frameworks, including FinCEN, Form 112, the BSA e-filing system, PMLA, and FIU India.

A Suspicious Activity Report (SAR) is more than a regulatory form — it is a critical AML reporting and financial crime intelligence tool. This lecture explains how SARs help regulators and law enforcement connect activity across financial institutions and identify patterns linked to money laundering, fraud, and terrorist financing.

In This Lecture, You Will:

▸ Understand what a SAR is and why suspicious activity reporting exists

▸ Understand how SARs help connect financial activity across banks and other institutions through FinCEN

▸ Identify the types of institutions subject to SAR reporting, including banks, financial institutions, money services businesses (MSBs), broker-dealers, mutual funds, insurance companies, mortgage lenders, and investment advisors

▸ Recognize what an MSB is and understand why remittance providers, currency exchange businesses, and money transfer agents are relevant to AML reporting

▸ Understand the principles of safe harbor and tipping off, including why SAR confidentiality is essential

▸ Identify when a SAR should be filed based on suspicion of illegal activity, rather than proof of wrongdoing

▸ Apply key SAR reporting thresholds, including the $5,000 threshold for banks and the $2,000 threshold for MSBs

▸ Recognize situations where different SAR rules apply, including insider activity, transactions of $25,000 or more with no identifiable suspect, and terrorist financing, where there is no minimum threshold

▸ Understand SAR filing timelines, including the standard 30-day filing period, the potential extension to 60 days when a suspect cannot be identified, and the 90-day continuing SAR requirement for ongoing suspicious activity

▸ Distinguish SAR reporting from CTR reporting and understand when both reports may be required for the same transaction

▸ FinCEN as the central system for receiving and analyzing SARs

▸The SAR reporting system used to submit suspicious activity information to FinCEN

Who This Lecture Is For

• AML and compliance professionals

• Compliance analysts and financial crime teams

• Banking and financial services professionals

• Money services business professionals

• Professionals involved in AML monitoring, suspicious activity reporting, and regulatory compliance

• Business users who need to understand when suspicious activity requires escalation and reporting

Why This Matters

Understanding SAR filing requirements helps business teams recognize when activity may require escalation rather than treating suspicious activity as an ordinary transaction.

The lecture provides practical clarity on:

• SAR thresholds and exceptions

• Reasonable suspicion vs proof of wrongdoing

• SAR filing deadlines

• Tipping-off restrictions and confidentiality

• Continuing SAR requirements

• The relationship between SAR and CTR reporting

This helps support timely escalation, consistent AML decision-making, and effective financial crime compliance.

When can a CTR and SAR/STR apply to the same activity? This lecture brings the three reporting concepts together through practical scenarios involving cash aggregation, structuring, and suspicious activity.

A real-world example demonstrates how a bank can have an automatic CTR reporting obligation while separately identifying a pattern that supports SAR filing for suspected structuring. The same concepts are then applied to India through CTR and STR reporting to FIU India.

In This Lecture, You Will:

▸ Apply the difference between CTR, SAR, and STR to practical transaction scenarios

▸ Understand how cash aggregation can automatically trigger a CTR when the applicable threshold is exceeded

▸ Recognize how repeated transaction patterns can indicate structuring and create a separate suspicious activity reporting obligation

▸ Distinguish between the fact captured by a CTR and the suspicion or intent captured through a SAR/STR

▸ Understand why filing a CTR does not replace a SAR/STR, and why both reports may be required for the same activity

▸ Compare the US and Indian approaches to threshold-based and suspicion-based reporting

▸ Understand the role of FIU India in receiving STRs and the reporting timeline described for suspicious activity

▸ Recognize how different jurisdictions use different terminology — SAR in the United States and United Kingdom, and STR in India — while serving a similar suspicious activity reporting purpose

▸ Use a simple framework to remember the distinction: a CTR focuses on scale, while a SAR/STR focuses on suspicion and judgment

Frameworks Covered

• FIU India reporting framework

• PMLA framework

• FATF global AML standards

• CTR, SAR and STR reporting concepts across the United States, India, and United Kingdom

Who This Lecture Is For

• AML and compliance professionals

• Financial crime and compliance analysts

• Banking and financial services professionals

• Professionals working with transaction monitoring and regulatory reporting

• Business users who need to understand CTR, SAR, STR, structuring, and AML reporting obligations

Why This Matters

The distinction between these reports is critical when handling large or unusual cash activity. A transaction can trigger a CTR based on its amount, while the broader pattern may separately require SAR/STR reporting because of suspected structuring or other suspicious activity.

This lecture helps business users:

• Understand CTR vs SAR vs STR

• Recognize when reporting obligations can apply simultaneously

• Understand the difference between threshold-based reporting and suspicion-based reporting

• Identify how transaction patterns can reveal structuring and deliberate reporting evasion

• Understand how these reporting mechanisms work together to provide regulators and law enforcement with a broader view of financial activity