The SAR narrative is the written heart of a Suspicious Activity Report that tells the FIU and law enforcement, in plain language, the who, what, when, where, why, and how of the suspicious activity. A strong narrative stands on its own and can turn a filing into a usable lead; a weak one can waste an otherwise solid investigation.
What is a SAR narrative, in plain English?
A Suspicious Activity Report has structured fields, but the part that actually communicates is the narrative: the written account that explains, in plain language, what the institution saw and why it looks suspicious. It covers the classic six questions, the who, what, when, where, why, and how, and it ties them to concrete details: amounts, dates, accounts, and the specific reasons the activity raised concern.
The gold standard is a narrative that stands on its own. A reader at the financial intelligence unit or in law enforcement should be able to understand the whole story from the narrative alone, without chasing the institution for context. When it works, a good narrative can turn a single filing into a usable lead that investigators can act on.
It is the payoff of the entire investigation. All the funds-flow tracing, KYC review, and analysis exist to be distilled into this account, so the quality of the writing directly determines whether the work reaches anyone who can use it.
How a strong narrative is built
Structure — Tell it chronologically. The activity is laid out in time order so the reader can follow the sequence of events.
Specify — Quantify with facts. Amounts, dates, accounts, and parties are stated precisely, not summarized vaguely.
Explain — Say why it is suspicious. The narrative makes the reason for suspicion explicit and states clearly what was and was not determined.
Discipline — Cut boilerplate, never tip off. Jargon and templated filler are stripped out, and the subject is never notified that a SAR was filed.
What it looks like in practice
In practice
A weak narrative reads: the customer engaged in transactions of unknown purpose that appeared potentially suspicious. It quantifies nothing, explains nothing, and hands the reader no thread to pull. It is the kind of empty filing that buries real intelligence.
A strong narrative on the same case reads: between two named dates, the personal account received eleven wires totaling a stated amount from ten unrelated senders, then transferred the sum in three payments to an overseas account, leaving a near-zero balance each cycle. It notes the customer was onboarded as an individual with no business, that two senders were identified elsewhere as fraud victims, and that no legitimate purpose could be established. Chronological, specific, and self-contained, it reads as a lead an investigator can immediately act on.
Why it matters to operators
A SAR is only as valuable as its narrative can make it. An institution can run a flawless investigation, but if the narrative is vague or boilerplate, the reader cannot see what the analyst saw, and the whole effort is wasted. The narrative is the single point where good work either reaches law enforcement in usable form or dies as an unreadable filing.
The craft is straightforward to state and easy to neglect: keep it chronological and specific, quantify the activity, avoid boilerplate and jargon, and state plainly what you did and did not determine. Two rules are non-negotiable. Never fill the narrative with templated filler that says nothing, and never tip off the subject that a SAR was filed. Get the narrative right and a filing becomes intelligence; get it wrong and even a strong case disappears.
Operator notes
Make it self-contained. The reader should understand the whole story from the narrative alone, without contacting you.
Quantify everything. Amounts, dates, accounts, and parties belong in the text; vague summaries waste the filing.
State what you did not determine. Being clear about the limits of what you found is part of an honest, usable narrative.
Cut jargon and boilerplate. Templated language that says nothing is the hallmark of a weak, defensive filing.
Never tip off the subject. Confidentiality is absolute; the customer must not learn a SAR was filed.
Quick questions
What should a SAR narrative include?
The who, what, when, where, why, and how of the activity, tied to specific amounts, dates, accounts, and parties, plus a clear statement of why it is suspicious and what was and was not determined. It should read as a complete, standalone account.
Why does the narrative matter more than the fields?
The structured fields capture data, but the narrative is what explains the story and the suspicion. A reader relies on it to understand the case and decide whether to act, so its quality determines whether the filing becomes a usable lead.
What makes a narrative weak?
Vagueness, boilerplate, jargon, and a lack of quantified facts. A narrative that says activity was of unknown purpose without amounts, dates, or reasoning gives the reader nothing to work with and squanders the investigation.
Can you tell the customer about a SAR?
No, never. Tipping off the subject that a SAR was filed is prohibited and can obstruct an investigation. Confidentiality of the filing is one of the strictest rules in the whole regime.
Why write chronologically?
Because a time-ordered account is the easiest for a reader to follow. Laying out the sequence of events lets an investigator reconstruct what happened without untangling a jumble, which makes the filing far more actionable.
Go deeper
FinCEN ↗ — The US financial intelligence unit. Bank Secrecy Act rules, advisories, and SAR and CTR guidance.
---
title: SAR narrativeとは？
source_page: https://www.sardine.ai/jp/fraud-aml-glossary/sar-narrative
canonical: https://www.sardine.ai/jp/fraud-aml-glossary/sar-narrative
format: text/markdown
description: The SAR narrative is the written heart of a SAR that tells the FIU and law enforcement, in plain language, the who, what, when, where, why, and how of the suspicious activity, including amounts, dates, accounts, and why it looks suspicious. A strong narrative stands on its own and can turn a filing into a usable lead.
---
**Quick links:** [Human page](https://www.sardine.ai/jp/fraud-aml-glossary/sar-narrative) · [Home](https://www.sardine.ai) · [Customers](https://www.sardine.ai/jp/customers) · [Blog](https://www.sardine.ai/jp/blog) · [Demo](https://www.sardine.ai/jp/demo)
---
# SAR narrativeとは？
**Read time:** 4
The SAR narrative is the written heart of a SAR that tells the FIU and law enforcement, in plain language, the who, what, when, where, why, and how of the suspicious activity, including amounts, dates, accounts, and why it looks suspicious. A strong narrative stands on its own and can turn a filing into a usable lead.
The SAR narrative is the written heart of a Suspicious Activity Report that tells the FIU and law enforcement, in plain language, the who, what, when, where, why, and how of the suspicious activity. A strong narrative stands on its own and can turn a filing into a usable lead; a weak one can waste an otherwise solid investigation.
What is a SAR narrative, in plain English?
A Suspicious Activity Report has structured fields, but the part that actually communicates is the narrative: the written account that explains, in plain language, what the institution saw and why it looks suspicious. It covers the classic six questions, the who, what, when, where, why, and how, and it ties them to concrete details: amounts, dates, accounts, and the specific reasons the activity raised concern.
The gold standard is a narrative that stands on its own. A reader at the financial intelligence unit or in law enforcement should be able to understand the whole story from the narrative alone, without chasing the institution for context. When it works, a good narrative can turn a single filing into a usable lead that investigators can act on.
It is the payoff of the entire investigation. All the funds-flow tracing, KYC review, and analysis exist to be distilled into this account, so the quality of the writing directly determines whether the work reaches anyone who can use it.
How a strong narrative is built
Structure — Tell it chronologically. The activity is laid out in time order so the reader can follow the sequence of events.
Specify — Quantify with facts. Amounts, dates, accounts, and parties are stated precisely, not summarized vaguely.
Explain — Say why it is suspicious. The narrative makes the reason for suspicion explicit and states clearly what was and was not determined.
Discipline — Cut boilerplate, never tip off. Jargon and templated filler are stripped out, and the subject is never notified that a SAR was filed.
What it looks like in practice
In practice
A weak narrative reads: the customer engaged in transactions of unknown purpose that appeared potentially suspicious. It quantifies nothing, explains nothing, and hands the reader no thread to pull. It is the kind of empty filing that buries real intelligence.
A strong narrative on the same case reads: between two named dates, the personal account received eleven wires totaling a stated amount from ten unrelated senders, then transferred the sum in three payments to an overseas account, leaving a near-zero balance each cycle. It notes the customer was onboarded as an individual with no business, that two senders were identified elsewhere as fraud victims, and that no legitimate purpose could be established. Chronological, specific, and self-contained, it reads as a lead an investigator can immediately act on.
Why it matters to operators
A SAR is only as valuable as its narrative can make it. An institution can run a flawless investigation, but if the narrative is vague or boilerplate, the reader cannot see what the analyst saw, and the whole effort is wasted. The narrative is the single point where good work either reaches law enforcement in usable form or dies as an unreadable filing.
The craft is straightforward to state and easy to neglect: keep it chronological and specific, quantify the activity, avoid boilerplate and jargon, and state plainly what you did and did not determine. Two rules are non-negotiable. Never fill the narrative with templated filler that says nothing, and never tip off the subject that a SAR was filed. Get the narrative right and a filing becomes intelligence; get it wrong and even a strong case disappears.
Operator notes
Make it self-contained. The reader should understand the whole story from the narrative alone, without contacting you.
Quantify everything. Amounts, dates, accounts, and parties belong in the text; vague summaries waste the filing.
State what you did not determine. Being clear about the limits of what you found is part of an honest, usable narrative.
Cut jargon and boilerplate. Templated language that says nothing is the hallmark of a weak, defensive filing.
Never tip off the subject. Confidentiality is absolute; the customer must not learn a SAR was filed.
Quick questions
### What should a SAR narrative include?
The who, what, when, where, why, and how of the activity, tied to specific amounts, dates, accounts, and parties, plus a clear statement of why it is suspicious and what was and was not determined. It should read as a complete, standalone account.
### Why does the narrative matter more than the fields?
The structured fields capture data, but the narrative is what explains the story and the suspicion. A reader relies on it to understand the case and decide whether to act, so its quality determines whether the filing becomes a usable lead.
### What makes a narrative weak?
Vagueness, boilerplate, jargon, and a lack of quantified facts. A narrative that says activity was of unknown purpose without amounts, dates, or reasoning gives the reader nothing to work with and squanders the investigation.
### Can you tell the customer about a SAR?
No, never. Tipping off the subject that a SAR was filed is prohibited and can obstruct an investigation. Confidentiality of the filing is one of the strictest rules in the whole regime.
### Why write chronologically?
Because a time-ordered account is the easiest for a reader to follow. Laying out the sequence of events lets an investigator reconstruct what happened without untangling a jumble, which makes the filing far more actionable.
Go deeper
FinCEN ↗ — The US financial intelligence unit. Bank Secrecy Act rules, advisories, and SAR and CTR guidance.
FFIEC BSA/AML Examination Manual ↗ — The manual US examiners use to assess BSA and AML programs.
