How to File Taxes on Token Vesting Income (And the One Spreadsheet That Saves You Hours)

If you've received tokens through vesting – as a founder, an early investor, an employee, an advisor, or via an airdrop with vesting attached – you have a tax problem most people misunderstand. Each tranche of vesting tokens is its own tax event. Not TGE. Not when you eventually sell. Each individual unlock or claim – depending on your jurisdiction – is a separate income-tax moment, valued in your local currency at that exact moment.

This guide explains how the tax actually works across major jurisdictions (and where they meaningfully differ), what software like Koinly, CoinTracker, and TurboTax need from you, and how Vestream collapses what is normally a 6-hour January spreadsheet into a 60-second download.

The Core Rule (And the Big Caveat)

The general two-step pattern across most major tax authorities looks like this:

1. 1At the taxable receipt event: the value of the tokens counts as ordinary income, taxed at your marginal rate. Value = (number of tokens) × (token's market price in your fiat currency at that moment).
2. 2At each later sale: the difference between your sale price and the price at the receipt event counts as capital gain or loss. The cost basis for the capital-gains calculation is the same value you reported as income.

The big caveat is what counts as the 'receipt event'. This is where jurisdictions diverge:

This means the value-at-receipt is the most consequential single number in your year-end vesting tax position. Get it right and everything else flows. Get it wrong – by using TGE price, year-end price, or "I'll figure it out later" – and you risk under- or over-paying both income tax now AND capital-gains tax later.

Vestream's Data Model: We Capture Claim Events

Important to understand what Vestream tracks: we index every on-chain claim transaction – the moment tokens leave the vesting contract and arrive in your wallet. For US filers, that's exactly the right tax event. For UK / Australia filers whose receipt event is the unlock date (not the claim), our claim-date data is still useful – but you'll need to map it forward to the unlock dates yourself or with your accountant.

• If you're in the US, Canada, Germany, most EU: Vestream's claim-date data IS the tax event. Use the CSV exports as-is.
• If you're in the UK or Australia: Vestream's claim-date data tells your accountant when you actually received the tokens. Your unlock schedule (also visible per-stream on the dashboard) tells them when those tokens became beneficially owned. They reconcile both for the right tax basis.
• Either way: the on-chain claim record is the canonical source of truth for what landed in your wallet, when, and at what price. That's the foundation every tax basis builds on.

What Counts as a 'Claim Event'?

A claim is any on-chain transaction that moves tokens from a vesting contract to your wallet. Different protocols call it different things:

The on-chain claim transaction is what Vestream indexes. Whether the claim is also the tax event depends on your jurisdiction (see the table further up). For US/Canada/Germany filers, the claim is the tax event. For UK/Australia filers, the unlock date can be earlier – your accountant maps Vestream's claim records back against the unlock schedule to assign income to the right tax year.

The Five Pieces of Information You Need Per Claim

For any tax-software import or accountant handover, every claim event needs to carry these five fields:

1. 1Date and time (UTC, to the second – block timestamp).
2. 2Token symbol and contract address (so software can match cost basis on later sales).
3. 3Quantity claimed, in whole token units (not raw on-chain wei).
4. 4USD value at claim, computed from the historical price on that exact date.
5. 5Transaction hash (proof, and the unique key that prevents double-counting).

How to Compute Historical Prices (And Why You Probably Shouldn't)

The historical-price lookup is where most people lose hours of tax-prep time. CoinGecko and CoinMarketCap both offer a free API that returns historical daily price data; Etherscan and BscScan offer historical price for the chain's native token but not arbitrary ERC-20s.

If you wanted to build the lookup yourself, the procedure is roughly:

1. 1For each claim event, take the block timestamp and convert to a UTC date.
2. 2Hit CoinGecko's /coins/{id}/history?date=DD-MM-YYYY with the token's CoinGecko ID for that date.
3. 3Read market_data.current_price.usd.
4. 4Multiply by the token quantity to get USD-at-claim.
5. 5Cache the result so you don't re-query for the same (token, date) twice.
6. 6Handle missing prices (illiquid tokens, pre-listing dates) with a manual cost basis or by accepting nearest-day.

It's about 200 lines of code per dimension – token resolution, rate-limit-aware fetching, caching, fallback ladder. Vestream does this once, server-side, with a 7-day fallback window and price-confidence flags so you know which numbers are exact-day vs nearest-day vs missing.

What Koinly, CoinTracker, and TurboTax Each Want

Each tax-software platform accepts a slightly different CSV shape. Vestream generates all three formats from the same underlying claim_events table:

All three CSVs need the same five fields per claim – date, token, quantity, USD value, tx hash – they just label and order them differently. Vestream's Exports tab generates each format exactly to spec.

The 60-Second Workflow on Vestream

1. 1Sign in at vestream.io and add the wallets that received your vesting tokens.
2. 2Open the Exports tab and hit Refresh claims. Vestream queries every supported protocol on every supported chain, indexes every withdrawal event since the wallet's first transaction, and computes USD-value-at-claim for each one.
3. 3Pick a tax year from the dropdown (e.g. 2025).
4. 4Click the format your accountant uses (Vestream generic / Koinly / CoinTracker / TurboTax). The CSV downloads instantly.
5. 5Optional: open the Income Statement for a P&L-style summary, then click Year-end PDF to generate a printable report you can email to your accountant directly.

Edge Cases Worth Knowing

• Continuous streams (Sablier, Superfluid): when you call withdraw, you receive everything that has accrued since the last withdrawal. That single transaction is one tax event – you don't pro-rate it across the days the tokens were accruing. The block timestamp of the withdraw is the canonical receipt date.
• Cliff unlocks: if a 6-month cliff unlocks 25% on day 180, the tax event timing depends on jurisdiction. In the US, the tax event happens when you claim those tokens, valued at the claim-date price. In the UK / Australia, the tax event can be the unlock date itself (day 180) regardless of when you claim. The price you use therefore differs: claim-date price for US, unlock-date price for UK/AU. Vestream surfaces the claim record; your accountant applies the right rule.
• Cancelled vests: if a stream is cancelled by the sender (cancellable vests), tokens already claimed are still income for the year they were claimed – the cancellation doesn't reverse it.
• Re-vesting / topped-up vests: some protocols allow the sender to add tokens to an existing vest. New tokens have their own clock; new claims against them are new tax events, valued at the new claim date.
• Non-EVM chains (Solana): Streamflow and Jupiter Lock store cumulative claimed amounts on-chain rather than per-event logs. Vestream uses a snapshot-diff model – the first refresh after you sign up captures pre-existing history as one baseline event; subsequent refreshes track new claims individually.

Timing, Forms, and When Returns Are Due

Some quick reference on key jurisdictions (verify with a local accountant):

Vestream does not provide tax advice. Use the data we surface to populate forms with your accountant. The CSV exports map cleanly to the import flows of Koinly, CoinTracker, and TurboTax – which themselves map to the right line items on the relevant local return.

FAQ

Get the Spreadsheet