FINTRAC STR – Suspicious Transaction Report

How to file an STR with FINTRAC, and how to stop writing them manually

🇨🇦 Official FINTRAC STR Filing

Suspicious Transaction Reports (STRs) are filed through FINTRAC's official Web Reporting System (often called FWR).

Official Government of Canada site

Note: Comply+ is not affiliated with FINTRAC. We provide software that helps reporting entities prepare, validate, and submit STRs more efficiently.

What is a FINTRAC STR?

An STR (Suspicious Transaction Report) is a regulatory report required by FINTRAC when there are reasonable grounds to suspect that a transaction, or attempted transaction, is related to money laundering or terrorist financing.

Unlike Large Cash Transaction Reports (LCTRs) or Electronic Funds Transfer Reports (EFTRs), there is no minimum dollar threshold for STRs. The trigger is suspicion, not the amount. If you suspect criminal activity, you must file, whether the transaction is $100 or $100,000.

STR obligations apply to all FINTRAC reporting entities: MSBs, casinos, real estate brokers, securities dealers, accountants, and others. The narrative section of the STR is critical. It must clearly explain why the activity is suspicious, not just describe the transaction.

STRs are filed through FINTRAC's Web Reporting System (FWR) or via the Report Ingest API for higher-volume filers.

How to File a Suspicious Transaction Report with FINTRAC

  1. 1Log in to FWR (after waiting to receive and verify a code sent to your email)
  2. 2Under 'Create a new report to submit to FINTRAC', select 'Suspicious Transaction Report (STR)'
  3. 3Enter your Reporting Entity Reference Number, select Activity Sector, and enter Contact information
  4. 4Manually add all transactions, starting/completing actions, including virtual currency details (if present), banking details, and conductor details (name, date of birth, address, ID number, occupation, etc.)
  5. 5Manually draft a Description of Suspicious Activities (Narrative) outlining: 1) Facts, 2) Context, 3) Indicators of ML/TF
  6. 6Review and attempt to submit the STR, decipher and correct any error messages, and re-submit if necessary

Or skip the manual process entirely. Build these reports in minutes using Comply+ Artificial Intelligence (AI) tools.

See how it works

Why STR Narratives Take So Long to Write

  • The narrative must clearly justify suspicion using facts, not conclusions
  • Transaction data must be translated into coherent reasoning
  • It is easy to under-explain or over-explain
  • Narrative quality varies across team members
  • Manual narrative writing can take hours per STR
  • Reviewer fatigue increases compliance risk

Don't Write Another STR Narrative by Hand

Comply+ uses AI to generate FINTRAC-grade STR narratives based on transaction data, indicators, and reporting context, in minutes, not hours.

  • AI-generated, structured STR narratives
  • Aligned with FINTRAC expectations
  • Built from transaction facts and indicators, not generic templates
  • Consistent quality across reports

Manual STR Filing vs Comply+

Manual FWR

  • Narrative written from scratch
  • Inconsistent quality
  • Hours per STR
  • Hard to scale
  • Reviewer fatigue

Comply+

  • AI-generated narrative
  • Consistent structure
  • Minutes per STR
  • Designed for volume
  • Faster, cleaner review

Generate FINTRAC-Ready STR Narratives in Minutes

See how Comply+ uses AI to create structured, compliant STR narratives, so your team can focus on review instead of writing.

STR FAQ

Related FINTRAC Resources