Poland DAC8 and CARF: Crypto Reporting from 2026

Poland implemented DAC8 and participation in the global CARF exchange system in 2026. Reporting crypto-asset service providers must cover relevant transactions from the beginning of 2026, even though the Polish law entered into force later. The system gives KAS more information, but it does not calculate a Polish taxpayer’s PIT-38 result.

What does DAC8 mean for Polish crypto users?

DAC8 extends automatic tax-information exchange across the European Union to relevant crypto-assets. Poland's implementing law requires reporting intermediaries to collect user and transaction information covering activity from 1 January 2026. The provider reports to the Head of the National Revenue Administration, and relevant information can be exchanged with the taxpayer's jurisdiction of residence.

This is not a new crypto tax and not a calculation of net income. Provider data can contain gross amounts and transfers without knowing historic acquisition cost, a previous exchange or whether the destination address belongs to the same user.

Poland's 2026 implementation

The Polish Ministry of Finance announced on 11 March 2026 that the President had signed the amendment implementing DAC8 and DAC9. The law entered into force on the day after publication and expressly covers crypto transactions occurring from the beginning of 2026. It also places Poland in the wider OECD CARF exchange system.

1. 1 January 2026: the first reportable period begins.
2. March 2026: national implementing legislation is signed and announced.
3. 20 July 2026: the Ministry opens technical consultations on draft CARF-R and CARF-I schemas.
4. June 30, 2027: the Polish provider deadline for the first annual user report, under Article 88l(1).
5. By 30 September 2027: first EU authority-to-authority exchange for 2026 data.

The last date is not the deadline for the individual's PIT-38. Polish personal filing follows its own timetable, generally from 15 February to 30 April of the following year.

Poland's enacted dates, rather than another country's deadline

The February 13, 2026 implementing Act, published March 17 entered into force on March 18. Article 10 makes 2026 the first reporting period, and Article 88l(1) sets June 30 of the following year for the provider's annual submission to KAS. Thus Poland's first provider deadline is June 30, 2027; it must not be replaced with a January deadline used in another jurisdiction. The EU authority exchange by September 30, 2027 is a later step.

Article 8 requires providers to request a residence self-certification from covered existing customers by October 31, 2026. That is the provider's request date, not a universal customer filing deadline. The transitional procedure requires repeat requests and provides for a final December 31, 2026 customer date; an unresolved certification then prevents reportable transactions until valid information is supplied. Respond to your own provider's request and keep the confirmation. This does not replace the April 30, 2027 PIT-38 deadline.

What are CARF-R and CARF-I?

As of the Ministry's July 2026 publication, the logical XSD structures and business-validation rules for CARF-R and CARF-I were consultation materials. Taxpayers should not confuse a draft technical format with a form they must personally file.

What information can be reported?

DAC8 and CARF combine due-diligence data with annual transaction aggregates. Depending on the user and service, the report can include:

• name, address, tax residence, TIN or other prescribed identifier, date and place of birth;
• entity and controlling-person information where applicable;
• provider identification;
• aggregate amounts, units and transaction counts for acquisitions and disposals against fiat;
• crypto-to-crypto exchanges and reportable retail payments;
• incoming and outgoing transfers, split by known transfer type;
• transfers to wallet addresses not known by the provider to belong to another service provider or financial institution.

These are generally annual aggregates by asset and category, not a guaranteed “perfect copy” of every tax lot. A gross amount does not establish deductible Polish cost. A provider can also report an outgoing transfer without knowing that the user retained ownership.

Self-custody, foreign exchanges and DeFi

A private wallet does not itself become an RCASP merely because it holds tokens. Nevertheless, an involved exchange may report a transfer to its address. Preserve transaction hashes and evidence linking the address to you. When coins later return to an exchange, historic cost should follow the documented position rather than restart at zero.

Non-EU operators can be required to register under DAC8 when they serve EU-resident users and are not already reporting through an equivalent participating jurisdiction. It is therefore inaccurate to publish a fixed list saying every Binance, Kraken or Coinbase account is always reported by the same entity. Check the contracting entity and provider notices.

Liquidity pools, lending, staking, bridges and wrapped assets can create transactions the centralised exchange cannot see. Reporting does not decide their Polish tax character. The Poland DeFi guide should be used alongside the provider reconciliation.

How CARF data relates to PIT-38

The Polish tax portal states that taxpayers report virtual-currency revenue and costs on PIT-38. It also states that eligible costs incurred in a tax year are disclosed even when no disposal revenue arose in that year. The filing deadline is generally 30 April of the following year.

The provider does not normally issue PIT-8C or PIT-11 merely for the user's purchases and sales of virtual currencies. The taxpayer must reconstruct PLN amounts and documented costs. CARF-I does not replace that work. See the complete Poland crypto tax guide for the tax calculation.

A reportable swap is not the same as Polish taxable revenue

Suppose the separately labelled annual data show PLN 30,000 of fiat disposals, PLN 45,000 of qualifying crypto-to-crypto exchanges and PLN 25,000 of transfers to the user's own wallet. Assume no spending, non-crypto rights or other sales. Only PLN 30,000 is paid-disposal revenue in this simplified Polish tax case. With PLN 12,000 current qualifying costs and PLN 8,000 prior unused costs, income is PLN 10,000 and ordinary PIT is PLN 1,900. Adding the three categories gives PLN 100,000 of different recorded activity, not a legal net-profit measure or a single prescribed CARF field.

Article 88n permits specified provider reporting values to use one consistently applied fiat currency. PIT conversion follows its own NBP rule. Differences can therefore remain even after every transaction is identified. Keep a bridge by transaction type, then by valuation currency and date; do not force a provider aggregate to equal your PLN income figure.

A practical reconciliation workflow

1. Confirm your legal name, tax residence and Polish identifier with every provider.
2. Download original CSV files and statements for every year.
3. Combine exchanges, wallets and protocols into one chronological ledger.
4. Match own-wallet transfers using hashes, quantities, time and fees.
5. Separate gross reportable transactions from PIT-38 revenue and deductible cost.
6. Mark missing costs or prices as unresolved rather than inserting zero.
7. Reconcile annual exchange totals with the Poland exchange report guide.

A defensible report explains differences instead of forcing two totals to match. Typical explanations include own-wallet movements, earlier acquisition on another platform, fees, different PLN conversion points or DeFi activity outside the exchange.

Common errors

• calling CARF the Common Reporting Standard instead of Crypto-Asset Reporting Framework;
• using PIT-37 rather than reviewing PIT-38 for private virtual-currency activity;
• treating every provider-reported transfer as taxable revenue;
• assuming the provider knows costs from external wallets;
• ignoring costs in a year without disposal revenue;
• confusing the 30 September exchange date with the personal filing deadline.

Frequently asked questions

Official sources

• Polish Ministry of Finance: 2026 DAC8 implementation
• Polish Ministry of Finance: CARF-R and CARF-I consultation
• Polish tax portal: virtual currencies and PIT-38
• European Commission: DAC8 scope and timeline

Legal and source review completed 9 October 2026.

Disclaimer: This article is for general informational purposes only and does not constitute tax advice. For individual tax advice, consult a licensed tax professional.