Skip to main content

Lesson 02 of 8

The Filing Trigger and the Decision to File

5 min read · SAR

Learn exactly when you must file: the $5,000 bank threshold, the 'know, suspect, or have reason to suspect' standard, and why it's suspicion, not proof. Plus how to document a defensible no-file decision, where under-filing hides.

Two questions before you write a word

  • First: do you have to file? (the trigger)
  • Second: how do you write it? (the narrative)
  • This lecture is entirely about the first question
  • Never start the narrative until the decision is made

Before you ever write a narrative, two separate questions have to be answered, and people routinely blur them. The first question is whether you are required to file at all. The second is, assuming you are, how you write the report.

Most of this workshop is about the second question, the craft. But the second question is meaningless until you've answered the first. In this lecture we focus entirely on the trigger and the filing decision, because a beautifully written narrative on activity that shouldn't have been filed, or worse, a missing filing on activity that should have been reported, is a failure no amount of polish can fix.

So let's get the decision right first.

The dollar threshold

  • Banks: file on $5,000 or more in aggregate where a suspect can be identified
  • Bank threshold rises to $25,000 where no suspect is identified
  • MSBs file at a lower $2,000 threshold (31 CFR 1022.320)
  • Thresholds aggregate related transactions — don't read each in isolation

Start with the dollar threshold, and know which rule applies to you. Under the bank rule, thirty-one C-F-R ten-twenty point three-twenty, a bank must file when a suspicious transaction or pattern of transactions aggregates to five thousand dollars or more and the bank can identify a suspect. Where the activity is suspicious but no suspect can be identified, the threshold is twenty-five thousand dollars.

The word aggregate matters: you don't look at each transaction in isolation, you add up related activity, which is how structuring just under reporting limits still trips the threshold. And the threshold differs by institution type. A money services business files under thirty-one C-F-R ten-twenty-two point three-twenty at a lower threshold, two thousand dollars for many transactions.

Casinos, broker-dealers, mutual funds, and insurers each have their own parallel rule. We teach the bank numbers as the example, but always confirm the threshold for your own institution type.

The suspicion standard — not proof

  • File when you know, suspect, or have reason to suspect
  • No apparent lawful purpose, evasion of BSA, or use to facilitate crime
  • You are not required to prove a crime occurred
  • Waiting for certainty is a common — and dangerous — error

Now the harder part, the suspicion standard, because the dollar amount only tells you when to evaluate, not whether to file. You file when you know, suspect, or have reason to suspect that funds come from illegal activity, that a transaction is structured to evade Bank Secrecy Act requirements, that it has no apparent lawful or business purpose, or that the institution is being used to facilitate criminal activity. The standard is genuinely a suspicion standard.

You do not have to prove a crime, name the predicate offense, or be certain. The exam-room version of the classic mistake, and the real-world version too, is the analyst who keeps an alert open for weeks waiting to be sure, when the rule never asked for sure. If reasonable suspicion is present and the threshold is met, the obligation has arisen.

Reasonable, documented suspicion is the bar, not proof beyond doubt.

Decisioning works in both directions

  • A file decision: write a SAR that holds up
  • A no-file decision: document why, with rationale
  • Under-filing hides in thinly justified no-file decisions
  • Both decisions must be defensible to an examiner later

Here's something many writers miss: the filing decision runs in both directions, and both directions have to be defensible. When you decide to file, your job becomes the narrative, which is the rest of this workshop. But when you decide not to file, you are making an equally important decision, and it needs a documented rationale just as much.

Examiners and quality reviewers look hard at the no-file population, the alerts and investigations that were closed without a SAR, because that is exactly where under-filing hides. A no-file decision that says nothing more than reviewed, no SAR is not a decision, it's a shrug. A good one explains what the activity was, why it looked suspicious at first, and the specific reason it turned out to have a lawful explanation.

Write your no-file rationales as if someone skeptical will read them a year later, because someone might.

From decision to draft

  • Once you decide to file, gather the facts before writing
  • Pull transactions, dates, parties, and the supporting documents
  • Identify the suspect(s) and the accounts involved
  • Now you're ready for the five elements — next lecture

Once you've decided to file, resist the urge to start typing the narrative immediately. The strongest narratives come from gathering the facts first. Pull the actual transactions with their dates and amounts, identify every party and account involved, line up the supporting documentation, and figure out who the suspect or suspects are.

A narrative is only as good as the facts behind it, and scrambling for a date or a dollar figure halfway through writing is how gaps and errors creep in. Think of it as building the case file in your head before you tell its story. With the decision made and the facts assembled, you're ready for the part of this workshop that does the heavy lifting: the five essential elements that every sufficient narrative contains, plus the sixth that makes it actionable.

That's next.

Recap and next

  • Trigger = threshold + suspicion standard, by institution type
  • Suspicion, not proof; don't wait for certainty
  • Document no-file decisions as carefully as filings
  • Next — the five elements: who, what, when, where, why, plus how

Quick recap. The filing trigger has two parts: a dollar threshold that depends on your institution type, five thousand dollars in aggregate for banks where there's a suspect, and a suspicion standard, you know, suspect, or have reason to suspect. The standard is suspicion, not proof, so don't wait for certainty that the rule never demanded.

And remember that decisioning runs both ways: a no-file decision deserves a documented rationale every bit as defensible as a filing, because that's where under-filing hides. With the decision made and the facts gathered, the next lecture starts the craft itself, the five essential elements of a narrative, who, what, when, where, and why, plus the practical sixth, how. That's where good SAR writing really begins.

Sources

  • 31 CFR 1020.320 — Reports by banks of suspicious transactions ($5,000 aggregate threshold)
  • 31 CFR 1022.320 — SAR rule for money services businesses ($2,000 threshold)
  • 31 USC 5318(g)
  • FFIEC BSA/AML Examination Manual — Suspicious Activity Reporting (identification, evaluation, and decisioning)

Test your knowledge

A few SAR questions on this material — pick an answer to see the explanation.

  1. Q1. When completing the structured subject and activity fields on Form 111, what is the relationship between those fields and the narrative?

  2. Q2. Suspicious activity by the same subject continues after an initial SAR is filed. What is the generally expected approach under FinCEN guidance?

  3. Q3. A well-structured SAR narrative is built around five essential elements plus one more. Which set best describes them?

  4. Q4. Which element of the five W's plus how is considered the analytical heart of the narrative — the part most often missing from weak SARs?

Ready to practice?

Put this lesson to work on real SAR questions.

Drill the full SAR bank →