Finland applies CARF through DAC8 and reports to the Finnish Tax Administration (Vero). Finland asks for a bit more than the EU minimum: extra detail on domestic gains and losses. A report built only to the DAC8 baseline meets the EU rule but misses the Finnish one. Kryptos covers both.
DAC8 sets a common floor, but member states can ask for more, and Finland does: extra domestic gain and loss detail beyond what the baseline exchange carries. A build scoped only to the DAC8 minimum meets the EU obligation and misses the Finnish one.
Reporting gains and losses, rather than just proceeds, means working out cost basis correctly per asset in the right currency. That is the same reconciliation Kryptos already runs for the report, so the Finnish extra is a view of data you already have, not a second build.
You register in one member state and report there for your EU-resident users, and that state exchanges the data onward. A provider based in Finland reports to Vero, once, with the domestic detail Finland asks for included.
First reporting lands in 2027, covering data collected through 2026. Finland applies the DAC8 penalties through national law, so the domestic gain and loss detail needs to be part of your data from the start, not added at the end.
It runs on one system. You send your own transaction and account data, Kryptos collects self-certifications and checks tax IDs at onboarding, works out gains on the right basis, and builds the exact file the authority accepts, checked against the schema before you submit.
Yes. Finland implements DAC8 but also asks for extra domestic gain and loss data beyond the EU baseline. A report scoped only to the DAC8 minimum does not satisfy the Finnish requirement.
The Finnish Tax Administration (Vero). It receives DAC8 crypto-asset reports and exchanges them with other EU member states and CARF partners.
No. Reporting gains and losses uses the same cost-basis work Kryptos already does for the report, so the Finnish detail comes from data you already have.
Book a demo. We'll go through your obligations and show it working on your own data.