Table of Contents
- What Is Digital Asset Accounting?
- Why Digital Asset Accounting Matters for CFOs
- Building a Digital Asset Accounting Framework
- Challenges CFOs Can Face
- Connect Payment Activity to the Accounting System With Paystand
- Frequently Asked Questions
Key Takeaways
- Digital asset accounting is broader than the accounting guidance for crypto assets. ASU 2023-08 applies only to assets that meet all of the scope criteria in ASC 350-60.
- For in-scope assets, ASU 2023-08 replaces the previous impairment model with fair value measurement each reporting period, with changes recognized in net income.
- A defensible framework combines scope assessment, valuation data, custody and authorization controls, transaction classification, reconciliation, disclosure, and tax coordination.
- Book and tax treatment do not automatically move together. Finance and tax teams need separate, documented policies for financial reporting and digital asset basis tracking.
- Paystand supports the payment-to-accounting workflow through automated cash application, deposit reconciliation, and ERP connectivity; it does not replace specialized digital asset accounting or tax systems.
Digital assets introduce accounting questions that traditional cash and payment workflows were not designed to answer. Finance teams may need to determine whether an asset falls within ASC 350-60, establish a repeatable fair value methodology, document custody and authorization controls, reconcile activity across systems, and maintain evidence that can stand up to audit.
ASU 2023-08 made that work more important by changing the subsequent measurement of qualifying crypto assets. For assets within scope, fair value changes now flow through net income each reporting period instead of being recognized only through the former cost-less-impairment model.
The result is a more current balance-sheet value, but also a greater need for disciplined data, controls, and reporting. This guide explains how digital asset accounting works under current U.S. GAAP, where ASU 2023-08 applies, and what CFOs and controllers should build into their accounting process. For finance leaders, that work sits within a broader business financial management framework that connects reporting, controls, liquidity, tax, and payment operations.
What Is Digital Asset Accounting?
Digital asset accounting is the process of identifying, recording, measuring, reconciling, and reporting transactions involving digitally represented assets. The accounting treatment depends on the rights and economics of the asset, how the business acquired it, how it is held, and which accounting guidance applies.
That distinction matters because "digital asset" is broader than the scope of ASU 2023-08. The standard created dedicated guidance in ASC 350-60 for certain qualifying crypto assets, but it does not establish one accounting model for every token, stablecoin, nonfungible token (NFT), or digitally represented asset.
What Changed Under ASU 2023-08
Before ASU 2023-08, many crypto assets held by non-investment companies were accounted for as indefinite-lived intangible assets. If fair value fell below carrying value, the company recognized an impairment loss, but subsequent recoveries generally were not recognized until disposal.
For assets within ASC 350-60, that subsequent measurement model has changed. Companies measure the assets at fair value at each reporting date and recognize changes in fair value in net income. A decline and a later recovery are therefore reflected in the periods in which those value changes occur.
ASU 2023-08 focuses on subsequent measurement, presentation, and disclosure. Initial recognition still depends on the transaction that brought the asset onto the books, so finance teams should document both the initial accounting conclusion and the subsequent measurement model.
Which Assets Are in Scope?
ASC 350-60 applies only when an asset meets all of the following criteria:
- It meets the definition of an intangible asset under U.S. GAAP.
- It does not provide the holder with enforceable rights to, or claims on, underlying goods, services, or other assets.
- It is created or resides on a distributed ledger based on blockchain or similar technology.
- It is secured through cryptography.
- It is fungible.
- It is not created or issued by the reporting entity or its related parties.
Bitcoin and Ether are common examples of assets that can meet these criteria. Other digital assets require a facts-and-circumstances assessment. A token should not be assumed to be in or out of scope solely because it is called a stablecoin, wrapped token, utility token, or digital asset.
This is especially important as FASB continues to evaluate related areas. Current projects address transfers of crypto assets, including additional guidance relevant to certain wrapped and receipt tokens, and whether certain digital assets may qualify as cash equivalents. Those projects should be monitored, but tentative Board decisions should not be treated as final GAAP until a standard is issued.
What This Means on the Financial Statements
For in-scope assets, the balance sheet presents crypto assets measured at fair value separately from other intangible assets that are not measured at fair value. The income statement also presents changes from remeasurement separately from changes in the carrying amounts of other intangible assets.
Disclosure requirements are more granular than a single digital-asset balance. For significant holdings, companies disclose the asset name, cost basis, fair value, and number of units. Annual disclosures also include an aggregate rollforward of activity, information about dispositions, the method used to determine cost basis, and other required details.
Cash-flow presentation depends on the transaction. One important ASU 2023-08 rule applies when a business receives an in-scope asset as noncash consideration in the ordinary course of business and converts it nearly immediately to cash: the resulting cash receipt is presented as an operating cash flow.
Why Digital Asset Accounting Matters for CFOs
The accounting model affects more than the balance-sheet classification. It changes how digital asset positions can flow through earnings, how evidence is prepared for audit, how tax and accounting teams coordinate, and how internal controls are designed around custody and transaction approval.
Fair Value Can Add Earnings Volatility
Consider a company holding $1 million of an in-scope digital asset. If its fair value falls 30%, the company recognizes a $300,000 loss through net income for that reporting period. If the value later recovers, the recovery is also recognized through net income rather than waiting until the asset is sold.
For companies with material digital asset holdings, that can make GAAP earnings more sensitive to market movements that are separate from operating performance. Finance teams may need to explain those movements in management reporting, covenant analysis, forecasts, and investor communications.
Book and Tax Treatment Need Coordination
Fair value accounting under U.S. GAAP does not automatically mean that every unrealized gain becomes taxable income. Financial reporting and federal tax rules are separate frameworks, and the tax result depends on the taxpayer and the transaction.
For corporations subject to the Corporate Alternative Minimum Tax, adjusted financial statement income can make book treatment relevant to the tax calculation. Other companies may still have significant book-tax differences even when unrealized fair value changes are not current taxable events. Finance teams should document the accounting policy and coordinate separately with tax advisors on basis, realization, reporting, and entity-specific consequences.
Audit Evidence Needs to Be Reproducible
Digital asset balances can require evidence from multiple sources: custodians, wallets, exchanges, blockchain records, pricing services, contracts, and the general ledger. The accounting conclusion is easier to defend when the organization can show where the asset is held, how ownership or control is established, which pricing source supports fair value, how transactions were authorized, and how activity reconciles to the books.
A strong close process produces that evidence as part of normal operations rather than reconstructing it at year-end. The objective is a repeatable audit trail from transaction initiation through financial statement presentation.
Controls Depend on the Custody Model
Control design should reflect how the company interacts with digital assets. A business that directly controls private keys has different risks from one that uses a qualified custodian or a managed payment provider.
For direct custody, controls may include multi-signature approval, role separation, address verification, key-management procedures, access reviews, and frequent wallet-to-ledger reconciliation. With third-party custody, finance teams still need controls over authorization, provider access, statement reconciliation, service-organization reporting, and the completeness of records received from the custodian.
The important point is not to apply "crypto controls" as a generic checklist. It is to map controls to the actual custody, settlement, approval, and accounting workflow used by the business.
Building a Digital Asset Accounting Framework
A scalable digital asset accounting framework should answer five questions: What is the asset? How is it valued? Who controls it? How does activity reach the ledger? What evidence supports the financial statements and tax records?
1. Document the Accounting Policy and Scope
Start with a written policy that explains how the company determines which accounting guidance applies. The policy should address:
- The process for evaluating whether an asset meets every ASC 350-60 scope criterion.
- The principal market and pricing source used for fair value, including a documented fallback source.
- How transaction types are classified, including purchases, disposals, assets received as payment, rewards, transfers, and other digital asset activity.
- How ownership, control, and custody are documented.
- How realized dispositions and cost basis are tracked for tax and disclosure purposes.
- Who approves policy changes when new asset types or transaction structures are introduced.
Tax basis methodology deserves separate documentation. For digital asset dispositions in 2025 and later, federal rules generally operate at the wallet or account level. Specific identification is available when the required identification and recordkeeping standards are met; when adequate specific identification is not made, FIFO generally applies within the relevant wallet or account.
Revenue Procedure 2024-28 provided transition relief for allocating previously unattached basis as taxpayers moved away from universal or multi-wallet methods; it should not be treated as a permanent alternative cost-flow method.
2. Build Reliable Data and Systems Integration
Most general ledgers were not designed to ingest wallet activity, custodian data, exchange transactions, token quantities, and market prices as a single accounting record. Depending on transaction volume and custody structure, companies may need a digital asset subledger or specialized accounting system between the source platforms and the ERP.
The system should preserve enough information to reproduce the accounting result, including:
- Transaction identifier, date, time, quantity, and asset.
- Source wallet, custodian, exchange, or counterparty where relevant.
- Transaction type and business purpose.
- Pricing source and fair value used for reporting.
- Cost-basis and lot information needed for dispositions and disclosure.
- Journal-entry mapping into the ERP or general ledger.
- A reconciliation trail from source activity to the recorded balance.
Spreadsheets can support low-volume environments, but complexity rises quickly when activity spans multiple wallets, custodians, entities, or transaction types. The system design should be based on the volume and evidence requirements of the business rather than on a blanket assumption that every company needs the same software stack.
3. Design Controls Around Authorization, Custody, and Reconciliation
Digital asset controls should make it possible to prove that transactions were authorized, assets remained under appropriate control, and the recorded balance is complete and accurate.
Depending on the operating model, controls may include:
- Segregation of duties between transaction initiation, approval, custody administration, and accounting.
- Defined approval thresholds and multi-signature requirements for directly controlled wallets.
- Periodic access reviews for custodians, exchanges, wallets, and accounting systems.
- Address verification or allowlisting procedures for direct digital asset transfers.
- Daily or periodic reconciliation based on transaction frequency and materiality.
- Change controls over valuation sources, account mappings, and digital asset master data.
- Documented exception handling for failed, disputed, or incorrectly classified transactions.
4. Build Reporting and Disclosure Into the Close
Disclosure should not be a year-end reconstruction exercise. Finance teams can make the close more repeatable by maintaining a digital asset position schedule that includes quantities, cost basis, fair value, period activity, restrictions, and the accounting guidance applied to each asset class.
For assets within ASC 350-60, the close process should support the required interim and annual disclosures, including significant holdings and the annual activity rollforward. For out-of-scope digital assets, the team should document which guidance applies and whether separate impairment, financial instrument, inventory, cash-equivalent, or other accounting considerations are relevant.
5. Keep Accounting and Tax Records Connected but Distinct
A digital asset subledger may support both financial reporting and tax data, but the calculations should not be treated as interchangeable. GAAP fair value, tax basis, realized gain or loss, broker reporting, and entity-specific tax positions can follow different rules. Reconcile the datasets, but preserve the distinct methodology and evidence required for each purpose.
Challenges CFOs Can Face
Fair Value and Principal-Market Determination
Digital asset prices can differ across trading venues, so a finance team should not select whichever price is most convenient at period end. ASC 820 requires fair value to reflect the principal market for the asset, or the most advantageous market when there is no principal market.
The practical control is consistency: document the market determination, identify the primary pricing source, retain the period-end evidence, and define how the team responds if the source is unavailable or no longer represents the principal market.
Transaction Classification
Different digital asset activities can lead to different accounting conclusions. Common examples include:
- Treasury holdings: evaluate whether the asset meets ASC 350-60 scope criteria before applying fair value accounting under that subtopic.
- Digital assets received as payment: recognize the underlying sale or service transaction under the applicable revenue guidance, then determine the accounting for the asset received and any subsequent holding period.
- Near-immediate conversion to cash: evaluate the specific cash-flow presentation guidance in ASU 2023-08 when an in-scope asset is received as noncash consideration in the ordinary course of business and converted nearly immediately.
- Staking, rewards, lending, and decentralized-finance arrangements: analyze the specific rights and obligations rather than assuming one treatment applies to every structure.
- Wrapped, receipt, and stable-value tokens: document the current accounting conclusion and monitor active FASB projects that may affect scope or classification.
A decision tree for recurring transaction types can reduce inconsistent treatment, but unusual arrangements should still be evaluated based on their specific contractual rights and economics.
Systems Integration and Reconciliation
The operational challenge is less about the number of transactions than the number of systems needed to explain them. A single activity may involve a wallet or custodian, a blockchain record, a pricing source, an accounting subledger, a bank account, and an ERP entry.
The integration objective is data lineage. Finance teams should be able to trace a recorded balance or journal entry back to the underlying transaction and valuation evidence without manually rebuilding the chain from screenshots or disconnected exports.
Regulatory Change and Audit Preparation
Digital asset accounting remains an active standard-setting area. FASB is working on additional guidance for transfers of crypto assets and on whether certain digital assets may qualify as cash equivalents. Federal tax reporting and basis rules have also continued to evolve.
That makes documentation part of the control environment. Accounting memos should identify the guidance used, the facts considered, the conclusion reached, and the date on which the conclusion was last reviewed. When standards change, the company can then update a documented position instead of rebuilding the analysis from scratch.
Connect Payment Activity to the Accounting System With Paystand
Digital asset accounting systems and B2B payment automation solve different problems. A company that directly holds digital assets may still need specialized subledger, custody, valuation, and tax tools. Paystand fits at the payment-to-accounting layer: helping finance teams automate receivables workflows and keep payment activity connected to the ERP.
Paystand is an agentic B2B payment network. Digital agents help automate collections, cash application, and reconciliation, while the network connects payment status and accounting data to the systems finance teams already use.
- Automate cash application and deposit reconciliation so incoming payments are matched and the deposit reconciles to the general ledger.
- Connect natively with NetSuite, Sage Intacct, Microsoft Dynamics 365, Acumatica, and Business Central through bi-directional ERP synchronization.
- Preserve accounting context such as custom fields, dimensions, subsidiaries, customers, invoices, and sales orders as payment activity moves through the workflow.
- Operate inside role-based permissions and maintain an audit trail across payment and workflow activity.
- Use the existing ERP as the system of record rather than requiring a finance team to replace the accounting structure it already runs.
Explore Paystand Receivables to see how automated cash application, reconciliation, and ERP connectivity can strengthen the payment-to-accounting workflow.
