FINTRAC and PCMLTFA testing requirements
The Proceeds of Crime (Money Laundering) and Terrorist Financing Act requires money services businesses to register with FINTRAC and all reporting entities to verify identity, report transactions, keep records, and run a compliance program. Testing against the Act verifies thresholds, 24-hour aggregation, report deadlines, and travel rule data. FintechAssuranceLabs produces onboarding scenario suites and transaction monitoring rule test matrices.
- Jurisdiction
- Canada (Proceeds of Crime (Money Laundering) and Terrorist Financing Act, S.C. 2000, c. 17, and Regulations SOR/2002-184)
- Primary source
- laws-lois.justice.gc.ca
Engineering interpretation of testing requirements, not compliance advice.
What the PCMLTFA and its Regulations require
The Proceeds of Crime (Money Laundering) and Terrorist Financing Act (PCMLTFA, S.C. 2000, c. 17, consolidated to 2026-07-21, checked on 2026-09-16) and its Regulations (SOR/2002-184) apply to the reporting entities in section 5 of the Act, which FINTRAC examines. Paragraph 5(h) covers money services businesses (MSBs) with a place of business in Canada, including dealers in virtual currencies. Paragraph 5(h.1) covers foreign MSBs that direct services at persons in Canada and serve clients in Canada. The rules that change test scope:
- Registration (Act ss. 11.1, 11.13, 11.19). MSBs and foreign MSBs register with FINTRAC, report changes within 30 days, and renew every two years unless a longer period is prescribed.
- Identity verification (Regulations ss. 95 and 105). An MSB verifies a person who requests an electronic funds transfer (EFT) of $1,000 or more (95(1)(b)), a virtual currency transfer or exchange of $1,000 or more (95(1)(d), (e)), or a foreign currency exchange of $3,000 or more (95(1)(c)), at the time of the transaction (105(7)(a)). Documents must be authentic, valid, and current (105(5)). FINTRAC's identification guidance says a remote process must authenticate the photo document, and viewing the document over video is not enough.
- Transaction reports (Regulations ss. 30 and 132). An MSB reports cash receipts of $10,000 or more within 15 days. International EFTs of $10,000 or more that the MSB initiates or finally receives, and virtual currency receipts of $10,000 or more, are reported within 5 working days. Amounts within 24 consecutive hours are one transaction when the MSB knows they share a condition in sections 126 to 129, such as the same requester or beneficiary. Foreign and virtual currency amounts convert at the Bank of Canada rate or, if none is published, the rate used in the ordinary course of business (s. 125). Suspicious transactions, including attempted ones, are reported at any amount (Act s. 7).
- Travel rule (Act s. 9.5; Regulations ss. 124, 124.1). SWIFT MT-103 messages or their equivalent and international EFTs carry the requester's name, address, and account or reference number, and the beneficiary's name, address, and account number if applicable. Virtual currency transfers that need a record carry the name, address, and any account or reference number of both parties. For received transfers, written risk-based policies decide whether to suspend or reject a transfer with missing information (124(4), 124.1(2)).
- Records (Regulations ss. 36, 148, 149). An MSB records EFTs and virtual currency transfers of $1,000 or more and every currency exchange (s. 36), keeps transaction records at least 5 years from creation (148(1)(c)), and can produce them within 30 days of an examination request (s. 149).
- Compliance program (Act s. 9.6; Regulations s. 156). The program has a compliance officer, written policies approved by a senior officer, a documented risk assessment, a training program and plan, and an effectiveness review plan (156(1)). A new technology is risk-assessed before it is introduced (156(2)). The review runs every two years (156(3)), and an entity reports its findings to a senior officer within 30 days (156(4)).
Since 26 March 2026 (S.C. 2026, c. 4, Bill C-12), Act subsection 9.6(1.1) requires the program to be reasonably designed, risk-based, and effective. The maximum penalty for a prescribed violation by an entity is $20,000,000, and for all violations on one notice the greater of $20,000,000 and 3% of gross global revenue (s. 73.1(2), (3)). Enrolment of other reporting entities waits for regulations (FINTRAC modernization page, modified 2026-04-13). Bank of Canada registration of payment service providers is on the RPAA page.
What PCMLTFA testing verifies
| Requirement | What we test | Evidence produced |
|---|---|---|
| Regulations ss. 95(1)(b), 105(7)(a): identity verified for EFT requests of $1,000 or more at transaction time | Outbound transfers of $999.99 and $1,000.00 from a synthetic unverified sender on web, app, and API | Identity verification decision log per transfer amount and channel |
| Regulations s. 125 with s. 95(1)(b): foreign currency amounts converted to Canadian dollars before the $1,000 check | USD and EUR transfers just below and just above CAD 1,000 at the Bank of Canada rate in effect | Conversion log with rate source, rate timestamp, and threshold decision per transfer |
| Regulations s. 105(5): photo identification document is authentic, valid, and current | Expired, altered, and valid synthetic identity documents in remote onboarding | Document authentication result per synthetic document |
| Regulations ss. 30(1)(f), 129(1), 132(2): virtual currency receipts combined over 24 consecutive hours and reported within 5 working days | Deposits of $6,000 and $4,000 in virtual currency by one synthetic client, 23 hours 59 minutes apart and 24 hours 1 minute apart | Large Virtual Currency Transaction Report trigger log with due date per deposit pair |
| Regulations ss. 30(1)(b), 127(1)(c): outbound international EFTs to one beneficiary combined over 24 consecutive hours | Three international EFTs of $3,500 each to one beneficiary from two requesters within 24 hours | EFT Report trigger log with aggregation reason per transfer set |
| Act s. 9.5, Regulations s. 124(3): requester and beneficiary information in outbound EFT messages | International transfers with long names, multi-line addresses, and no beneficiary account number | Captured outbound payment messages with requester and beneficiary fields |
| Regulations s. 124.1: virtual currency travel rule data sent, and missing data on received transfers handled by written policy | A $1,000 withdrawal to another virtual currency dealer and an inbound transfer with no requester address | Travel rule message capture with allow, suspend, or reject decision per transfer |
| Regulations ss. 148(1)(c), 149: transaction records kept 5 years from creation and producible within 30 days | Retrieval of backdated synthetic EFT and virtual currency transfer records by client and date range | Record retrieval log with query time and field completeness per request |
Artifacts FINTRAC examiners request
FINTRAC's assessment manual (July 2025) describes what examiners review:
- Compliance program documents: compliance officer appointment, approved policies and procedures, risk assessment, and training program and plan (Regulations s. 156(1)).
- The latest two-year effectiveness review and the written report of its findings to a senior officer (s. 156(3), (4)).
- A dated risk assessment for each new technology introduced since the last review (s. 156(2)).
- Lists and records of transactions, which examiners compare with submitted reports to find missing and late reports.
- Policies, records, and reports that show how amounts are combined under the 24-hour rule.
- Rejected reports that were not corrected and resubmitted.
- For reports sent by a third-party service provider, proof that each report carries the reporting entity's identification.
Common FINTRAC findings
- Threshold compared in the send currency. A USD 800 transfer, worth more than CAD 1,000 at any rate above 1.25, skips identity verification because the check compares 800 with 1,000. The defect breaks Regulations s. 95(1)(b) read with s. 125.
- 24-hour window reset at midnight. Aggregation groups deposits by calendar day, so virtual currency deposits of $6,000 at 23:00 and $5,000 at 01:00 produce no report. The defect breaks the "24 consecutive hours" condition in Regulations s. 129(1).
- Aggregation by requester only. EFTs to one beneficiary from different requesters are never combined. The defect breaks Regulations s. 127(1)(c).
- Requester address cut from outbound messages. The message mapping sends only the first address line and no reference number for wallet-funded transfers. The defect breaks Act s. 9.5(a).
- Inbound virtual currency credited without a policy decision. A transfer with no requester information credits the client, and no suspend or reject decision is recorded. The defect breaks Regulations s. 124.1(2).
- Retention counted from account opening. A purge job deletes transaction records 5 years after account opening, so records of later transactions are deleted less than 5 years after creation. The defect breaks Regulations s. 148(1)(c).
How we cover FINTRAC requirements
KYC, AML and fraud testing delivers the "Onboarding and verification scenario suite" for Regulations ss. 95 and 105 and the "Transaction monitoring rule test matrix" for the report triggers in s. 30 and the 24-hour rule. The same evidence feeds the two-year effectiveness review under s. 156(3). The FX rate application testing guide covers the conversion checks behind s. 125.
Crypto exchange and wallet testing covers virtual currency travel rule data and large receipts in the "Deposit and withdrawal test suite per supported chain". EU rules for the same flows are on the EU AML and KYC page.
We test PCMLTFA flows for remittance providers, crypto exchanges, neobanks, KYC and AML vendors, BaaS programmes, business banking, AP and AR platforms, and trading apps. All test identities, wallets, and account data are synthetic.
Related
Segments
Questions
What does FINTRAC do?
Who does FINTRAC regulate?
What is FINTRAC reporting?
Scope your testing
Send FintechAssuranceLabs your product, segment, money flows, and the standards that need evidence, and get a proposed test scope with its deliverables.
Scope your testing