Lithuania's tax inspectorate spells out the crypto user data platforms owe under DAC8

For a platform, the date that sets the workload is the start of the collection year. According to Bitcoin.com News, full operational reporting took effect across the EU on Jan. 1, 2026, and exchanges between member-state tax administrations begin in mid-2027 ^[6]. That puts about 18 months between the first reportable record and the first exchange ^[10]. A platform that switches on residency and identification capture late in that first year has saved itself no time. We'd expect it to spend the following months completing files for customers it onboarded without those fields ^[2].

The report contradicts its own timeline. Another passage says data collected by platforms "throughout 2027" will be exchanged beginning in mid-2027 ^[11]. A full year of 2027 records cannot exist by the middle of 2027, so one of the two dates is wrong. We would build to Jan. 1, 2026. It is the date in the report's key takeaways, and a platform that starts early loses little if the later reading holds.

What the state wants is information. The order leaves Lithuania's baseline capital gains tax rates on virtual assets unchanged, according to the report ^[9]. The same report says operators serving Lithuanian residents must update onboarding workflows and back-end systems immediately to avoid penalties ^[9]. It does not include penalty amounts. Scope sets the size of the bill. Bloomberg, as cited by Bitcoin.com News, reported that the order clarifies which individual and corporate users fall under mandatory reporting ^[3]. Every account in scope then needs the identification numbers, transaction logs and account balances the technical instructions cover ^[4].

For a firm serving Lithuanians from elsewhere in the EU, this can go three ways. Applied as written, the duplicate-filing exemption makes Lithuania a place where the firm collects data and files nothing, provided it has registered and met its reporting duties in another member state ^[5]. A firm behind on its home filing may find the exemption does not reach it. Should the Inspectorate lean on the clause pointing to international standard interpretations where national law is silent ^[4], edge cases get one answer across borders and a system built to CARF needs few Lithuanian additions. If it writes its own answers instead, each Lithuanian customer costs more to onboard.

A separate cost line arrived earlier in the year. Since March 2, firms that transfer e-money tokens on behalf of customers, or run certain custodial wallets that allow third-party transfers, need additional authorization to provide payment services ^[7]. Crypto-to-crypto and crypto-to-fiat exchanges involving those tokens are not automatically payment services under the guidance ^[8]. A pure exchange can stay outside that requirement. A custodial wallet of the kind described cannot.

We think VA-63 is mostly a specification document aligning national procedure with DAC8 and CARF ^[1]. For a platform already built to CARF, the extra cost of Lithuanian users is small, and the exposure is whatever part of the collection year it has run without the new fields. The counter-case is scope: if Lithuania reads corporate-user coverage more widely than the international standard does, national fields come back. A Lithuanian filing demand on a firm already reporting elsewhere, or a national interpretation that departs from the international one, would show us wrong.