NFT Royalty Income Accounting: Revenue You Can't Always Enforce

On paper, an NFT creator royalty is the kind of revenue stream a finance team dreams about: a fixed percentage of every secondary resale, in perpetuity, with no further work required. The catch sits in one word — enforceability. Many on-chain royalties are not enforced at the protocol level, so whether the creator is actually paid often comes down to whether the marketplace chooses to honour the royalty. A "right" that a third party can decline to pay is not the same as a receivable. This article works through recognising creator royalty income under that uncertainty, kept separate from the questions of holding or disposing of NFTs, and hedged because the recognition timing is an auditor judgement.

The short version

• Royalty income is not the same question as NFT holding or disposal accounting — it is an income stream (the creator's percentage of secondary resales), not a balance-sheet asset question. For those, see NFT holding and disposal accounting.
• Enforceability is the catch: many on-chain royalties are not protocol-enforced, so payment can depend on the marketplace honouring it, making the inflow effectively discretionary or contingent.
• Where enforceability is weak, a conservative position recognises the income on receipt — when control of the consideration is obtained — rather than as an advance receivable.
• Royalties received in crypto create two layers: the income recognition and the subsequent crypto-asset accounting.
• Enforcement practices evolve, so the assessment should be reassessed rather than fixed.
• This is a framework- and fact-specific auditor judgement, not accounting advice.

A distinct stream

Holding accounting carries an NFT as an asset; disposal accounting is gain/loss on sale. Royalty income is separate: the original creator receiving a percentage of secondary resales of an NFT they no longer own. The question is about an income stream, not an asset, with its own enforceability complication — treated distinctly, an auditor judgement.

Why enforceability is central

Many on-chain royalties are not protocol-enforced — whether the royalty is actually paid can depend on the marketplace honoring it rather than a guaranteed contractual right. If the inflow is effectively discretionary or contingent on third-party behaviour, that affects whether and when income can be recognised vs only when received. The enforceability assessment is central — fact-specific, auditor-confirmed; not an assumption of a guaranteed receivable.

When to recognise

Recognition depends on whether there is a sufficiently enforceable arrangement and the income is measurable, with a conservative position recognising when received / when control of consideration is obtained where enforceability is weak. Recognising a royalty receivable in advance assumes an enforceable right that on-chain royalties may not provide. Timing is framework-/fact-specific, auditor-confirmed.

Measurement — two layers

Royalties are typically received in crypto → measured at the value of consideration when received/control obtained; the received crypto is then a separate asset under the applicable classification. As with other in-kind crypto income, one royalty event = two layers (income recognition + subsequent crypto-asset accounting), both auditor-confirmed.

Practices evolve

Royalty enforcement practices and standards evolve; a change in whether marketplaces honor royalties can change the enforceability assessment and therefore recognition. The accounting should reflect the current reality of how the royalty is actually realised, reassessed as the environment changes — an ongoing auditor-confirmed judgement.

The enforceability landscape in 2026

The timeline of royalty enforcement is a useful reference for the audit judgement:

2017–2021. Most NFT marketplaces (OpenSea, Rarible) enforced creator royalties by default. Royalties were embedded in the smart contract (via the ERC-2981 standard or custom implementations) and the marketplace honored them on every sale. From an accounting perspective, a creator with active listings on these platforms had a reasonably enforceable expectation of royalty income on sales, supporting accrual on a sale-by-sale basis where income was measurable.

2022–2023. The royalty-enforcement debate intensified when Blur launched as a zero-royalty marketplace and captured significant market share from OpenSea among professional traders. OpenSea initially attempted to enforce royalties only for collections using an on-chain enforcement mechanism (operator filter registry), then progressively retreated. By early 2023, both major Ethereum marketplaces offered optional or zero-royalty trading for many collections. The enforcement expectation that had supported earlier accruals became substantially weaker.

2024–2026. Royalty practices remain fragmented by marketplace, chain, and collection. Some collections using on-chain enforcement contracts (Manifold's series, certain Solana programs) maintain reliable enforcement. Others rely entirely on marketplace discretion. The auditor's assessment must therefore be collection-specific and marketplace-specific: which platforms does this collection's secondary market actually use, and do those platforms enforce royalties? An entity cannot assume a uniform enforcement environment.

Solana specifics. The Metaplex Token Metadata standard allowed creators to set royalties in the NFT metadata, but enforcement was marketplace-dependent. In October 2022, Metaplex introduced Programmable NFTs (pNFTs) with on-chain royalty enforcement as an optional upgrade. Collections using pNFTs have stronger enforceability than those on standard NFTs, which is a relevant distinction for the auditor's enforceability assessment.

Practical checklist for creator royalty accounting

1. Map where the collection's secondary market actually trades — which marketplaces, and do they enforce royalties?
2. Distinguish protocol-enforced from marketplace-discretion royalties — on-chain enforcement (ERC-2981 operator filter, Metaplex pNFT) is stronger evidence of enforceability.
3. Do not accrue royalty receivables without documented enforceability — conservative default is recognition at receipt.
4. Reassess enforceability at each reporting period — marketplace policies change.
5. Record the received crypto as a separate asset at FMV on receipt — two-layer discipline.
6. Document the enforceability assessment and its basis — the auditor will ask.

Practical guidance

1. Treat royalty income as its own stream — not NFT holding/disposal.
2. Assess enforceability first — on-chain royalties are often not protocol-enforced.
3. Default to recognise on receipt/control where enforceability is weak.
4. Don't book an advance receivable assuming a guaranteed right.
5. Account the two layers — income then subsequent crypto-asset accounting.
6. Reassess as enforcement practices change; confirm with your auditor — fact-specific; not accounting advice.

Choosing and configuring a tool

Because the hard part of royalty accounting is the enforceability judgement rather than the bookkeeping, the tool's job is to record inflows in a way that supports a conservative, receipt-based position. Tools such as Cryptio and Bitwave can record royalty receipts; before relying on one, confirm it can:

• record royalty income at the point of receipt, valued at the price when control of the consideration is obtained, without prompting you to accrue a receivable the on-chain royalty may not support;
• carry the received crypto as a distinct asset under your classification — the second of the two layers — rather than collapsing it into the income figure;
• tag royalty income by collection and marketplace, so the enforceability picture can be reassessed per source as practices change;
• keep royalty income separate from any gain or loss on NFTs the entity itself holds and disposes of.

The tool records the inflow; the enforceability assessment and the recognition timing remain auditor judgements.

How Wag3s fits in

Wag3s Ledger records royalty receipts with their value and timestamp and books the subsequent crypto asset, keeping an audit trail behind both. The enforceability assessment and the recognition timing stay with the entity's auditor — Ledger supplies the dated, sourced record and is built to support that review, not to make the judgement for them. See the Ledger product page.

Further reading

• NFT Accounting (Corporate)
• NFT Cost Basis and Disposal Tracking
• Crypto Revenue under IFRS 15
• Crypto Asset Account Classification
• GameFi & Play-to-Earn Accounting
• Crypto Revenue and Expense Accounts

Sources

• IFRS — IFRS 15 Revenue from Contracts with Customers: the requirement for a sufficiently enforceable arrangement and measurable consideration that drives whether royalty income can be recognised before receipt or only when control of the consideration is obtained.
• IFRS — IAS 38 Intangible Assets, and FASB — ASU 2023-08: the second layer — accounting for the crypto received as royalty consideration as a distinct asset.
• IRS — Digital assets hub and Frequently asked questions on digital asset transactions: the US framework for income received in digital assets. The tax treatment is determined separately from the accounting and confirmed with a tax adviser.