Large Virtual Currency Transactions: Reports, Records, and the 24-Hour Rule

A Large Virtual Currency Transaction Report (LVCTR) is a threshold-driven obligation. Per current FINTRAC guidance, the trigger is receiving virtual currency equivalent to CAD 10,000 or more — whether that arrives as a single transaction or as several smaller ones that must be aggregated under the 24-hour rule. The direction matters: the obligation attaches to receipts of virtual currency, so an exchange that accepts $12,000-equivalent of bitcoin from a client, or a platform that receives a large deposit into a client's account, is squarely in scope.

Because virtual currency prices move constantly, the threshold question is really a valuation question. Current FINTRAC guidance explains how to convert the amount received into Canadian dollars; whatever rate source and method a business uses, it should apply that method consistently and keep evidence of the rate used for each transaction. A threshold decision that cannot be reconstructed later is difficult to defend.

The 24-hour rule exists so that linked transactions cannot slip under the threshold one piece at a time. Multiple receipts of virtual currency that individually fall below CAD 10,000, but that together reach it within a 24-hour window, are aggregated and reported as if they were one large transaction. Treating each small transfer in isolation is the single most common way businesses miss LVCTR filings.

Current FINTRAC guidance treats the window as a static 24-hour period rather than a rolling one, and it sets out how transactions are grouped — for example, receipts conducted by or on behalf of the same person, or for the same beneficiary. The precise grouping tests should be confirmed against the current LVCTR guidance rather than assumed. Operationally, aggregation requires four things in your data: a reliable timestamp for every receipt, a stable client identifier, a beneficiary identifier where one exists, and the CAD-equivalent value at the time of receipt. Without all four, no aggregation logic can run.

Recordkeeping starts well below the reporting threshold. Per current FINTRAC guidance, virtual currency transfer records attach to transfers of $1,000 or more — so a business can owe detailed records on a transaction it never has to report. The record set typically covers the payer and payee, the transfer instruction itself, custody details (which wallets or addresses were involved and who controlled them), and conversion details where virtual currency was exchanged for funds or another virtual currency, including amounts in both the virtual currency and its CAD equivalent.

When a transaction does trip the LVCTR threshold, a corresponding large virtual currency transaction record arises alongside the report. The practical lesson from businesses that have been through a FINTRAC examination is to design the full record set before launch — retrofitting payer, beneficiary, and rate data onto historical transactions after the first alert is slow, expensive, and often impossible.

Separately from reporting and recordkeeping, PCMLTFR s. 124.1 imposes the virtual-currency travel rule: when sending a virtual currency transfer, the sender must include the originator's and beneficiary's name, address, and account or reference number, and take reasonable measures to ensure that information accompanies the transfer. It is an information requirement on transfers, not a dollar-threshold rule, and it should not be conflated with the LVCTR threshold or the record thresholds above. A business that sends transfers needs a mechanism — protocol-level messaging, counterparty exchange, or documented reasonable measures — for moving that information with the value.

Pulled together, the operating picture looks like this: every receipt and transfer is timestamped, valued in CAD at the time of the transaction, and tied to identified parties; an aggregation check evaluates linked receipts against the 24-hour window; transactions of $1,000 or more generate the transfer record set; and receipts at or above CAD 10,000-equivalent — alone or aggregated — generate an LVCTR filed within the timeline set out in current FINTRAC guidance.

Documentation is what makes the system examinable. Businesses typically write down their valuation method, their aggregation logic and the grouping tests it applies, and the procedure for filing — then keep the underlying data so any individual threshold decision can be reconstructed. When the exact mechanics matter (grouping tests, filing timelines, field-level record requirements), check the current FINTRAC LVCTR and recordkeeping guidance rather than relying on summaries, including this one.