Web3 Gaming — In-Game Token Issued by Game Developer (Deferred Revenue)
Recording the proceeds from selling in-game utility tokens (e.g., game currency or governance tokens in a play-to-earn game) — initially deferred as the developer has not yet delivered the in-game utility.
| Account Name | Type | Debit ($) | Credit ($) |
|---|---|---|---|
| Cash / Crypto Received (In-Game Token Sale) | Asset (+) | 2,500,000.00 | - |
| Deferred Revenue — In-Game Token (Platform Not Yet Launched) | Liability (+) | - | 2,500,000.00 |
💡 Accountant's Note
Web3 game developers often raise funds by pre-selling in-game tokens before the game launches. These tokens promise future utility (in-game currency, governance rights, NFT upgrades). The proceeds create a deferred revenue liability — the developer has received cash but has not yet delivered the performance obligation (the functioning game). Revenue is recognised as the game delivers value to token holders — on game launch, on feature delivery, or over the period players use the tokens. If the token is classified as a financial instrument (security) rather than a utility token, the proceeds go to equity or a financial liability, not deferred revenue.
Practitioner & Systems Framework
💻 ERP Architecture
In-game tokens raise nearly identical accounting questions to ICO tokens — the IFRS 15 vs. IAS 32 vs. IFRS 9 classification analysis is required. For most game utility tokens: (1) the token grants in-game utility (not ownership rights) → IFRS 15 deferred revenue, (2) revenue recognised when the game is operational and players can use the tokens, (3) breakage income recognised for tokens permanently unspent. The game's delay or cancellation may create a legal obligation to refund token holders — this would reclassify the deferred revenue to a refund liability.
⚠️ Audit Flags
Auditors perform the IFRS 15 / IAS 32 classification analysis, then test the revenue recognition against actual game delivery milestones. For games that raised pre-launch token sales but never launched, the deferred revenue may be a refund liability. Token holders' legal rights (whether they can demand a refund) affect the classification. Test the breakage estimate for permanently unspent tokens against actual player engagement data.
📄 Required Documentation
In-game token whitepaper, legal opinion on token classification (utility vs. security), IFRS 15 performance obligation identification, game launch and development milestone schedule, revenue recognition trigger documentation, player engagement and token usage data (post-launch), breakage estimate methodology, and refund obligation assessment.
Professional Excel Template
Get the automated version of this entry. Includes built-in IFRS checks, VAT calculators, and SAP-ready upload formats.
Expert Analysis by Qusai Ahmad
General Accountant Supervisor & IFRS Specialist
Specialized in SAP GUI automation and Middle Eastern tax compliance. Building digital tools for the next generation of finance leaders.