IFRS vs GAAP: Tokenized Asset Accounting Standards for Enterprise Balance Sheets
When a bond, a fund interest, or a slice of commercial real estate is issued or held as a blockchain token, the finance team is left with a deceptively simple-looking question: what exactly goes on the balance sheet, and under which rules? This is the practical problem behind tokenized asset accounting standards — the question of how existing accounting frameworks, not a brand-new rulebook, should be applied to assets that now exist in tokenized form. Enterprises increasingly hold tokens that represent bonds, equities, real estate, commodities, fund interests, receivables, and other financial instruments, but the accounting answer does not come from inspecting the blockchain. It comes from analyzing what the token legally and economically represents. The central question every CFO and controller needs to answer is: what economic rights and obligations does the token actually represent? Because IFRS and US GAAP approach classification, recognition, and measurement differently, the same tokenized holding can, depending on facts and circumstances, land in different places on an IFRS balance sheet than it would under US GAAP — which is exactly why the two frameworks need to be evaluated independently rather than assumed to converge.
From a financial-reporting standpoint, "tokenization" refers to the process of creating a blockchain-based digital record that represents ownership of, or a right to, an asset. That digital record can take fundamentally different forms, and the difference matters enormously for accounting purposes.
Broadly, tokens fall into two categories:
A. A token representing an existing traditional asset. Here the token is a technology wrapper — a digital record layered on top of a bond, an equity interest, a real estate holding, or a receivable that already has a legal and economic identity independent of the blockchain. The underlying instrument, not the token, generally continues to drive the accounting analysis.
B. A native digital asset. Here there is no separate traditional asset behind the token; the token itself is the asset, in the way that bitcoin or ether are native to their respective ledgers rather than digital certificates for something else.
These two categories should not automatically receive the same accounting treatment. A tokenized corporate bond and a native digital asset can sit in entirely different places on the balance sheet, be measured under entirely different models, and generate entirely different disclosure obligations — even though both are, technically, "tokens." The accounting analysis has to start with economic substance and contractual rights, not with the technological format the asset happens to be recorded in.
It is worth being direct about a common misconception: there is no single standard, under IFRS or US GAAP, called "tokenized asset accounting standards." Tokenized asset accounting standards, as a practical matter, refers to the body of existing financial-reporting requirements that enterprises must map a tokenized holding onto — IAS 32, IFRS 9, IFRS 13, IAS 2, IAS 38, IAS 40, IFRS 7, and IFRS 15 on the IFRS side; and the relevant sections of the FASB Accounting Standards Codification covering financial instruments, digital assets, investments, fair value, intangible assets, inventory, and disclosures on the US GAAP side.
For every tokenized holding, an enterprise needs to work through:
This section is the framework the rest of the article works through. Everything that follows — the IFRS analysis, the US GAAP analysis, the worked examples — is an application of these same six questions to different types of tokenized holdings.
Before any standard can be applied, the enterprise needs a practical classification framework for what sits behind the token.
Tokenized Equity. If the token represents a genuine equity interest in an entity, the accounting analysis is generally driven by the nature of that underlying equity interest — voting rights, dividend rights, and how those rights are legally documented — rather than by the fact that ownership is recorded on a distributed ledger.
Tokenized Debt. A tokenized bond or note typically raises the question of whether the token creates a contractual right to receive cash or another financial asset. If it does, characteristics such as the contractual cash flow terms and the enterprise's business model for holding the instrument become central to classification and subsequent measurement.
Tokenized Real Estate. Real estate tokens can represent very different legal positions: direct fractional ownership of property, an equity interest in a special-purpose entity that owns the property, a contractual financial claim against an issuer, or simply a digital representation with no independent legal standing. Each of these possibilities can point to a different accounting outcome.
Tokenized Commodity. Whether a commodity token is accounted for as inventory, a financial instrument, or something else can depend on the contractual rights attached to the token and on the enterprise's own business model — for example, whether it holds the token for sale in the ordinary course of business.
Tokenized Fund Interest. A token representing an interest in a fund may raise questions relevant to investment accounting, including how the enterprise's level of influence or control over the fund should be assessed.
Native Digital Asset. Because a native digital asset does not represent an underlying traditional asset or a contractual claim on another party, its accounting treatment can differ materially from a token that wraps a traditional financial instrument.
The principle that should be repeated at every stage of this analysis: do not classify an asset solely because it is represented as a token. The token is the delivery mechanism; the classification question is about what sits behind it.
IFRS does not have a bespoke standard for tokenized assets. Instead, enterprises need to work through the existing suite of standards and determine which one applies to the specific rights the token conveys.
IAS 32 (Financial Instruments: Presentation) provides the definition of a financial asset — broadly, cash, an equity instrument of another entity, a contractual right to receive cash or another financial asset, or certain contracts settled in the entity's own equity instruments. This definition is the starting point for determining whether a tokenized holding is a financial instrument at all. A widely referenced 2019 IFRS Interpretations Committee agenda decision on holdings of cryptocurrencies concluded that a cryptocurrency meeting certain narrow characteristics — not issued by a jurisdictional authority and not giving rise to a contract between the holder and another party — does not meet the IAS 32 definition of a financial asset, because it does not represent cash, an equity instrument of another entity, or a contractual right to receive cash or another financial asset. The Committee accordingly concluded that such cryptocurrency holdings fall under IAS 2 Inventories when held for sale in the ordinary course of business, and under IAS 38 Intangible Assets otherwise. This conclusion is important context, but it applies specifically to that narrow category of asset — a genuinely native digital currency with no contractual claim attached — and does not extend automatically to a token that represents a bond, an equity interest, or a real-estate claim, which may meet the IAS 32 financial-asset definition depending on the rights involved.
IFRS 9 (Financial Instruments) becomes relevant once a tokenized holding is determined to be a financial asset. It governs classification (amortized cost, fair value through other comprehensive income, or fair value through profit or loss) based on the entity's business model for managing the asset and the contractual cash flow characteristics of the instrument — the same tests applied to any other financial asset, regardless of how it is recorded.
IFRS 13 (Fair Value Measurement) applies wherever fair value measurement is required, whether that requirement arises from IFRS 9, IAS 2's broker-trader exception, or the IAS 38 revaluation model. IFRS 13 governs how fair value should be determined, including the fair value hierarchy and the use of observable versus unobservable inputs — a set of questions that becomes especially significant for tokenized assets trading in thin or fragmented markets.
IAS 2 (Inventories) may apply where a tokenized asset is held for sale in the ordinary course of business, or where the enterprise qualifies as a commodity broker-trader.
IAS 38 (Intangible Assets) applies to tokenized holdings that are identifiable, non-monetary, and lack physical substance, and that do not otherwise meet the definition of a financial asset or fall within inventory.
IAS 40 (Investment Property), IFRS 7 (Financial Instruments: Disclosures), and IFRS 15 (Revenue from Contracts with Customers) may become relevant depending on the specific fact pattern — for example, where a token represents an interest in investment property, where financial-instrument disclosures are triggered, or where tokenization forms part of a revenue-generating contract with a customer.
Several questions should guide the IFRS analysis in every case: Is the token a financial asset under IAS 32? Does it create a contractual right? Does it represent an underlying financial instrument or an underlying tangible or intangible asset? Is it held for trading, or for sale in the ordinary course of business? Could inventory accounting apply? Is intangible-asset treatment more appropriate? How should subsequent measurement — cost, amortized cost, or fair value — be determined? Where the answer genuinely depends on the specific legal documentation and business model, that should be stated plainly rather than resolved by assumption.
US GAAP guidance for tokenized holdings likewise depends on what the token represents, and enterprises should not assume that all tokenized assets fall under the same model.
For certain in-scope crypto assets, the FASB issued Accounting Standards Update 2023-08, Accounting for and Disclosure of Crypto Assets, which created ASC 350-60. This guidance addresses the subsequent measurement, presentation, and disclosure of crypto assets within its scope, but does not address their initial measurement, recognition, or derecognition, which continue to be governed by other applicable GAAP. Under ASC 350-60, an entity measures in-scope crypto assets at fair value on the balance sheet, with gains and losses from remeasurement recognized in net income each reporting period, a departure from the historical cost-less-impairment model that previously applied to these holdings as indefinite-lived intangible assets. The guidance is effective for all entities for fiscal years beginning after December 15, 2024, with early adoption permitted.
Scope matters enormously here. ASU 2023-08 excludes crypto assets that provide the holder with enforceable rights to another asset, meaning tokens that represent a claim on an underlying good, service, or other asset generally fall outside this specific fair-value model. That means a tokenized traditional asset — a tokenized bond, a tokenized equity interest, a tokenized real-estate claim — is likely to be evaluated under the accounting model applicable to the underlying instrument (financial instruments guidance, investment accounting, or intangible-asset guidance, as applicable), rather than under ASC 350-60, which was built around qualifying native digital assets such as bitcoin and ether.
The distinction the FASB drew is therefore central to any US GAAP analysis: tokenized traditional assets — where the token is a wrapper around a contractual claim on something else — should generally be evaluated under the existing GAAP framework that governs that underlying claim (for example, ASC 320/321 for investments, or the financial-instruments guidance applicable to receivables and debt securities). Qualifying native digital assets without such enforceable rights to another asset are the category ASU 2023-08 was designed to address. Enterprises holding tokens outside the ASU's scope should also monitor developments closely: the FASB has an active research project, added in 2025, exploring further targeted improvements to digital-asset accounting and disclosure, including questions such as whether certain payment digital assets should be treated as cash equivalents and how transactions like crypto lending should be accounted for — an indication that this area of GAAP continues to evolve and enterprises should verify the current state of guidance before finalizing a position.
Where the two frameworks are substantially aligned — for example, the general structure of fair value measurement, or the logic of recognizing gains and losses once classification is settled — that similarity is worth stating rather than manufacturing a difference that doesn't exist in the guidance.
Balance-sheet presentation is a direct consequence of accounting classification, not an independent decision. Once an enterprise has determined what the token represents and which standard applies, the presentation question generally answers itself.
Depending on the classification analysis, a tokenized holding might appear as:
The token itself does not determine which of these line items is appropriate. A tokenized corporate bond and a tokenized piece of vacant land might both be represented by similar-looking blockchain infrastructure, but one is likely to be a financial asset and the other is not — the balance-sheet line item follows the underlying economic substance, not the wrapper.
Consider a hypothetical enterprise that purchases a tokenized corporate bond issued by a third party. A reasonable accounting analysis would proceed roughly as follows:
Throughout this process, the token infrastructure — the distributed ledger, the smart contract, the wallet — should be treated as separate from the underlying financial instrument the token represents. The infrastructure can support the accounting analysis with evidence; it does not substitute for it.
Now consider a hypothetical tokenized equity holding. The analysis should address what rights the token actually provides — voting rights, dividend entitlements, a residual claim on the issuing entity's assets — and whether those rights are consistent with an equity interest as defined under the applicable framework. Classification then depends on the level of influence the holding conveys and the relevant investment-accounting guidance. Measurement considerations include whether fair value is required or available, and if so, what valuation inputs exist given that many tokenized equity instruments trade in limited or nascent secondary markets. Financial statement presentation and disclosure follow from these determinations. Because the accounting outcome depends heavily on the specific rights conveyed and the applicable framework, a universal conclusion for "tokenized equity" as a category would be inappropriate — the facts of each holding need to be worked through individually.
Tokenized real estate tends to raise particularly complex accounting questions because the legal structure behind the token can vary widely. An enterprise needs to distinguish between: direct fractional ownership of the underlying property; an equity interest in an entity that owns the property; a contractual financial claim (such as a loan secured by the property) against an issuer; and a token that is purely a digital representation without independent legal standing of its own. Each of these structures can lead to a materially different accounting outcome — direct or indirect real estate accounting, investment accounting, financial-instrument accounting, or something else entirely. Because the accounting conclusion turns so heavily on legal structure, thorough legal documentation review is a prerequisite to the accounting analysis, not a parallel workstream that can be deferred.
Where fair value measurement applies — whether required by IFRS 9, IAS 2's broker-trader exception, the IAS 38 revaluation model, or ASC 350-60 — enterprises face genuine valuation challenges specific to tokenized assets. Relevant considerations include whether quoted prices exist in an active market, or whether the market is inactive or illiquid; whether observable inputs are available or whether valuation must rely on unobservable, Level 3-type inputs; the depth and liquidity of the relevant market; the reliability of available pricing sources, including third-party valuation providers and blockchain oracle data; and the valuation methodology and models used when observable prices are unavailable.
IFRS 13 and the corresponding US GAAP fair-value framework under ASC 820 both emphasize using the most reliable observable inputs available and disclosing the methodology and assumptions used. A point worth stating plainly: a blockchain transaction price does not automatically establish the appropriate accounting fair value. A transaction price reflects a single trade at a single point in time, potentially in a thin or non-orderly market, and potentially between related parties — none of which automatically satisfies the fair value definition under either framework. Enterprises holding tokenized assets, particularly those without deep secondary markets, generally need documented valuation policies, defined pricing-source hierarchies, and independent review procedures to support the fair values used in financial reporting.
Blockchain records and financial-reporting evidence are related but distinct concepts, and this distinction matters especially for auditors and controllers. Blockchain records can provide reliable evidence of transaction history, timestamps, wallet activity, token movements, and smart-contract execution — the ledger is, by design, good at recording what happened on-chain.
What on-chain records do not automatically establish is legal ownership, accounting classification, valuation, control for accounting purposes, the existence of contractual rights, or the appropriate financial statement presentation. A wallet address moving a token is not the same as a legally enforceable transfer of the underlying asset; a smart contract executing as coded is not the same as a determination of fair value; and possession of a private key is not, by itself, proof of beneficial ownership recognized under the applicable accounting framework. Enterprises need to supplement on-chain evidence with the same categories of legal and financial documentation that would support any other asset held on the balance sheet.
Auditors working with tokenized holdings face a distinct set of practical challenges, including confirming wallet ownership and private-key control, understanding custody arrangements (whether self-custodied or held with a third-party custodian), evaluating the operation of relevant smart contracts, verifying transactions, assessing valuation and the reliability of pricing sources, confirming legal ownership, testing existence and completeness assertions, reconciling on-chain records to the general ledger and subledger, and identifying related-party transactions that may not be obvious from wallet addresses alone.
Enterprises can strengthen their audit trail by maintaining clear custody documentation, implementing wallet-level access controls with defined authorization protocols, retaining independent confirmation of key balances and transactions where feasible, and documenting the valuation methodology and pricing sources used at each reporting date.
A practical internal-control framework for tokenized holdings should address several distinct areas:
Wallet controls — clear assignment of wallet ownership, defined access rights, authorization protocols for transactions, and governance over private-key management (including multi-signature requirements where appropriate).
Transaction controls — approval workflows for token transfers, segregation of duties between transaction initiation and authorization, and ongoing transaction monitoring.
Valuation controls — defined and documented pricing sources, consistently applied valuation models, and independent review of significant valuations.
Reconciliation controls — regular reconciliation between blockchain records, custody records, the general ledger, and relevant subledgers.
Financial reporting controls — controls over classification determinations, measurement, disclosure preparation, and period-end procedures specific to tokenized holdings.
Because tokenized asset accounting sits at the intersection of several disciplines, Finance, Legal, Tax, Treasury, Compliance, and Technology teams generally need to collaborate rather than operate in silos — legal input is needed to confirm what rights the token conveys, technology input is needed to understand custody and wallet architecture, and finance input translates both into an accounting position.
It is worth stating explicitly: accounting treatment does not equal tax treatment, and neither equals legal classification. An asset can be classified one way for financial-reporting purposes, treated differently for tax purposes, and characterized differently again under securities or property law. Enterprises should separately evaluate financial reporting, tax treatment, legal ownership, applicable securities regulation, custody requirements, and the specific contractual rights involved, rather than assuming that a conclusion reached in one domain automatically carries over to another. This article addresses financial-reporting treatment only and does not provide jurisdiction-specific tax or legal advice.
A practical checklist for CFOs and controllers evaluating a new tokenized holding:
A practical sequence enterprises can follow when a tokenized holding is created or acquired:
Token Created or Acquired → Identify Legal & Economic Rights → Identify Underlying Asset → Determine Accounting Classification → Select Applicable IFRS / US GAAP Guidance → Initial Recognition → Subsequent Measurement → Valuation → Balance-Sheet Presentation → Disclosure → Audit & Internal Controls
Each stage feeds the next: legal and economic rights determine classification; classification determines which standard applies; the applicable standard determines recognition, measurement, and presentation; and presentation and measurement together drive the disclosure and control requirements that support the reported figures.
Accounting should not be treated as a reporting exercise that happens after a tokenized asset has already been issued or acquired. Before a tokenization project goes live, enterprises benefit from understanding, in advance, the intended ownership structure, the contractual rights the token will convey, the token's technical design, any transfer restrictions, the intended valuation methodology, custody and settlement arrangements, how transaction records will be captured and retained, the likely accounting classification, and the resulting reporting requirements.
This matters because accounting requirements can — and often should — influence how the tokenization structure itself is designed. A token structured without clear contractual rights, for instance, may be far harder to support as a financial asset than one drafted with those rights explicit from the outset. Involving the accounting team early avoids discovering, after issuance, that the token's legal design creates an unintended or unfavorable accounting outcome.
Returning to the question this article set out to answer — how should enterprises account for tokenized assets on the balance sheet? — the honest answer is that it depends on what the token represents, what rights and obligations it creates, the enterprise's specific facts and circumstances, and the accounting framework being applied. There is no shortcut that bypasses this analysis, and no single line item that all tokenized holdings belong in. Enterprises building out tokenized asset accounting standards internally — meaning their own policies for mapping tokenized holdings onto IFRS and US GAAP — should expect the answer to vary by instrument, by jurisdictionally applicable framework, and by the specific legal documentation behind each token.
The accounting challenge, ultimately, is not simply determining whether an asset is "on-chain." It is determining what economic substance sits behind the token, and how that substance should be recognized, measured, presented, and disclosed under the accounting framework that applies.
1. What are tokenized asset accounting standards? The term refers to the application of existing IFRS and US GAAP requirements — rather than a single, dedicated standard — to assets held or issued in tokenized form. Which specific standards apply depends on what the token represents.
2. How are tokenized assets accounted for under IFRS? IFRS applies existing standards based on classification: IAS 32 and IFRS 9 where the token is a financial asset, IAS 2 where it is held for sale in the ordinary course of business, IAS 38 where it is an intangible asset, and IFRS 13 wherever fair value measurement is required. A 2019 IFRIC agenda decision addressed a narrow category of cryptocurrency holdings specifically, concluding they generally fall under IAS 2 or IAS 38.
3. How are tokenized assets treated under US GAAP? US GAAP treatment depends on scope. Certain in-scope crypto assets that don't provide enforceable rights to another asset are measured at fair value through net income under ASC 350-60 (from ASU 2023-08). Tokenized traditional assets — tokens representing a claim on an underlying bond, equity, or other instrument — are generally evaluated under the GAAP guidance applicable to that underlying claim.
4. Does tokenization change the accounting treatment of an asset? Not by itself. Tokenization is a technology and record-keeping format. The accounting treatment depends on the legal and economic substance of what the token represents, evaluated under the applicable accounting framework.
5. Are tokenized assets classified as intangible assets? Sometimes, but not universally. A tokenized holding may be classified as an intangible asset under IAS 38 (IFRS) if it does not meet the definition of a financial asset and is not held for sale in the ordinary course of business. Tokens representing financial instruments, real property interests, or inventory can be classified differently.
6. How are tokenized assets valued for financial reporting? Where fair value is required, IFRS 13 and ASC 820 apply, prioritizing observable market inputs where available and requiring documented valuation methodology where they are not. A blockchain transaction price alone does not automatically establish accounting fair value, particularly in thin or illiquid markets.
7. What challenges do auditors face when auditing tokenized assets? Common challenges include confirming wallet ownership and private-key control, verifying custody arrangements, assessing valuation and pricing sources, confirming legal ownership, and reconciling blockchain records to the general ledger.
8. Do IFRS and US GAAP treat tokenized assets differently? They can. Most notably, US GAAP's ASC 350-60 creates a specific fair-value-through-net-income model for certain qualifying native digital assets, while IFRS has no equivalent dedicated standard and instead applies a facts-and-circumstances analysis across IAS 32, IAS 2, and IAS 38. For tokenized traditional assets, the two frameworks are more likely to converge, since both apply the existing guidance for the underlying instrument type.
