The process itself looks procedural on paper. Fill out six sections, submit electronically, done. In practice, three judgment areas often need care: establishing reasonable grounds to suspect, meeting the "as soon as practicable" timing standard, and completing the form with a clear, factual narrative.
This guide covers who must report, what the reporting threshold really means (including sanctions-evasion treatment under current FINTRAC guidance), submission deadlines and channels, what goes into the report, and common drafting pitfalls - without claiming which deficiencies "recur most often."
TL;DR
- File an STR as soon as practicable once you suspect ML, TF, or sanctions evasion where applicable - no dollar threshold applies
- "Reasonable grounds to suspect" is lower than "believe," built from facts, context, and ML/TF/sanctions-evasion indicators
- Submit via FINTRAC Web Reporting System or API
- Pitfalls to avoid: using too high a threshold, thin transaction details, and vague suspicion narratives
- Reporting failures are among the issues FINTRAC has cited when imposing administrative monetary penalties (AMPs)
Who Must Report and What Counts as a Suspicious Transaction
Who Must Comply
Every reporting entity and its employees must report suspicious transactions. That includes:
- Financial entities and banks
- Money services businesses
- Securities dealers
- Mortgage administrators and brokers
- Casinos
- Real estate brokers and developers
- Life insurance companies and agents
Employees don't need to file duplicate reports when their employer is already actively reporting. FINTRAC only expects an employee to step forward if they believe the employer failed to submit a required STR.
Third-party service providers can submit STRs on a reporting entity's behalf. But that arrangement doesn't transfer legal responsibility. If the report is late, incomplete, or never filed, the reporting entity carries the accountability, not the vendor.
What Is a Suspicious Transaction Report
An STR is required whenever a financial transaction, completed or attempted, occurs and there are reasonable grounds to suspect it relates to a money laundering offence, terrorist financing, or sanctions evasion (under current FINTRAC treatment). "Attempted" matters here; a transaction that never completes can still trigger the obligation.
What makes the STR unique among FINTRAC's reporting forms is the free-form narrative section. Unlike structured reports (large cash, EFT, virtual currency), the STR lets a reporting entity explain, in its own words, why a transaction raised concern. That narrative is often what gives FINTRAC's analysts something to actually work with.
One rule that trips people up: no tipping off. You cannot inform a client, directly or indirectly, that an STR has been or will be filed if doing so could prejudice a criminal investigation. This applies even to casual conversation with a relationship manager who wants to "give the client a heads up."
Understanding Reasonable Grounds to Suspect
This is where most of the real judgment calls happen. The threshold sits above a gut feeling ("simple suspicion") and below "reasonable grounds to believe," which would require verified, corroborated facts.
FINTRAC breaks the assessment down into three components:
- Facts — what actually happened in the transaction
- Context — the client's profile, history and stated purpose
- Indicators — recognized ML/TF and related red flags (structuring, inconsistent explanations, unusual use of third parties, high-risk jurisdictions, sanctions-evasion patterns, and similar indicators under current FINTRAC guidance)
Example: A client makes several cash deposits just under the $10,000 large cash reporting threshold across different branches in the same week, then gives a vague or shifting explanation for the source of funds. No single fact proves wrongdoing. Combined, though, the pattern (structuring) plus the context (inconsistent explanation) is enough to meet the threshold.
You don't need to verify or prove an offence occurred. The test is whether a reasonable person, with similar training, would reach the same conclusion based on what was observed.
The line between "this seems a bit odd" and "this meets reasonable grounds to suspect" requires judgment. Documenting facts, context, and indicators at the time of the decision supports defensibility if the file is later reviewed. Having a senior reviewer stress-test the judgment before an examination can be more valuable than any policy update alone.
When and How to Submit a Suspicious Transaction Report
"As soon as practicable" doesn't mean "whenever convenience allows." It means once you've completed the measures needed to establish reasonable grounds to suspect, submitting the STR becomes a priority task. There's no dollar threshold that triggers the clock: suspicion alone is the trigger.
FINTRAC has been direct about this: the longer the delay, the more explanation you'll need to provide if questioned.
Submission channels (current FINTRAC guidance):
- FINTRAC Web Reporting System (FWR): the primary channel for most reporting entities
- API report submission: system-to-system transfer, suited to higher-volume filers
Electronic filing via FWR or API is the expected route. Legacy paper channels are not treated as a routine current option in this guide.
If you need to correct a submitted STR, you have 20 days from identifying the need for a change to resubmit the revised report with an explanation.
If a subject resurfaces in a later transaction, that follow-up activity typically needs its own report, referencing the prior report number so FINTRAC can connect the dots.
What Goes Into the Report and Other Linked Obligations
The STR form has six sections:
| Section | Purpose |
|---|---|
| General information | Reporting entity and contact details |
| Transaction information | Status, date, method, location, purpose |
| Starting action | Source of funds, conductor, third party |
| Completing action | Disposition, beneficiary, other involved parties |
| Details of suspicion | Free-form narrative: facts, context, indicators |
| Action taken | What the entity did in response |
A single STR can cover multiple related transactions, and each transaction can have more than one starting or completing action depending on client instructions.
STRs don't always travel alone. Depending on the activity, you may also need to file one or more of these reports alongside it:
- Large Cash Transaction Report
- EFT Report
- Large Virtual Currency Transaction Report
- Casino Disbursement Report
Submitted STRs and their supporting documentation must be kept for five years after the date the report was sent.
Common STR Drafting Pitfalls and How to Avoid Them
Neutral drafting guidance (not a claim that these deficiencies "recur most often"):
- Applying a higher threshold than required: reporting only when there's "reasonable grounds to believe," rather than "reasonable grounds to suspect." This can cause under-reporting.
- Incomplete structured fields: listing transactions and accounts only in the narrative instead of the dedicated fields. Summarizing isn't a substitute for structured data.
- Missing parties: failing to name all known conductors, third parties, beneficiaries, directors or beneficial owners when that information is available.
- Disconnected narratives: a "Details of Suspicion" section that states general concern without tying facts, context and indicators to the transactions reported.
- Sanctions-evasion blind spots: under current FINTRAC treatment, sanctions-evasion indicators and related property or transaction concerns should be considered alongside ML/TF indicators where facts support it - do not limit STR thinking to classic laundering patterns alone.
These drafting issues can matter during compliance assessments. Internal sign-off alone may miss them: the person who wrote the narrative is seldom the best person to judge whether it is complete and explainable under regulatory scrutiny.
Independent, senior-level review of STR quality and consistency—not a routine QA checklist—reduces that exposure. AlphaDelta provides this kind of review for Canadian reporting entities preparing for effectiveness reviews or examinations.
FINTRAC published a $9,185,000 AMP against a Canadian bank in 2024 and a $1,329,150 AMP against a Canadian bank in 2023, both citing failures to submit STRs where reasonable grounds existed. Neither penalty was allocated solely to STR failures, but both examinations flagged them as central issues.
Frequently Asked Questions
When should an STR report be filed?
File as soon as practicable after you complete the measures that establish reasonable grounds to suspect a link to money laundering, terrorist financing, or sanctions evasion where applicable. There is no dollar threshold.
How is an STR report structured?
An STR has six structured sections. The Details of Suspicion narrative should align with, and not contradict, the data entered in the structured fields.
What is an STR report in banking?
It is a mandatory report that banks and other reporting entities file with FINTRAC when they have reasonable grounds to suspect a transaction is linked to money laundering, terrorist financing, or sanctions evasion where applicable.
Can an STR be corrected after submission?
Yes. Corrections must be submitted, with an explanation, within 20 days of identifying the need for a change.
Does contacting law enforcement replace the need to file an STR?
No. Contacting police or another agency doesn't remove the separate legal obligation to submit an STR to FINTRAC.
What happens if a reporting entity fails to file an STR on time?
Late or missed STRs can trigger administrative monetary penalties and may be examined during FINTRAC assessments, as illustrated in recent multi-million-dollar AMP notices.
