Key takeaways
- EFTR filing errors commonly occur because MSBs misidentify who legally initiated a transfer or confuse intermediaries with final recipients.
- Initiation is when the MSB accepts the first customer instruction to send funds internationally; final receipt is when funds are made available to the beneficiary in Canada.
- The 24-hour aggregation rule requires combining multiple transfers under CAD $10,000 if they total $10,000+ within 24 consecutive hours and involve the same party.
- The MSB must use official Bank of Canada exchange rates for currency conversion and document the rate used on the transaction day.
- Filing an EFTR does not remove the separate obligation to file a Suspicious Transaction Report if the activity is suspicious.
Introduction
Filing an Electronic Funds Transfer Report (EFTR) is one of the most operationally complex regulatory obligations for a Canadian Money Services Business (MSB). Unlike physical cash transactions, electronic funds transfers involve interconnected systems, multiple financial institutions, third-party payment processors, and cross-border settlement channels. This complexity dictates that a reportable transfer cannot be accurately assessed merely by looking at a single payment instruction or a ledger line item.
Correctly identifying the direction of the transfer and the specific parties involved is paramount. EFTR filing errors frequently occur because compliance teams misunderstand who legally initiated the transfer, who the final recipient actually is, and whether the MSB is acting as an intermediary or the primary reporting entity. A transaction system must capture sufficient, granular data to distinctly identify an originator, a sender, an instructing party, and a beneficiary. Without this structural clarity, MSBs risk immense administrative penalties for under-reporting, or conversely, compromise their data integrity by over-reporting non-reportable domestic movements.
Crucially, even when an MSB utilizes third-party reporting software or relies on an external payment processor, the MSB remains entirely legally responsible for the accuracy and timeliness of the EFTR. Automation can streamline data extraction, but it cannot replace human compliance judgement. Understanding the precise nuances of initiation, final receipt, and 24-hour aggregation is mandatory for building a resilient operational workflow.
Quick Answer
A concise summary of EFTR obligations includes:
- An international Electronic Funds Transfer (EFT) is reportable when it involves the transmission of instructions for the transfer of funds across the Canadian border.
- The reporting threshold is CAD $10,000 or more, either in a single transaction or aggregated under the 24-hour rule.
- Reporting entities must file an outgoing EFTR when they initiate an international EFT, and an incoming EFTR when they are the final recipient.
- Initiation occurs when the MSB receives the very first instruction to send the funds internationally.
- Final receipt occurs when the MSB makes the funds available to the final intended beneficiary in Canada.
- The 24-hour aggregation rule mandates combining multiple transfers under CAD $10,000 if they occur within a consecutive 24-hour period and involve the same person or entity.
- Always verify current FINTRAC requirements and technical specifications before filing, as data mapping schemas are periodically updated.
What Is a FINTRAC Electronic Funds Transfer Report?
A FINTRAC Electronic Funds Transfer Report (EFTR) records the movement of significant funds into or out of Canada. It creates a robust financial intelligence trail that FINTRAC utilizes to track illicit money movement, terrorist financing networks, and major capital flight. Reporting entities with this obligation typically include MSBs, banks, credit unions, casinos, and trust companies.
The international element is the core trigger. Under the Proceeds of Crime (Money Laundering) and Terrorist Financing Act (PCMLTFA), the obligation arises when funds cross the Canadian border. It is vital to distinguish between the underlying transfer of funds (the financial settlement) and the report submitted to FINTRAC (the regulatory data payload). They are separate actions; completing the financial transfer successfully does not automatically guarantee the regulatory report was generated.
The general threshold for filing an EFTR is CAD $10,000 or more. The filing deadline is strictly mandated: the report must be submitted to FINTRAC no later than five working days after the day of the transfer's initiation or final receipt. MSBs must consult official FINTRAC sources to verify exact current thresholds and deadlines.
What Counts as an Electronic Funds Transfer?
FINTRAC defines an EFT as the transmission of instructions for the transfer of funds through any electronic, magnetic, or optical device, telephone instrument, or computer. This encompasses SWIFT messages, non-SWIFT proprietary remittance networks, and various digital payment rails. However, not every electronic movement of funds qualifies as a reportable EFT.
Transfers sent electronically across the Canadian border (outgoing) or received electronically from outside Canada (incoming) fall within scope. The transfer must involve financial institutions, MSBs, or casinos at the sending or receiving end. Domestic transfers — where both the initiation and final receipt occur within Canada — are generally excluded from EFTR obligations unless a specific FINTRAC ministerial directive applies.
Transfers completed through correspondent or intermediary institutions can complicate analysis, but the obligation rests on the entities handling the initiation and final receipt. MSBs must distinguish between a payment message and the actual movement of funds; the EFTR is triggered by the transmission of the instructions. Transfers involving multiple operational systems within the same corporate group must be mapped carefully to avoid duplicate reporting.
Sending an International EFT
A reporting entity must file an outgoing EFTR when it initiates an international EFT of CAD $10,000 or more. The MSB must accurately identify several key elements: the person or entity requesting the transfer, whether that client is conducting the transaction for someone else (requiring identification of the third party), the intended recipient, and the destination jurisdiction. If the MSB uses a wholesale payment provider to route the funds, the role of intermediaries must be noted, but the MSB receiving the initial instruction remains the initiating party.
The amount sent, accurate currency conversion, and the exact date and time of initiation are mandatory fields. For example, if a Canadian resident asks an MSB in Toronto to send CAD $12,000 to a relative in London, UK, the Toronto MSB initiates the transfer. Even if the MSB uses a larger Canadian bank to route the funds, the MSB is responsible for the outgoing EFTR.
Receiving an International EFT
Conversely, an incoming EFTR is required when a reporting entity is the final recipient of an international EFT of CAD $10,000 or more. The entity that makes the funds available to the beneficiary holds the reporting obligation.
The MSB must record the person or entity sending the transfer from abroad, and the person or entity on whose behalf it was sent. The final recipient (the Canadian beneficiary) and the originating jurisdiction must be identified. If the MSB is merely a software provider routing data, it might not be the final recipient. The obligation falls on the entity holding the account or cash register where funds are disbursed. The amount received, currency conversion applied upon receipt, exact date and time of final receipt, and beneficiary identification must be collected. For instance, if an MSB in Vancouver receives instructions and settlement from a partner in Dubai to pay out CAD $15,000 in cash to a local customer, the Vancouver MSB is the final recipient and files the incoming EFTR.
Initiation of an EFT
Initiation occurs when the reporting entity receives the very first instruction to send funds internationally. The transfer process begins at this exact moment, regardless of how long internal ledger settlements take. There is a strict difference between the originator (the person wanting to send money), the sender (the MSB in the messaging system), the instructing party, and the intermediary. An MSB should document the initiation point based on the timestamp when the customer's instruction is accepted and committed to the system.
An internal transfer between systems — such as moving funds from a retail ledger to a treasury account — is not the legal initiation point for the EFTR; the customer's request is. When agents are involved, the workflow must be centralized. If a sub-agent accepts the cash and instruction, the principal MSB is generally deemed the initiator.
Final Receipt of an EFT
Final receipt is the endpoint of the international transfer chain. It occurs when the funds reach the final intended recipient or are made available for them to withdraw. There is a distinct difference between an intermediary receiving funds and the final recipient receiving them.
If a Canadian wholesale bank receives a transfer destined for a retail MSB's client account, the wholesale bank is merely an intermediary. The retail MSB that ultimately credits the client's wallet achieves final receipt. Funds are considered available when the beneficiary gains unconditional access to them. If a transfer is rejected or incomplete before being made available, it does not constitute final receipt. The final-receipt point must be documented with a timestamp showing when the ledger was credited or cash was disbursed. Correspondent institutions are rarely the final recipient unless the transfer specifically pays an invoice owed to them.
Initiation vs Final Receipt: Key Differences
| Feature | Initiation (Outgoing EFT) | Final Receipt (Incoming EFT) |
|---|---|---|
| Core Meaning | Accepting the first instruction to send funds abroad. | Making funds available to the final beneficiary in Canada. |
| Direction of Transfer | Out of Canada. | Into Canada. |
| Relevant Party | The entity receiving the client's instruction. | The entity paying out the final beneficiary. |
| Key Timestamp | Date/time instruction is accepted. | Date/time funds become available. |
| Required Transaction Data | Sender details, intended beneficiary, destination. | Originator details, actual beneficiary, origin country. |
| Intermediary Involvement | MSB initiates; may use intermediaries to route. | Intermediaries pass funds; MSB does final payout. |
| Supporting Evidence | Customer receipt, signed request form. | Payout receipt, account credit log, ID verification. |
| Common Errors | Failing to identify the third-party requester. | Intermediary bank incorrectly assumes reporting duty. |
| Typical Report Type | Outgoing EFTR. | Incoming EFTR. |
| Practical Example | Client pays CAD to send to Mexico. | Client receives CAD originating from Japan. |
The CAD $10,000 Reporting Threshold
The reporting threshold applies strictly to transfers of CAD $10,000 or more. The amount must always be assessed in Canadian dollars, even if the entire transaction was conducted in a foreign currency. To determine if a foreign-currency transfer meets the threshold, the MSB must apply a specific currency conversion method.
FINTRAC dictates using the official exchange rate published by the Bank of Canada for the day of the transaction. If the transaction occurs on a weekend or holiday when no rate is published, the rate from the previous business day is generally applied. If a Bank of Canada rate is unavailable, the MSB must use the exchange rate it would utilize in the normal course of business for that transaction.
Maintaining exchange-rate evidence is a regulatory necessity. The threshold calculation is based on the principal amount. Administrative fees levied by the MSB are generally excluded from the reportable principal unless explicitly bundled into the instruction. Near-threshold transfers (e.g., CAD $9,950) should be heavily reviewed, as they often indicate deliberate structuring, necessitating a Suspicious Transaction Report (STR).
The FINTRAC 24-Hour Rule for EFTs
The FINTRAC 24-hour rule guidance dictates that multiple EFTs under CAD $10,000 must be aggregated and reported as a single large transaction if they total CAD $10,000 or more within a consecutive 24-hour period. This rule applies exclusively when the transactions involve the same person or entity, or are conducted on behalf of the same person or entity.
The knowledge condition is crucial: aggregation is only required if the reporting entity knows the transactions are connected to the same party. Transaction systems must identify related transfers using unique identifiers. The MSB must document the aggregation decision. A consecutive 24-hour period is a rolling window (e.g., 2:00 PM to 1:59 PM next day) and is entirely different from a calendar day. For exhaustive breakdowns, refer to the dedicated FINTRAC 24-hour rule examples guide.
EFTR Aggregation Examples
Example 1: Two outgoing transfers by the same individual
A client sends CAD $6,000 to France at 10:00 AM and CAD $4,500 to Spain at 4:00 PM. Because the same individual initiated both outgoing transfers within 24 consecutive hours, totaling CAD $10,500, they must be aggregated. An outgoing EFTR is required.
Example 2: Multiple outgoing transfers on behalf of the same company
Employee A sends CAD $5,000 on behalf of ABC Corp at 9:00 AM. Employee B sends CAD $6,000 on behalf of ABC Corp at 1:00 PM the next day. Since the transactions fall outside a 24-hour window (28 hours apart), they are not aggregated for EFTR purposes, though they should be monitored.
Example 3: Incoming transfers received for the same beneficiary
An MSB receives three inbound transfers of CAD $4,000 each for the same Canadian beneficiary. The funds are made available at 11:00 AM, 3:00 PM, and 9:00 AM the following morning. Since the final receipt for all three totals CAD $12,000 within 24 hours for the same entity, they are aggregated, triggering an incoming EFTR.
Example 4: Transfers in different currencies
A client sends USD $4,000 (CAD equivalent $5,400 based on the Bank of Canada rate) and later sends EUR $3,500 (CAD equivalent $5,100). The total CAD equivalent is $10,500 within 24 hours. The MSB must aggregate and file an EFTR, reporting the currencies and official conversion rates used.
Example 5: Transactions crossing midnight
A transfer of CAD $7,000 is initiated at 11:30 PM Monday. Another transfer of CAD $4,000 is initiated by the same client at 1:00 AM Tuesday. Despite occurring on different calendar days, they fall within a 2-hour window. Aggregation is mandatory.
Example 6: Transactions through separate branches or agents
A client sends CAD $8,000 from a Toronto branch at noon, and CAD $3,000 from a Mississauga agent at 2:00 PM. Centralized monitoring must identify related transfers across the network. The principal MSB aggregates the total and files the EFTR.
Example 7: Unrelated transfers with a similar amount
Two unrelated customers each send CAD $6,000 to the same destination simultaneously. Since they do not involve the same person or entity, similar values alone are not sufficient for aggregation. No EFTR is filed.
Example 8: Returned or cancelled EFT
A client initiates a CAD $11,000 transfer, triggering an outgoing EFTR. Due to an invalid account number, funds are returned two days later. If the instruction was transmitted, the outgoing EFTR obligation was met. MSBs must assess case-specific compliance guidance for the returned funds.
Information Required for an EFTR
When preparing an EFTR, MSBs must provide mandatory information defined by current FINTRAC technical specifications. This data is organized into practical groups including reporting entity information, transaction details, initiating party information, third-party details, recipient information, account information, location information, currency and amount, reference numbers, intermediary information, and third-party information. MSBs must verify current fields using official reporting guidance. Do not state that optional information is mandatory, but best practice dictates capturing robust verifiable data.
EFTR Filing Workflow for an MSB
Implementing a reliable filing workflow requires systematic precision. By utilizing robust FINTRAC reporting software, an MSB can navigate the following sequential steps:
- Capture the transaction instruction accurately at the point of sale.
- Determine whether the transfer is international (crossing the Canadian border).
- Identify whether the MSB is handling the initiation (outgoing) or final receipt (incoming).
- Identify all relevant parties, including third parties.
- Convert the amount into Canadian dollars where required using the Bank of Canada rate.
- Check the individual threshold against the CAD $10,000 limit.
- Apply the 24-hour aggregation rule against the customer's profile.
- Review exemptions or exclusions supported by official FINTRAC guidance.
- Validate mandatory fields against FINTRAC's schema.
- Conduct human compliance review to ensure narratives and party relationships make sense.
- Submit the report through the available reporting channel.
- Record the submission acknowledgement ID securely in the database.
- Resolve validation or rejection errors immediately within the 5-day deadline.
- Retain supporting evidence for the statutory period.
- Escalate related suspicious activity separately where appropriate.
It is paramount to make clear that an EFTR and an STR are separate reporting obligations. Filing an EFTR does not remove the need to consider an STR. Knowing how to write an effective STR narrative is a distinctly separate compliance skill.
FINTRAC Web Reporting vs API Submission for EFTRs
MSBs have distinct choices for filing channels. Manual web submission (F2R) is suitable for low-volume MSBs, requiring staff to type data directly into FINTRAC's secure portal. API-based submission allows internal systems to transmit JSON payloads automatically, which is vital for high-volume workflows. API systems manage validation instantly, returning acknowledgements directly to the MSB's software. Review the FINTRAC API vs Web Reporting System guide for an extensive comparison. Business-continuity arrangements must be in place to file manually if the API experiences an outage.
Common EFTR Filing Errors
Regulatory audits frequently uncover the following errors, resulting in severe administrative monetary penalties:
- Treating an intermediary as the final recipient: Listing a correspondent bank as the beneficiary instead of the actual individual receiving funds.
- Using the wrong initiation point: Calculating the 5-day deadline from the day the ledger settled rather than when the instruction was given.
- Failing to identify the person on whose behalf the transfer was conducted: Ignoring third-party determination requirements.
- Missing related transfers within the 24-hour period: Failing to aggregate due to weak system profiling.
- Aggregating unrelated transactions: Combining transfers from different people just because they went to the same country.
- Using an unsupported currency conversion method: Relying on a retail markup rate rather than the official Bank of Canada rate.
- Filing the wrong directional report: Filing an incoming EFTR for an outgoing transaction.
- Missing mandatory information: Leaving out critical address data or occupation details.
- Submitting duplicate reports: Filing via API and then accidentally filing the same transaction manually.
- Ignoring failed-validation messages: Assuming a transmitted report was accepted when FINTRAC actually rejected it.
- Failing to retain acknowledgement records: Losing the proof that the report was successfully filed.
- Treating software output as a substitute for compliance review: Submitting automated reports blindly without verifying data integrity.
- Confusing an EFTR with an STR: Believing that crossing the $10,000 threshold removes the need to file a Suspicious Transaction Report.
These errors can be prevented through rigorous staff training and strict configuration of internal monitoring rules.
Recordkeeping and Audit Evidence
An MSB must retain comprehensive evidence to support its EFTR decisions. Under PCMLTFA regulations, records related to EFTs must generally be kept for at least five years. Required evidence includes customer instructions, transaction records, account records, and verified beneficiary details. Identification records used to verify the customer must be securely stored. The MSB must retain exchange-rate evidence showing the exact conversion method used on the transaction day. Aggregation results, compliance officer review notes, validation messages, submission acknowledgements, and records of corrections or cancelled transfers form a complete audit trail. Crucially, the MSB must keep documented decisions where a report was explicitly not filed (e.g., documenting why an $9,900 transfer was deemed non-suspicious and un-aggregated).
Internal Controls for Reliable EFTR Filing
Maintaining compliance requires robust internal controls. Engaging external AML advisory services can assist in designing these frameworks. Practical controls include centralised transaction monitoring to view all activity across the business, consistent time-zone settings across servers to accurately calculate 24-hour aggregation, cross-branch aggregation and agent transaction visibility to prevent structuring, mandatory field validation built into the point-of-sale system, currency conversion controls locked to the Bank of Canada daily API feed, exception queues where flagged transactions wait for a compliance officer's approval, maker-checker review protocols for high-risk corridors, submission-status monitoring and failed-report alerts, daily reconciliation of reportable transactions to submitted reports to catch missing files, change management protocols for when FINTRAC updates API schemas, and periodic quality assurance and independent testing to validate system accuracy. While not every control is a direct legal requirement, they represent recommended operational practices to meet FINTRAC expectations.
How Reporting Software Can Support EFTR Compliance
Specialized software can profoundly assist with transaction-data capture, automated currency conversion, and calculating 24-hour aggregation windows accurately across time zones. For comprehensive remittance compliance support, the system enforces mandatory field validation before a transaction is finalized and facilitates rapid API submission. Software also centralizes exception management, tracks acknowledgements, creates immutable audit trails, and manages corrections.
However, MSBs must acknowledge its limitations. Software cannot fix incorrect source data; if a cashier misspells a name, the software reports the misspelled name. Incorrect field mapping causes systemic failures. Poor rule configuration, unreviewed exceptions, and unsupported report types compromise compliance. Vendor outages can disrupt filing timelines. The reporting entity remains strictly responsible for the accuracy, completeness, and timeliness of each report. No private platform is FINTRAC-approved in a way that absolves the MSB of liability.
