Suspicious activity reports by banks under 31 CFR 1020.320, explained

A bank must report suspicious transactions of at least $5,000 within 30 calendar days of first detecting facts that may support a filing, or 60 days at most when no suspect is identified, keep the report confidential and retain it for five years.

What triggers a filing

Every bank must file with the Treasury Department a report of any suspicious transaction relevant to a possible violation of law or regulation, to the extent the rule requires. A transaction must be reported if it is conducted or attempted by, at or through the bank, involves or aggregates at least $5,000 in funds or other assets, and the bank knows, suspects or has reason to suspect that [1]:

  • it involves funds derived from illegal activities, or is intended or conducted to hide or disguise such funds as part of a plan to violate or evade federal law or a transaction reporting requirement;
  • it is designed to evade any requirement of FinCEN’s regulations or other Bank Secrecy Act regulations; or
  • it has no business or apparent lawful purpose or is not the sort in which the customer would normally be expected to engage, and the bank knows of no reasonable explanation after examining the available facts.

A bank may also file voluntarily on activity it believes is relevant to a possible violation even when the rule does not require a report. Two exceptions apply: a robbery or burglary reported to the appropriate law enforcement authorities, and lost, missing, counterfeit or stolen securities reported under 17 CFR 240.17f-1 [1].

The October 2025 FAQs address one common question about the evasion test. A transaction or series of transactions at or near the $10,000 currency transaction report threshold is not, on its own, enough to require a SAR. A filing is required only if the bank knows, suspects or has reason to suspect the activity is designed to evade reporting [2].

The banking agencies’ parallel thresholds

The agencies’ own rules sit alongside FinCEN’s, and the FAQs list them [2]. The OCC’s rule for national banks, for example, sets four filing triggers. Three cover known or suspected federal criminal violations: insider abuse involving any amount where the bank has a substantial basis for identifying an insider; violations aggregating $5,000 or more where the bank has a substantial basis for identifying a possible suspect; and violations aggregating $25,000 or more regardless of potential suspects. The fourth covers transactions aggregating $5,000 or more that involve potential money laundering or violate the Bank Secrecy Act [3].

The 30-day and 60-day clock

A bank must file a SAR no later than 30 calendar days after the date of initial detection of facts that may constitute a basis for filing. If no suspect was identified on the date of detection, the bank may delay filing for an additional 30 calendar days to identify one. In no case may reporting be delayed more than 60 calendar days after the date of initial detection of a reportable transaction [1].

For violations that require immediate attention, such as ongoing money laundering schemes, the bank must also immediately notify an appropriate law enforcement authority by telephone, in addition to filing a timely SAR [1].

The rule measures the deadline from the date of initial detection of facts that may constitute a basis for filing [1]. In our view, an alert-to-case workflow should record that date as a field that cannot be overwritten, because every filing deadline is counted from it. That is a practice point, not a requirement of the rule.

Continuing activity

The rule itself says nothing about repeat filings on the same customer. On October 9, 2025, FinCEN, the Federal Reserve, the FDIC, the NCUA and the OCC issued joint FAQs on SAR requirements that cover continuing activity among other topics. They state that the answers do not alter existing Bank Secrecy Act legal or regulatory requirements or establish new supervisory expectations [2].

  • No separate review is required. FinCEN suggested in October 2000 that institutions report continuing suspicious activity at least every 90 days. The FAQs say a bank is not required to conduct a separate review, manual or otherwise, of a customer or account after filing a SAR. It may instead rely on risk-based policies, procedures and controls reasonably designed to identify and report such activity [2].
  • The optional timeline. For a bank that elects to follow FinCEN’s continuing activity guidance, the FAQs give this sequence where a subject is identified: day 0, detection; day 30, initial SAR; day 120, end of the 90-day period; day 150, SAR for continued activity. Where no subject is identified and the initial SAR is filed at day 60, each later date moves out by 30 days [2].
  • No-file decisions. There is no requirement or expectation to document a decision not to file. In most cases, the FAQs say, a short statement will likely suffice if a bank chooses to document one [2].

Confidentiality and the safe harbor

A SAR, and any information that would reveal its existence, is confidential. No bank, and no director, officer, employee or agent of a bank, may disclose it except as the rule allows. A bank that is subpoenaed or otherwise asked to disclose a SAR must decline, cite the rule and 31 U.S.C. 5318(g)(2)(A)(i), and notify FinCEN of the request and its response [1].

Provided no person involved in the reported transaction is told it was reported, the rule permits [1]:

  • disclosure of a SAR to FinCEN, law enforcement, a federal regulator that examines the bank for Bank Secrecy Act compliance, or a state regulator with that role;
  • disclosure of the underlying facts, transactions and documents, including to another financial institution to prepare a joint SAR, and in certain employment references or termination notices as 31 U.S.C. 5318(g)(2)(B) allows; and
  • sharing a SAR within the bank’s corporate organizational structure for purposes consistent with the Bank Secrecy Act, as determined by regulation or guidance.

Government authorities are bound too: they may disclose a SAR only as necessary to fulfill official duties consistent with the Bank Secrecy Act, which excludes responding to a request for non-public information or for use in a private legal proceeding [1]. A bank and its people are protected from liability for a SAR disclosure, or for not notifying the person named in it, to the full extent of 31 U.S.C. 5318(g)(3) [1].

Records and examination

A bank must keep a copy of each SAR and the original or business record equivalent of the supporting documentation for five years from the filing date. The supporting documentation must be identified and kept as such, and is deemed filed with the SAR. The bank must make it available on request to FinCEN, law enforcement, its federal regulator, and a state regulator that oversees its Bank Secrecy Act compliance [1].

Banks are examined by FinCEN or its delegatees for compliance with the rule. A failure to meet it may be a violation of the Bank Secrecy Act and of FinCEN’s rules, and may also violate provisions of title 12 of the Code of Federal Regulations [1].

Status

As checked on November 14, 2026, the eCFR text of 31 CFR 1020.320, which eCFR showed as up to date as of November 12, 2026, reads as described above; its source note cites 75 FR 65812 (October 26, 2010), as amended at 76 FR 10517 (February 25, 2011) [1].

This explainer describes the rule; it is not legal advice, and organizations should confirm with counsel how it applies to them.

Moraph’s teams help organizations with work like this. See our solutions.

Spotted an error? Tell us and we will check it and correct the explainer where needed.

  • FinCEN
  • Bank Secrecy Act
  • SAR
  • 31 CFR 1020.320
  • AML
  • OCC
  • continuing activity