The FINTRAC Large Virtual Currency Transaction Report: threshold, 24-hour rule, fields and timing

The FINTRAC large virtual currency transaction report, usually shortened to LVCTR, is the report a Canadian reporting entity must file when it receives virtual currency equivalent to CAD 10,000 or more in a single transaction, or in two or more transactions within a consecutive 24-hour period that together reach that amount from the same person or entity. The report is due within five working days after the day of receipt and must carry the virtual currency amount, its Canadian dollar value and the source of the rate, the wallet addresses, the transaction identifier and the details of the parties. This article explains the threshold, the 24-hour rule, the reported fields, the timing and how a Canadian MSB or its partner institution operationalises the obligation for stablecoin settlement.

Who must file an LVCTR and when did the obligation begin?

The obligation sits with reporting entities under the Proceeds of Crime (Money Laundering) and Terrorist Financing Act that deal in virtual currency, which in practice means money services businesses and foreign money services businesses registered with FINTRAC, together with financial entities, securities dealers, casinos and other sectors when they receive virtual currency in the course of their activities. The requirement came into force on 1 June 2021 as part of the amendments that brought virtual currency dealing inside the Canadian regime and required virtual currency businesses to register as MSBs.

The important word in the obligation is receive. The LVCTR is triggered when the reporting entity receives virtual currency, whether as an exchange for fiat, as an incoming transfer for a client, or as payment for its own services. Sending virtual currency does not trigger an LVCTR, though it does trigger record keeping and Travel Rule obligations. For a stablecoin settlement platform serving a Canadian MSB, the receipt side of every flow is therefore the side to instrument: an inbound USDC payment from a foreign counterparty to the MSB's wallet, or a client depositing stablecoins for conversion to Canadian dollars, both count as receipts.

How does the CAD 10,000 threshold and the 24-hour rule work?

The threshold is measured in Canadian dollars at the time of receipt. The reporting entity converts the virtual currency amount using an exchange rate from a publicly available source at the time the transaction is received, and it must record which source was used. There is no prescribed source, but the choice must be consistent and documented. A single receipt worth CAD 10,000 or more is reportable on its own. Where no single receipt reaches the threshold, the 24-hour rule applies: two or more receipts within a consecutive 24-hour window are aggregated if they are conducted by the same person or entity, on behalf of the same person or entity, or for the same beneficiary, and a report is filed if the aggregate is CAD 10,000 or more.

FINTRAC's guidance describes the 24-hour window as consecutive rather than as a calendar day, and a reporting entity may define its own fixed window, such as 00:00 to 23:59 or a rolling 24 hours from the first transaction, provided the choice is documented in the compliance programme and applied consistently. The rule is also applied separately for each aggregation basis, which means a system must be able to group receipts three ways: by conductor, by the person on whose behalf the transaction was conducted, and by beneficiary. A single LVCTR can then report all the transactions in the aggregation together.

Which fields does the LVCTR require?

The LVCTR form is structured in parts and the detail required is greater than for a fiat large cash transaction report, because the on-chain data is available and FINTRAC expects it. The list below summarises the main parts as described in FINTRAC's reporting guidance and form; the reporting entity should check the current form for exact field names and mandatory markings, since FINTRAC revises its reporting forms periodically.

• Reporting entity information: the entity's identifier, contact details, and the location where the transaction took place, which for a virtual currency receipt is typically the branch or system through which it was recorded.
• Transaction information: the date and time of receipt, the type of virtual currency, the amount in virtual currency, the Canadian dollar equivalent, the exchange rate used, the source of that rate and the method by which the transaction was conducted.
• Starting action: the details of the virtual currency sent, including the sending virtual currency address and the transaction identifier or hash, where known.
• Completing action: what the reporting entity did with the virtual currency received, such as crediting an account, exchanging it to fiat or transferring it onward, together with the receiving virtual currency address.
• Conductor information: the person or entity that conducted the transaction, including name, address, date of birth for an individual, identification document details, occupation or nature of business, and account details where relevant.
• Third party and beneficiary information: whether the transaction was conducted on behalf of another person or entity, and the beneficiary's name and address, plus the indicator that the report was filed under the 24-hour rule when that applies.

Where a field is unknown after reasonable measures have been taken, FINTRAC's guidance allows the reporting entity to indicate that, but the file should show what measures were taken. A recurring finding in FINTRAC examinations is reports where the conductor's occupation, the sending address or the exchange rate source is missing without explanation.

What are the timing and submission rules?

The LVCTR must be submitted within five working days after the day on which the reporting entity received the virtual currency. Working days exclude weekends and statutory holidays. For a 24-hour rule report, the clock runs from the receipt that caused the aggregate to cross the threshold, and the report includes all the transactions in the window. Reports are submitted electronically through FINTRAC's web reporting system or by system-to-system transfer for larger volumes. A copy of each report must be retained for at least five years from the date it was submitted, together with the records that supported it.

The LVCTR is not a difficult report to write. It is a difficult report to trigger correctly, because the trigger lives in the aggregation logic and the exchange rate, not in the form.

There is one relief worth noting. FINTRAC does not require an LVCTR where the virtual currency is received from a financial entity or a public body, or from a very large corporation or subsidiary under the alternative to large transaction reporting, but the conditions are specific and the reporting entity should confirm them against the current regulations rather than assume they apply to a counterparty.

How does a Canadian MSB operationalise the LVCTR for stablecoin settlement?

The starting point is to identify every receipt event. On a settlement platform that means every inbound on-chain transfer to a wallet the MSB controls, whether the sender is a foreign counterparty institution, a business client on-ramping, or a return of funds after a failed payout. Each receipt needs a timestamp, a token and network, an amount, a sending address, a transaction hash, and an attribution to a conductor and a beneficiary. That attribution is the hard part on-chain, because the blockchain knows only addresses: the KYB and KYC layer must map the sending address to a known counterparty, and the Travel Rule payload received in IVMS101 form is the primary source for the originator details.

The second step is valuation. At the moment of receipt the system converts the amount to Canadian dollars using the documented rate source and stores the rate, the source and the time. For a USDC or USDT receipt this is a two-step conversion, stablecoin to US dollar and US dollar to Canadian dollar, and both rates should be stored. The third step is aggregation. The system maintains a rolling 24-hour view per conductor, per person on whose behalf, and per beneficiary, and raises a filing task when any view crosses CAD 10,000. The fourth step is production: the filing task pre-populates the LVCTR fields from the transfer record, the compliance officer reviews and submits, and the submission acknowledgement is stored against the transactions with the five-year retention flag set.

What should a partner institution ask of a Canadian MSB?

A bank or foreign institution that settles with a Canadian MSB in stablecoins is not itself the LVCTR filer, but its data feeds the report, and its own reputation depends on the MSB filing correctly. The partner should ask for four things. First, a written allocation of the obligation stating that the MSB files for receipts into its wallets and how it identifies the conductor and beneficiary from the partner's Travel Rule data. Second, confirmation of the exchange rate source and timing convention, so that both sides value the same transfer the same way for reconciliation. Third, evidence that the 24-hour aggregation runs across all three bases and across all of the MSB's receiving addresses, not per address. Fourth, a sample of filed LVCTRs with acknowledgements, redacted as required, and the MSB's most recent FINTRAC examination findings on reporting.

The partner should also expect the MSB to ask for complete originator and beneficiary data in the pacs.008 or the IVMS101 payload on every inbound settlement, because a receipt whose conductor cannot be identified will still be reported, but with gaps that draw examiner attention to both parties.

Where StableNet fits

StableNet, built by SpendTheBits, is a cross border B2B payment and settlement platform for banks, credit unions, licensed money service businesses, exchange houses and remittance fintechs, and its data model gives a Canadian MSB the inputs an LVCTR needs. Every inbound settlement in regulated stablecoins such as USDC and USDT is recorded with its network, transaction hash, sending and receiving addresses and timestamp, linked by UETR to the ISO 20022 pacs.008 that carries the structured originator and beneficiary details, with Travel Rule data exchanged in IVMS101 form. KYB and KYC onboarding maps counterparty addresses to identified parties, wallet screening and KYT run on receipt, and the tamper evident audit trail preserves the valuation and the filing record for the five-year retention period. Customers keep custody of their own wallets throughout. SpendTheBits is a Bank of Canada registered payment service provider and a named finalist in the Swift Hackathon 2026 Technical Challenge.