Accounting for Stablecoin Yield: What Your Auditor Will Ask

Stablecoin yield accounting starts with a simple question: what did the company legally and economically acquire? A USDC balance placed into an interest-bearing account, a loan to a counterparty and a token received from a decentralised protocol can produce similar returns, but they may require different accounting treatment.

Your auditor will want more than an annual percentage yield and a wallet balance. Expect requests for the governing terms, ownership evidence, transaction history, valuation policy, income calculation and a reconciliation from the blockchain to the general ledger.

The correct treatment depends on your reporting framework, jurisdiction and the specific arrangement. US GAAP and IFRS do not apply one universal model to every stablecoin or yield product, so confirm the policy with your accounting adviser and auditor before the reporting date.

Start by identifying the yield arrangement

Do not classify a position based only on how it is labelled in a product interface. Review the contract and transaction mechanics to determine where the principal sits, who owes repayment and how the return arises.

The legal terms should explain redemption rights, liquidity windows, fees, withdrawal restrictions, loss allocation and whether assets are lent onward. These details affect classification and disclosure as well as the assessment of credit, liquidity and smart-contract risk.

Before allocating idle treasury through an earn product, retain the terms in force on the allocation date. A later website screenshot may not establish the rights that applied during the accounting period.

Classify the principal before recording yield

The accounting for the principal drives the accounting for its return. Under IFRS, some directly held crypto assets are commonly assessed under IAS 38 as intangible assets, while broker-traders may consider IAS 2 in limited circumstances. A contractual right to receive cash or another financial asset may instead fall within financial-instrument guidance.

Under US GAAP, the fair-value guidance introduced by ASU 2023-08 applies only to crypto assets meeting specified criteria. Some fiat-backed stablecoins or yield positions may fall outside its scope because of their contractual rights or other features. The name “stablecoin” does not determine the answer.

Document a position for each materially different product rather than applying one policy to every USDC or USDT balance. The memo should cover:

• The legal issuer, borrower, custodian or protocol involved.
• The company’s redemption and withdrawal rights.
• Whether depositing stablecoins creates a new asset or maintains the original balance.
• Whether the position has a quoted or otherwise observable fair value.
• Applicable impairment, expected credit loss or fair-value requirements.
• Liquidity restrictions, lock-ups and presentation as current or non-current.

Record accrued yield using the enforceable entitlement

Yield accounting should follow the amount the company has earned under the arrangement, not a projected return based on an advertised APY. Rates may vary daily, depend on utilisation or compound through an increasing token value.

For a simple non-compounding example, assume the company has a $500,000 position earning 5% per year for 12 days. A basic accrual using a 365-day convention would be:

$500,000 × 5% × 12 ÷ 365 = $821.92

Use this method only if it matches the contract. If returns accrue through an exchange-rate change, a changing quantity of receipt tokens or daily compounding, calculate income from the actual position data.

Illustrative journal entries

If earned yield is enforceable but has not yet been credited, an illustrative entry may be:

• Debit: Yield receivable — $821.92
• Credit: Yield income — $821.92

When the yield is received:

• Debit: Stablecoin or applicable asset — $821.92
• Credit: Yield receivable — $821.92

If yield is automatically added to the position, the debit may instead increase the carrying amount of the relevant asset. Transaction fees should be recorded separately according to the company’s policy rather than netted invisibly against income. Foreign-exchange movements, stablecoin price changes and yield are also different economic components and may require separate ledger accounts.

Apply a defensible reporting-date cut-off

Blockchain networks operate continuously, while accounting systems usually close at a defined time and timezone. Your close policy should specify the reporting timestamp, the corresponding block or reliable data snapshot, and how transactions awaiting confirmation are treated.

For each position, capture:

• Network and wallet address.
• Token contract address, symbol and decimal precision.
• Block number and timestamp used for the snapshot.
• Principal deposited, withdrawals, claimed yield and unclaimed accrual.
• Receipt-token quantity and conversion rate, where relevant.
• Market price and source used to translate the position into the functional currency.

A token designed to track one US dollar should not automatically be valued at exactly $1. Your policy should address observable depegging, market liquidity and principal-recovery risk at the reporting date.

Build the audit evidence chain

Onchain data proves that a transaction occurred at an address; it does not by itself prove that your company owns or controls that address. Strong audit evidence connects corporate authority, wallet control, blockchain activity and the ledger.

A period-end evidence pack should normally include:

• Executed agreements, product terms and fee schedules.
• A register mapping each wallet and account to the legal entity.
• Evidence of wallet control, such as approved signing records or an auditor-requested verification procedure.
• Transaction hashes, network names and explorer records for deposits, withdrawals and yield claims.
• Position statements or protocol data showing accrued and unclaimed yield.
• The calculation workbook, including rates, day-count convention and rounding.
• Independent price evidence and the documented valuation methodology.
• A roll-forward from opening balance to deposits, withdrawals, yield, fees, valuation movements and closing balance.
• General-ledger entries and proof of subsequent withdrawal or conversion, where available.

For self-custodial MPC vaults, retain the approval history showing which authorised participants approved a transfer under the company’s quorum policy. MPC, or multi-party computation, divides signing authority so that no single person holds the complete private key. Stablerail’s audit log and evidence packs can help finance teams connect approvals and treasury activity to reconciliation records, but management remains responsible for the accounting policy and completeness of evidence.

Use a repeatable monthly reconciliation

Do not wait for the annual audit. Reconcile each material yield position monthly using the same process:

• Export wallet, platform and protocol activity for the period.
• Match each transaction to a ledger entry using the transaction hash as a reference.
• Recalculate earned yield independently of the displayed dashboard total.
• Separate yield income, network fees, realised disposals and valuation changes.
• Investigate differences caused by timing, token decimals, failed transactions or unclaimed rewards.
• Obtain review and approval from someone other than the preparer.

A clear crypto accounting policy, consistent cut-off and complete audit evidence will answer most auditor questions before fieldwork begins. The goal is not merely to prove that tokens exist. It is to demonstrate what the company owns, how the position is measured, when yield was earned and how every reported amount ties back to verifiable activity.