Accounting for Stablecoin Yield: What Your Auditor Will Ask

Stablecoin yield should be accounted for according to the substance of the arrangement, not the advertised annual percentage yield. A lending receivable, tokenized money market fund, deposit product and decentralized finance position can produce similar returns while requiring different classification, recognition, measurement and disclosure decisions.

The policy must reflect the company’s reporting framework, functional currency and contractual rights. Finance teams should agree the conclusion with their auditor before a material allocation is made, rather than trying to reconstruct it at year-end. This is an operational guide, not accounting advice.

Start with the instrument, not the yield rate

The first question is what the company receives after transferring USDC or USDT. The dashboard may describe the resulting balance as cash, savings or earned yield, but those labels do not establish its accounting treatment.

Retain the product documents that applied during each reporting period. Terms can change, so a current web page is not necessarily evidence of the rights that existed on the reporting date. The file should establish:

• Legal counterparty: Identify the entity, borrower, fund, custodian or protocol involved and which party owes an obligation to the company.
• Asset flow: Determine whether the stablecoins remain in a controlled wallet, are lent, are exchanged for units or are deposited into a smart contract.
• Redemption rights: Record notice periods, redemption windows, gates, lockups, minimums and any dependence on available liquidity.
• Return methodology: Establish whether the return is fixed, variable, discretionary, rebasing or reflected through a rising redemption value.
• Fees: Capture management, performance, platform, network and redemption charges, including fees deducted before a net distribution.
• Risk allocation: Document who bears counterparty, stablecoin, smart-contract, custody, liquidity and market risk.

Classify the position based on its substance

There is no universal accounting category called a yield-bearing stablecoin. Classification depends on the asset created by the transaction and the requirements of IFRS, US GAAP or the company’s other applicable framework.

Do not classify a position as a cash equivalent merely because it targets one dollar or is usually redeemable quickly. The analysis generally considers maturity, liquidity, convertibility to a known amount of cash and exposure to changes in value. Notice periods, withdrawal gates, counterparty exposure or variable redemption values may change the conclusion.

Define when yield is recognized

The accounting policy should name the event that creates recognizable income. That event may be the passage of time, the establishment of an enforceable receivable, the crediting of a reward or a change in the measured value of the instrument.

Contractual return earned over time

If a contractual return accrues over time, income may need to be recorded before tokens reach the company’s wallet. The exact calculation and account presentation depend on the instrument and applicable standard.

Illustrative accrual: debit the financial asset or an accrued-yield receivable; credit interest income or the approved income account. On payment, clear the receivable against the stablecoins or other asset received.

Maintain the principal balance, rate history, day-count convention and accrual period. If identifiable fees are material, record them according to the approved gross-versus-net policy rather than treating the net wallet increase as the entire return.

Variable or discretionary rewards

A reward that can be changed, cancelled or withheld before distribution may not support accrual on the same basis as contractual interest. Recognition may occur when the amount is credited, becomes claimable or enters a company-controlled wallet. The policy should define that trigger and explain how unclaimed rewards are tested at each close.

Increasing token or unit value

Some products do not distribute additional tokens. Instead, each token represents an increasing claim on an underlying pool. The change may therefore arise through measurement of the asset rather than a separate interest receipt. Finance teams should avoid automatically presenting every increase in redemption value as yield income.

Measure the balance and separate currency effects

At every close, capture both the quantity held and the value under the approved accounting policy. Depending on the instrument and framework, the basis could involve fair value, amortized cost or another measurement model.

The valuation memo should identify the reporting cut-off time and time zone, source market or administrator, price used, treatment of bid-ask spreads, and process for investigating stablecoin deviations from its reference currency. If the yield-bearing token lacks an active market, document how a redemption value, net asset value or other valuation input was obtained and why it is appropriate.

A company whose functional currency differs from the stablecoin’s reference currency may need to distinguish product return from foreign-exchange movement. For example, a EUR-functional entity holding a USD-denominated position can earn contractual yield while also experiencing a EUR/USD remeasurement gain or loss. Preserve both the native-unit calculation and the functional-currency translation.

Build an onchain-to-ledger roll-forward

A block explorer supports existence at an address, but it does not by itself prove that the reporting entity owns or controls that address. Audit evidence must connect the legal owner, wallet or provider account, product entitlement and general ledger.

Use network timestamps consistently and document how transactions near period-end are assigned to the reporting period. Where a provider pools assets, the protocol’s wallet balance will not prove the company’s individual entitlement. Obtain a provider statement or subledger and reconcile credited yield, deposits and redemptions to the company’s records.

Prepare evidence for the auditor

Auditors commonly test existence, rights and obligations, completeness, accuracy, valuation, cut-off and presentation. A repeatable evidence pack should answer each assertion without relying only on screenshots, which can omit metadata and are difficult to reproduce.

1. Maintain a wallet and account inventory with network, address, purpose, legal owner, custodian and control method.
2. Retain complete transaction exports with hashes, timestamps, token contract addresses and originating and destination addresses.
3. Archive signed contracts, dated terms, fee schedules, liquidity provisions and risk disclosures.
4. Save provider statements, reward reports and independently reproducible yield calculations.
5. Document the valuation source, observation time, functional-currency rate and treatment of unusual pricing.
6. Reconcile opening balance, additions, income, fees, withdrawals, remeasurement and closing balance to the ledger.
7. Retain approvals for allocations and redemptions, plus relevant sanctions or address-screening records.

Control evidence should demonstrate wallet authority without exposing private keys or recovery material. For an MPC or multisignature setup, useful support can include the authorized signer list, quorum configuration, approval logs and a controlled message-signing procedure agreed with the auditor.

Systems should also preserve the separation between initiating, approving and signing a transfer. For example, Stablerail supports approvals and signing quorum, sanctions and address screening before send, and exportable audit evidence for USDC and USDT treasury activity. Whatever system is used, exports should be retained with the close file rather than reconstructed after staff or configurations change.

Resolve the policy before deploying funds

Before treasury moves stablecoins into a yield product, finance, legal and treasury should approve a short accounting memo. It should identify the instrument, legal owner, classification, recognition trigger, measurement basis, income and fee presentation, impairment or credit-risk considerations, liquidity restrictions and required disclosures.

The practical rule is simple: if finance cannot explain what the company owns, how it can redeem, when the return becomes enforceable and how the closing value can be independently reproduced, the position is not ready for an audit-efficient close.