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

"A one-year cliff means no cost until year one" is one of the most common founder assumptions about token grants, and the accounting contradicts it. Once a token grant is a share-based payment, the expense accrues over the service period from grant; the cliff only gates when the award becomes exercisable. This article picks up after the scope question is settled and focuses on one thing: how the expense is recognised over a vesting schedule. The prior step, whether the grant is even in IFRS 2 scope, is covered in the token compensation accounting article.

The recognition rule in brief

• A cliff does not delay the expense to the cliff date; cost is recognised over the vesting and service period, starting from grant.
• For an equity-settled award under IFRS 2 (or ASC 718), the measure is grant-date fair value, not subsequently remeasured, spread over the service period. Straight-line recognition is common for a simple cliff unless another allocation better reflects the benefit received.
• Cash-settled (liability-classified) awards behave differently: they are remeasured each reporting date.
• Graded vesting is effectively several sub-awards, allocated per the applicable standard rather than on an assumed flat line.
• Forfeitures and leavers are part of the model, through the framework's service-condition treatment.
• All of this assumes IFRS 2 scope. Settle the IFRS 2 vs IAS 19 question first; out of scope, the grant generally falls under IAS 19 and is recognised as service is rendered.

The cliff does not defer the cost

The recurring misconception is that 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 and 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 more faithfully reflects 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 the equity-versus-cash classification are settled first (see token compensation accounting and token vesting accounting); what follows is the recognition pattern after that.

Graded vesting is not one straight line

Graded vesting (tranches vesting on a schedule, for example 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 rather than an assumed flat line.

Forfeitures and leavers

Awards that do not vest because a service condition is not met, such as 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 the entity's policy, and market versus non-market conditions are treated differently. The exact mechanics are framework-specific; the point is that 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 own 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, which is 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. For equity-settled awards use grant-date fair value, not remeasured; cash-settled awards are remeasured.
3. Treat graded vesting as multiple sub-awards, allocated per the standard.
4. Model forfeitures and leavers under the service-condition rules.
5. Confirm the scope first (IFRS 2 versus IAS 19); this article assumes IFRS 2.
6. Document the recognition policy and confirm it with your auditor.

Configuring a tool for vesting recognition

The data that drives this expense calculation lives in whatever platform administers your vesting schedules, so the configuration that matters is whether that data is complete and exportable. Schedule administration is not the same as the accounting recognition, and a tool that tracks vesting cleanly can still leave you short of what the standard needs. Before you rely on one, check that it exposes:

• the grant date and the grant-date fair value, since that is the measure for an equity-settled award;
• the service period and the full tranche schedule, so graded vesting can be allocated correctly;
• forfeiture and leaver events, so the cumulative expense can be trued up.

Platforms such as Toku and Liquifi administer vesting schedules and grant data of this kind; the recognition itself still has to be performed against the applicable standard.

How Wag3s supports the recognition

Wag3s HR tracks the grant date, fair value, vesting and cliff schedule, tranches, and forfeitures, and feeds the IFRS 2-scope expense recognition (over the service period, with grant-date fair value not remeasured for equity-settled awards) on an audit trail, once the scope question has been settled. Because recognition turns on the scope determination and the precise arrangement terms, Wag3s is built to support your auditor's review of the policy, not to replace it. 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 — IFRS 2 Share-based Payment: equity-settled awards are measured at grant-date fair value, not subsequently remeasured, and recognised over the vesting (requisite service) period; cash-settled awards are remeasured each reporting date. Graded vesting and service-condition (forfeiture) treatment follow the standard.
• IFRS — IAS 19 Employee Benefits: the fallback where a token grant is not a share-based payment, recognised as the employee renders service. Settle the scope question first (see token compensation accounting).
• FASB — ASU 2023-08: US GAAP measurement of crypto assets at fair value, relevant where a US filer's token-grant accounting interacts with how the underlying tokens are carried.