Token Compensation Accounting: IFRS 2 or IAS 19?

Pay the team in tokens and the assumption is usually "that's IFRS 2." It often is not. IFRS 2 applies to an entity's own equity instruments, and most native tokens are not equity in the granting entity. This article is about the one question that decides how token pay is measured: whether the token is the entity's equity instrument, and therefore whether IFRS 2 or IAS 19 governs. The vesting mechanics that sit downstream of that choice are covered separately in token vesting accounting.

The standard-selection fork in brief

• Token compensation is not automatically IFRS 2. The fork turns on whether the token is the entity's equity instrument.
• If yes, IFRS 2 applies: an equity-settled award is measured at grant-date fair value and not remeasured, expensed over vesting; a cash-settled award is remeasured each period.
• If no, the grant is generally a non-cash employee benefit under IAS 19, recognised as the service is rendered.
• The US-GAAP parallel runs the same logic: ASC 718 for share-based payment versus ASC 710 for general compensation.
• Most native and utility tokens are not the entity's equity, so the arrangement often lands in IAS 19 or general-benefit treatment rather than IFRS 2.
• There is no dedicated crypto-compensation standard, so the scope judgement is both the deliverable and where the audit risk sits.

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.

Choosing a tool for token compensation

Because the scope determination can send the same grant to IFRS 2 or to IAS 19, the tool that posts the expense has to support both. If you are evaluating one — Cryptio and Request Finance track grant, vesting, and valuation data — confirm it can:

• build an IFRS 2 grant-date-fair-value schedule (equity-settled, not remeasured) and a cash-settled, remeasured schedule;
• alternatively recognise an IAS 19 or general-benefit expense as the service is rendered;
• avoid hard-coding "token comp = IFRS 2", which cannot represent the common non-equity-token case;
• retain the grant, vesting, and valuation data that supports the documented scope judgement.

How Wag3s fits in

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 behind the documented scope judgement. That judgement is arrangement-specific and audit-critical, with no bespoke crypto standard to fall back on, so Ledger supplies the figures and trail your auditor reviews rather than fixing the classification itself. 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 — IFRS 2 Share-based Payment: scope covers the entity's own equity instruments (or cash based on their price); equity-settled awards are measured at grant-date fair value and not remeasured, cash-settled awards are remeasured at each reporting date.
• IFRS — IAS 19 Employee Benefits: non-cash employee benefit treatment where the token is not the entity's equity instrument, recognised as the service is rendered.
• US GAAP — ASC 718 (share-based payment) versus ASC 710 (general compensation) in the FASB Accounting Standards Codification.
• There is no dedicated crypto-compensation standard under IFRS or US GAAP; a cryptocurrency standard remains under deliberation, so the scope determination is made by the substance of the arrangement.