Zondacrypto scandal and KSeF - tax transparency 2026

The Zondacrypto scandal revealed that Poland's crypto market operated without oversight, mandatory documentation, or investor protection. Three pillars of new transparency - KSeF (mandatory e-invoices), DAC8 (crypto transaction reporting), and MiCA (exchange licensing) - aim to close this gap from 2026.

Any crypto company issuing VAT invoices (commissions, fees, advisory services) must use KSeF. Tools like KSeFGPT automate XML FA(3) generation, validation, and submission - critical for the high transaction volumes typical of exchanges and crypto desks.

Affected Zondacrypto clients who lost access to their transaction history must still file PIT-38 tax returns. Missing documentation does not exempt from tax obligations - and the tax authority has its own data sources on crypto transactions.

On April 23, 2026, Zondacrypto - Poland's largest cryptocurrency exchange, formerly known as BitBay - went offline. Clients lost access to their funds and transaction history. Within two weeks, the District Prosecutor's Office in Katowice received over 1,500 criminal reports. According to media reports, client losses may have exceeded $100 million.

This is not just a crypto investor drama. It is a case study showing what happens when a market operates without oversight and tax documentation depends on a single platform. In May 2026 - with KSeF already mandatory, DAC8 in force since January, and Poland's parliament debating MiCA implementation - the Zondacrypto collapse becomes a catalog of threats that new regulations aim to eliminate.

This article analyzes how the KSeF + DAC8 + MiCA triangle reshapes tax transparency in the crypto sector - and what it means in practice for businesses, accounting firms, and affected exchange clients.

Zondacrypto (formerly BitBay) was Poland's largest crypto exchange, serving tens of thousands of clients across Poland and Europe. The company sponsored the Tour de Suisse cycling race and cultivated an image of a reliable market player.

In March 2026, warning signs appeared: withdrawal delays, platform errors, no support response. On-chain analysis revealed that the exchange's BTC reserves dropped 99.7% - from approximately 55.7 BTC to just 0.18 BTC. On April 23, 2026, the Zondacrypto website went offline.

The Katowice District Prosecutor's Office launched an investigation. By May 12, 2026, over 1,500 criminal reports had been filed. According to media reports, CEO Przemyslaw Kral was reportedly in Dubai. On May 11, 2026, Tour de Suisse officially terminated its sponsorship contract.

The answer is simple: Polish law required almost nothing from crypto exchanges. Until the Zondacrypto collapse, exchanges operated based on a simple registration as 'virtual currency activity'. No KNF (financial supervision) license, no capital requirements, no client fund segregation, no proof-of-reserves.

The EU adopted the MiCA regulation (Markets in Crypto-Assets) precisely to close this gap. The problem: Poland did not implement MiCA. President Nawrocki vetoed the implementation bill twice. On May 12, 2026, Poland's Sejm (lower house) began debating five separate crypto asset bills.

Three regulations - each at a different level - together create a system where financial anonymity in crypto becomes practically impossible.

KSeF (Poland's National e-Invoice System) has been mandatory since February 1, 2026 (large taxpayers) and April 1, 2026 (all others). Any crypto company issuing VAT invoices - for commissions, transaction fees, advisory services, wallet hosting - must send them as XML FA(3) through KSeF. Important caveat: crypto trading itself is VAT-exempt under art. 43(1)(7)(e) of the Polish VAT Act. But commissions and service fees are not.

DAC8 (Directive on Administrative Cooperation - 8th amendment) has been in force across the EU since January 1, 2026. It requires crypto exchanges and desks to report transaction data to tax authorities: user identification, buy/sell values, transfers to external wallets. First reports for 2026 are due to Poland's KAS (National Revenue Administration) by January 31, 2027.

MiCA (Markets in Crypto-Assets Regulation) introduces exchange licensing, capital requirements, and client fund segregation - exactly what was missing in the Zondacrypto case. In Poland, the MiCA implementation bill is still being debated (as of May 12, 2026).

Affected Zondacrypto clients face a double problem. They lost not only their funds but also access to transaction history - the sole source of documentation needed for PIT-38 tax returns for 2025.

Polish tax law is unambiguous: the tax obligation from crypto disposal arises at the moment of transaction, regardless of whether the exchange later collapses. The PIT-38 filing deadline was April 30, 2026 - one week after the exchange went offline.

The option for those affected: 'czynny zal' (voluntary disclosure) - reporting the delinquency to the tax office before an audit is initiated, combined with filing a return based on alternative documentation (bank statements, screenshots, CSV exports from when the exchange was still operational).

Crypto firms - exchanges, desks, advisory - often ask whether KSeF applies to them. The answer: yes, but with an important caveat. Crypto trading itself is VAT-exempt. However, every commission, transaction fee, advisory service, and wallet hosting fee is a VAT-taxable transaction requiring a KSeF invoice.

Accounting firms serving crypto clients face an additional challenge: they must simultaneously handle VAT invoices in KSeF (commissions, fees) and PIT-38 returns (crypto trades across multiple exchanges).

KSeFGPT addresses these needs: automatic XML FA(3) generation, pre-submission validation, bulk import/export of invoices to KSeF, and an AI analytics module. Paid plans with a 1-day free PRO trial. Free tools (PDF-to-XML converter, XML validator) available without registration at /darmowe-narzedzia. Learn more about KSeFGPT features.

Below we answer the most common questions about KSeF, cryptocurrency, and tax obligations in the context of the Zondacrypto scandal.

If you found this article useful, explore these related materials:

Can you avoid using KSeF in 2026? - KSeF obligation, exceptions, and consequences

Bulk invoice submission to KSeF - how to send hundreds of documents at once

KSeFGPT - import, export, and AI analytics - full overview of the application

XML validation and processing in KSeF - how to avoid invoice rejections