Crypto fair value accounting under ASU 2023-08

The deliverable is a crypto subledger that keeps each asset by wallet or account and by acquisition lot. A row records units, date acquired, cost, the fair value at each month end, the price source and the unrealized gain or loss. The subledger feeds a monthly journal entry that moves the carrying amount to fair value and books the change to net income. Alongside it is a reconciliation of on-chain or exchange balances to the general ledger, so the unit count agrees as well as the dollars.

For the adoption year we prepare the cumulative-effect adjustment support: the carrying amount at the start of the year under the old model, the fair value at that date and the difference to opening retained earnings. For each annual close we prepare the disclosure support the standard asks for, including the rollforward and a list of contractual sale restrictions and holdings that are significant. A scope memo draft documents which holdings meet the criteria and which, like most NFTs and stablecoins, need separate analysis.

First, a scope pass. ASU 2023-08 applies to assets that meet the definition of an intangible asset, give the holder no enforceable rights to goods, services or other assets, sit on a distributed ledger secured by cryptography, are fungible, and were not created or issued by the holder or its related parties. We list each holding and the criteria it meets, and the company and its auditor decide the scope.

Second, data access. We ask for read-only API keys from exchanges, statement exports and public wallet addresses. Where a wallet is controlled by a custodian or a multi-signature setup, we need only the address and the transaction history. Third, we load the history, assign lots, record price sources and reconcile units to the balances. Each month end we pull the price from the source the company has chosen, measured at a stated time, post the remeasurement and reconcile the result before the close is final. Staking rewards, token receipts for services and payments made in crypto are each flagged to the policy the company has adopted.

The fit is an operating company whose crypto is incidental to the business or part of the treasury: a SaaS company that accepts crypto payments, a services firm that holds tokens received as payment, a startup with a token treasury, a protocol foundation with fiat operations alongside its holdings, or a family-owned business that bought bitcoin as a reserve. The common feature is that crypto sits on the balance sheet and someone, usually an auditor or a lender, now asks for fair value.

It is not for an individual who wants a trading history cleaned up for a Form 8949, and it is not a custody or trading service. Tokens that the company itself issued fall outside the standard's scope and need their own analysis.

The first is a ledger that still carries crypto at cost less impairment under the old model, with no plan for adoption. The second is price sources chosen on the day: a different exchange each month, with no documented cut-off. The third is one lump crypto account with no lot detail, so nobody can say what was bought when or at what cost, and tax basis is a guess. The fourth is wallet balances that do not agree to the ledger because transfers between the company's own wallets were booked as sales or purchases. The fifth is staking and similar rewards recorded inconsistently, some as revenue, some as a reduction of cost, some not at all.

The general ledger stays in QuickBooks Online, Xero or NetSuite. The subledger can live in a controlled Excel or Google Sheets workbook, or in a crypto accounting tool the company already has; we reconcile to the general ledger in either case and do not rely on a tool's own totals. Data arrives as read-only exchange API connections, statement exports and public blockchain addresses. We do not use tools that need signing authority, and we do not trade, transfer or custody anything.

Scope depends on the number of wallets and exchange accounts, the number of transactions per month and whether the adoption-year entry and prior periods have to be rebuilt. The monthly remeasurement for a small treasury can fit inside monthly reporting scope. Heavy transaction volume or multi-year history is quoted separately in writing before work starts. Current tiers are published on the pricing page.

Every month end, the subledger is checked three ways before it is delivered. Units per wallet agree to the exchange or blockchain balance. The carrying amount agrees to the general ledger. Each price used is traceable to the documented source and time. We also keep a written note for any transfer, reward or payment that required a judgment, so the auditor can follow it without a call. The standard we hold the file to is that a reviewer can pick any holding and trace it from the wallet to the lot to the fair value to the journal entry.

Setting up the subledger usually takes one to three weeks depending on the number of accounts and how much history has to be loaded. A mid-year adoption or a multi-year rebuild takes longer and is scoped up front. If your books are not reconciled, we begin with a catch-up and, where crypto sits in more than one legal entity, set up multi-entity accounting first. For the wider picture on crypto businesses, see our crypto and Web3 industry page.