Crypto as Customer Consideration: Revenue under IFRS 15

When a customer pays in crypto, the wrong question is "how many tokens did we get?" The right one is IFRS 15 non-cash consideration: measure it at fair value, generally at contract inception, recognise revenue on that — then account for the crypto received as an asset separately. This guide is that two-part mechanic, hedged, because the measurement is an auditor judgement.

TL;DR

• Crypto from a customer = non-cash consideration under IFRS 15 — measured at fair value (or, if not reasonably estimable, by reference to the stand-alone selling price).
• Generally measured at contract inception; later price moves are the asset's question, not a revenue remeasurement.
• One crypto-paid sale → two accounting questions: (1) revenue measurement, (2) subsequent crypto-asset accounting (IAS 38/IAS 2/ASU 2023-08).
• Separate revenue from subsequent remeasurement so volatility doesn't distort revenue.
• US GAAP differs (ASC 606 + ASU 2023-08) — dual-reporting applies each.
• Measurement/date a fact-specific auditor judgement. Not accounting advice.

Revenue = measured consideration, not token count

Crypto received from a customer is non-cash consideration. Under IFRS 15, non-cash consideration is generally measured at fair value; where fair value cannot be reasonably estimated, the entity refers to the stand-alone selling price of the goods/services. Revenue is not "the number of tokens" — it is the measured value of the consideration. Measurement and its timing are fact-specific auditor judgements.

Measured generally at contract inception

IFRS 15 generally measures non-cash consideration at fair value at contract inception; subsequent changes in the crypto's value are a separate question — the accounting for the asset received, not a continuous revenue remeasurement. Treating later price moves as revenue adjustments is a common error. The precise measurement date and any constraint are framework-/fact-specific, auditor-confirmed.

Then: the crypto is an asset

Once recognised, the crypto received is an asset under the applicable crypto guidance — typically IAS 38 intangible (cost/revaluation), IAS 2 inventory for a broker-trader, or US GAAP ASU 2023-08 fair value if in scope (see crypto asset account classification). A single crypto-paid sale → two distinct questions: revenue measurement and subsequent asset accounting. Both auditor-confirmed.

Volatility between contract and settlement

Generally the revenue reflects the consideration measured under IFRS 15 at the relevant point; price movements after that flow through the asset, not by re-opening revenue — though the exact treatment of any inception-to-receipt period depends on facts/framework. The discipline: separate revenue measurement from subsequent crypto remeasurement so volatility doesn't distort reported revenue. Auditor judgement.

US GAAP differs

The non-cash-consideration-at-fair-value principle is broadly shared, but the specific revenue standard (ASC 606) and subsequent crypto accounting (ASU 2023-08 fair value through net income) differ in detail from IFRS 15 / IAS 38. A dual-reporting entity applies each framework's revenue and asset guidance (see crypto CoA GAAP/IFRS mapping) — auditor-confirmed.

Practical guidance

1. Treat crypto received as non-cash consideration — measure at fair value, not token count.
2. Measure generally at contract inception; don't re-open revenue for later price moves.
3. Account for the received crypto as an asset under the applicable standard.
4. Separate revenue from subsequent remeasurement — protect reported revenue from volatility.
5. Apply each framework if dual-reporting (IFRS 15/IAS 38 vs ASC 606/ASU 2023-08).
6. Confirm measurement, date, and asset treatment with your auditor — fact-specific; not accounting advice.

How vendor tools handle crypto revenue

Cryptio and Bitwave can capture the value of crypto received and separate it from the subsequent asset remeasurement. Confirm the tool records the consideration value at the right point and keeps revenue distinct from remeasurement — the tool records it; the IFRS 15 measurement is an auditor judgement.

How Wag3s helps

Wag3s Ledger records the value of crypto received from customers at the relevant point and tracks the subsequent asset separately with an audit trail, so revenue and crypto-asset remeasurement stay distinct and evidenced — while the IFRS 15 measurement and subsequent treatment stay auditor-confirmed. See the Ledger product page.

Further reading

• Crypto & IFRS 13 Fair Value Measurement
• Crypto Asset Account Classification
• Crypto Revenue and Expense Accounts
• Crypto CoA: GAAP and IFRS Mapping
• Crypto & IAS 7 Cash-Flow Statement
• Paying Contractors in Crypto

Sources

• Crypto received from a customer is non-cash consideration; IFRS 15 generally measures it at fair value, or by reference to the stand-alone selling price if fair value cannot be reasonably estimated — revenue is the measured consideration, not the token count
• Generally measured at contract inception; subsequent crypto value changes are the asset's accounting, not a revenue remeasurement (treating later price moves as revenue adjustments is a common error)
• The received crypto is then an asset under the applicable guidance (IAS 38 cost/revaluation, IAS 2 broker-trader, or US GAAP ASU 2023-08 if in scope) — one crypto-paid sale = two distinct accounting questions
• US GAAP differs in detail (ASC 606 + ASU 2023-08) from IFRS 15 / IAS 38; dual-reporting applies each — measurement/date/treatment are fact-specific auditor judgements, not accounting advice