Key takeaways
- Reasonable grounds to suspect is a legal threshold — not a hunch; more than one red flag required; must trigger STR submission.
- "As soon as practicable" means after you form reasonable grounds — not after you've assembled proof or client explanation.
- Facts, context, and indicators must be woven together — not listed separately or assumed FINTRAC will connect the dots.
- Second reviewer must verify accuracy, specificity, and clarity before any STR is filed to reduce deficiencies.
- Attempted transactions can be reported — even blocked or abandoned transactions warrant STRs if reasonable grounds exist.
Your suspicious transaction report (STR) narrative is a critical compliance document. FINTRAC relies on it to understand not just what happened, but why you believe reasonable grounds to suspect money laundering, terrorist financing, or sanctions evasion exist.
Yet many reporting entities submit narratives that are vague, overly brief, or packed with unexplained red-flag lists. Some copy internal monitoring alerts verbatim, complete with acronyms and jargon that mean nothing to an external examiner. Others delay submission while gathering more evidence, misunderstanding that "as soon as practicable" means submission after you've formed reasonable grounds—not after you've assembled proof.
A well-written narrative demonstrates rigorous thinking, protects your compliance defense, and helps FINTRAC perform its mandate. This guide walks you through the core principles of narrative construction, the distinction between narrative and structured fields, how to connect facts and indicators, and the quality standards that make your STR defensible under examination.
The Decision Before Writing: When Reasonable Grounds to Suspect Are Reached
Before you write anything, you must answer a single threshold question: Have you completed sufficient measures to establish reasonable grounds to suspect that this transaction or pattern is connected to money laundering, terrorist financing, or sanctions evasion?
Reasonable grounds to suspect is a legal standard. It is not a hunch or a concern. It requires more than one isolated red flag. It does not require proof, certainty, or knowledge beyond a reasonable doubt. It means that, based on facts and context, a prudent compliance professional would conclude there is a plausible basis to believe illicit activity may be occurring.
Once that threshold is crossed, you must submit the STR as soon as practicable. Delays waiting for confirmation, additional documentation, or client explanation are not acceptable. Practical measures—customer due diligence (CDD), transaction documentation review, beneficial owner verification, business purpose inquiry—form the foundation of your suspicion. Your narrative will explain why those measures and the resulting facts support your conclusion.
There is no monetary floor. A $50 transaction warrants an STR if reasonable grounds exist. Equally, not every unusual transaction triggers reporting. Many transactions are legitimate, even if they appear outside normal patterns. Your job is to apply context: Does this activity align with what you know about the customer's business, profile, and past behavior? Or does it depart significantly, and if so, why?
Facts, Context and Indicators: Understanding the Difference
A fact is objective: the date of a transaction, the amount transferred, the destination jurisdiction, the customer's stated business.
Context is the framework: the customer's stated purpose, their history with your institution, their industry norms, external events or regulatory environment.
An indicator (or red flag) is a characteristic that, in light of facts and context, suggests potential illicit activity.
Good narratives do not list these separately. Instead, they integrate them. For example:
"Customer ABC Inc. stated its business purpose as domestic consulting services. On March 15, 2026—just four days after account opening—the customer initiated a wire transfer of $180,000 to a beneficiary in Pakistan with no documented contractual relationship. This departure from the stated domestic-only business purpose, combined with the speed and geographic destination, raises suspicion of potential value transfer unrelated to legitimate consulting activity."
Notice that the fact (wire transfer date, amount, destination), context (stated business purpose, timing relative to account opening), and indicator (geographic red flag, velocity mismatch) are woven together, not presented as a bulleted list.
The narrative should explain how the specific facts and indicators led you to reasonable grounds to suspect. Do not assume FINTRAC will connect the dots for you. Make the reasoning transparent and logical.
Structured STR Fields vs Details of Suspicion vs Action Taken
FINTRAC's STR form contains mandatory structured fields and a narrative section for your details of suspicion. Understanding the difference is crucial.
- Structured fields include customer name, account number, transaction date, amount, and the jurisdiction or institution involved. These fields are populated based on your records.
- The Details of Suspicion field (often labeled "Narrative") is where you explain why the facts and activity establish reasonable grounds to suspect.
- The Action Taken field records steps your institution took in response—whether you rejected the transaction, requested additional documentation, filed a suspicious activity report with a regulator, or froze the account.
Your narrative does not replace the structured fields. Both must be complete and accurate. A filled-out STR with customer information, transaction details, and action taken—but with a vague or missing narrative—is incomplete. FINTRAC examiners will note this as a deficiency. Conversely, a rich narrative paired with incorrect account numbers or transaction dates undermines credibility.
Accuracy in both structured fields and narrative is non-negotiable.
A Practical STR Narrative Blueprint
Use this framework to organize your narrative:
Who was involved?
Name the customer, account holder, and any third parties, intermediaries, or beneficiaries. Provide their role and relationship. If available, state their business, occupation, or background.
What occurred?
Describe the specific transaction or pattern. Include amounts, dates, frequency, method (wire, draft, cash), and currency if relevant.
When did it occur?
State the transaction date. Flag whether the activity is new, accelerated compared to historical patterns, or inconsistent with seasonal or business norms.
Where did funds originate and where were they sent?
Trace the source and destination. Include intermediary accounts, institution details, jurisdictions, and final beneficiary information.
Why is this activity suspicious?
Explain the departure from the customer's known profile or stated business purpose. Identify which indicators are present: unusual velocity, geography, payment methods, lack of documentation, inconsistent business activity, unclear source of funds, etc.
How does this connect to money laundering, terrorist financing, or sanctions evasion?
Articulate the link. Explain which predicate offence or financing activity the transaction may facilitate or conceal. Do not make unsupported accusations, but do draw the connection between observed facts and the suspicion.
Weak vs Improved Narrative Example
WEAK NARRATIVE:
"Customer initiated suspicious wire transfers. Account activity is unusual. Funds appear to lack clear business justification. Geographic destination is a concern."
Problems: Vague language ("suspicious" and "unusual" without explanation). No specific dates, amounts, or destinations. No reference to the customer's stated business purpose. No explanation of why geography alone is a concern. The narrative assumes FINTRAC will understand your suspicion; it will not.
IMPROVED NARRATIVE:
"Customer XYZ Ltd., a domestic recruiting firm established in January 2026, opened an account with a stated business purpose of staffing services to Canadian employers. On July 5, 2026, customer initiated three wire transfers totalling $425,000 USD to undisclosed beneficiaries in the UAE within a 48-hour period. Supporting documentation was not provided. Prior account activity showed only domestic deposits from two Canadian clients totalling $12,000 over six months. The three outbound transfers represent a 3,500% increase in transaction velocity and depart entirely from the customer's stated business and documented revenue base. The rapid account growth, large outbound transfers to beneficiaries with no documented business relationship, absence of supporting invoices or contracts, and geographic destination align with indicators for potential value transfer or proceeds laundering. No clear business rationale supports these transfers relative to the customer's stated domestic recruiting function. Based on these facts and context, there are reasonable grounds to suspect the account may be used to facilitate proceeds of crime or value transfer."
Why this is stronger: Specific dates, amounts, and destinations. Clear reference to stated business purpose and how the activity departs. Transaction history provided for context. Indicators named explicitly. A logical flow from facts to indicators to conclusion. Specific mention of what documentation is absent. The reasoning is transparent and defensible.
What a Reviewer Should Check Before Submission
Before any STR is filed, a second reviewer—ideally a supervisor or dedicated compliance officer—should verify:
- Accuracy: Are the customer name, account number, transaction date, and amount correct? Are jurisdictions and institution names spelled correctly? Errors damage credibility.
- Specificity: Does the narrative include dates, amounts, and party names? Or is it written in generalities that could apply to any transaction?
- Context: Is the customer's stated business purpose clearly stated? Does the narrative explain how the activity departs from that purpose?
- Connection to indicators: Are specific red flags named and explained? Is the link between facts and suspicion logical and transparent?
- Language and clarity: Is unexplained jargon or internal acronyms used? Would a FINTRAC examiner without knowledge of your institution understand the narrative?
- Tone: Is the narrative objective and analytical, not accusatory or conclusory? Does it avoid unsupported claims or irrelevant personal information?
- Status: Is the transaction completed or attempted? Is this status clearly stated?
- Threshold: Does the narrative articulate facts sufficient to establish reasonable grounds to suspect, or does it read as a collection of concerns without a clear legal conclusion?
Corrections, New Information and Subsequent Transactions
If after submission you discover that an STR contains material errors—an incorrect account number, wrong transaction amount, misidentified beneficiary—do not simply resubmit a corrected version and hope FINTRAC notices. Document the error and the correction. Contact FINTRAC via the Web Reporting System or your designated compliance contact. Provide the original STR reference number, explain the error clearly, and provide the corrected information. FINTRAC will advise whether a supplementary report is required or whether the correction can be noted in your file.
If new information emerges after submission—a customer provides documentation that changes your understanding, or you discover additional related transactions—assess whether the new facts materially change or strengthen your suspicion. If they do, document this and contact FINTRAC. You may be directed to file an additional STR. Reference the original STR in the new report. Do not assume that FINTRAC will automatically link related reports; make the connection explicit.
If the same customer initiates multiple suspicious transactions over time, each may warrant a separate STR. These are not duplicates; they are separate reportable events. Reference earlier STRs in the narrative of new reports so FINTRAC can construct a full picture of the customer's activity.
When Senior Compliance Review Is Needed
Some STR decisions are straightforward; others are nuanced. Complex scenarios—a customer with legitimate business in multiple jurisdictions but suspicious patterns in one; activity that could indicate sanctions evasion but requires geopolitical context; attempted transactions that the customer does not complete—benefit from experienced review.
AML advisory services in Canada can strengthen your STR assessment process. An independent compliance advisor reviews your proposed narratives, tests whether the facts and context truly support reasonable grounds to suspect, and identifies gaps in documentation or analysis before submission. This reduces examination risk and builds confidence in your reporting decisions.
Similarly, a fractional compliance officer in Canada provides ongoing support: reviewing STR narratives before submission, coaching your team on red-flag assessment, ensuring escalation procedures are followed, and reinforcing narrative standards through feedback and training. This role improves consistency and quality across all suspicious transaction reporting and serves as a second set of experienced eyes on complex decisions.
Final Takeaway
An STR narrative is not a summary of internal alerts or a complaint about a customer. It is your explanation of why a competent, experienced compliance professional—reading only your narrative and the transaction facts—would conclude that reasonable grounds to suspect exist. FINTRAC needs specificity: clear dates, amounts, parties, jurisdictions, and documented source and destination of funds. It needs context: the customer's stated business purpose and how the activity departs from it. It needs connection: a logical flow from observed facts to specific indicators to a conclusion.
Submit narratives as soon as practicable after reasonable grounds are established. Do not delay waiting for proof or client explanation. Have a second reviewer assess clarity and completeness before filing. When narratives are precise, analytically sound, and clearly written, they demonstrate compliance rigor and strengthen your institution's defense.
Frequently Asked Questions
Does every unusual transaction require an STR?
Can attempted transactions be reported?
Can a client be informed that an STR was submitted?
What if the original STR contains an error?
When is a new STR required after an earlier submission?
ComplyFactor is a specialist FINTRAC compliance advisory firm working with MSBs, PSPs, fintechs and other reporting entities. Our advisors bring direct experience in STR narrative development, FINTRAC examination support, and compliance training for reporting teams.
