Lithuania crypto tax is not a separate standalone tax regime. In practice, crypto taxes in Lithuania depend on who earns the income, what the transaction is, how the activity is characterized for tax purposes, and whether the business falls inside the MiCA Crypto-Asset Service Provider perimeter. In 2026, the decision cannot be made on tax alone: founders and compliance teams must assess the full stack of VMI tax administration, Bank of Lithuania authorization, FNTT AML/CFT controls, EU Travel Rule obligations under the recast Transfer of Funds Regulation, and DORA ICT resilience requirements. For companies, the baseline corporate income tax rate is 15%, subject to general Lithuanian tax rules and any qualifying reduced-rate conditions. For CASPs, MiCA capital thresholds remain a core entry filter: €50,000, €125,000, or €150,000 depending on services. VAT analysis also requires care: the CJEU judgment in Hedqvist (C-264/14) supports VAT exemption for certain fiat-to-bitcoin exchange services, but not every Web3 activity inherits that treatment automatically.
This page is an editorial compliance guide, not legal or tax advice. Lithuanian crypto tax treatment depends on taxpayer status, source and character of income, accounting treatment, residency, documentation quality, and the facts of each transaction. Confirm filing positions with the State Tax Inspectorate under the Ministry of Finance of the Republic of Lithuania (VMI) or a qualified Lithuanian tax adviser before acting.
Essential tax treatment, filing windows and compliance pressure points at a glance.
Regulation (EU) 2023/1114 created the EU-wide CASP framework and replaced the long-term relevance of legacy VASP framing.
From this point, crypto businesses targeting the EU needed to map services against MiCA rather than rely on older local-only labels.
Lithuanian market materials still use VASP terminology, but in 2026 the legally relevant perimeter is CASP under MiCA and related EU rules.
Founders now need one integrated model covering tax, accounting, AML, Travel Rule, governance, and ICT controls.
A taxable event in Lithuania is generally linked to a realization, receipt, or business-income trigger rather than mere passive holding. For practical analysis, crypto taxes in Lithuania should be tested event by event. The most common mistake is treating all crypto activity as one bucket. That approach fails both tax and audit logic because VMI will look at the legal character of each transaction, while accountants and CASP compliance teams must also preserve a clean transaction trail. Another operational point often missed by founders: a crypto-to-crypto swap can create a tax analysis issue even where no fiat hits the bank account, because value has still been disposed of and re-acquired. For VAT, separate the direct tax question from the indirect tax question; they do not always move together.
Buying crypto with fiat and continuing to hold
Usually non-taxable
Selling crypto for fiat
Usually taxable
Crypto-to-crypto swap
Usually taxable
Staking rewards
Usually taxable
Mining proceeds
Usually taxable
Airdrops
Usually taxable
Salary paid in crypto
Usually taxable
Transfer between own wallets with no disposal
Usually non-taxable
| Event | Treatment | Why | Value Basis | Records Needed |
|---|---|---|---|---|
| Buying crypto with fiat and holding | Usually not taxed at acquisition stage by itself | A purchase without disposal usually does not create realized income. The tax issue is deferred until later disposal, receipt of rewards, or another taxable characterization event. | Acquisition cost in EUR plus directly attributable fees | Exchange confirmation, bank payment trail, wallet address, timestamp, EUR conversion record, transaction fee data. |
| Selling crypto for fiat | Usually a taxable disposal event | Conversion into fiat is the clearest realization event. Gain or loss is typically measured against acquisition cost and allowable direct fees. | Disposal proceeds in EUR minus cost basis minus allowable fees | Sale confirmation, exchange export, EUR proceeds, original acquisition records, wallet movement evidence, fee ledger. |
| Crypto-to-crypto swap | Often treated as a taxable disposal plus acquisition | Even without fiat, one asset is disposed of and another is acquired. This is a frequent blind spot in internal ledgers and one of the first reconciliation issues in crypto tax reviews. | Fair market value in EUR at time of swap, compared against cost basis of asset disposed | Swap transaction hash, platform statement, market-price source, timestamp, cost basis file, gas and execution fee records. |
| Staking rewards | Fact-specific income event, commonly analyzed as taxable upon receipt or later disposal depending on characterization | Rewards create accession to value. The tax point and classification should be tested against Lithuanian tax guidance and the taxpayer's status. For companies, accounting policy and revenue recognition become critical. | EUR value at receipt and later disposal value if sold | Protocol statement, validator or platform report, wallet logs, token receipt timestamps, EUR valuation source. |
| Mining proceeds | Usually analyzed as taxable income where value is generated through activity | Mining is closer to productive activity than passive holding. For individuals, frequency and organization matter; for companies, revenue and expense matching matters. | EUR value of coins received, with separate tracking of equipment, electricity, hosting, and other deductible cost candidates | Mining pool reports, wallet receipts, hardware invoices, electricity bills, hosting contracts, depreciation support, EUR valuation records. |
| Airdrops | Fact-specific and potentially taxable | Airdrops are not uniform. Tax analysis depends on whether the receipt is promotional, reward-based, work-related, or linked to prior holdings or protocol participation. | EUR value at receipt if taxable on receipt; later disposal value if sold | Airdrop announcement, eligibility basis, wallet receipt, token valuation source, evidence of any service or promotional condition. |
| Salary or contractor compensation paid in crypto | Usually taxable as employment or service income, not merely as investment gain | The underlying legal relationship matters more than the payment rail. Payroll, withholding, and social contribution analysis may arise separately from later disposal taxation. | EUR value at payment date, plus later gain/loss on subsequent disposal | Employment or service contract, payroll records, payment date valuation, wallet transfer proof, withholding documents. |
| Transfer between own wallets | Usually not taxable if beneficial ownership does not change | A self-transfer is not a disposal if the same taxpayer retains beneficial ownership. The practical risk is proving that both wallets are controlled by the same person or entity. | No disposal value if purely internal transfer | Wallet ownership evidence, internal transfer logs, transaction hashes, reconciliation file linking source and destination wallets. |
The first legal question is not the token type but the taxpayer type. In Lithuania, crypto taxes for an individual investor, a self-employed or business-like trader, and a company should not be merged into one narrative. This is where many public guides become unreliable. VMI will assess the person or entity earning the income, the frequency and organization of activity, the source of funds, the documentation trail, and whether the activity resembles investment, business, or regulated service provision. For founders, there is a second layer: a Lithuanian UAB can be a tax subject even where the founder is foreign, and a CASP can be regulated by the Bank of Lithuania while taxes remain administered by VMI and AML/CFT obligations remain relevant under FNTT oversight. A useful practical distinction is this: tax classification answers who is taxed and on what basis; MiCA classification answers whether authorization is required to perform the service at all.
A person buying and holding crypto for personal investment usually enters tax analysis at disposal or receipt of taxable rewards rather than at mere acquisition. Frequency, intent, and recordkeeping still matter.
A person trading, mining, validating, or providing services in an organized and recurring way may face a different characterization than a passive investor. The legal label follows facts, not marketing language.
A UAB or other legal entity holding or transacting in crypto is taxed under company rules. Crypto may appear as inventory, treasury asset, service consideration, or operating revenue depending on the model.
| Criterion | Occasional Investor | Self-employed Activity | Company |
|---|---|---|---|
| Main source of tax logic | Personal tax treatment linked to disposal and personal income characterization | Business-income style analysis, depending on facts and continuity | Corporate income tax and accounting treatment |
| Key authority | VMI | VMI; other registrations may matter depending on activity | VMI, with Bank of Lithuania and FNTT relevant if regulated activity exists |
| Typical trigger | Sale, swap, reward receipt, compensation receipt | Recurring revenue generation, organized trading or mining, service provision | Revenue recognition, asset disposal, treasury operations, payroll, service income |
| Main records needed | Exchange statements, wallet logs, EUR values, acquisition history | All investor records plus invoices, expense files, business contracts | Full accounting ledger, board-approved policies, invoices, wallet controls, reconciliations |
| Licensing overlay | Usually none unless providing services to others | May enter CASP perimeter if services are provided professionally | Must assess MiCA service scope, capital, governance, AML, Travel Rule, DORA |
For individuals, Lithuania crypto tax analysis usually begins when value is realized or received, not when crypto is merely purchased and held. The practical rule is simple: holding is not the same as disposal. However, the answer becomes more technical once the person trades frequently, receives staking or mining proceeds, or is paid in crypto for work. In those cases, the characterization of income may change. Public summaries often oversimplify this by saying there is one flat crypto tax. That is not a safe compliance position. VMI will look at the facts, including whether the activity is occasional investment or business-like. Another point often missed is foreign-platform usage: using a non-Lithuanian exchange does not remove Lithuanian tax reporting duties if the person is taxable in Lithuania. For audit readiness, the investor should maintain a EUR-denominated ledger and not rely only on screenshots from apps.
A safe working formula for individuals is: taxable gain or loss = disposal proceeds in EUR minus acquisition cost minus directly attributable fees. For example, if crypto was bought for €10,000, sold for €14,000, and fees were €200, the gain is €3,800. This formula does not replace taxpayer classification, but it is the core calculation starting point.
| Rule | Practical Treatment |
|---|---|
| Buying and holding crypto does not usually create tax by itself | Acquiring BTC, ETH, or another crypto-asset with fiat and continuing to hold it is generally not the taxable event. The tax issue usually arises later, when the asset is sold, swapped, or used in a way that realizes value. |
| Selling for fiat is the clearest taxable event | When an individual disposes of crypto for EUR or another fiat currency, the gain or loss should be measured against the acquisition cost and directly attributable fees. This is the cleanest example of a realization event. |
| Crypto-to-crypto swaps should not be ignored | A swap from one token into another can still create a taxable analysis issue because one asset has been disposed of. This is a common source of underreporting where no fiat bank movement exists. |
| Rewards and compensation require separate classification | Staking rewards, mining income, airdrops, and salary or contractor payments in crypto should be tested separately. They may be taxable on receipt, on disposal, or both depending on the legal characterization and facts. |
| Frequency and organization can change the tax profile | An individual who trades or mines in a structured, recurring, and commercial way may not be viewed the same as a passive investor. The legal analysis depends on substance, not on how the person describes the activity. |
| Recordkeeping is part of the tax position | If the individual cannot prove acquisition cost, wallet ownership, or EUR value at the relevant date, the filing position becomes weaker. Missing records are often more damaging than the tax rule itself. |
For companies, crypto taxes in Lithuania are usually analyzed through ordinary corporate tax and accounting principles rather than through a special crypto-only tax code. The baseline corporate income tax rate is 15%. A company may hold crypto as treasury, receive it as customer payment, trade it as part of operations, issue tokens, or provide regulated crypto-asset services. Each of those models creates a different accounting and tax profile. The most important practical point is that tax treatment follows the legal and accounting characterization of the transaction. A Lithuanian UAB that cannot explain whether tokens are inventory, intangible exposure, customer assets, or proprietary treasury assets will struggle both in tax review and in MiCA licensing conversations. Founders also often miss the segregation issue: client assets, company treasury, and fee income should not sit in one undifferentiated wallet architecture. That is not only a governance problem; it also creates tax and audit noise.
The reduced corporate tax rate that may apply to some small Lithuanian entities is subject to statutory conditions and should not be assumed for crypto businesses without checking eligibility. In practice, founders should treat 15% as the baseline and confirm any reduced-rate position only after reviewing ownership, employee, revenue, and anti-fragmentation conditions under current Lithuanian tax law.
| Topic | Treatment | Records |
|---|---|---|
| Trading income and treasury disposals | Where a company disposes of crypto held on its own balance sheet, gains and losses are generally analyzed within taxable profit under normal corporate tax rules. The exact treatment depends on accounting classification, valuation approach, and whether the asset is held as inventory, treasury, or another category. | Board-approved accounting policy, acquisition records, disposal records, EUR valuation methodology, wallet segregation evidence, reconciliation between blockchain data and general ledger. |
| Service revenue paid in crypto | If the company provides services and receives payment in crypto, the underlying revenue is still business revenue. The fact that the customer paid in tokens does not erase revenue recognition or tax analysis. | Invoices, contracts, payment-date EUR valuation, wallet receipts, customer identification data where relevant, bookkeeping entries. |
| Deductible expenses | Ordinary expense principles remain relevant. Legal fees, accounting, compliance tooling, blockchain analytics, custody infrastructure, and certain operating costs may be relevant to taxable profit analysis if properly documented and deductible under general rules. | Supplier invoices, contracts, proof of business purpose, payment records, allocation methodology for mixed-use costs. |
| Payroll and contractor payments in crypto | Compensation paid in crypto does not avoid payroll or service-income analysis. The company must identify the EUR value at payment date and preserve support for withholding and labor or service classification where applicable. | Employment or service agreements, payroll registers, payment-date valuation source, wallet transfer evidence, tax and social filing support. |
| CASP operating model | A regulated CASP must align tax books with prudential and AML segregation. Client-asset flows, fee income, treasury positions, and safeguarding arrangements should be identifiable separately. This is a tax control issue as much as a compliance issue. | Client asset mapping, wallet labeling, internal control matrix, transaction monitoring outputs, monthly reconciliations, policy documents. |
DeFi and reward-based activity should never be collapsed into one tax label. In Lithuania, the right approach is to isolate the legal source of value: validation reward, liquidity incentive, mining output, governance-token distribution, promotional airdrop, or compensation for work. That distinction matters because the tax point may arise on receipt, on disposal, or under a business-income analysis depending on facts. It also matters for CASPs because some on-chain reward models create additional AML monitoring and Travel Rule edge cases when funds move between hosted and self-hosted wallets. A further nuance often missed in public guides is valuation-source consistency. If a taxpayer values receipt using one market source and disposal using another without policy justification, audit reconciliation becomes harder.
Where public Lithuanian guidance does not answer a DeFi fact pattern directly, the defensible approach is to document the transaction mechanics, identify the moment of economic benefit, preserve valuation evidence, and obtain a written tax position. This is especially important for protocol rewards and bridge events, which are often misclassified in retail tax tools.
| Event | Typical Treatment | Valuation Basis |
|---|---|---|
| Staking rewards | Usually analyzed as income linked to receipt of reward, with a second tax analysis on later disposal if the rewarded tokens are sold or swapped. Classification depends on taxpayer status and facts. | EUR fair market value at receipt; later disposal value in EUR |
| Mining proceeds | Usually treated as income from productive activity rather than passive appreciation. For companies, expense matching and asset/equipment records are central. For individuals, regularity and organization matter. | EUR value when mined coins are received |
| Liquidity mining or yield farming incentives | Fact-specific. The tax profile may differ depending on whether the reward is interest-like, incentive-based, governance-related, or part of a broader business activity. Smart-contract risk does not remove tax analysis. | EUR value at receipt, with separate tracking of entry and exit transactions |
| Airdrops | Potentially taxable, but the answer depends on why the tokens were received. Airdrops linked to marketing, protocol participation, prior holdings, or services rendered may not all be treated identically. | EUR value at receipt if taxable on receipt; later disposal value if sold |
| Wrapped-token or bridge-related movements | Not automatically tax-neutral. Whether a bridge or wrap is a disposal depends on legal and economic substance, custody structure, and whether the original asset is extinguished or merely represented. | Case-specific EUR valuation at the point of conversion or redemption |
Tax reporting and regulatory reporting are different calendars. In Lithuania, a crypto founder can be fully focused on MiCA authorization and still miss a tax or accounting obligation. The practical solution is to run one integrated compliance calendar covering VMI, corporate accounting, payroll where relevant, and regulated-entity obligations. For CASPs, add AML reporting, suspicious transaction escalation, and ICT incident governance under the broader 2026 compliance stack. Another operational point: tax records should be closed monthly even if the formal filing happens annually. Waiting until year-end to reconstruct wallet flows is one of the main causes of filing error.
| Period | Obligation | Owner | Deadline |
|---|---|---|---|
| At each transaction date | Capture wallet movement, counterparty context where available, EUR valuation, fees, and supporting evidence for every acquisition, disposal, reward, or compensation event. | Taxpayer / finance team | Real time or same-day control |
| Monthly | Reconcile exchange statements, self-hosted wallet data, bank movements, and general ledger. Review unmatched transfers and missing cost basis entries. | Accounting / finance | Month-end close |
| Quarterly | Review taxpayer classification, VAT exposure, payroll-in-crypto events, and whether business activity has moved into MiCA CASP scope. | Tax lead / legal / compliance | Quarter-end governance review |
| Annual tax cycle | Prepare and submit annual tax filings based on taxpayer status, including company or individual reporting as applicable under Lithuanian law. | Individual taxpayer or company management with advisers | According to current VMI filing deadlines |
| Before CASP application | Align tax ledger methodology with business plan, source-of-funds narrative, AML controls, and wallet architecture before filing with the Bank of Lithuania. | Founder / CFO / legal / MLRO | Pre-application |
| Ongoing for regulated firms | Maintain AML monitoring, suspicious activity escalation, Travel Rule data handling, incident logging, and third-party ICT oversight. | Compliance / MLRO / ICT governance | Continuous |
Keep continuously and archive by tax year
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.
The main Lithuania crypto tax risk is not complexity alone; it is undocumented complexity. In 2026, tax, AML, and licensing failures often originate from the same operational weakness: poor data governance. A company that cannot prove cost basis usually also cannot explain source of funds, client-asset segregation, or Travel Rule controls. For founders, the practical lesson is that tax risk and CASP approval risk should be managed together, not in separate workstreams.
Legal risk: Taxable gain cannot be supported reliably, increasing exposure to reassessment, denied deductions, or disputes over reported profit.
Mitigation: Maintain acquisition ledger in EUR, preserve exchange exports, and reconcile wallet inflows to original purchases before filing.
Legal risk: Underreporting may occur because disposals are missed where no fiat proceeds are visible in bank statements.
Mitigation: Track swaps as disposal-and-acquisition events and apply a consistent EUR valuation methodology at transaction time.
Legal risk: Overbroad reliance on Hedqvist can create VAT exposure for services that are not equivalent to exempt fiat-to-bitcoin exchange.
Mitigation: Test each activity separately: exchange, advisory, software, token issuance, NFT-related services, custody, and other Web3 models.
Legal risk: The application narrative may fail to identify the actual CASP service perimeter, capital class, governance model, and prudential implications.
Mitigation: Map the business model directly to MiCA crypto-asset services and align tax, AML, and operational descriptions with that mapping.
Legal risk: This creates tax confusion, accounting weakness, AML monitoring gaps, and potential safeguarding concerns in a regulated context.
Mitigation: Implement wallet labeling, role-based access controls, monthly reconciliations, and separate ledger treatment for each asset population.
Legal risk: This can delay CASP authorization, trigger AML concerns, and undermine the credibility of tax filings and accounting entries.
Mitigation: Prepare a documented source-of-funds pack with bank evidence, investment agreements, historical wealth records, and transaction trail support.
Legal risk: Fact-specific transactions may be reported inconsistently across tax years, leading to audit challenge and internal control failure.
Mitigation: Adopt a written classification and valuation policy, preserve protocol evidence, and escalate unusual transactions for tax review before filing.
These answers are written for the 2026 legal and operational context. They are short by design and should be read together with VMI guidance, Bank of Lithuania materials, and the underlying EU regulations.
Yes. Lithuania does not operate a separate standalone crypto-only tax, but crypto-related income can still be taxed under ordinary tax rules. The answer depends on the taxpayer, the transaction, and the legal characterization of the income. For tax administration, the key authority is VMI.
Individuals and companies are not taxed under the same logic. For individuals, the analysis often centers on disposal events and the character of personal income. For companies, crypto is usually analyzed through corporate income tax, accounting treatment, revenue recognition, and deductibility rules. The baseline Lithuanian corporate income tax rate is 15%.
They can be. A crypto-to-crypto swap should not be assumed tax-neutral simply because no fiat was received. In many practical tax analyses, one crypto-asset is disposed of and another is acquired, so the swap needs EUR valuation and cost-basis support.
Holding by itself is usually not the taxable event. The tax issue generally arises when the asset is sold, swapped, used for compensation, or generates rewards such as staking or mining proceeds. Proper records should still be kept while holding.
Not always, and not never. The VAT position depends on the type of activity. The CJEU decision in Hedqvist (C-264/14) supports VAT exemption for certain exchange services involving traditional currency and bitcoin, but other Web3 activities require separate analysis under Lithuanian and EU VAT rules.
Often yes, if the business is providing custody and administration of crypto-assets on behalf of clients. In 2026, the legally relevant framework is MiCA and the authorization process is handled by the Bank of Lithuania. Legacy commercial labels like 'wallet license' are not the legal test.
MiCA sets minimum capital thresholds of €50,000, €125,000, and €150,000 depending on the crypto-asset services provided. Capital is only one part of the file; governance, AML/CFT, ICT controls, and operational substance are equally important.
The regulatory perimeter is split. The Bank of Lithuania handles authorization and financial supervision within its scope, FNTT is central to AML/CFT enforcement, VMI administers taxes, and the Centre of Registers is relevant for company registration and corporate records. These are different functions and should not be conflated.
Yes, foreign ownership is generally possible, but ownership does not remove local compliance obligations. The company still needs proper corporate registration, UBO transparency, tax compliance, and, if applicable, MiCA authorization, AML controls, and operational substance.
The practical timeline depends on how complete the file is. Preparation often takes weeks before submission, and regulatory review can extend over several months. Under MiCA processes, the formal assessment clock is tied to a complete application, so incomplete files create the biggest delays.
The exact staffing model depends on the business and regulatory expectations, but a CASP must have credible AML/CFT governance, clear accountability, and operationally effective controls. Founders should not assume that a nominal or outsourced function with no real authority will satisfy supervisory expectations.
Keep exchange statements, wallet addresses, transaction hashes, timestamps, EUR valuation records, acquisition cost support, fee and gas records, contracts, invoices, payroll documents where relevant, and monthly reconciliations. For regulated firms, align these records with AML, Travel Rule, and governance documentation.
MiCA authorization is designed for EU-wide operation within the applicable framework, but passporting is not the same as worldwide validity. The firm must still comply with MiCA conditions, local conduct requirements where relevant, and any other applicable EU laws such as the Transfer of Funds Regulation and DORA.
Lithuanian CASPs operating in 2026 must treat Travel Rule compliance as an operational requirement, not a policy footnote. The recast Transfer of Funds Regulation requires originator and beneficiary information handling for relevant transfers, and self-hosted wallet scenarios require additional control design.
A defensible Lithuania setup in 2026 requires one integrated model across tax, accounting, MiCA scope, AML/CFT, Travel Rule operations, and ICT controls. If the business is deciding between passive holding, active trading, treasury management, or a regulated CASP model, the right sequence is classification first, filing position second, and application strategy third. Related guides: /crypto-taxes/, /crypto-regulations/lithuania/, /crypto-licence/lithuania/, and /accounting/lithuania/.
