Welcome: Why SAR Narratives Matter (and the Legal Duty)

Welcome to AMLReady. Let's start with a claim we'll spend the whole workshop earning. The narrative of a Suspicious Activity Report may be the single most consequential paragraph anyone in your institution will write.

A Suspicious Activity Report, a SAR, has two parts. There are the structured fields, the names, dates, account numbers, and dollar amounts you select and enter. And there is the narrative, the free-text section where you tell the story in your own words.

The fields tell a reader that something happened. The narrative tells them why it matters. When an analyst at FinCEN or an investigator at a law-enforcement agency pulls your filing, the narrative is what they read to decide whether to open a case, connect it to another, or set it aside.

Your institution can run brilliant monitoring, catch a genuinely suspicious pattern, and then waste all of it with three vague sentences nobody can act on. This workshop is about making sure that never happens to your filings.

Here's the map. Over eight short lectures we'll go from why SARs exist all the way to a checklist you can keep beside you while you write. We start with the legal duty to file and the standard that triggers it.

We cover the filing decision itself, where the threshold sits and how to document the call. Then we get into craft: the five essential elements every narrative needs, who, what, when, where, and why, plus a sixth that FinCEN's guidance emphasizes in practice, the how. We'll cover how to structure a narrative so a reviewer passes it on the first read, the specific mistakes reviewers flag most often, the deadlines and the confidentiality rules you cannot get wrong, and finally how to review your own draft the way a quality reviewer or an examiner would.

By the end you'll have a repeatable way to write SARs that hold up.

This is not optional paperwork, so let's be precise about the duty. The obligation to file SARs is statutory, set out at thirty-one U-S-C fifty-three eighteen, paragraph g, and implemented for banks in the regulation at thirty-one C-F-R ten-twenty point three-twenty. Other kinds of institutions file under their own parallel rules, and we'll name those, but the bank rule is our worked example throughout.

The standard for filing is important and people get it wrong. You file when you know, suspect, or have reason to suspect that a transaction involves funds from illegal activity, is designed to evade Bank Secrecy Act requirements, has no apparent lawful purpose, or uses the institution to facilitate criminal activity. Notice the standard is suspicion, not proof.

You are not the prosecutor and you do not have to prove a crime occurred. You have to recognize and report suspicion. And failing to file when you should is itself a violation, which is exactly why the narrative skill matters so much.

Here's why this is worth doing well, beyond just satisfying the rule. The people who receive SARs are triaging an enormous volume of them. A narrative that is clear, specific, and self-contained stands out, and a filing that connects cleanly to facts already in front of an investigator can become the piece that links your institution's data to an active case.

A vague filing, by contrast, gets read once, understood by no one, and filed away. The difference between those two outcomes is not luck and it is not how interesting the underlying activity was. It is whether the writer organized the facts and explained them plainly.

That is a learnable skill, and it is the skill this workshop builds. We'll treat every weak pattern as something with a specific fix, so that here's the mistake reviewers flag becomes here's exactly how you fix it.

A quick word on how to get the most from this. Each lecture is short and built around concrete examples and real citations. When we state a rule, we'll name its public source, the regulation or the FinCEN guidance, so you can verify it yourself and cite it with confidence.

We'll practice on fabricated, generic fact patterns, never real filings, and the goal is for you to apply the same moves to your own drafts at work. As we go, you'll assemble a pre-filing checklist, and by the final lecture it'll be a single page you can run before any SAR leaves your desk. Watch actively, pause when a citation is new, and treat the worked examples as exercises rather than something to skim.

The point is not to memorize a definition. The point is to write a better narrative on Monday.

Now, one important thing, said plainly before we go further. AMLReady is an independent, public-source training workshop. This is educational content, not legal advice, not tax advice, and not compliance advice for your specific situation.

We are not affiliated with, authorized by, or endorsed by FinCEN or the U.S. Department of the Treasury, and nothing here speaks for them.

Everything in this workshop is built from public sources, the Bank Secrecy Act regulations at thirty-one C-F-R, the statute at thirty-one U-S-C fifty-three eighteen, FinCEN's published guidance on writing a complete and sufficient narrative, and the F-F-I-E-C BSA slash AML Examination Manual, and we name those sources as we use them. We reproduce no real SAR, no confidential filing, and no real exam content; all our examples are invented. When you sit down to file for real, follow your institution's own written program, your compliance leadership, and your legal counsel.

What we promise here is serious, structured practice in a skill that genuinely matters. In the next lecture, we get to the first real decision: when are you actually required to file.