TL;DR: This guide examines FASB’s latest accounting standards affecting cryptocurrency, focusing on ASU 2025-06 for internal-use software accounting. Key changes include new software innovation assessment criteria, simplified capitalization thresholds, and detailed implementation requirements for organizations handling crypto assets.

The landscape of cryptocurrency accounting continues to evolve, and maintaining compliance with Financial Accounting Standards Board (FASB) Accounting Standards Updates (ASUs) is essential for financial professionals. This comprehensive guide examines the latest FASB standards affecting crypto asset accounting, with a particular focus on the technical specifications that impact your daily operations.

Understanding FASB’s Authority and Recent Updates

Before examining specific standards, it’s important to establish the foundation of FASB’s authority. The FASB Accounting Standards Codification serves as the single official source of authoritative US Generally Accepted Accounting Principles (GAAP)[1]. This makes new ASUs the definitive guidance for accounting professionals across the United States.

In recent developments, FASB issued ASU 2025-06 on September 18, 2025, implementing targeted improvements to accounting for internal-use software under ASC 350-40[2]. This update has significant implications for organizations dealing with crypto assets, particularly those developing internal software solutions for crypto accounting.

Key Technical Specifications of ASU 2025-06

The new standard introduces several important changes that accounting professionals need to understand. Here’s a detailed breakdown of the core technical requirements:

Software Innovation Assessment Requirements

Under ASU 2025-06, entities must evaluate their software based on two key criteria:

  • Whether the software contains technological innovations or novel, unique, or unproven functions
  • If uncertainty in development is resolved through coding and testing processes

These assessments must be conducted at the software project level[3].

Capitalization Threshold Changes

A significant modification in the standard is that entities developing internal-use software no longer need to review detailed program design for high-risk development issues to meet the probable-to-complete threshold[3]. This change streamlines the capitalization process while maintaining appropriate controls.

Practical Implementation Examples

To illustrate how these standards work in practice, let’s examine a real-world scenario:

Consider Entity Y’s development of an AI module for their SaaS ERP system. The module includes:

  • Extract functionality for reading contracts
  • Write functionality utilizing generative AI for revenue recognition

In this case, Entity Y must assess the feasibility for capitalization based on the new ASU criteria[3].

This example shows how modern technology and accounting standards intersect, particularly for organizations developing crypto-related software solutions.

Scope and Application

The reach of these standards is comprehensive. ASU 2025-06 applies to all entities that fall under FASB Accounting Standards Codification Subtopic 350-40, specifically addressing Intangibles-Goodwill and Other-Internal-Use Software[2].

For cryptocurrency-focused organizations, this has particular relevance when:

  • Developing internal trading platforms
  • Creating crypto asset management software
  • Implementing blockchain-based accounting solutions
  • Designing compliance tracking systems

Additionally, there are important considerations for equity securities. ASU 2022-03 provides clarity regarding contractual sale restrictions on equity securities, establishing that such restrictions are not considered part of the unit of account under ASC 820. This update also mandates specific disclosures[4], which may affect how organizations report certain crypto-related securities.

Transition Considerations

As organizations adapt to these new standards, several key transition elements require attention:

Timeline Implementation

  • Review existing software development projects
  • Assess current capitalization practices
  • Plan for systematic updates to internal processes

Documentation Requirements

  • Update internal control procedures
  • Revise software development policies
  • Create new assessment templates aligned with ASU criteria

Staff Training Needs

  • Technical training on new assessment criteria
  • Process updates for development teams
  • Communication protocols between IT and accounting departments

Successful implementation requires coordination between accounting teams, software development groups, and compliance officers to ensure all stakeholders understand their roles while maintaining efficient operations.

Implementation Requirements

Organizations need to carefully plan their approach to implementing these FASB ASU standards. The process begins with a thorough assessment of current crypto asset holdings and accounting practices, including a complete inventory of digital assets and evaluation of recording methods.

Essential implementation steps include:

  • Documentation and Policy Development: Create comprehensive written policies outlining standard application, including procedures for recognition, measurement, and disclosure requirements.
  • System and Process Updates: Review and modify existing accounting systems to accommodate new requirements, including updates to charts of accounts and control implementations.
  • Training and Education: Develop comprehensive training programs for staff and stakeholders covering technical requirements and practical applications.

The implementation timeline is crucial. With ASU 2025-06 being issued on September 18, 2025[2], organizations should follow a structured approach:

  1. Assessment Phase (2-3 months)
  2. Development Phase (3-4 months)
  3. Testing Phase (2-3 months)
  4. Go-Live Phase (1-2 months)

Practical Challenges and Solutions

Organizations typically encounter several implementation challenges. Here are practical solutions to address them:

  1. Technical Complexity: Create detailed process flows and bring in technical experts during initial implementation.
  2. System Limitations: Invest in specialized software or develop custom modules within existing systems.
  3. Staff Expertise: Implement comprehensive training programs covering cryptocurrency concepts and specific FASB requirements.
  4. Valuation Challenges: Establish clear valuation hierarchies and documentation procedures.

Risk Management Considerations

Implementing FASB ASU standards for crypto assets requires careful attention to risk management:

  1. Operational Risk: As noted in recent guidance, entities need to assess whether their software has ‘technological innovations or novel, unique, or unproven functions or features’[3]. This applies to both assets and accounting systems.
  2. Compliance Risk: Since the FASB Accounting Standards Codification is the single official source of authoritative US GAAP[1], organizations must:
    • Monitor standard updates regularly
    • Document compliance procedures
    • Conduct periodic reviews
    • Maintain auditor communication
  3. Market Risk: Develop specific approaches for:
    • Handling market fluctuations
    • Establishing revaluation thresholds
    • Creating impairment testing procedures
    • Documenting value sources

Remember that risk management requires ongoing review and updates as standards and the crypto asset landscape continue to develop.

References

  1. FASB Accounting Standards
  2. FASB Issues Standard That Makes Targeted Improvements to Internal-Use Software Guidance
  3. FASB ASU Amends Software Costs Guidance – Deloitte
  4. ASU Updates for Public and Non-Public Companies – CohnReznick

Interested in TRES?

Schedule a demo with one of our expert team members to show how we can streamline your financial operations and make Web3 finance the easiest part of your workflow.
Schedule a Demo