Binance, Coinbase and Kraken Tax Reports for Poland in 2026
A Binance, Coinbase or Kraken export is not a Polish PIT-38 return. Poland uses a statutory annual revenue-and-cost model for qualifying virtual currencies: paid disposals create PLN revenue, documented direct acquisition and disposal expenditure enters annual cost fields, and unused excess cost rolls into the next year. Crypto-to-crypto exchange is generally outside paid disposal, and the official portal confirms a 19% rate rather than progressive 12% or 32% tax. This guide shows how to consolidate exchange and wallet data without inventing per-platform gains or losing carried costs.
The Polish virtual-currency model in one page
Prepare Your Crypto Tax Workpapers
Import your transactions, review the results and generate detailed tax workpapers without building the entire calculation manually in spreadsheets.
Start for free →The Polish Ministry of Finance provides a dedicated official explanation for paid disposal of virtual currencies. The central rules are:
- file PIT-38 when you made a paid acquisition or paid disposal of qualifying virtual currency;
- paid disposal includes exchange for legal tender, goods, services or another property right, and settlement of another liability;
- an exchange between qualifying virtual currencies is not taxed at that stage;
- income equals annual paid-disposal revenue minus qualifying annual costs;
- the tax rate is 19%;
- if costs exceed revenue, taxable income is zero and the excess cost increases the next year’s virtual-currency costs.
This is not a conventional capital-loss calculation and not a trade-by-trade FIFO gain schedule. The official guidance explicitly says that paid disposal of virtual currency never creates a tax loss. An economic negative result can instead produce unused qualifying cost carried into the next tax year.
What to download from Binance, Coinbase and Kraken
Download the raw history for every relevant product and retain the original files. Even though the tax calculation pools annual costs rather than matching tax lots to each sale, earlier-year information is needed to reconcile holdings, prove transfers and carry forward previously filed costs correctly.
| Platform | Source records | Typical gap |
|---|---|---|
| Binance | Spot, Convert, deposits, withdrawals, distributions, Earn, futures, funding and fees; read-only tax-report API where used | Separate wallets and products may require several exports. API and CSV data may overlap. |
| Coinbase | Transaction history and custom statements in CSV; historic Coinbase Pro records where relevant | Coinbase.com tax data does not automatically include Coinbase Wallet or former Coinbase Pro activity. |
| Kraken | Trades and Ledgers, deposits, withdrawals, fees, staking/Earn and separate futures history | Trades show executions; Ledgers show balance changes. Both are required for complete cash and token reconciliation. |
Binance’s tax-report API can feed third-party software, but it does not create PIT-38 and should have no trading or withdrawal permission. Coinbase reports designed for US users do not determine Polish revenue. Kraken’s balance snapshot helps confirm holdings but does not replace Trades and Ledgers.
The Ministry of Finance states that exchanges generally have no statutory obligation to issue PIT-8C or PIT-11 information for crypto purchase, sale or exchange transactions. The taxpayer must therefore build the annual schedule from exchange and wallet records.
Reconcile exchanges, banks and self-custody wallets
A transfer between accounts owned by the same taxpayer does not create paid-disposal revenue merely because one exchange records a withdrawal and another records a deposit. Match the two sides using asset, quantity, timestamp, network, addresses and transaction hash. Keep the network fee separately because its tax treatment depends on whether it is a direct qualifying acquisition or disposal cost.
- Import all exchanges, wallets, fiat deposits and withdrawals.
- Normalise time zones while preserving source timestamps.
- Link own-wallet transfers without creating acquisition or disposal revenue.
- Remove genuine API/CSV duplicates without deleting split fills or separate fees.
- Reconcile token balances and PLN cash flows to statements and bank records.
- Carry forward only the unused cost confirmed by the previous filed PIT-38.
- Flag unsupported deposits, withdrawals and negative balances for review.
An unmatched deposit is not automatically zero-cost income, and an unmatched withdrawal is not automatically a taxable sale. The report should show the unresolved quantity and continue processing the unaffected data.
Calculate PLN revenue and annual cost pools correctly
Paid-disposal revenue
Revenue arises when qualifying virtual currency is exchanged for PLN, EUR or other legal tender; for a good, service or property right other than virtual currency; or when it settles another obligation. A card purchase funded by crypto can therefore create revenue even if no fiat was withdrawn to a bank.
Convert foreign-currency amounts to PLN using the applicable documented tax conversion rule and retain the exchange-rate date and source. Do not use the current exchange rate or a year-end rate for every disposal.
Current-year acquisition and disposal costs
The official portal recognises documented expenditure directly incurred to acquire virtual currencies and costs connected with disposal, including documented expenditure paid to intermediaries involved in the sale. All qualifying costs incurred in the tax year are shown even if no disposal revenue arose in the same year.
The same guidance excludes expenditure not directly connected with acquisition or disposal, including financing costs, costs connected with swapping one virtual currency for another, mining equipment and electricity used for mining. Software should not treat every fee-labelled row as deductible automatically.
Prior-year and closing excess cost
PIT-38 keeps current-year cost, prior-year unclaimed cost and year-end unclaimed cost distinct. Start with the amount supported by the prior return, add the current qualifying cost once, subtract it through the annual statutory calculation and carry only the remaining excess forward.
Example: a taxpayer brings forward PLN 18,000, incurs PLN 7,000 new qualifying costs and has PLN 20,000 paid-disposal revenue. Total available cost is PLN 25,000, taxable virtual-currency income is zero and PLN 5,000 continues to the next year. It is not a PLN 5,000 capital loss available against shares, salary or derivatives.
A Binance–Kraken reconciliation with an excluded swap charge
Fictional 2026 example, already converted to PLN using the applicable NBP dates: a Binance acquisition costs PLN 10,000 plus a direct PLN 100 purchase commission. A later qualifying crypto-to-crypto conversion has a PLN 50 charge. Coins move to the user's Kraken account and are sold for gross PLN 16,000, with PLN 160 of direct sale commission. The user has PLN 2,000 of unused declared prior costs; no other disposals, eligible expenses or foreign taxes arise.
| Export item | Polish annual treatment | Amount |
|---|---|---|
| Fiat-funded purchase and purchase commission | Current cost | PLN 10,100 |
| Qualifying virtual-currency conversion | No disposal revenue; swap charge excluded from this cost category | PLN 50 recorded separately |
| Withdrawal plus matching own-account deposit | One ownership-preserving transfer | No sale revenue |
| Kraken gross sale and direct commission | Revenue PLN 16,000; current disposal cost PLN 160 | Net fiat received PLN 15,840 |
| Available costs | 10,100 + 160 + 2,000 | PLN 12,260 |
| Income and ordinary PIT | 16,000 − 12,260 = 3,740; × 19% | PLN 710.60 before final rounding; PLN 711 due |
Attach the original Binance purchase rows, the conversion rows, the withdrawal/deposit pair and Kraken sale/ledger entries. Recording only net cash proceeds and also deducting the sale commission would deduct that commission twice. The 2025 PIT-38 brochure, pages 7–8 explains the checked full-PLN rounding convention. Verify the final form for 2026 when filing; retain both the calculation before rounding and the submitted amount.
Crypto swaps, rewards, DeFi and derivatives
A swap from one qualifying virtual currency to another is generally not paid disposal. Keep both legs in the holdings history, but do not generate current PIT-38 revenue merely because an exchange labels the operation “sell BTC / buy ETH.” The official guidance also excludes costs connected with this virtual-currency-to-virtual-currency exchange from the qualifying cost pool.
The legal definition of virtual currency still matters. A tokenised share, unique NFT, derivative contract or other property right may not be a qualifying virtual currency. Exchanging BTC for such a right can be paid disposal even though the platform places both products under a “crypto” menu.
Staking, mining, lending and airdrop receipts can raise an income question before later disposal. The later exchange of a qualifying received token for fiat may enter PIT-38, but that does not erase the receipt classification. Keep income value, token quantity and later disposal separate; see the Poland staking and DeFi guide.
Futures and perpetuals are contracts, not virtual-currency units merely because BTC is the reference asset. An opening order or an unrealised position snapshot is not itself proof of realised derivative income. Identify actual contractual settlements, including any daily settlement while a position remains open. Realised P&L, funding and fees need a separate legally classified derivatives schedule and do not automatically belong in the virtual-currency pool.
Does business trading change the PIT-38 route?
The official portal states that paid acquisition and disposal of virtual currency are reported on PIT-38 even when undertaken within a business. It identifies a specific exception for business activity of the type described in Article 2(1)(12) of the Polish AML Act—professional virtual-currency services such as exchange or intermediation—where the transactions are accounted for in that non-agricultural business.
Frequent proprietary trading does not automatically let a taxpayer choose progressive business rates or deduct all overhead. The report should distinguish proprietary holdings from providing regulated virtual-currency services and retain business registration, contracts and accounting evidence.
How the report reaches PIT-38
For transactions during 2025, PIT-38 is filed between 15 February and 30 April 2026. It can be filed electronically through Twój e-PIT, e-Urząd Skarbowy or e-Deklaracje, or on paper. A return is required when the taxpayer had a paid acquisition even if there was no paid disposal revenue.
The working paper should reconcile four numbers:
- PLN revenue from paid disposal during the year;
- documented qualifying costs incurred during the year;
- unclaimed qualifying costs brought forward from prior years;
- unclaimed excess cost carried into the next year.
Do not report a negative virtual-currency income. Taxable income floors at zero, and the 19% tax applies only to positive income after the statutory cost calculation. The PIT-38 filing guide explains the field-level workflow, while the Poland cost-and-loss guide covers roll-forward controls.
Do not wait for the exchange to prefill Twój e-PIT
The official brochure requires self-submission where revenue or costs differ from the information provided through PIT-8C. Export coverage is therefore a taxpayer check even if Twój e-PIT already displays another investment return. Confirm the gross fiat sales, direct costs and previous year's unused crypto costs, then submit and save the UPO receipt. The ordinary 2026 return is due April 30, 2027; a provider's CARF submission does not replace it.
Final control checklist
- All exchange products, self-custody wallets and bank flows are included.
- Own transfers are matched and do not create revenue.
- Paid disposals are separated from crypto-to-crypto exchanges.
- Every PLN conversion has a documented rate and date.
- Direct qualifying costs are separated from financing, mining and swap-related expenditure.
- Prior cost comes from the filed prior PIT-38, not from a newly recalculated duplicate.
- Closing excess cost is carried forward once and is not labelled a tax loss.
- Rewards, DeFi, NFTs and derivatives remain in separate classification schedules.
- Missing data is marked not calculable rather than replaced with zero.
Frequently asked questions
Does Binance issue Polish PIT-8C or PIT-11 for crypto?
The Ministry of Finance says exchanges generally have no statutory obligation to issue those information forms for crypto purchases, sales and exchanges.
What tax rate applies to Polish virtual-currency income?
The official rate is 19%, not the progressive 12%/32% scale.
Is a BTC-to-ETH swap taxable?
An exchange between qualifying virtual currencies is generally not taxed as paid disposal, but both legs must remain in the records.
Does Poland require FIFO for PIT-38 crypto?
The official annual model pools paid-disposal revenue and qualifying costs. It does not calculate PIT-38 income as a freely selected per-sale FIFO gain schedule.
Must I file if I only bought crypto?
Yes. The Ministry instructs taxpayers to file PIT-38 when qualifying acquisition costs were incurred, even without disposal revenue.
Can excess crypto cost offset salary or stock gains?
No. It increases the next year’s virtual-currency disposal costs and is not a general capital loss.
Are futures included in the virtual-currency pool?
Not automatically. A futures or perpetual contract needs separate legal classification and a derivatives schedule.
Official and platform sources
- Polish Ministry of Finance: paid disposal, costs, PIT-38 and 19% rate
- Polish Ministry of Finance: current PIT forms
- Polish Ministry of Finance: Twój e-PIT
- Coinbase Help: statements and transaction exports
- Kraken Support: Trades, Ledgers and balance exports
- Binance Support: tax-report API and statements
Sources checked on 9 October 2026. The article follows the official Polish annual virtual-currency revenue-and-cost model.
Related Resources
Generate Your Crypto Tax Report
Import your transactions, review the results and generate a detailed PDF report with a transaction-level audit trail.
Start for free →Disclaimer: This article is for general informational purposes only and does not constitute tax advice. For individual tax advice, consult a licensed tax professional.