Token Compensation Accounting: IFRS 2 or IAS 19?

"We pay the team in tokens, so it's IFRS 2" is the assumption — and it is often wrong. IFRS 2 is for the entity's own equity instruments. Most native tokens are not that. This guide is the standard-selection fork that decides how token pay is measured and where the audit risk really sits.

TL;DR

• Token comp is not automatically IFRS 2. The fork: is the token the entity's equity instrument?
• Yes → IFRS 2 (equity-settled: grant-date fair value, not remeasured, over vesting; cash-settled: remeasured).
• No → IAS 19 non-cash employee benefit (recognise as service is rendered).
• US GAAP parallel: ASC 718 (share-based) vs ASC 710 (general compensation).
• Most native/utility tokens are not the entity's equity → often IAS 19 / general benefit, not IFRS 2.
• No dedicated crypto-comp standard — the scope judgement is the deliverable and the audit risk. Distinct from the vesting mechanics in token vesting accounting.

The fork, stated precisely

IFRS 2 Share-based Payment applies when an entity receives goods or services in exchange for its own equity instruments, or for cash amounts based on the price of those equity instruments. So the threshold question is:

Does the token granted meet the definition of the entity's equity instrument?

• Yes → the arrangement is in IFRS 2 scope.
• No → it is generally a non-cash employee benefit under IAS 19, recognised when the employee renders the service.

This is a scope determination, not a presentation choice. It is decided by what the token is, not by the fact that compensation was paid in crypto.

Why most native tokens are not IFRS 2

A native utility or protocol token typically does not represent equity in the granting entity — it is not a share, not a residual interest in the entity's net assets. Granting it to an employee is therefore frequently not a share-based payment of the entity's equity, which pushes the arrangement toward IAS 19 (a non-cash benefit) rather than IFRS 2. The common error is reflexively applying IFRS 2 because "it vests like options." Vesting mechanics do not make a non-equity token an equity instrument.

IFRS 2 measurement (if in scope)

The equity- vs cash-settled distinction is what determines whether you remeasure — a frequent source of error when token awards settle in a way that is economically cash-like.

The US GAAP parallel

US GAAP runs the same threshold logic with different labels:

• ASC 718 — share-based payment: compensation expense over vesting at grant-date fair value; cash-settled awards liability-classified and remeasured.
• ASC 710 — general (non-share-based) compensation.

Same question, different citation: is the token a share-based payment instrument of the entity (ASC 718) or another form of compensation (ASC 710)?

No bespoke standard — the judgement is the work

There is no crypto-specific standard for token compensation under IFRS or US GAAP; a dedicated cryptocurrency standard remains under deliberation. Entities apply the existing frameworks to the substance of the arrangement. Because there is no bespoke rule, the scope determination and its documentation are where the effort and the audit risk concentrate — exactly like the classification judgements elsewhere in crypto accounting.

Practical guidance

1. Ask the scope question first — is the token the entity's equity instrument?
2. Default-test, do not assume IFRS 2 — vesting alone does not make a token equity.
3. If IFRS 2, fix the equity- vs cash-settled classification (it decides remeasurement).
4. If IAS 19, recognise the non-cash benefit as service is rendered.
5. US GAAP: route to ASC 718 or ASC 710 by the same threshold.
6. Document the scope judgement — it is the audit-critical artefact; no bespoke standard backstops it.

How vendor tools handle token compensation

Cryptio and Request Finance track token grant, vesting, and valuation data and post the resulting expense. Confirm the tool can support both an IFRS 2 grant-date-fair-value schedule and an IAS 19 / general-benefit treatment — a tool that hard-codes "token comp = IFRS 2" cannot represent the common non-equity-token case correctly.

How Wag3s helps

Wag3s Ledger records token grant, vesting, and valuation data and supports the expense schedule under whichever framework the scope determination requires — IFRS 2 (equity- or cash-settled) or an IAS 19 / general-benefit treatment — with the supporting data for the documented scope judgement. See the Ledger product page and the Wag3s for accountants page.

Further reading

• Token Vesting Accounting
• IAS 38: Crypto as an Intangible Asset
• FASB ASU 2023-08: Fair-Value Crypto Accounting
• Staking Rewards Accounting
• DAO Accounting
• French GAAP for Crypto: The ANC Rules

Sources

• IFRS 2 Share-based Payment — scope: entity's own equity instruments (or cash based on their price); equity-settled measured at grant-date fair value, not remeasured; cash-settled remeasured at each reporting date
• IAS 19 Employee Benefits — non-cash employee benefit treatment where the token is not the entity's equity instrument (recognised as service is rendered)
• US GAAP — ASC 718 (share-based payment) vs ASC 710 (general compensation)
• No dedicated crypto-compensation standard under IFRS/US GAAP; a cryptocurrency standard remains under deliberation — scope determination by arrangement substance