Crypto is generally taxable in Denmark when you dispose of it or receive it as income. For most individuals, Bitcoin and altcoins are typically assessed under rules tied to speculative acquisition, while certain stablecoin positions may require separate treatment. The practical rule is simple: if you sold, swapped, spent, staked, mined, or received crypto in 2025, assume a Danish tax consequence and document the fair market value in DKK at the exact time of the event.
This page is a legal-practical guide, not an individual tax ruling. Danish crypto taxation depends on facts, residency, source of income, asset classification, and whether Skattestyrelsen has issued explicit guidance for the transaction type. For complex DeFi, derivatives, hacked assets, or unclear stablecoin treatment, consider obtaining case-specific advice or a binding ruling.
Essential tax treatment, filing windows and compliance pressure points at a glance.
This is the period whose crypto transactions are generally reported in the 2026 filing cycle.
This is the standard reference point commonly used for filing the 2025 Danish return through TastSelv.
Some taxpayers with specific non-Danish income circumstances may have a later deadline. Confirm the current-year position directly in TastSelv.
DAC8 implementation and CARF-style reporting logic materially increase cross-border crypto transparency.
A Danish crypto tax event usually arises when you dispose of crypto or receive crypto as income. Disposal includes selling for fiat, swapping one token for another, or spending crypto on goods and services. Receipt includes salary, freelance compensation, staking rewards, mining proceeds, airdrops, and lending interest when the asset is actually received and can be valued in DKK.
The practical distinction that many taxpayers miss is that receipt taxation and later disposal taxation are two separate moments. If you are paid in crypto, you may have taxable income at receipt, and then a second gain or loss when you later sell or swap that same crypto. That two-step logic is one of the most common sources of underreporting in Denmark crypto tax cases.
For unclear DeFi events, use a confidence framework: official guidance, reasonable interpretation, and gray area. That is safer than copying generic software labels into TastSelv without source support.
Buy crypto with fiat
Usually non-taxable
Hold crypto
Usually non-taxable
Transfer between own wallets
Usually non-taxable
Sell crypto for fiat
Usually taxable
Swap crypto for crypto
Usually taxable
Spend crypto
Usually taxable
Receive salary in crypto
Usually taxable
Receive staking rewards
Usually taxable
Receive mining rewards
Usually taxable
Receive airdrops
Usually taxable
Bridge or wrap tokens
Usually taxable
| Event | Treatment | Why | Value Basis | Records Needed |
|---|---|---|---|---|
| Selling crypto for DKK or other fiat | Usually taxable disposal. | A sale converts the asset into fiat and crystallizes a gain or loss. The standard calculation is proceeds in DKK minus cost basis in DKK. Disposal fees should be documented because they may affect net proceeds or basis depending on the transaction structure. | Executed sale value in DKK at transaction timestamp. | Exchange trade confirmation, CSV export, bank statement showing fiat receipt, wallet address, and timestamped price evidence. |
| Swapping one crypto for another | Usually taxable disposal of the asset given up. | A swap is not tax-free merely because no fiat touches your bank account. Denmark crypto tax analysis generally treats the outgoing token as disposed of at its fair market value in DKK at the time of the swap. | FMV in DKK of the asset disposed of at the exact trade time. | DEX or CEX trade log, tx hash, token quantities, execution time, and DKK valuation source. |
| Spending crypto on goods or services | Usually taxable disposal. | Using Bitcoin or another token to buy goods, travel, subscriptions, or gift cards is economically equivalent to selling the token and spending the cash value. The taxable amount is measured in DKK at payment time. | FMV in DKK at payment timestamp. | Merchant invoice, wallet tx hash, checkout receipt, and price conversion evidence. |
| Salary or freelance income paid in crypto | Taxable on receipt; later disposal also taxable. | The first tax point is the value of the crypto when you receive control over it. That same DKK amount then becomes the basis for a later sale or swap. This is a two-stage tax profile, not a single event. | FMV in DKK at the time the crypto is received and usable. | Employment or freelance agreement, invoice, payroll or payment statement, wallet receipt, and DKK valuation proof. |
| Mining, staking, airdrops, lending interest | Usually taxable on receipt; later disposal may create additional gain or loss. | When crypto rewards are credited and the taxpayer can use or withdraw them, Danish practice commonly treats the DKK value at receipt as taxable income. A second tax calculation applies if the tokens are later disposed of at a different value. | FMV in DKK at receipt time; later disposal uses separate DKK proceeds. | Protocol statements, validator or pool reports, tx hashes, screenshots for on-chain claims, and consistent DKK pricing methodology. |
| Stablecoin disposals | Potentially separate treatment from ordinary altcoins. | Some Denmark crypto tax guides distinguish certain stablecoin positions under financial-contract or capital-income style logic. The key compliance point is not to mix these transactions casually with Bitcoin and altcoin disposals. | DKK value at acquisition and disposal, tracked separately. | Trade logs, token identifiers, separate ledger, and reporting-box mapping. |
| Transfers between your own wallets | Generally not taxable if beneficial ownership does not change. | A pure internal transfer is usually not a disposal. The compliance risk is evidentiary: if you cannot prove both wallets are yours, a later reviewer may misread the chain of custody. Network fees on transfers should be logged separately because their treatment is not always straightforward. | No gain on principal transfer; fee should be valued in DKK if material. | Source and destination wallet addresses, tx hash, explorer screenshots, and wallet ownership evidence. |
| Wrapping, LP deposits, liquid staking, bridge moves | High-risk gray area; conservative practitioners often analyze whether a disposal occurred. | If the original asset is exchanged for a legally or economically distinct token, a tax authority may view the step as more than a simple transfer. The correct treatment depends on whether beneficial ownership, legal rights, counterparty exposure, and token identity changed. | DKK value at the moment the original token is exchanged or locked. | Protocol documentation, tx hashes, wallet trail, screenshots, token contract addresses, and a written classification memo. |
Danish crypto tax analysis starts with classification. For individuals, crypto is commonly discussed as a personal asset, but the decisive question is often whether it was acquired for speculative purposes. That point matters because speculative acquisition is what typically pulls many Bitcoin and altcoin gains into taxable treatment under Danish practice.
The phrase speculative purpose is not a slogan. It is a legal filter. Skattestyrelsen and Danish tax practice look at the asset’s nature, volatility, expected profit potential, and the taxpayer’s conduct. A token with no ordinary consumer use, high price volatility, and obvious upside motive is more likely to be viewed as speculative than an asset acquired for a narrow operational function.
Burden of proof matters here. If you argue that a token was not acquired speculatively, you should be able to show contemporaneous facts, not just a later narrative. That means wallet history, platform use, contract documentation, and a coherent explanation of why the asset was acquired.
Most Denmark crypto tax cases for individuals fall here. The core question is whether the crypto was acquired with a speculative profit motive. If yes, disposals are commonly taxable and rewards may be taxed on receipt.
If crypto activity is organized, repeated, service-based, or tied to a commercial operation, the tax analysis may move beyond passive investing. Mining, validator activity, or crypto accepted in business can shift the profile.
A Danish company holding or using crypto is not taxed under the same personal-asset logic as an individual. Corporate accounting, valuation, and documentation standards apply, and the legal analysis is usually more balance-sheet driven.
| Criterion | Occasional Investor | Self-employed Activity | Company |
|---|---|---|---|
| Purpose of acquisition | Profit expectation, trading intent, or holding for value appreciation points toward speculative treatment. | Acquisition tied to service delivery, treasury use, or operating activity may indicate business context. | Assessed in the context of corporate purpose, treasury policy, and accounting treatment. |
| Frequency and organization | Occasional trades can still be taxable if assets were speculative. | Repeated, structured, revenue-oriented activity is a stronger business signal. | Recorded through company books with recurring operational processes. |
| Type of receipts | Capital deployment and occasional rewards. | Client payments, service fees, mining or validator income linked to work effort. | Business receipts, treasury transactions, or proprietary trading. |
| Evidence expected | Purchase records, wallet trail, DKK valuations, and basis reconstruction. | Invoices, contracts, bookkeeping entries, wallet logs, and business rationale. | Board or management records, accounting policy, ledgers, and audit trail. |
| Stablecoin handling | Should be isolated rather than mixed blindly with altcoins. | Needs separate ledger treatment if used operationally or as settlement rail. | Should follow formal accounting classification and tax mapping. |
For individuals, Denmark crypto tax usually turns on two mechanics: tax on receipt and tax on disposal. Receipt covers salary, freelance payments, staking, mining, airdrops, and similar rewards. Disposal covers selling, swapping, or spending crypto. Those are distinct computations and should not be merged into one line item.
For Bitcoin and altcoins, many practical guides describe the result as taxation under personal income style rules when the asset was acquired for speculative purposes. Effective taxation can be high because the crypto result sits inside the broader Danish income architecture. That is why generic claims like “crypto tax is 42%” or “crypto tax is always 52%” are too crude to rely on.
Stablecoins need extra care. In Danish practice discussions, some stablecoin transactions are treated separately under a financial-contract or capital-income framework. The operational lesson is simple: maintain a separate ledger for stablecoins and do not assume that USDT, USDC, DAI, Bitcoin, and memecoins all belong in one tax bucket.
A practical valuation hierarchy improves defensibility: use the executed exchange price first; if unavailable, use a reliable market quote at the exact timestamp; then convert to DKK using a documented FX source; for illiquid tokens, retain screenshots, contract address, and a written valuation memo. That evidence stack is often more important than the software export itself.
| Rule | Practical Treatment |
|---|---|
| Selling Bitcoin or altcoins is generally taxable. | The standard calculation is Gain/Loss = Proceeds in DKK - Cost Basis in DKK. Use a consistent timestamp and valuation source. If fees were paid, keep them separately documented because they may affect the net calculation. |
| Crypto-to-crypto swaps are generally taxable even without fiat. | A BTC-to-ETH or ETH-to-SOL trade is normally treated as a disposal of the outgoing token at its fair market value in DKK. This is one of the most frequently missed Denmark crypto tax triggers. |
| Getting paid in crypto creates income at receipt. | If you receive salary, consulting fees, or freelance compensation in crypto, the DKK value when you receive control over the asset is the first taxable amount. That same DKK value becomes the basis for later disposal. |
| Staking, mining, airdrops, and lending rewards are commonly taxed when received. | The critical timing point is when the reward is actually credited, claimable, or withdrawable. For auto-compounding or protocol-level accruals, the exact taxable moment can be fact-sensitive and should be documented carefully. |
| Stablecoins may require separate reporting treatment. | Do not mix stablecoin gains and losses with ordinary altcoin disposals unless you have verified the correct Danish treatment. Separate wallet tagging and separate reporting-box mapping materially reduce filing errors. |
| FIFO is the practical cost-basis method to expect. | If you bought the same asset multiple times, the first acquired units are generally treated as the first disposed units. Missing basis records can create a severe under-documentation problem. |
| Wallet transfers are generally not taxable, but evidence matters. | If you move crypto from an exchange to your own Ledger or from one self-custody wallet to another, the principal transfer is usually not a disposal. Still keep tx hashes and ownership proof so the movement is not misread as a sale or gift. |
| Losses are not a free-for-all netting exercise. | Danish crypto loss treatment is more restrictive than many users expect. Separate reporting, same-asset conditions, and reduced effective value of deductions are the areas where overstatements often happen. |
Corporate crypto tax in Denmark does not follow the same personal-asset logic used for private individuals. A company is generally assessed through corporate accounting, recognition, and tax rules applicable to the legal entity’s activity. That means the analysis starts with the company’s business model, not with speculative-purpose language designed for private holders.
If a Danish company holds crypto as treasury, accepts crypto from customers, trades actively, or participates in staking or mining, it should maintain formal bookkeeping in DKK, a documented valuation policy, and a transaction-level audit trail. The tax answer often depends on how the asset is recorded in the accounts and what legal rights the company actually holds.
For companies interacting with stablecoins, DeFi, or cross-border exchanges, governance matters as much as tax math. Board-approved accounting policies, wallet control logs, and segregation between client assets and proprietary assets can materially reduce later disputes.
If the company is a crypto business, related pages on this site may also be relevant from a regulatory angle, including /crypto-licence/, /casp-license/, /mica-license/, and /crypto-regulations/. Tax, licensing, and safeguarding controls increasingly intersect in 2026.
| Topic | Treatment | Records |
|---|---|---|
| Treasury holdings of crypto | A company holding Bitcoin, ETH, or stablecoins as treasury should classify the position consistently in its accounts and keep a clear acquisition-purpose memo. Corporate tax treatment depends on the legal entity's accounting and business facts, not on retail investor assumptions. | General ledger, acquisition approvals, wallet ownership records, exchange statements, and DKK valuation files. |
| Customer payments received in crypto | If a business accepts crypto as payment, the company should recognize the value in DKK when the payment is received. A later sale or conversion of that crypto may create a separate taxable difference. | Invoices, payment references, wallet receipts, merchant processor statements, and DKK pricing evidence. |
| Staking, mining, and validator activity | Commercial staking or mining inside a company requires formal revenue recognition, expense tracking, and a clear timing policy for when rewards are considered received. Infrastructure costs, custody arrangements, and counterparty exposure should also be documented. | Validator or pool reports, node logs, reward statements, equipment or service invoices, and accounting policy notes. |
| Stablecoins and financial-contract style exposure | If the company uses stablecoins operationally or for trading, separate classification is prudent. The legal and tax treatment can diverge from ordinary altcoin holdings, especially where the economic profile resembles a financial instrument. | Token-level ledger, contract terms, exchange logs, treasury policy, and reporting-box rationale if relevant. |
| DeFi and wrapped assets | Corporate use of LP tokens, bridges, wrappers, or liquid staking derivatives should be documented with a written position memo. The company should not assume that every protocol movement is a non-taxable internal transfer. | Protocol screenshots, tx hashes, smart-contract addresses, internal approvals, and reconciliation schedules. |
DeFi is the part of Denmark crypto tax that competitors oversimplify. Some events are reasonably treated as taxable on receipt, such as staking rewards or lending interest when the taxpayer can actually control the tokens. Other events, including wrapping, bridging, LP deposits, liquid staking, or collateralized borrowing, sit in a gray area where explicit Skattestyrelsen guidance may be limited or highly fact-dependent.
The safest approach is to classify each DeFi action by legal effect: did you merely move the same asset between addresses you control, or did you exchange it for a different right, claim, or token? That legal-effect test is stronger than labeling everything “transfer” because many protocols issue a new token that represents a different bundle of rights.
Use three confidence levels in practice: official guidance, reasonable interpretation, and seek a binding ruling. That framework is especially useful for liquid staking tokens such as stETH, wrappers such as WBTC, LP receipt tokens from Uniswap, and lending positions on Aave.
For gray-area DeFi, keep a transaction memo with five items: protocol name, contract address, token in, token out, rights changed, and your chosen tax treatment. That memo is often the difference between a defensible filing and an improvised one. If the position is material, a binding ruling can be more valuable than any software categorization.
| Event | Typical Treatment | Valuation Basis |
|---|---|---|
| Staking rewards | Usually treated as taxable when the reward is actually received, credited, or becomes withdrawable and under the taxpayer's control. A later sale creates a second gain or loss calculation. | FMV in DKK at the time the reward becomes usable. |
| Mining rewards | Usually treated as taxable on receipt. If mining is organized commercially, the fact pattern may move toward business treatment rather than passive investor treatment. | FMV in DKK at the time the block reward or pool payout is received. |
| Airdrops and promotional distributions | Often treated as taxable when received if the taxpayer obtains control and the token has measurable value. Low-liquidity or restricted tokens require stronger valuation evidence. | FMV in DKK at receipt, using a documented market source or manual valuation memo. |
| Lending interest or yield | Usually analyzed as taxable income when credited or claimable. Reinvested yield should not be ignored merely because it stays on-platform. | FMV in DKK when the interest is credited or can be withdrawn. |
| Bridge transfer of the same asset | Potentially non-taxable if it is truly the same beneficial ownership and no economically distinct asset is received, but evidence must support that conclusion. | No disposal value if treated as internal movement; fees should still be tracked in DKK. |
| Wrapping tokens, such as BTC to WBTC | Gray area. Conservative practitioners often test whether the original asset was exchanged for a different token with distinct legal and counterparty features, which may support disposal treatment. | DKK value of the original token at the time of wrapping. |
| Liquid staking, such as ETH to stETH | Gray area. A conservative analysis often asks whether the user exchanged native ETH for a derivative token representing a different claim and liquidity profile. | DKK value of the asset given up when the derivative token is received. |
| LP deposit and LP receipt token | Gray area. If the user contributes assets to a pool and receives a new LP token, some practitioners treat that as an exchange rather than a pure transfer. | DKK value of assets deposited at the time the LP position is created. |
| Borrowing against crypto collateral | Borrowing itself is often not treated like a sale, but collateral movements, liquidation events, and protocol fees need separate analysis. | Loan proceeds, collateral value, and any liquidation value should all be tracked in DKK. |
Danish crypto reporting is done through TastSelv, and the tax year runs from 1 January to 31 December. For most individuals, the practical reference deadline for filing the return for the 2025 tax year is 1 May 2026, with a later date in some specific non-Danish income situations. Always distinguish the tax year from the filing year; many errors come from mixing those two.
The most useful operational rule is to separate transactions before you open TastSelv: ordinary Bitcoin and altcoin gains, ordinary Bitcoin and altcoin losses, stablecoin gains, stablecoin losses, and crypto income on receipt such as staking or mining. If you do this classification first, the reporting boxes become much easier to map.
Commonly cited box mapping in Denmark crypto tax practice is: Box 20 for gains on Bitcoin and altcoins and for crypto income such as staking, mining, airdrops, and interest; Box 58 for losses on Bitcoin and altcoins; Box 346 for gains on certain stablecoin or financial-contract style positions; and Box 85 for losses on those stablecoin positions. If your facts are unusual, verify the current-year box logic directly in TastSelv.
| Period | Obligation | Owner | Deadline |
|---|---|---|---|
| Throughout 2025 | Track every acquisition, disposal, reward, fee, and wallet transfer in DKK with timestamps. Separate ordinary altcoins from stablecoins and tag gray-area DeFi events for manual review. | Individual taxpayer | Ongoing during the tax year |
| Year-end close | Reconcile exchange CSV exports, API data, self-custody wallets, and bank statements. Rebuild missing basis before filing rather than after an audit request. | Individual taxpayer | As soon as possible after 31 Dec 2025 |
| Return preparation | Map gains, losses, and income to the relevant TastSelv boxes. Typical practical mapping: Box 20, Box 58, Box 346, Box 85. | Individual taxpayer or adviser | Before filing submission |
| Ordinary filing deadline | Submit the Danish tax return for the 2025 tax year through TastSelv. | Individual taxpayer | 1 May 2026 |
| Special deadline context | If you have specific non-Danish income circumstances, confirm whether a later filing date applies. | Individual taxpayer | Potentially 1 July 2026, subject to current-year rules |
| Post-filing retention | Keep the full evidence stack, including tx hashes, valuation sources, and wallet ownership proof, in case Skattestyrelsen asks follow-up questions. | Individual taxpayer | After filing and during retention period |
Audit-ready checklist for the 2025 tax year filed in 2026
These items define perimeter clarity, application readiness, and first-line control credibility.
Sequence these after the core perimeter, governance, and launch-control decisions are stable.
Skattestyrelsen can often track crypto more effectively than taxpayers assume. The visibility comes from three sources working together: KYC data from exchanges, public blockchain evidence, and cross-border reporting frameworks. In 2026, this environment is materially stronger than it was a few years ago because EU and OECD reporting architecture is moving toward routine crypto data exchange.
The two frameworks to know are DAC8 in the EU and the OECD CARF. They matter because they reduce the practical gap between an exchange account, a wallet trail, and a tax identity. Once a taxpayer has used centralized platforms, fiat rails, or KYC-linked services, the idea that crypto is invisible becomes much less realistic.
The main audit risks are not only deliberate non-disclosure. They are also ordinary compliance mistakes: missing swaps, no DKK valuation, mixed stablecoin treatment, broken basis history, and casual assumptions that every DeFi move was tax-free. Those errors can lead to underreporting, overpaying, or difficult follow-up questions from Skattestyrelsen.
Legal risk: Underreporting because crypto-to-crypto disposals are commonly taxable even without fiat. This is one of the highest-frequency Denmark crypto tax errors.
Mitigation: Reconstruct all swaps from exchange exports and on-chain history. Revalue each disposal in DKK at the trade timestamp.
Legal risk: Misclassification risk because certain stablecoin positions may require separate treatment and separate reporting boxes.
Mitigation: Maintain a separate stablecoin ledger and verify the current-year box mapping before filing.
Legal risk: Basis denial risk. If you cannot document acquisition cost, the practical result can be extremely unfavorable and may resemble a zero-basis outcome.
Mitigation: Rebuild basis using historic CSV files, bank transfers, wallet trails, and explorer evidence before filing.
Legal risk: Some transfers are harmless, but wrappers, bridges, LP receipts, and liquid staking can involve a change in legal rights or token identity.
Mitigation: Create a transaction memo for each gray-area event and apply a consistent treatment policy.
Legal risk: Timing error because reward income is commonly recognized when received or withdrawable, with a second tax event on later disposal.
Mitigation: Split receipt taxation from disposal taxation and keep reward timestamps in DKK.
Legal risk: Weak valuation evidence. A tax authority can challenge unsupported conversions or inconsistent timestamps.
Mitigation: Retain the spot price source, FX source, timestamp, and screenshots for non-standard assets.
Legal risk: Loss claims in these cases are not automatic and may fail if there is no disposal event or insufficient proof.
Mitigation: Keep exchange correspondence, police report where relevant, wallet evidence, and consider a binding ruling for material amounts.
Legal risk: Cross-border non-disclosure risk is rising under DAC8, CARF, KYC linkage, and public-chain analytics.
Mitigation: Disclose consistently across all venues and reconcile foreign-platform activity into the Danish return.
These are the practical questions most often asked by individuals filing Denmark crypto tax in 2026.
Yes. Crypto is generally taxable in Denmark when you dispose of it or receive it as income. For many individuals, the tax analysis turns on whether the asset was acquired for speculative purposes.
Usually no. Buying crypto with fiat is generally not a taxable event by itself. The risk starts later if you sell, swap, spend, or otherwise dispose of the asset.
Generally yes, in the sense that mere holding without disposal is not usually taxed. But you still need acquisition records because future gains and losses depend on documented cost basis.
Usually yes. Swapping one token for another is commonly treated as a taxable disposal of the outgoing token at its fair market value in DKK at the time of the trade.
Staking rewards are commonly treated as taxable when received, credited, or withdrawable. If you later sell those rewarded tokens, a separate gain or loss calculation usually applies.
Mining rewards are commonly taxed on receipt based on their DKK value at that time. If the mining activity is organized commercially, the facts may point toward business treatment rather than passive investor treatment.
Generally no, if both wallets belong to you and beneficial ownership does not change. Keep tx hashes and wallet ownership evidence because proof is what makes the transfer defensible.
The core formula is: Gain/Loss = Proceeds in DKK - Cost Basis in DKK. For income receipts such as salary or staking, the DKK value at receipt becomes the basis for later disposal.
FIFO is the practical method commonly referenced for Denmark crypto tax calculations. That means the first acquired units are generally treated as the first disposed units.
Use the executed price or reliable market price at the exact timestamp, then convert it to DKK using a documented FX source. Keep the source name, timestamp, and calculation record.
They may be. Some Danish crypto tax guidance and practitioner analysis treat certain stablecoin positions separately from ordinary altcoins, often under financial-contract or capital-income style logic. Keep them in a separate ledger.
A commonly cited practical mapping is: Box 20 for gains on Bitcoin and altcoins and for crypto income such as staking or mining; Box 58 for losses on Bitcoin and altcoins; Box 346 for certain stablecoin gains; and Box 85 for certain stablecoin losses. Confirm current-year treatment in TastSelv.
For the 2025 tax year, the ordinary reference filing deadline is generally 1 May 2026. Some taxpayers with specific non-Danish income circumstances may have a later date, often referenced as 1 July 2026.
Yes. Exchange KYC, bank links, public blockchain evidence, DAC8, and CARF all increase visibility. In 2026, the compliance environment is materially less forgiving than in earlier years.
Classify the event by legal effect, document your reasoning, and keep a written memo. For material or unusual cases such as wrapping, LP deposits, liquid staking, or hacked assets, case-specific advice or a binding ruling is often the safest route.
Before filing, make sure you have done eight things: reconciled all exchanges and wallets; rebuilt missing basis; separated ordinary altcoins from stablecoins; valued every taxable event in DKK; split receipt income from later disposals; reviewed DeFi gray areas manually; mapped figures to the correct TastSelv boxes; and retained your audit evidence pack. If your activity includes a company, treasury holdings, or cross-border crypto operations, related pages such as /accounting/, /crypto-regulations/, /mica-regulation/, and /bank-account-opening/ may also be relevant.
