FINTRAC LVCTR Guide: Valuation, Wallets and Filing

Introduction

Filing a Large Virtual Currency Transaction Report (LVCTR) is a highly technical requirement for Canadian Money Services Businesses (MSBs) dealing in digital assets. Unlike fiat currency, virtual-currency reporting demands significantly more operational oversight than simply checking a transaction value. Compliance teams must navigate extreme price volatility, decentralized network mechanics, and complex layers of wallet ownership.

LVCTR filing errors often occur because businesses misunderstand how fundamental data points interact. Wallet addresses, blockchain transaction hashes, and customer information must be intricately connected to form a reliable compliance narrative. If a compliance team uses an undocumented exchange rate, the Canadian-dollar equivalent will fail regulatory scrutiny. Consequently, valuation methodology must be reasonable, consistent, and documented at the precise time of the transaction.

Aggregation may involve separate wallets, different digital assets, or distinct platform transactions, forcing MSBs to maintain centralised visibility over all user activities. Furthermore, blockchain visibility does not automatically establish a customer's real-world identity or beneficial ownership. Crucially, the reporting entity remains strictly responsible for the accuracy and timeliness of every LVCTR, even when a blockchain analytics tool or third-party reporting platform automates data capture. This guide outlines the essential steps required to execute LVCTR obligations confidently and compliantly.

Quick Answer

A concise summary of LVCTR obligations includes the following parameters:

• An LVCTR is required when a reporting entity receives virtual currency equivalent to CAD $10,000 or more.
• Receiving virtual currency means obtaining control over the asset, whether in a hosted wallet, a custodial account, or an address controlled for a customer.
• The valuation must be determined in Canadian dollars using a documented, reproducible exchange rate at the time of the transaction.
• The 24-hour aggregation rule mandates combining multiple receipts under CAD $10,000 if they total CAD $10,000 or more within a consecutive 24-hour period by or on behalf of the same person or entity.
• Reports require granular technical data, including sending and receiving wallet addresses and the blockchain transaction hash.
• The filing deadline is strictly within five working days after the day the virtual currency is received.
• Reporting entities must independently verify current FINTRAC requirements before submission.

What Is a Large Virtual Currency Transaction Report?

An LVCTR records the receipt of significant amounts of virtual currency by a reporting entity. It provides the Financial Transactions and Reports Analysis Centre of Canada (FINTRAC) with vital intelligence regarding the movement of digital wealth into the regulated financial ecosystem. Reporting entities with LVCTR obligations typically include domestic and foreign MSBs dealing in virtual currencies, banks, and trust companies.

The legal trigger for an LVCTR is the receipt of virtual currency. There is a distinct difference between the underlying blockchain transaction and the report submitted to FINTRAC. The blockchain transaction is the financial event; the LVCTR is the regulatory disclosure. The current threshold is CAD $10,000 or more. The LVCTR must be submitted to FINTRAC within five working days after the day the funds are received.

LVCTR filing is inextricably linked to virtual-currency recordkeeping. The data points collected for the report must be retained securely. MSBs must consult official FINTRAC sources to verify exact current thresholds and scope. Not every crypto transaction must be reported; only receipts meeting the CAD $10,000 threshold or aggregation criteria trigger an LVCTR.

What Counts as Virtual Currency for FINTRAC Reporting?

FINTRAC defines virtual currency as a digital representation of value that can be used for payment or investment purposes, is not a fiat currency, and can be readily exchanged for funds or another virtual currency. This definition encompasses a broad spectrum of digital assets.

Cryptocurrency (e.g., Bitcoin or Ether), stablecoins, and various utility tokens all fall under this definition if they hold exchangeable value. Convertible digital assets that function as a medium of exchange are in scope. The reporting obligation applies whether the virtual currency is received in exchange for goods, fiat currency, or exchanged for another virtual currency.

Transactions encompass both internal ledger movements (crediting a customer's balance on a database) and direct blockchain transfers (receiving tokens into cold storage). However, certain assets like closed-loop gaming tokens or retail loyalty points typically fall outside the definition. Where classification depends on the asset's unique characteristics, a specific assessment is required. MSBs should not assume every digital token is automatically virtual currency for FINTRAC purposes.

When Is Virtual Currency Considered Received?

According to FINTRAC virtual-currency reporting requirements, virtual currency is considered received when it is transferred to a wallet controlled by the reporting entity or to a wallet controlled for the customer.

Receipt occurs in hosted-wallet arrangements and custodial accounts as soon as the reporting entity acquires operational or legal control over the assets. If a customer deposits Bitcoin into a unique deposit address, receipt occurs when the exchange's system recognizes the deposit and credits the user's account. This includes transfers moving through intermediary payment processors.

Internal account credits — where a customer buys virtual currency with fiat on the platform, and the MSB credits their hosted wallet — also constitute a receipt. Pending blockchain transactions sitting unconfirmed in the mempool are generally not considered received until they achieve a sufficient number of blockchain confirmations according to the MSB's documented policy.

If a transaction is rejected or returned before control is fully established, it typically does not constitute a completed receipt. Transfers between two wallets entirely controlled by the same business do not trigger an LVCTR, as no external funds are received. When agents or branches are involved, the principal MSB must aggregate and report. The business must assess its legal and operational control rather than relying on a universal blockchain-confirmation rule.

The CAD $10,000 LVCTR Threshold

The reporting threshold applies strictly to the receipt of virtual currency equivalent to CAD $10,000 or more. The value must always be assessed in Canadian dollars, regardless of the denomination of the virtual asset. A single transaction meeting this value triggers a report, but multiple smaller transactions may also reach the threshold through the 24-hour aggregation rule.

When calculating the threshold, MSBs must focus on the principal amount received. Based on official guidance, network gas fees deducted prior to the reporting entity receiving the funds impact the final received amount; the threshold is calculated on the net amount actually received and controlled by the MSB. Near-threshold transactions (e.g., a receipt of CAD $9,950) should be meticulously reviewed for deliberate structuring, which warrants a Suspicious Transaction Report (STR).

The extreme volatility of digital assets means the value of virtual currency may change significantly between the moment the customer initiates the transfer, the moment it is confirmed, and the day the report is filed. The valuation must be locked at the exact time of receipt.

How to Value Virtual Currency for an LVCTR

Current FINTRAC valuation requirements demand a consistent approach. The relevant valuation time is the exact date and time the virtual currency is considered received by the reporting entity. MSBs must use an exchange rate that is reasonable and derived from a documented source.

For assets with direct CAD trading pairs, the MSB can use the spot rate on its own platform or a reputable global index at the time of receipt. For assets without a direct CAD pair, conversion through another fiat currency or another virtual currency is required. For example, if a token trades only against USD, the token is first valued in USD using a reliable index, and then the USD value is converted to CAD using the official Bank of Canada daily exchange rate.

Stablecoin valuation must follow the same rigorous process; MSBs cannot assume 10,000 USDC automatically equals 10,000 USD without checking the market peg. Illiquid or thinly traded assets require careful documentation of the pricing source used. If multiple exchange venues or internal pricing engines are utilized, the methodology must be formally documented. The chosen methodology must be reasonable, consistent, reproducible, supported by retained evidence, and applied uniformly.

Virtual-Currency Valuation Examples

Example 1: Bitcoin received with a direct CAD market price

A customer deposits 0.15 BTC. At the exact time of receipt, the MSB's internal trading engine prices BTC at CAD $70,000. The calculated value is CAD $10,500. The MSB logs the internal order book rate, meeting the threshold and triggering an LVCTR.

Example 2: US-dollar stablecoin received

A customer transfers 8,000 USDT to their hosted wallet. The MSB uses an aggregate index showing USDT is exactly $1.00 USD. The MSB then applies the Bank of Canada exchange rate for that day. The value is CAD $10,800. An LVCTR is required.

Example 3: Asset without a direct CAD trading pair

An MSB receives 5,000 units of an obscure altcoin. The coin only trades against Ether (ETH). The MSB records the Altcoin/ETH rate, converts that to the ETH/USD rate, and finally applies the Bank of Canada USD/CAD rate. This multi-step conversion must be documented to prove the CAD equivalent.

Example 4: Price changes after receipt

A customer receives 5 ETH valued at CAD $9,800 on Tuesday morning. By Wednesday, a market surge pushes the value to CAD $11,000. Because the relevant valuation time was Tuesday morning at the time of receipt, the CAD $10,000 threshold was not met. A later market value does not replace the value at the time of receipt.

Example 5: Multiple assets received within 24 hours

A customer deposits CAD $6,000 worth of Bitcoin at 9:00 AM and CAD $4,500 worth of Litecoin at 3:00 PM. Each asset is converted into Canadian dollars at the exact time of its respective receipt. The total CAD equivalent is $10,500, triggering aggregation and a report.

Example 6: Fees deducted from the transaction

A customer intends to deposit CAD $10,010 worth of crypto, but network mining fees deduct CAD $20 before it reaches the MSB. The MSB receives and controls only CAD $9,990. Based on verified FINTRAC guidance, the threshold is calculated on the amount actually received, so no LVCTR is required.

The FINTRAC 24-Hour Rule for Virtual Currency

The FINTRAC 24-hour rule guidance dictates that multiple virtual-currency receipts under CAD $10,000 must be aggregated if they total CAD $10,000 or more within a consecutive 24-hour period. This applies to transactions involving the same person or entity, or received on behalf of the same person or entity.

Aggregation must occur even if receipts flow through separate wallets, distinct deposit addresses, or separate branches owned by the MSB. Different types of virtual currency must be aggregated by calculating their Canadian-dollar conversion at the time of each receipt. The knowledge condition requires the MSB to aggregate when its centralised monitoring system connects the transactions to the same profile. The decision must be documented. A consecutive 24-hour period is a rolling window (e.g., 3:00 PM to 2:59 PM the next day) and is not automatically identical to a calendar day.

LVCTR Aggregation Examples

Example 1: Two Bitcoin receipts by the same customer

A customer deposits CAD $6,000 in BTC at 10:00 AM and CAD $5,000 in BTC at 4:00 PM. They are aggregated because they occurred within 24 consecutive hours by the same person, totaling CAD $11,000. An LVCTR is filed.

Example 2: Bitcoin and Ether received by the same customer

A customer deposits CAD $7,000 in BTC and later CAD $4,000 in ETH. Both are valued at their respective receipt times. The total CAD equivalent exceeds $10,000 within 24 hours, mandating aggregation and an LVCTR.

Example 3: Receipts into separate deposit addresses

An MSB generates a unique deposit address for every transaction. A customer sends CAD $5,000 to Address A and CAD $6,000 to Address B within 12 hours. Because the MSB's backend maps both addresses to the same verified user account, they must be aggregated.

Example 4: Transactions crossing midnight

A receipt of CAD $8,000 occurs at 11:45 PM on Monday. A second receipt of CAD $3,000 occurs at 1:15 AM on Tuesday. Strict calendar-day controls might split these, but they occurred within a 1.5-hour rolling window. Aggregation is legally required.

Example 5: Similar wallet activity involving unrelated customers

Two unrelated users each deposit CAD $7,000 in BTC at the same time. Similar values and timing alone do not prove they are acting on behalf of a third party. Without evidence linking the individuals, they are not aggregated.

Wallet Information Required for an LVCTR

An LVCTR requires highly specific technical data to construct a financial intelligence trail. Mandatory wallet-related information includes the sending wallet address and the receiving wallet address. The unique transaction hash must be recorded, identifying the exact cryptographic event.

MSBs must identify the specific blockchain or distributed ledger and the exact asset type. Where applicable, wallet ownership information, customer account identifiers, and internal transaction references must be provided. Information regarding intermediary wallets, beneficiary information, and originator information is required if the transaction structure necessitates it. MSBs must never treat a public wallet address as absolute proof of the identity of its owner; it is merely an alphanumeric routing identifier.

Hosted and Unhosted Wallets

Understanding wallet structures is critical for LVCTR compliance. Hosted wallets (custodial wallets) are controlled by a third-party service provider or exchange. The MSB holds the private keys and credits the customer via an internal ledger account. The MSB may use an omnibus wallet containing pooled funds, meaning the transaction hash must be precisely mapped to the internal ledger credit.

Unhosted or self-hosted wallets interact directly with the blockchain. When a customer sends funds from an unhosted wallet to an MSB's unique customer deposit address, the MSB must document the sending address.

The wallet type affects the information available to the reporting entity. Customer due diligence and source of funds analysis may be more complex with unhosted wallets, requiring advanced blockchain analytics to track historical exposure. However, compliance teams must not imply that an unhosted wallet is automatically suspicious, nor should they state that blockchain analytics can conclusively identify the beneficial owner of every unhosted address.

Transaction Hashes and Blockchain Evidence

Under FINTRAC virtual-currency recordkeeping guidance, MSBs must retain robust evidence of the transaction. This includes the transaction hash, the blockchain name, the timestamp, sending and receiving addresses, and the exact asset amount.

Evidence such as a screenshot or API log from a block explorer, internal platform records, customer instructions, and valuation evidence must be retained. The status of the transaction — such as the number of block confirmations required to establish receipt — must be documented.

MSBs must understand the limitations of public blockchain data. Blockchain records show the movement of tokens between alphanumeric addresses but do not establish legal ownership, beneficial ownership, the customer's true identity, the purpose of the transaction, or the relationship between the parties. Blockchain visibility must always be paired with off-chain Know Your Customer (KYC) data to form a complete LVCTR.

Third-Party Determination and Acting on Behalf of Another Person

When receiving CAD $10,000 or more in virtual currency, an MSB must determine whether the customer is conducting the transaction on behalf of another person or entity (a third party). This applies to corporate transactions where employees act for a business, or retail transactions where family members or nominees control the funds.

The MSB must ask the customer if a third party is involved and record the response. If the transaction involves wallets controlled by another party, the MSB must collect information about that third party and document the determination. If the customer claims to act alone, but blockchain analytics suggest they are a money mule for an illicit network, the MSB must escalate the file. Third-party determination asks who is directing the specific transaction; it must not be confused with beneficial-ownership verification.

Information Required for an LVCTR

Current official technical specifications group the required LVCTR information into the following categories:

• Reporting entity information: MSB name, location, and FINTRAC registration number.
• Transaction details: Date, time of receipt, and transaction type.
• Virtual-currency details: Type of asset and amount received.
• Canadian-dollar value: The calculated CAD equivalent and the exact exchange rate used.
• Valuation methodology: The source of the exchange rate.
• Wallet addresses: Sending and receiving alphanumeric identifiers.
• Transaction hash: The unique cryptographic identifier on the blockchain.
• Person or entity from whom the virtual currency was received: Customer identity details.
• Person or entity on whose behalf it was received: Third-party information.
• Beneficiary information: If the receipt is destined for someone other than the sender.
• Account information: Internal platform account numbers.
• Location information: IP addresses or physical branch locations.
• Related transaction information: Links to aggregated receipts under the 24-hour rule.

LVCTR Filing Workflow for an MSB

To ensure precision and avoid penalties, MSBs should integrate the following workflow, ideally utilizing robust FINTRAC reporting software:

1. Capture the virtual-currency transaction via internal platform or blockchain node.
2. Determine whether the asset meets the current statutory virtual-currency definition.
3. Determine exactly when receipt occurred based on operational control and confirmations.
4. Identify the customer and any relevant connected parties.
5. Capture the sending/receiving wallet addresses and the exact transaction hash.
6. Determine whether the customer is acting for a third party.
7. Calculate the Canadian-dollar value using a documented exchange rate at the time of receipt.
8. Check the individual threshold (CAD $10,000+).
9. Apply the 24-hour aggregation rule across all wallets and assets for that customer.
10. Validate mandatory report fields against FINTRAC schemas.
11. Conduct a human compliance review of the data.
12. Submit the report through the available FINTRAC reporting channel within 5 working days.
13. Retain the submission acknowledgement ID securely.
14. Resolve any validation or rejection errors immediately and correct the report where required.
15. Retain all valuation and blockchain evidence for the statutory period.
16. Consider a separate STR where reasonable grounds exist.

Filing an LVCTR does not remove the obligation to consider suspicious transaction reporting. An LVCTR and an STR are separate reporting obligations. If a large receipt triggers suspicion, knowing how to write an effective STR narrative is a vital supplementary skill.

FINTRAC Web Reporting vs API Submission for LVCTRs

MSBs can choose how to file an LVCTR depending on their transaction volume. Manual web submission requires compliance staff to type alphanumeric hashes and wallet addresses by hand, which is highly prone to typographical errors. API-based submission allows internal transaction systems to transmit structured JSON payloads automatically. Integrated reporting via API manages validation handling instantly, tracks submission acknowledgements, and supports high-volume workflows efficiently. Business-continuity arrangements must be maintained to file manually if the API connection fails.

Common LVCTR Filing Errors

MSBs frequently encounter regulatory deficiencies due to the following errors:

• Using the wrong valuation time: Applying a daily average rate instead of the exact rate at the time of receipt.
• Using an undocumented exchange rate: Failing to record where the CAD conversion price originated.
• Failing to retain valuation evidence: Discarding the API log showing the price at the time of the transaction.
• Missing transactions across separate wallets: Failing to link a user's mobile app wallet to their web platform wallet.
• Treating wallet addresses as confirmed identities: Assuming a sender's wallet address proves their legal name.
• Missing third-party information: Ignoring signs that a retail account is being used for an unlicensed corporate business.
• Incorrectly aggregating unrelated transactions: Merging transactions merely because they occurred at the same time.
• Failing to aggregate different virtual assets: Treating BTC and ETH deposits as entirely separate isolated events.
• Missing transaction hashes: Submitting an LVCTR without the cryptographic proof of the transfer.
• Using internal account credits without verifying the underlying blockchain transaction.
• Filing duplicate reports: Sending an LVCTR via API and then accidentally filing it again manually.
• Ignoring validation errors: Assuming a rejected JSON payload was successfully processed.
• Failing to retain submission acknowledgements: Losing the audit trail of regulatory compliance.
• Confusing an LVCTR with an STR: Assuming a large threshold report shields the MSB from suspicion reporting.
• Treating blockchain analytics output as conclusive evidence: Without verifying the physical off-chain reality.
• Relying entirely on reporting software: Blindly trusting automated scripts without human quality assurance.

These errors can be prevented through rigorous staff training and strict configuration of internal monitoring rules.

Recordkeeping and Audit Evidence

Under PCMLTFA regulations, records related to large virtual currency transactions must be kept for at least five years from the date the transaction occurred. MSBs must retain customer instructions, identification records, account records, wallet addresses, and the specific transaction hashes linking to blockchain evidence.

The valuation source and the exact exchange-rate calculation must be archived. Aggregation results, third-party determination records, internal review notes, validation messages, and submission acknowledgements form the backbone of an audit trail. Records of reversed or returned transactions, system logs, and escalation records must be kept. MSBs must maintain documented decisions detailing why a report was not filed.

Internal Controls for Reliable LVCTR Filing

Maintaining compliance requires robust, documented internal controls. Engaging professional AML advisory services helps structure these frameworks. Practical controls include:

• Centralised monitoring across all wallets and infrastructure.
• Strict customer-to-wallet mapping to ensure accurate aggregation.
• Cross-branch and agent visibility.
• Consistent time-zone settings across all servers for the 24-hour rule.
• Automated Canadian-dollar valuation using locked API price feeds.
• Retained exchange-rate evidence captured at the moment of receipt.
• Mandatory field validation preventing submission with missing hashes.
• Exception queues for transactions failing automated data checks.
• Maker-checker review for high-risk or complex receipts.
• Failed-report alerts and submission-status monitoring.
• Daily reconciliation of reportable transactions to submitted reports.
• Wallet-risk escalation protocols.
• Change management for API specification updates.
• Ongoing staff training and independent quality assurance testing.

It is vital to distinguish between direct FINTRAC legal requirements (e.g., the 5-day deadline) and recommended operational controls (e.g., automated maker-checker queues).

How Reporting Software Can Support LVCTR Compliance

To manage the technical burden of cryptocurrency AML compliance, sophisticated software assists with wallet and transaction data capture, precise customer-to-wallet mapping, and instant Canadian-dollar valuation. It creates permanent exchange-rate evidence, monitors the 24-hour aggregation window seamlessly, enforces mandatory field validation, and facilitates direct FINTRAC API submission. It also centralises exception management and tracks audit trails.

However, MSBs must recognize software limitations. Software cannot cure incomplete source data, incorrect wallet attribution, or incorrect valuation configuration resulting from poor setup. It cannot automatically generate missing third-party information or effectively map unsupported obscure assets without manual intervention. Unreviewed exceptions, API specification changes, vendor outages, and a false confidence in blockchain analytics can derail compliance. The reporting entity remains solely responsible for the accuracy, completeness, and timeliness of each report. No private software platform is FINTRAC-approved in a manner that transfers legal liability away from the MSB.