Poland Crypto Tax 2026

Poland has one of the cleanest crypto tax regimes in the EU: a flat 19%, crypto-to-crypto not taxable, one form (PIT-38), and a cost-carryforward that quietly works in the holder's favour. The simplicity is genuine — the points that catch people are the crypto-to-crypto treatment and the carry-forward mechanic. This guide covers both, plus the DAC8 cross-check.

TL;DR

• Flat 19% on income from disposing crypto for fiat, goods, or services (income from money capital).
• Crypto-to-crypto is NOT taxable — only fiat/goods/services disposals are taxable events.
• Costs carry forward indefinitely until matched against crypto income — report costs even in no-sale years.
• PIT-38 form, filed by 30 April of the following year.
• DAC8: from 1 Jan 2026 CASPs report; cross-check on declared taxable disposals.

The flat 19%

Poland taxes income from the disposal of crypto-assets at a flat 19% (treated as income from money capital / kapitały pieniężne). It is not progressive and there is no separate rate option for individuals in this category. The computation is: taxable disposal income minus deductible costs, taxed at 19%.

This puts Poland among the lower-rate, simpler EU regimes — compare Sweden's 30%, Finland's 30/34%, or Ireland's 33%. The simplicity advantage is real; the nuances are in what is taxable and how costs work.

Crypto-to-crypto is not taxable

The most important structural point: Poland does not treat crypto-to-crypto exchanges as taxable events. The taxable event is disposal of crypto for fiat currency, for goods or services, or to settle obligations. Swapping ETH for BTC, or rotating between tokens, is outside the taxable scope.

This is a sharp contrast with Spain and Italy (where crypto-to-crypto is taxable) and aligns more with the France-style "fiat exit is the event" logic. For an active on-chain trader who rarely cashes to fiat, the Polish regime can defer tax substantially — but the records must still track everything, because the eventual fiat disposal's cost basis depends on the full history.

The cost-carryforward mechanic

Poland's quietly favourable feature: acquisition costs are deductible against crypto disposal income, and excess costs carry forward to subsequent years until matched against crypto income — effectively indefinitely. The practical implications:

• In a year with no disposal, you still report costs on PIT-38 to preserve them.
• In a year where costs exceed income, the excess is not lost — it carries to the next year.
• Over a multi-year horizon, a buyer who accumulates for years and sells later has the cumulative cost base available against that eventual disposal.

The failure mode is not reporting costs in no-sale years, then losing easy substantiation later. The discipline is to file PIT-38 with costs even when nothing was sold.

PIT-38 and the deadline

Crypto income and costs are reported on the PIT-38 form as part of the annual return, due by 30 April of the year following the tax year. You report:

• The year's crypto disposal income (fiat/goods/services disposals only).
• Deductible costs, including costs carried forward from prior years.
• If there was no disposal: still file the costs to carry them forward.

DAC8 and Poland

From 1 January 2026, CASPs report Polish residents' crypto activity, exchanged to KAS (Krajowa Administracja Skarbowa) by 30 September 2027 for FY 2026 (see DAC8 transposition by country). Because Poland taxes only fiat/goods disposals (not crypto-to-crypto) at a flat 19%, the cross-check focuses on whether taxable disposals and proceeds were declared on PIT-38. Note a reconciliation nuance: CASP-reported data may include crypto-to-crypto volume that is not taxable in Poland — so a naive comparison can over-flag. Documenting which reported activity is non-taxable crypto-to-crypto is the Polish-specific reconciliation step (see DAC8 impact on individuals).

Practical workflow for Polish residents

1. Reconstruct history, separating taxable disposals (to fiat/goods/services) from non-taxable crypto-to-crypto.
2. Track costs, including carried-forward costs from prior years.
3. Compute 19% on disposal income minus deductible costs.
4. File PIT-38 by 30 April — including in no-sale years, to carry costs forward.
5. Reconcile against DAC8 data, documenting non-taxable crypto-to-crypto so the comparison is not over-flagged.

How vendor tools handle Poland

Koinly and Divly support Polish PIT-38 output. Two decisive checks: confirm the tool treats crypto-to-crypto as non-taxable in Poland (a tool applying a generic "every swap is taxable" model will massively overstate Polish tax), and confirm it carries excess costs forward rather than discarding them in no-sale years. Neither tool decides the business-activity boundary if the activity is genuinely professional.

How Wag3s helps

Wag3s Folio reconstructs history with the taxable/non-taxable disposal distinction Poland requires, preserves carried-forward costs across years, and reconciles against DAC8-reported activity (including flagging non-taxable crypto-to-crypto so the cross-check is not over-flagged). For Polish entities operating on-chain, Wag3s Ledger provides audit-ready records and multi-chain reconciliation. See the Folio and Ledger pages.

Further reading

• How to Do Crypto Taxes
• Spain Crypto Tax Guide 2026 — contrast: crypto-to-crypto IS taxable
• Sweden Crypto Tax Guide 2026
• Finland Crypto Tax Guide 2026
• DAC8 Impact on Individuals
• DAC8 Transposition by Country

Sources

• Krajowa Administracja Skarbowa (KAS) — PIT-38 instructions and guidance on taxation of crypto-asset disposal income (flat 19%, cost carry-forward, crypto-to-crypto non-taxable)
• Council Directive (EU) 2023/2226 (DAC8) — EUR-Lex