AICPA Updates Practice Aid: Stablecoin Accounting and Mining Revenue Auditing

The American Institute of CPAs has released a significant update to its digital assets practice aid, adding dedicated guidance on stablecoin issuer accounting, mining revenue auditing, and alignment with the latest auditing standards through SAS No. 148. For accounting firms and CFOs navigating US GAAP crypto accounting, the release fills several long-standing gaps and reshapes how practitioners should approach stablecoin obligations and proof-of-work revenue arrangements.

What the AICPA Updated and Why It Matters

The AICPA practice aid on digital assets is a non-authoritative but widely referenced resource that helps CPAs apply existing US GAAP and auditing standards to crypto-specific fact patterns. The August 2026 update is the most substantive revision in some time, introducing two entirely new chapters and refreshing existing content to track current professional standards.

Di Krupica, senior manager for digital assets, assurance and advisory innovation at the AICPA, framed the update plainly: digital asset business models keep evolving, practitioners keep encountering complex questions, and the gap between real-world arrangements and available guidance has grown wide enough to require a formal response. The update is the profession's answer to that demand.

Scope of the revision

At a high level, the update covers four distinct areas:

• A new chapter on accounting for stablecoin issuers
• A new auditing chapter on mining revenue arrangements
• Updates through SAS No. 148, including revisions related to SAS No. 146 (AU-C Section 220) on quality management
• Streamlined consolidation of existing question-and-answer content in Chapter 5, with no change to underlying guidance

Each of these has distinct implications for preparers and auditors, and they are worth examining separately.

Stablecoin Accounting: The New Chapter Explained

Stablecoin issuers have occupied an awkward accounting position for years. There is no dedicated US GAAP standard that addresses the recognition and measurement of tokens issued in exchange for fiat or other reserve assets, and practitioners have had to reason by analogy from existing guidance on financial liabilities, deposits, and similar instruments. The new AICPA chapter brings structured thinking to this space for the first time at the practice-aid level.

Recognition of token issuance obligations

The guidance addresses how an issuer should recognise the obligation that arises when it issues a stablecoin. The core question is whether the issued tokens give rise to a financial liability (because the holder can redeem for fiat) or some other form of obligation, and how that liability should be measured at inception and subsequently. The practice aid provides considerations rather than a single prescribed answer, acknowledging that the contractual terms of different stablecoin programmes can vary materially.

For accounting teams at stablecoin issuers or at firms auditing them, this is consequential. Getting the liability classification wrong affects the balance sheet, the income statement (through changes in fair value or redemption amounts), and potentially regulatory capital calculations if the issuer is subject to any prudential oversight.

Reserve asset accounting considerations

The second dimension of the new stablecoin chapter covers the assets held in reserve to back issued tokens. Stablecoin reserves can include US Treasuries, repo agreements, cash deposits, and in some programmes, other digital assets. Each of those asset classes carries its own GAAP measurement model, and the practice aid sets out considerations for how reserve assets should be classified and measured, and how the relationship between the reserve and the issued liability should be presented.

This matters beyond just the issuer. Auditors of entities that hold significant stablecoin balances, such as a corporate treasury holding USDC as a working capital tool, need to understand the counterparty's reserve structure when assessing the asset's recoverability. The AICPA guidance informs that analysis even when the client is not itself an issuer.

For US GAAP preparers already applying ASC 350-60 (the FASB's fair value framework for crypto assets adopted in 2024), stablecoins sit in a specific category: most dollar-pegged stablecoins are excluded from ASC 350-60's scope because they are not subject to significant price volatility in the way that bitcoin or ether are. The AICPA chapter operates in that gap, giving issuers a structured way to think through obligations and reserves under the broader liability and asset standards that do apply.

Mining Revenue: Auditing Considerations for Complex Arrangements

Proof-of-work mining has grown into a multi-layered industry. A miner today may operate its own hardware, participate in a pool that aggregates hash rate across thousands of machines, lease capacity to or from a data centre host, or enter into revenue-sharing arrangements that blend elements of all three. Each structure raises different revenue recognition questions, and auditing those revenue streams has become meaningfully more complex.

Mining pool participants and revenue recognition

When a miner contributes hash rate to a pool, the timing and amount of revenue recognition depends on the pool's reward method: pay-per-share, full-pay-per-share, or proportional, among others. The AICPA's new auditing chapter addresses how auditors should evaluate the performance obligation in these arrangements and what procedures are appropriate for verifying the amounts reported as mining revenue. Example audit procedures are included, giving engagement teams a starting point for designing their own substantive testing.

Data centre hosting arrangements

Data centre hosts that provide space, power, and cooling to third-party miners are in a different position: they may receive fees in crypto, in fiat, or through a hybrid arrangement. The practice aid considers how hosts should think about their revenue recognition model and what an auditor should focus on when evaluating those contracts. The distinction between hosting as a service and hosting as a joint-mining arrangement has real accounting consequences, and the guidance helps draw that line.

For audit firms with mining clients, the new chapter reduces the need to construct bespoke procedures from scratch. For CFOs at mining operations, it signals that auditors will be asking structured questions about pool contracts, hash rate contribution records, and hosting agreements. Having clean documentation for those items before audit fieldwork begins will shorten engagement timelines.

Auditing Standards Updates: SAS 146 and SAS 148

The practice aid has been updated to reflect auditing standards through SAS No. 148. The most operationally significant revision relates to SAS No. 146, which amended AU-C Section 220 on quality management at the engagement level. These standards have been effective for periods ending on or after June 15, 2025, which means they are already in scope for many current engagements.

What changes for digital asset engagements

AU-C Section 220 under SAS No. 146 shifts quality management from a compliance-checklist mindset to a risk-based model. Engagement teams are expected to identify quality risks specific to the engagement, design responses proportionate to those risks, and document their reasoning. For digital asset engagements, that means the quality management narrative cannot be generic. The specific risks of crypto custody verification, blockchain data reliability, and valuation of non-liquid tokens need to be addressed explicitly in the engagement's quality management approach.

The AICPA's updates to the practice aid incorporate these requirements, ensuring that the digital asset-specific guidance practitioners rely on does not lag behind the auditing standards framework within which they are working. Firms that have already updated their standard engagement templates for SAS No. 146 should cross-reference those templates against the revised practice aid to confirm alignment.

Practical Implications for Accounting Firms and CFOs

The AICPA guidance is non-authoritative, meaning it does not carry the force of a FASB standard or an SEC rule. But non-authoritative guidance issued by the AICPA carries significant weight in practice, particularly when it is the most detailed resource available on a given topic. Auditors who deviate from it need a well-documented reason. Preparers who ignore it risk questions from their auditors.

For accounting firms

Firms with digital asset clients should schedule a technical update session to work through the new stablecoin and mining chapters alongside their existing ASC 350-60 documentation. Engagement risk assessments for stablecoin issuer clients will need to be refreshed to reflect the new recognition and reserve considerations. Mining clients should be asked to provide pool agreement documentation and data centre hosting contracts as standard information requests, given the new example audit procedures the AICPA has published.

Firms should also review their SAS No. 146 implementation against the updated practice aid to confirm that quality management documentation on digital asset engagements is genuinely risk-based rather than formulaic. The combination of the new auditing standards and the updated practice aid raises the bar for what a defensible engagement file looks like.

Staff development is a related consideration. The technical demands of digital asset auditing continue to rise, and firms that have experienced turnover in specialist roles face a real knowledge gap. The reporting risk that comes with losing experienced staff is amplified in a practice area where the guidance itself is still catching up to business models.

For corporate CFOs and treasury teams

CFOs at companies holding stablecoins as working capital instruments should revisit how those balances are classified and disclosed. Even though the holder-side accounting is not the primary focus of the AICPA's new stablecoin chapter (which addresses issuers), the reserve analysis considerations are relevant to understanding the credit risk of the stablecoin and, by extension, whether impairment or reclassification is appropriate.

For companies that have adopted ASC 350-60, the stablecoin exclusion from that standard needs to be clearly documented. The AICPA guidance reinforces that stablecoins require a separate analytical framework, and CFOs should ensure their accounting policy memos reflect that distinction explicitly rather than relying on a catch-all crypto asset policy. This connects directly to broader shifts in global crypto accounting and policy frameworks that are reshaping how digital assets are treated on corporate balance sheets.

Frequently Asked Questions

Is the AICPA practice aid authoritative under US GAAP?

No. The practice aid sits in the non-authoritative category of the GAAP hierarchy. It offers implementation guidance and illustrative considerations rather than binding standards. However, it is widely used by practitioners and auditors, and departures from it require documented justification. Authoritative guidance for crypto assets held by entities comes primarily from FASB ASC 350-60 and the broader ASC framework.

How does the stablecoin chapter interact with ASC 350-60?

ASC 350-60 covers crypto assets that meet a specific definition, which generally excludes assets that an entity itself has created or that represent a claim on the issuer. Most stablecoins are excluded from ASC 350-60's scope on the holder side because they do not meet the in-scope definition, and on the issuer side because the issued tokens represent a liability, not an asset. The AICPA's new chapter fills this gap by addressing how issuers account for those liabilities and the reserve assets backing them under the applicable liability and asset standards.

What are SAS No. 146 and SAS No. 148, and when do they apply?

SAS No. 146 amended AU-C Section 220, introducing a risk-based approach to engagement-level quality management. SAS No. 148 is the most recent Statement on Auditing Standards, and the AICPA practice aid has been updated to reflect standards through that point. SAS No. 146 is effective for audits of financial statements for periods ending on or after June 15, 2025, meaning it is already in scope for most current engagements.

Do the mining revenue considerations apply to proof-of-stake validators?

The new auditing chapter focuses specifically on proof-of-work mining arrangements, including pool participation and data centre hosting. Proof-of-stake validation involves different economic structures and legal characterisations. The AICPA practice aid does not, based on this update, address staking revenue in the same depth. Practitioners with staking clients will need to reason from the existing revenue recognition standards (ASC 606) and look to other emerging guidance for that specific fact pattern.

Where can practitioners access the updated practice aid?

The practice aid is available through the AICPA directly. Members and subscribers can access it via the AICPA website. The organisation has made the document available as part of its ongoing effort to help the profession keep pace with digital asset developments.

Source: AICPA & CIMA