FINTRAC's answer to these gaps is its policy interpretations program: Interpretation Notices (FINs) and a public database of case-specific responses. These are useful, but they're not law, and treating them as such can quietly undermine your compliance program.
This article explains what FINTRAC policy interpretations are, where they sit in FINTRAC's guidance hierarchy, the areas they cover most often, and how to apply them to your own operations without exposing your program to unnecessary risk - including readiness for a FINTRAC examination.
Key Takeaways
- FINTRAC Interpretation Notices and the policy database give fact-specific answers but carry no force of law
- The 24-hour aggregation rule uses a static window, not a rolling one—mixing them up is a common reporting error
- Two entities in the same sector can build different, equally defensible policies from one published interpretation
- Interpretations go stale as legislation or FINTRAC’s views change, so ongoing monitoring is essential
What Are FINTRAC Policy Interpretations
FINTRAC publishes two related but distinct types of interpretive content. Interpretation Notices (FINs) are numbered, published technical positions on specific provisions of the PCMLTFA and its Regulations. They tend to address recurring or high-impact questions that apply broadly across a sector or requirement.
The broader Policy Interpretations (PI) database contains FINTRAC's written responses to direct questions submitted by reporting entities, dating back to 2008. These are narrower and more fact-specific than a FIN, built around whatever scenario the requesting entity described.
Both carry an important caveat. FINTRAC states plainly that FINs "do not have the force of law" and are "not a substitute for the law." The PI database answers are labelled as general information, not legal advice, reflecting only the legislation in force at the time each response was written.
Where Policy Interpretations Fit Among FINTRAC Materials
FINTRAC's materials are not an official ranked four-tier hierarchy. Each type has a distinct purpose:
| Material | What it does | Legal status |
|---|---|---|
| Guidelines | Plain-language explanation of obligations | Explanatory, not binding |
| FINs | Technical interpretation of a specific provision | No force of law |
| PI database | Case-specific answer to a submitted question | General information only |
| Ministerial Directives | Mandated countermeasures under Part 1.1 of the PCMLTFA | Legally binding |
Describe these by purpose - not as an invented official ranking. The PCMLTFA is principles-based legislation. It sets out obligations in general terms and leaves interpretation to fill gaps as new business models, products, and technologies emerge.
That gap-filling is why the volume of interpretive content has grown so large. FINTRAC has published responses through its policy interpretation database since 2008, and a 2015 industry review by McMillan LLP noted that FINTRAC had already released several hundred interpretations by that point. The archive has only expanded since.
Key Areas Covered by FINTRAC Policy Interpretations
Published interpretations span a wide range of topics: reporting thresholds, professional triggering activities, transaction channels, and how corporate structures interact with reporting obligations. The examples below are illustrative - not a claim that three report types create most interpretation questions.
The 24-Hour Rule and the $10,000 Threshold
The $10,000 threshold triggers three report types once a single transaction meets or exceeds it:
- Large Cash Transaction Reports (LCTRs) — $10,000 or more received in cash
- Electronic Funds Transfer Reports (EFTRs) — international EFTs of $10,000 CAD or more
- Casino Disbursement Reports (CDRs) — disbursements of $10,000 or more
Below that threshold, the 24-hour rule can still trigger a report. If two or more transactions of the same reportable type (including LCTR, LVCTR, or applicable EFT types) total $10,000 or more within a consecutive 24-hour period, they are aggregated into one report when FINTRAC's conductor, third-party, and/or beneficiary links apply.
Here's where entities most often go wrong: FINTRAC requires a static 24-hour window, not a rolling one. A static window has a defined start and end point. A single transaction can't be counted across two different windows. Different business lines can use different static windows, but the mechanics within each window must stay consistent.
Triggering Activities for Professionals
FINTRAC's interpretations have drawn a sharp line for accountants between giving instructions and providing advice. Giving instructions means directing the movement of funds—for example, requesting a transfer between accounts on a client's direction. Providing advice means making a recommendation or suggestion. Advice alone does not trigger reporting obligations.
Insolvency practitioners get a related carve-out. FINTRAC has confirmed that trustee-in-bankruptcy and insolvency services are not triggering activities under the legislation. An accountant who also practices insolvency may still have obligations, but only for their non-insolvency work.
Multi-Entity Organizations and Centralized Reporting
Corporate groups frequently centralize AML operations, using one compliance team or service provider to manage reporting across multiple related businesses. FINTRAC's guidance is clear that PCMLTFA obligations attach to the specific legal entity carrying out the reportable activity. Centralizing the operational side of reporting does not shift where legal responsibility sits. Each entity's compliance program must reflect its own obligations, not only its parent group's.
The same need for entity-level clarity shows up as FINTRAC brings new sectors into scope. Title insurers became reporting entities effective October 1, 2025, and must now build compliance programs, apply client due diligence, and meet reporting obligations from scratch. Further interpretations will follow as newly regulated sectors hit their own grey areas.
Why Policy Interpretations Matter for Your Compliance Program
Because the PCMLTFA is principles-based, policy interpretations play a practical role. They shape how legal obligations are translated into day-to-day procedures, training materials, and system logic. Without them, reporting entities would be left guessing at how FINTRAC expects a provision to apply in practice.
When FINTRAC examines a program, examiners aren't checking boxes. They're assessing whether an entity's judgment calls were reasonable and defensible given the published interpretations available at the time, not whether a rigid checklist was followed to the letter.
This is why two brokerages can rely on the same published interpretation and still end up with different policies. A reasonable, risk-based response depends on factors such as:
- Client base
- Product mix
- Delivery channels
- Risk assessment
A firm serving institutional clients through in-person onboarding faces different practical questions than one serving retail clients through a mobile app, even under identical FINTRAC guidance.
The international dealer exemption shows how much weight a single interpretation can carry. FINTRAC's published interpretation clarified that the PCMLTFA's securities dealer definition turns on being authorized to deal or advise, not on formal registration.
That meant foreign dealers relying on Canada's registration exemption were still captured as securities dealers. Reporting, record-keeping, and compliance program obligations applied to Canadian activity they had not previously mapped.
One caution worth repeating: FINTRAC states its interpretations are based solely on the facts supplied and "may be subject to change." Relying on a five-year-old answer without checking whether it's still current is its own kind of program risk.
How to Access and Apply the FINTRAC Policy Interpretations Database
FINTRAC publishes its policy interpretations on its website, organized by topic. That structure keeps research manageable if you work methodically. Before relying on any interpretation, work through these steps:
- Identify the exact provision your question touches, then search the relevant topic area rather than keyword-guessing.
- Read the full fact pattern the interpretation addresses, not just the conclusion.
- Compare your own facts point by point against the original scenario, especially around entity type, product, and delivery channel.
- Check the publication date against any subsequent amendments to the Act or Regulations.
- Document your reasoning for why the interpretation applies (or doesn't) to your situation.
The biggest mistake is copying a published conclusion wholesale without recording how your facts line up with the original question. If your circumstances diverge even slightly, that same conclusion may not hold up under examination scrutiny.
Common Pitfalls When Interpreting FINTRAC Guidance
A few patterns show up repeatedly across reporting entities:
- Applying interpretations generically rather than adapting them to your specific business context, product set, or client base
- Misapplying the 24-hour rule by treating it as a rolling window instead of FINTRAC’s static window—leading to over-reporting or missed reports
- Treating FINTRAC interpretation notices (FINs) as binding law, which creates false confidence, since FINTRAC has been explicit that these notices carry no legal force on their own
None of these pitfalls are exotic. They tend to come from teams under time pressure borrowing a conclusion that was close enough, rather than confirming it was actually the right fit.
When to Bring in Senior AML Advisory Support
Some interpretation questions are straightforward enough for a documentation review. Others need judgment shaped by direct regulatory and institutional accountability, not just a literature search through the PI database.
Situations that typically call for senior AML advisory support include:
- New reporting entity classifications
- Novel products that don't map cleanly to existing categories
- Findings coming out of a FINTRAC examination
AlphaDelta's advisory work is built around this kind of grounded experience. The firm's practitioner background spans the full Canadian regulatory lifecycle. That shapes how a technical FINTRAC interpretation becomes policies and procedures that hold up when an examiner tests them, and what evidence the examiner will actually look for.
An independent assessment of how your current interpretations and controls perform in practice is especially useful when your organization is:
- Approaching an effectiveness review
- Preparing for a FINTRAC examination
- Making a significant program change
Every engagement includes one optional findings clarification session within 90 days of the final report. If FINTRAC formally initiates a compliance examination within 12 months of the final report, AlphaDelta will provide up to 10 hours of review-related senior advisory support at no additional cost. That gives your team structured support when interpretation questions tend to surface.
Frequently Asked Questions
Which reports must be submitted to FINTRAC?
Report types depend on your sector and activity. They can include Suspicious Transaction Reports, Large Cash Transaction Reports, Electronic Funds Transfer Reports, Casino Disbursement Reports, Large Virtual Currency Transaction Reports, and listed-person or entity property reports where applicable. No fixed set of three report types accounts for most interpretation questions.
What is the $10,000 rule for FINTRAC?
Large cash transactions, international EFTs, and casino disbursements of $10,000 or more each trigger a report. The 24-hour rule also aggregates multiple smaller transactions by the same person into a reportable total within a static 24-hour window.
Why do FINTRAC policies and procedures differ across brokerages?
FINTRAC's risk-based approach means each brokerage's client base, products, and risk assessment shape its specific policies. Two firms can rely on identical published interpretations and still land on different, equally defensible procedures.
Are FINTRAC interpretation notices legally binding?
No. FINTRAC states explicitly that FINs and policy interpretations do not have the force of law. Only Ministerial Directives issued under the PCMLTFA carry that legal weight.
How often does FINTRAC update its policy interpretations?
There's no fixed schedule. FINTRAC updates interpretations as new questions, sectors, or risks emerge. Older answers can become outdated as legislation changes, so entities should monitor for updates rather than assume permanence.
What's the difference between a FINTRAC guideline and a FINTRAC interpretation notice?
Guidelines explain obligations in plain language for general understanding. Interpretation notices provide technical, fact-specific positions on ambiguous or narrow provisions of the Act and Regulations.
