Token Vesting & Cliff Accounting: Recognising the Expense Over the Schedule

A founder's instinct is that a one-year cliff means "no cost until year one." Accounting disagrees. Once a token grant is a share-based payment, the expense accrues over the service period from grant — the cliff just gates exercisability. This guide is the recognition pattern, after the scope question is settled.

TL;DR

• A cliff does not delay the expense to the cliff date — cost is recognised over the vesting/service period from grant.
• Equity-settled IFRS 2 (or ASC 718): grant-date fair value, not remeasured, over the service period; straight-line common for a simple cliff unless another allocation is more reflective.
• Cash-settled/liability awards are remeasured each reporting date — different.
• Graded vesting = effectively several sub-awards; allocation per the standard, not an assumed flat line.
• Forfeitures/leavers are part of the model (service-condition treatment) — framework-specific.
• Assumes IFRS 2 scope — settle the IFRS 2 vs IAS 19 question first; not-in-scope → IAS 19, recognise as service rendered.

The cliff does not defer the cost

The recurring misconception: a one-year cliff means no expense until year one. For an equity-settled share-based payment in IFRS 2 (or ASC 718) scope, the grant-date fair value is recognised as an expense over the vesting/service period, not deferred to the cliff. For a simple cliff that vests after a service period, straight-line recognition over that period is the common pattern unless another allocation is more reflective of the benefit received. The cliff affects when the award becomes exercisable, not when the cost is recognised.

The recognition basis (equity-settled)

The scope and equity-vs-cash classification are settled first (see token compensation accounting and token vesting accounting); this is the recognition pattern after that.

Graded vesting is not one straight line

Graded vesting (tranches vesting on a schedule — e.g. monthly after a one-year cliff) means the award is effectively several sub-awards with different service periods. Recognition is more complex than a single straight line and depends on the framework's approach to graded awards. The principle is unchanged — cost over the service received — but the allocation across tranches must follow the applicable standard, not an assumed flat line.

Forfeitures and leavers

Awards that do not vest because a service condition is not met (a leaver before the cliff) generally do not result in a recognised cumulative expense for those awards, under the relevant framework's treatment of service (vesting) conditions; estimates or true-ups may apply depending on the standard and policy. Market vs non-market conditions are treated differently. The exact mechanics are framework-specific — the point: forfeiture is part of the model, not an afterthought.

Only if in IFRS 2 scope

All of the above assumes IFRS 2 scope. If the token is not the entity's equity instrument and the arrangement is not a share-based payment, it generally falls under IAS 19 as a non-cash employee benefit, recognised when the employee renders the service — a different recognition basis. Settle the IFRS 2 vs IAS 19 scope question first; this article does not apply if the answer is IAS 19.

Practical guidance

1. Recognise from grant over the service period — a cliff does not defer the cost.
2. Equity-settled: grant-date FV, not remeasured; cash-settled: remeasured.
3. Treat graded vesting as multiple sub-awards — allocate per the standard.
4. Model forfeitures/leavers under the service-condition rules.
5. Confirm the scope first — IFRS 2 vs IAS 19; this assumes IFRS 2.
6. Document the recognition policy and confirm with your auditor.

How vendor tools handle vesting recognition

Toku and Liquifi administer vesting schedules and grant data that feed the expense calculation. Confirm the tool exposes grant date, fair value, service period, tranche schedule, and forfeitures so the accounting can recognise cost over the service period (not at the cliff) — schedule administration is not the accounting recognition itself.

How Wag3s helps

Wag3s HR tracks grant date, fair value, vesting/cliff schedule, tranches, and forfeitures, and feeds the IFRS 2-scope expense recognition (over the service period, grant-date FV not remeasured for equity-settled) with an audit trail — once the scope question is settled. See the HR product page.

Further reading

• Token Compensation Accounting: IFRS 2 or IAS 19?
• Token Vesting Accounting
• BSPCE vs Token Grants for French Web3 Startups
• Web3 Employee Token Grant Structuring
• Token Compensation Tax Withholding
• Web3 Payroll Guide

Sources

• IFRS 2 / ASC 718 — equity-settled share-based payment: grant-date fair value, not subsequently remeasured, recognised over the vesting/requisite service period (cliff does not defer to the cliff date; straight-line common unless another allocation more reflective); cash-settled awards remeasured each reporting date
• Graded vesting allocated per the applicable standard (effectively multiple sub-awards); service-condition forfeiture treatment (market vs non-market conditions differ) — framework-specific
• Out of IFRS 2 scope → IAS 19 non-cash benefit recognised as service rendered (settle the scope question first — see token compensation accounting)