August 10, 2026

SAR Filing Requirements and Deadlines in 2026

Axle Team

Key takeaways

The core SAR filing requirements have not changed: banks file on suspicious transactions of $5,000 or more, within 30 calendar days of initial detection — 60 if no suspect is identified.
The October 2025 interagency FAQs retired two long-standing de facto expectations: the separate 90-day continuing activity review, and documenting decisions not to file.
Proximity to the $10,000 CTR threshold is not, by itself, enough to require a SAR — structuring requires knowledge, suspicion, or reason to suspect intent to evade.
The clock runs from initial detection of facts, not from when an investigator opens the case. Triage lag is the most common self-inflicted timeliness failure.

SAR filing requirements in brief: banks must file within 30 calendar days of initially detecting facts that may constitute a basis for filing; if no suspect is identified, filing may be delayed up to 60 days. The threshold is $5,000 for banks ($2,000 for most money services businesses), filed through FinCEN's BSA E-Filing System, with records retained five years.

SAR filing requirements: thresholds and triggers

Under 31 CFR 1020.320, a bank must report a transaction conducted or attempted by, at, or through it that involves or aggregates at least $5,000 and that the bank knows, suspects, or has reason to suspect involves funds from illegal activity, is designed to evade BSA requirements, has no business or apparent lawful purpose, or facilitates criminal activity. Most money services businesses report at $2,000 under 31 CFR 1022.320.

SARs are filed electronically through FinCEN's BSA E-Filing System. The filing and supporting documentation must be retained for five years, and the existence of a SAR cannot be disclosed to the subject — confidentiality is a statutory obligation, not a courtesy.

Deadlines: the 30/60-day clock and what starts it

"A bank is required to file a SAR no later than 30 calendar days after the date of initial detection by the bank of facts that may constitute a basis for filing a SAR. If no suspect was identified on the date of the detection of the incident requiring the filing, a bank may delay filing a SAR for an additional 30 calendar days to identify a suspect. In no case shall reporting be delayed more than 60 calendar days after the date of initial detection of a reportable transaction."
— 31 CFR 1020.320(b)(3)

"Initial detection" is not necessarily the alert date, and it is not the day the investigation concludes. It is the point at which the institution becomes aware of facts that may constitute a basis for filing — in most programs, that lands somewhere in triage. For ongoing schemes requiring immediate attention, the regulation also requires immediate telephone notification to law enforcement in addition to a timely SAR.

The deadlines at a glance:

Suspect identified at detection — 30 calendar days from initial detection (31 CFR 1020.320)
No suspect identified — up to 60 calendar days from initial detection (31 CFR 1020.320)
Continuing activity (elective FinCEN timeline) — 90-day review period; continuing SAR filed by day 150 after initial detection (Oct. 2025 interagency FAQs)
Ongoing violations requiring immediate attention — immediate telephone notice to law enforcement, plus a timely SAR (31 CFR 1020.320)
Record retention — 5 years from date of filing (31 CFR 1020.320)

What the October 2025 interagency FAQs changed

On October 9, 2025, FinCEN and the federal banking agencies issued joint FAQs aimed at cutting low-value filing work. They do not alter the regulation — the agencies say so explicitly — but they retire two expectations that had hardened into exam practice.

First, the post-SAR lookback. FinCEN's October 2000 suggestion to re-report continuing activity every 90 days had, over 25 years, turned into a de facto mandatory review queue. The FAQs are blunt about it:

"A financial institution is not required to conduct a separate review—manual or otherwise—of a customer or account following the filing of a SAR to determine whether suspicious activity has continued."
— FinCEN, Federal Reserve, FDIC, NCUA, and OCC, SAR FAQs, Oct. 9, 2025

Institutions may instead rely on risk-based policies, procedures, and controls. For those that keep the elective continuing activity cadence, the FAQs restate the timeline:

Day 0 — detection of facts that may constitute a basis for filing
Day 30 — initial SAR filed
Day 120 — end of the 90-day review period
Day 150 — SAR filed for continued suspicious activity

Second, no-file documentation. The FAQs settle a question that has consumed real analyst hours for years:

"There is no requirement or expectation under the BSA or its implementing regulations for a financial institution to document its decision not to file a SAR."
— SAR FAQs, Oct. 9, 2025

The FAQs also confirm that transactions at or near the $10,000 CTR threshold are not, on their own, sufficient to require a SAR — structuring still requires knowledge, suspicion, or reason to suspect intent to evade. A short, concise statement remains a reasonable practice for close no-file calls, but it is now clearly a risk decision, not a regulatory mandate.

Practitioner note: the tempting move after the October FAQs is to delete the 90-day review queue and bank the analyst hours. The better trade is repointing some of them at detection-date discipline. In most SAR timeliness findings, the model was not late and the writer was not slow — the case sat in a triage queue for two or three weeks before anyone documented the facts, and the institution then argued about when the clock started. Examiners test timeliness from the case file. Fixing intake dating buys more defensibility than any downstream automation.

SAR filing requirements are, operationally, a throughput problem: the deadline pressure sits in investigation and narrative-writing time. That is the job of Sam, Axle's SAR agent, which drafts evidence-cited narratives from case data — and it compounds with Rose on alert triage upstream. The ROI calculator puts numbers on the deadline-risk side of the case.

FAQ

When does the 30-day SAR clock start?

At initial detection — when the institution becomes aware of facts that may constitute a basis for filing. That is not necessarily the date an automated alert fires; it is when review identifies such facts. Programs should record that date explicitly in the case file, because examiners test timeliness against it.

Do I have to file a SAR for every alert my monitoring system generates?

No. Alerts are leads, not filings. The obligation attaches when the institution knows, suspects, or has reason to suspect reportable activity at the applicable threshold — and under the October 2025 FAQs, you are not required to document every decision not to file.

What happens if a SAR is filed late?

Late filing violates the BSA reporting requirement and surfaces in exams as a timeliness finding; patterns of lateness have featured in public enforcement actions. Consequences scale with willfulness and overall program weakness, so an isolated miss is treated differently than a systemic backlog.

Meeting SAR filing requirements gets easier when the narrative is not the bottleneck. See how Sam turns a completed investigation into a filing-ready SAR narrative.

SAR Filing Requirements and Deadlines in 2026

More from the blog