AICPA Adds Stablecoin and Mining Revenue Chapters to Digital Assets Practice Aid
The American Institute of CPAs has updated its digital assets practice aid with two new chapters and a suite of standard-alignment revisions, giving US accounting practitioners their clearest framework yet for stablecoin issuer accounting and mining revenue auditing. For firms whose clients sit anywhere in the digital asset value chain, the August 2026 release is not optional reading.
What the AICPA Updated and Why It Matters
The AICPA's digital assets practice aid has served as the primary non-authoritative guidance source for practitioners navigating crypto accounting under US GAAP since digital assets entered mainstream corporate balance sheets. Until now, stablecoin issuers and mining operators existed in something of a grey zone: FASB's ASC 350-60 addressed fair value measurement for certain crypto assets held by entities, but it said little about the issuer-side obligations that arise when a company creates and distributes tokens pegged to a reference asset. Separately, mining revenue arrangements, particularly those involving pool participants and third-party data centre hosts, lacked any dedicated audit guidance.
Di Krupica, CPA, senior manager for Digital Assets, Assurance and Advisory Innovation at the AICPA, framed the update directly: as digital asset business models evolve, practitioners are encountering increasingly complex accounting and auditing questions, and the new chapters aim to provide clarity where demand for guidance has grown and help professionals align with current standards and emerging practices.
That framing matters. The practice aid carries non-authoritative status under the AICPA's hierarchy, but in the absence of explicit FASB pronouncements on these specific scenarios, non-authoritative guidance from a recognised standard-setter body is exactly what auditors and preparers are expected to consult. Departing from it without documented justification creates audit risk.
Stablecoin Issuer Accounting: The New Chapter Unpacked
The new chapter dedicated to stablecoin issuers tackles two questions that have made CFOs and controllers uncomfortable for years: when and how does an issuer recognise the obligation created by the tokens it puts into circulation, and how should the reserve assets backing those tokens be carried on the balance sheet?
Recognition of Issued-Token Obligations
When a company issues a stablecoin, it receives consideration, typically fiat currency or other liquid assets, and the holder of that token has a claim against the issuer. The central accounting question is whether that claim constitutes a financial liability, a non-financial liability, or something else entirely under US GAAP. The new chapter addresses the recognition criteria and the conditions under which the obligation is derecognised, for example when tokens are redeemed or burned. For companies issuing USD-pegged tokens such as USDC-equivalent instruments, getting this classification wrong has direct consequences for the income statement, the balance sheet presentation, and potentially for regulatory capital calculations if the entity is a regulated entity. Stablecoin accounting under US GAAP has lacked this level of specificity, and the new chapter closes a meaningful gap.
Reserve Asset Considerations
The backing assets held in reserve are the other side of the equation. These may include cash, short-duration Treasuries, or other instruments, and each carries its own US GAAP measurement and classification requirements independent of any crypto-specific rules. The chapter sets out considerations for how to classify and present reserve assets, including the disclosure implications that arise because of their purpose as backing collateral. This is particularly relevant for firms auditing stablecoin issuers: the reserve portfolio is precisely where audit risk concentrates, and having AICPA guidance on what to look for materially strengthens the audit programme.
Mining Revenue: A Dedicated Audit Chapter
Mining revenue has always been conceptually straightforward at the surface level: a miner expends computing resources, receives a block reward, and recognises revenue. In practice, the arrangements are far more layered.
Pool Participants and Revenue Timing
Most large-scale mining operations today participate in pools rather than mining independently. A pool aggregates hashing power across multiple participants, earns block rewards collectively, and distributes proceeds according to a agreed protocol. The accounting question is when a pool participant should recognise revenue: at the point the pool earns a block reward, at the point of distribution to the participant, or on some other basis? The new chapter addresses this timing question and the conditions that inform the answer. Audit teams need to understand the specific pool arrangement their client is party to before applying the guidance, because different pool structures may lead to different conclusions.
Data Centre Host Arrangements
A growing number of miners outsource physical infrastructure to data centre hosts under managed hosting agreements. These arrangements can blur the line between the entity doing the mining, for accounting purposes, and the entity providing a service. The new chapter addresses the considerations relevant to data centre host transactions, including how to evaluate whether the miner or the host is the principal in the arrangement and what that determination means for revenue and cost recognition. For auditors, this is the area most likely to require careful inspection of contracts and an assessment of the substance of the arrangement rather than its legal form.
Auditing Standard Alignment: SAS No. 148 and SAS No. 146
Beyond the two new chapters, the practice aid has been updated to reflect auditing standards through Statement on Auditing Standards No. 148 and includes revisions related to SAS No. 146, which addresses quality management at the engagement level under AU-C Section 220.
What SAS No. 148 Changes for Digital Asset Audits
SAS No. 148 updates the suite of risk assessment standards, tightening the linkage between an auditor's understanding of the entity and its environment, the assessment of risks of material misstatement, and the design of audit responses. In a digital asset context, this is particularly significant. The expanded risk assessment requirements mean auditors can no longer treat crypto holdings or crypto revenues as a straightforward extension of existing controls testing. The practice aid's alignment to SAS No. 148 ensures that the specific digital asset audit procedures described in the guidance now sit within the correct procedural framework that US auditors are required to apply for engagements governed by this standard.
SAS No. 146 and Engagement Quality
SAS No. 146 reshapes how firms think about quality management at the engagement level, shifting from a largely retrospective quality control review to a more dynamic, ongoing process. The revisions to the practice aid reflect this shift. For firms with digital asset clients, the implication is that engagement quality considerations, including the competence of the engagement team to address complex crypto accounting questions, should be assessed continuously rather than at a single point in the engagement lifecycle. The AICPA's revisions to Chapter 5 of the practice aid, which consolidate existing question-and-answer content without altering the underlying guidance, also contribute to this by making the document easier to navigate under time pressure during an active engagement.
Practical Implications for Accounting Firms and CFOs
The release arrives at a moment when digital asset accounting is under close regulatory scrutiny. The SEC has continued to focus on the adequacy of disclosures around digital asset holdings and obligations, and the PCAOB has signalled interest in how registered firms approach crypto-related audit risk. Against that backdrop, the updated practice aid serves multiple functions.
For Audit and Assurance Teams
Firms should treat the two new chapters as a prompt to revisit any client in the stablecoin or mining space. Existing audit programmes that predate this guidance may not address the specific risk areas the AICPA has now flagged as material. In particular, teams should check whether their procedures for stablecoin issuer clients cover both the liability recognition question and the reserve asset presentation. For mining clients, the pool arrangement and data centre host questions should be explicitly addressed in the risk assessment and in the design of substantive procedures.
The alignment to SAS No. 148 also means that firms should confirm their engagement documentation reflects the updated risk assessment framework, not earlier versions of the standards. Any engagement that commenced before SAS No. 148 became effective and is still ongoing should be reviewed for gaps. Understanding how FASB crypto fair value rules intersect with financial reporting quality is essential context here, particularly for teams working across multiple digital asset client types simultaneously.
For CFOs and Controllers at Digital Asset Companies
If your company issues stablecoins, the new chapter is the closest thing to authoritative US GAAP guidance you have on the issuer-side obligation question. Work with your external auditor to assess whether your current accounting policy aligns with the positions set out in the chapter. If there are differences, document your reasoning carefully. The absence of documented justification for departing from non-authoritative guidance issued by the AICPA is an audit finding waiting to happen.
For companies with mining operations, the chapter on pool arrangements and data centre hosts is similarly relevant to your internal accounting team. Revenue recognition policies should be reviewed against the timing considerations the guidance raises, and any arrangements with data centre hosts should be assessed for principal versus agent implications. Keeping pace with global crypto policy shifts affecting US accounting teams is equally important given how quickly the regulatory environment is moving alongside these standard updates.
The Broader Context: US GAAP vs. IFRS on Crypto Assets
It is worth placing this update in international context, even though the AICPA guidance is US-specific. The IASB's agenda decision on crypto assets under IAS 38, which directs IFRS preparers to account for most crypto assets as intangible assets unless they are held for trading, does not address the stablecoin issuer question with anything like the depth the AICPA is now providing. For multinational groups reporting under both frameworks, the gap between US GAAP treatment of stablecoin issuance obligations and the IFRS position remains material. The AICPA's move may add pressure on the IASB to accelerate its own work in this area, but for now, crypto US GAAP accounting has a meaningful head start on the issuer-side question.
ASC 350-60, which FASB finalised to require fair value measurement for entities holding certain crypto assets, addressed the asset-holder side of the equation. The AICPA's new chapter now complements that by addressing the issuer side. Together, they give US preparers a more complete picture than exists under IFRS for stablecoin accounting, though gaps remain and practitioners should monitor FASB's agenda for further developments.
Frequently Asked Questions
Does the AICPA practice aid carry the same authority as a FASB standard?
No. The AICPA digital assets practice aid is non-authoritative guidance. It sits below FASB Accounting Standards Codification in the US GAAP hierarchy. However, when no authoritative guidance directly addresses a transaction, preparers and auditors are expected to consult relevant non-authoritative sources, and departing from them requires documented justification. In areas like stablecoin issuer obligations, where ASC 350-60 and other codification topics do not provide specific direction, the practice aid carries significant practical weight.
How does the new stablecoin chapter affect USDC accounting for issuers?
For any entity that issues a USD-pegged token, the chapter requires consideration of whether the outstanding tokens represent a financial liability under US GAAP and how derecognition occurs on redemption or burn. It also addresses how the reserve assets backing those tokens should be classified and presented. Any issuer, including those operating USDC-equivalent instruments, should review their existing accounting policies against this guidance and discuss any departures with their external auditor.
What should audit teams do immediately following this release?
Teams should review all active and upcoming engagements involving stablecoin issuers or mining operators. Audit programmes should be updated to explicitly address the liability recognition and reserve asset questions for stablecoin clients, and the pool participant timing and data centre host principal-versus-agent questions for mining clients. Engagement quality assessments under SAS No. 146 should also confirm that team competence in these areas has been evaluated as part of the ongoing quality management process.
Does SAS No. 148 change what evidence auditors need for crypto-related assertions?
SAS No. 148 strengthens the link between risk assessment and the design of audit responses, which means auditors must be more explicit about how identified risks at the assertion level drive their choice of procedures. For digital asset engagements, this typically means more rigorous documentation of why specific substantive procedures were chosen to address, for example, the completeness of stablecoin obligations or the existence of reserve assets. Teams should not assume that existing programmes designed under earlier risk assessment standards automatically satisfy SAS No. 148 requirements.
Is there equivalent guidance under IFRS for stablecoin issuers?
Not at this level of specificity. The IASB's existing agenda decision directs preparers to account for most crypto assets as intangible assets under IAS 38 or, if held for trading, as inventory under IAS 2. That guidance focuses on the holder, not the issuer. Stablecoin issuers reporting under IFRS must apply general financial instruments and liability recognition standards without dedicated crypto-specific direction. The AICPA's update creates a meaningful asymmetry that multinational groups will need to manage carefully across their reporting frameworks.
Source: Journal of Accountancy