← Back to guides

Tax Reporting Obligations for Crypto Companies

2026-04-18 · Web3 Compliance AI

The Evolving Tax Landscape

Tax authorities worldwide have moved aggressively to close the crypto tax reporting gap. Two major frameworks are reshaping the landscape: the OECD's Crypto-Asset Reporting Framework (CARF) and the US Infrastructure Act's broker reporting requirements. By 2027, most major jurisdictions will require crypto businesses to collect customer tax identification numbers and report transaction data to tax authorities — who will then exchange that information internationally.

For crypto businesses, tax reporting is no longer a customer responsibility that you can ignore. You are becoming a reporting intermediary, with legal obligations to collect data, file reports, and face penalties for non-compliance.

Global Frameworks

OECD Crypto-Asset Reporting Framework (CARF)

CARF is the global standard for automatic exchange of tax information related to crypto-assets. Finalized by the OECD in 2023 and endorsed by the G20, it is being implemented across 50+ jurisdictions through 2027.

What CARF requires of Reporting Crypto-Asset Service Providers:

  1. Identify customer tax residence — Determine where each customer is tax-resident using self-certification and reasonableness checks.
  2. Collect Tax Identification Numbers (TINs) — Obtain the TIN for each reportable customer. Different countries use different TIN formats (SSN/EIN in the US, UTR/NI in the UK, TFN in Australia, etc.).
  3. Report annually to local tax authority — Submit:
    • Customer identification (name, address, TIN, date of birth)
    • Tax residence jurisdiction(s)
    • Aggregate gross proceeds from crypto dispositions by crypto-asset type
    • Number and type of transactions
    • Fair market value where applicable
  4. Automatic exchange — Your local tax authority exchanges the data with counterpart authorities in the customer's tax residence jurisdiction under the Common Reporting Standard (CRS) framework.

CARF implementation timeline:

Jurisdiction Group Expected Go-Live Status
Early adopters (UK, Canada, several EU states) 2026 Legislation enacted or in progress
EU (via DAC8) January 2026 reporting; exchanges from 2027 Directive adopted
Broader OECD members 2027 Implementing legislation in progress
Remaining committed jurisdictions 2027-2028 Various stages

Scope: CARF covers exchanges, brokers, ATM operators, and certain DeFi intermediaries. Stablecoins and NFTs used as investment instruments are included. CBDCs and specified electronic money products are excluded.

EU — DAC8 (Directive on Administrative Cooperation, 8th Revision)

The EU implemented CARF through DAC8, adopted in October 2023. DAC8 requires all EU-based crypto-asset service providers to report customer transaction data to their national tax authority.

Key DAC8 requirements:

  • Reporting start: First reporting period begins January 1, 2026. First reports due by January 31, 2027.
  • Scope: CASPs authorized under MiCA, plus certain operators without MiCA authorization (triggering registration obligations).
  • Reportable transactions:
    • Exchange of crypto-assets for fiat currency
    • Exchange of crypto-assets for other crypto-assets
    • Transfers of crypto-assets (reportable if above EUR 50,000 aggregate in a calendar year)
    • Retail payment transactions using crypto-assets
  • Customer data required: Name, address, TIN, date and place of birth, member state of tax residence.
  • Transaction data required: Type of crypto-asset, number of units, aggregate consideration (in fiat), fair market value, number of transactions.
  • Penalties: Set by each member state. Must be "effective, proportionate and dissuasive." Expect significant fines for non-reporting.

Interaction with MiCA: DAC8 obligations apply on top of MiCA authorization requirements. Your MiCA compliance program must incorporate tax reporting data collection from day one.

United States — Broker Reporting

The Infrastructure Investment and Jobs Act (2021) expanded the definition of "broker" to include crypto exchanges, certain DeFi protocols, and other intermediaries. The IRS has issued final regulations establishing detailed reporting requirements.

Form 1099-DA (Digital Assets)

Requirement Timeline
Gross proceeds reporting Tax year 2025 (forms issued early 2026)
Cost basis reporting Tax year 2026 (forms issued early 2027)
DeFi front-end broker definition Tax year 2027

What must be reported on Form 1099-DA:

  • Customer identification (name, TIN)
  • Description of the digital asset(s)
  • Date of transaction
  • Gross proceeds from disposition
  • Cost basis (beginning 2026)
  • Gain or loss (beginning 2026)
  • Whether the disposition was short-term or long-term

Broker obligations:

  1. Collect TINs — Request customer SSN/EIN (for US persons) or W-8 form (for foreign persons) at onboarding. Backup withholding (24%) applies if TIN is not provided.
  2. Track cost basis — Beginning with 2026 tax year, brokers must track and report the cost basis of digital assets. Use the customer's specified identification method, or default to FIFO.
  3. Transfer statements — When crypto is transferred between brokers, the sending broker must provide cost basis information to the receiving broker (similar to equity transfer statements).
  4. Filing: Submit 1099-DA to both the IRS and the customer by January 31 of the following year.

IRS final regulations: TD 10000 (gross proceeds, custodial brokers) and TD 10001 (DeFi brokers, transfer statements) provide detailed implementation rules. Read them.

Tax treatment of crypto in the US:

  • IRS treats crypto as property (IRS Notice 2014-21)
  • Capital gains/losses on disposal
  • Mining and staking income taxed as ordinary income at fair market value when received
  • Form 1040 includes a mandatory crypto question ("At any time during the tax year, did you receive, sell, send, exchange, or otherwise acquire any digital assets?")
  • Currency Transaction Reports (CTRs) required for cash transactions over $10,000 — FinCEN has proposed extending this to crypto

United Kingdom — HMRC

Current requirements:

  • HMRC treats crypto as property, subject to Capital Gains Tax (CGT) for individuals and Corporation Tax for businesses.
  • Annual exempt amount for CGT: GBP 3,000 (2024/25 onward, reduced from GBP 6,000).
  • Self-assessment filing required for individuals with crypto gains.
  • HMRC has been sending "nudge letters" to crypto users identified through data-sharing agreements with exchanges.

CARF implementation:

  • UK committed to CARF implementation from 2026.
  • Crypto businesses will be required to report customer transaction data to HMRC.
  • Legislation expected to follow closely the OECD CARF model.

Taxable events for crypto:

  • Selling crypto for fiat
  • Exchanging one crypto for another
  • Using crypto to pay for goods or services
  • Gifting crypto (except to spouses, civil partners, or charities)
  • Receiving mining or staking rewards (income tax)
  • Receiving airdrop tokens (income tax if received in return for a service)

Business income: If crypto trading constitutes a trade (based on badges of trade), profits are subject to Income Tax (individuals) or Corporation Tax (companies) rather than CGT.

Singapore — IRAS

Singapore has a distinctive tax position that makes it attractive for crypto businesses:

  • No capital gains tax — Singapore does not tax capital gains. Individuals holding crypto as investments pay no tax on disposal gains.
  • Business income: If crypto trading constitutes a business activity (companies and sole proprietors trading as a business), profits are subject to income tax at the corporate rate (17%).
  • GST: Digital Payment Tokens (DPTs) are exempt from GST when exchanged for fiat or other DPTs. This exemption was introduced in January 2020.
  • CARF commitment: Singapore has committed to CARF implementation. IRAS will require crypto businesses to report customer data for international exchange.

Key resource: IRAS e-Tax Guide on Income Tax Treatment of Digital Tokens provides detailed guidance on when crypto income is taxable.

Other Key Jurisdictions

Germany

  • Crypto held for over one year is tax-free for individuals (no capital gains tax after 12-month holding period).
  • Crypto held for less than one year: taxable as private disposal, exempt if total annual gains from all private disposals are under EUR 1,000 (increased from EUR 600 in 2024).
  • Staking rewards: subject to income tax; some controversy over whether staking extends the holding period.
  • BaFin-licensed entities subject to Corporation Tax on crypto income.

Japan

  • Crypto gains taxed as "miscellaneous income" at progressive rates up to 55% (combined national and local tax).
  • Tax reform discussions ongoing to potentially reduce crypto tax rates.
  • Annual tax return required for gains exceeding JPY 200,000.
  • JFSA-registered CAESPs required to provide transaction history reports to customers for tax filing.

UAE

  • No personal income tax and no corporate income tax on crypto gains (with limited exceptions for certain activities).
  • Free zone entities may have specific tax arrangements.
  • UAE has committed to CARF implementation — reporting obligations will apply to VASPs.

Canada

  • CRA treats crypto as a commodity for tax purposes.
  • Capital gains: 50% inclusion rate (increasing to 66.7% for gains above CAD 250,000 per year, effective 2024).
  • Business income: fully taxable if crypto trading is a business activity.
  • Barter transactions: crypto-to-crypto swaps are taxable events.
  • FINTRAC-registered MSBs will have CARF reporting obligations.

Australia

  • ATO treats crypto as CGT assets.
  • 50% CGT discount available for assets held over 12 months.
  • Personal use exemption for crypto purchases under AUD 10,000 (narrowly interpreted).
  • ATO has been active in data matching, obtaining bulk data from exchanges.
  • Australia committed to CARF implementation.

Practical Implementation for Crypto Businesses

Step 1: Collect TINs at Onboarding

Build tax identification number collection into your KYC/onboarding flow from day one. Retrofitting TIN collection on an existing customer base is expensive and disruptive.

  • What to collect: TIN, tax residence jurisdiction, self-certification of tax status.
  • Validation: Verify TIN format against the jurisdiction's known format. Perform reasonableness checks (does the address match the claimed tax residence?).
  • US-specific: W-9 (US persons) or W-8BEN/W-8BEN-E (foreign persons). Implement backup withholding (24%) if TIN not provided.

Step 2: Build Reporting Infrastructure

Invest in systems that can aggregate transaction data by customer, by crypto-asset type, and by tax jurisdiction.

Required data per transaction:

  • Customer identifier
  • Transaction type (buy, sell, swap, transfer, receive)
  • Crypto-asset type and amount
  • Fiat equivalent at time of transaction
  • Date and time
  • Counterparty (if applicable)
  • Cost basis (if tracking)

System requirements:

  • Aggregate gross proceeds by customer per reporting period
  • Separate reporting by crypto-asset type
  • Handle multi-jurisdiction reporting (a customer may be reportable in multiple jurisdictions)
  • Generate reports in the format required by each tax authority
  • Support corrections and amendments to previously filed reports

Step 3: Implement Cost Basis Tracking

For US broker reporting (Form 1099-DA, beginning 2026), you must track acquisition cost for each unit of crypto-asset.

Methods:

  • FIFO (First In, First Out) — Default method in many jurisdictions
  • Specific identification — Customer selects which lot to sell. Requires tracking individual lots.
  • Average cost — Permitted in some jurisdictions (UK for share pooling, some EU states)

Challenge: When customers deposit crypto from external wallets, you may not have cost basis data. The IRS requires brokers to use "reasonable methods" to determine cost basis for transferred-in assets, or report cost basis as "unknown."

Step 4: Engage Tax Counsel

Tax reporting rules are technically complex and vary across jurisdictions. Budget for professional guidance:

  • US: Tax attorney or CPA with crypto reporting experience
  • EU: Tax advisor in your home member state familiar with DAC8
  • Multi-jurisdictional: International tax firm with crypto practice

Step 5: Build a Compliance Calendar

Deadline Obligation Jurisdiction
January 31 File Form 1099-DA with IRS and deliver to customers US
January 31 DAC8 reports due to national tax authorities EU
January 31 Self-assessment tax return deadline (online) UK
March 1 CARF reports due (where applicable) Various
April 15 Individual tax return deadline (Form 1040) US
April 30 Individual tax return deadline Canada
Various Corporate tax return deadlines Varies by jurisdiction

Common Pitfalls

  1. Not collecting TINs at onboarding — Retroactive collection is painful and incomplete. Many customers will not respond to post-onboarding TIN requests. Build it into KYC.
  2. Ignoring crypto-to-crypto swaps — In most jurisdictions, swapping one crypto for another is a taxable event that must be reported. Do not treat swaps as non-reportable.
  3. No cost basis tracking — Without cost basis data, you cannot fulfill US 1099-DA obligations (starting 2026). Start tracking now.
  4. Treating CARF as distant — 2026/2027 is not far away. System development, TIN collection, and testing take 12-18 months. Start implementation now.
  5. Assuming no reporting obligation for DeFi — The US IRS has classified DeFi front-ends that effectuate transactions as brokers starting 2027. If you operate a DeFi interface, prepare for reporting obligations.
  6. Missing transfer statement requirements — When assets move between brokers, cost basis must be transferred. Build this capability before it becomes mandatory.

Resources