Get ahead before the holidays. Individual webinars are $149 throughout October. *Pricing automatically applied in cart.

What types of transactions must financial institutions report under the Bank Secrecy Act?

Short Answer

Financial institutions must report currency transactions exceeding a specified threshold, suspicious activities that may indicate money laundering or other financial crimes, and certain international fund transfers. These reporting obligations help government agencies detect and investigate illicit financial activity.

Comprehensive Answer

The Bank Secrecy Act (BSA) reporting framework is built around a few distinct report types, each with its own trigger, content, and handling rules. Understanding how these differ in practice helps compliance teams avoid both under-reporting and unnecessary filings.

Currency Transaction Reports

A Currency Transaction Report (CTR) is triggered by physical currency, meaning coin and paper money, moving in or out of the institution above the regulatory threshold in a single business day. Checks, wire transfers, and card transactions are not currency and do not count toward it.

  • Aggregation: Multiple currency transactions conducted by or on behalf of the same person on the same business day are treated as one transaction. A customer who makes several deposits at different branches or ATMs may therefore require a CTR even though no single deposit exceeds the threshold.
  • Cash in and cash out: Deposits and withdrawals are generally totaled separately by direction rather than netted against each other.
  • Identification: The filing must identify the person conducting the transaction and the person or entity on whose behalf it is conducted, which can differ.
  • Exemptions: Certain established customers may be exempted from CTR filing under defined procedures, but the exemption requires documented eligibility and periodic review. It is not automatic.

CTRs are filed based on facts, not suspicion. Staff should not decide whether a transaction seems legitimate before filing one.

Suspicious Activity Reports

A Suspicious Activity Report (SAR) is judgment-based. Institutions file when they know, suspect, or have reason to suspect that a transaction or pattern involves funds from illegal activity, is designed to evade BSA requirements, has no apparent lawful or business purpose, or involves use of the institution to facilitate criminal activity. Dollar thresholds apply in various circumstances, but the analysis centers on the behavior rather than the amount alone.

Common patterns that prompt review

  • Structuring: breaking up cash transactions to stay beneath the CTR threshold. Structuring is itself unlawful, even if the underlying money is legitimate.
  • Rapid movement of funds through an account with little other activity.
  • Transactions inconsistent with a customer's known business or profile.
  • Reluctance to provide identifying information or unusual interest in avoiding reporting.
  • Insider activity, such as an employee assisting a customer in evading controls.

Confidentiality

SAR confidentiality is a core requirement. An institution generally may not disclose that a SAR was filed, or reveal information that would show one exists, to the subject of the report or to unauthorized parties. A CTR carries no comparable secrecy rule, and customers may be told that a CTR is required.

Cross-Border Reporting

International obligations take more than one form, and they fall on different parties.

  • Cross-border transport of currency or monetary instruments: Persons, including institutions, who physically transport, mail, or ship currency or certain monetary instruments above a set amount into or out of the United States must file a report. This is filed by the transporter or recipient, not only by banks.
  • Foreign financial account reporting: U.S. persons with financial interests in or signature authority over foreign accounts above a specified aggregate value must report them. Institutions should recognize this obligation when advising or onboarding customers, even though the filing duty belongs to the account holder.
  • Funds transfer recordkeeping: Beyond reporting, institutions must collect and pass along specified information on certain funds transfers. These are recordkeeping and transmittal requirements rather than filings, but examiners treat them as part of the same program.

Reporting Versus Recordkeeping

Teams sometimes conflate the two. Many BSA obligations require retaining records, such as purchases of monetary instruments with cash or funds transfer details, without triggering a report to the government. Those records must be retrievable on request. A strong program maps each product and transaction type to either a filing duty, a recordkeeping duty, or both.

Edge Cases and Practical Controls

  • Non-bank businesses: Money services businesses, casinos, and certain other entities have their own BSA obligations, with differing thresholds and report formats. Do not assume bank rules apply unchanged.
  • Joint and third-party activity: When someone deposits cash into another person's account, both parties may need to be identified.
  • Continuing activity: Suspicious conduct that persists generally calls for ongoing monitoring and follow-up filings rather than a single report.
  • Documentation of non-filing: When an alert is reviewed and no SAR is filed, record the reasoning. Examiners often test the quality of these decisions.

Building a Defensible Process

  1. Map every product and channel to its reporting and recordkeeping triggers.
  2. Configure systems to aggregate currency activity across accounts, branches, and related parties.
  3. Establish an escalation path from frontline staff to a designated compliance officer.
  4. Track filing timeframes and retain copies and supporting documentation for the required period.
  5. Train staff by role, including how to avoid tipping off a SAR subject.
  6. Test the program independently and correct gaps promptly.

Because thresholds, forms, and timeframes are set by regulation and can be amended, always confirm specifics against the governing rules and your regulator's guidance before finalizing procedures.