FASB modernizes internal-use software accounting with ASU 2025-6

Kim Garcia
Ian Shapiro
November 7, 2025

Abbreviations are defined at the end.

On September 18, 2025, the FASB issued ASU 2025-06, Intangibles—Goodwill and Other—Internal-Use Software (Subtopic 350-40): Targeted Improvements to the Accounting for Internal-Use Software, marking a significant modernization of software cost accounting under U.S. GAAP.

This new guidance replaces the decades-old, stage-based framework with a principles-based approach that better reflects how software is developed today—through iterative and agile methods rather than the traditional linear “waterfall” model. The ASU is designed to enhance consistency, reduce complexity, and align accounting with current technology and business realities.  The new standard does not change the types of costs that are capitalized once the threshold for capitalization is met or when capitalization ceases.

A shift away from project stages

Under the previous model, entities classified internal-use software development into three project stages—preliminary, application development, and post-implementation—with capitalization typically beginning in the second stage. However, that structure often failed to fit modern software development, which is inherently non-sequential and involves continual refinement.

ASU 2025-06 eliminates all references to project stages, replacing them with a more flexible “probable-to-complete recognition threshold”. According to the standard, capitalization of internal-use software costs now begins only when:

  1. Management has authorized and committed funding for the software project; and
  1. It is probable that the project will be completed and that the software will perform its intended function (the “probable-to-complete recognition threshold”).

By removing rigid stage-based terminology, the new guidance accommodates various development approaches — whether agile, hybrid, or traditional — and allows for a more uniform interpretation across industries.

Clarifying the probable-to-complete recognition threshold

The probable-to-complete concept is the cornerstone of the updated standard.  The standard defines “probable” as likely to occur. To meet this threshold, entities must first resolve any significant development uncertainty, defined as either:

  • The presence of novel, unique, or unproven technological functions or features that have not yet been validated through coding and testing, or
  • Significant performance requirements that have not been identified or are still undergoing substantial revision.

Once these uncertainties are resolved, eligible costs can be capitalized. This approach increases reliance on professional judgment but facilitates a consistent link between cost capitalization and the technical feasibility of the software being developed.

The FASB also noted that for cloud computing or SaaS-related projects, the new rules may reduce capitalization since uncertainty often remains later in development, making these costs more likely to be expensed as incurred.

Expanded disclosure requirements

In addition to redefining capitalization thresholds, ASU 2025-06 introduces new disclosure requirements to enhance transparency. Entities must now apply the disclosure framework of ASC 360-10 (Property, Plant, and Equipment) to all internal-use software costs, regardless of whether they are presented as intangible assets or within PP&E.

Elimination of website development guidance

The update also supersedes ASC 350-50, which previously provided separate guidance for website development costs. That content is now incorporated into ASC 350-40, along with illustrative examples. The change is not expected to significantly alter practice, as website development is already conceptually similar to software application development.

This consolidation simplifies the Codification in that all internal-use software, including websites, now follows a single accounting model.

Internal controls implications

The move to a judgment-based approach increases the importance of internal controls around capitalization assessments. Management must establish and document:

  • Approval and funding commitments for software projects;
  • The evaluation and resolution of significant development uncertainties; and
  • The timing of when capitalization begins.

Entities may need to update policies, processes, and documentation controls to align with the new probable-to-complete framework. Clear evidence supporting these judgments will be critical for auditability and compliance.

Effective date and transition options

The new standard is effective for fiscal years beginning after December 15, 2027, including interim periods within those years. Early adoption is permitted for any interim or annual financial statements not yet issued (or made available for issuance), provided the standard is adopted as of the beginning of the fiscal year.

Entities have three transition options:

  1. Prospective – Apply the new guidance only to software costs incurred after adoption, including for projects already in process.
  1. Retrospective – Restate prior periods and record a cumulative effect adjustment to the opening balance of retained earnings.
  1. Modified prospective – Apply prospectively to new and in-process projects, but derecognize any previously capitalized in-process costs that no longer qualify, adjusting retained earnings at the date of adoption.

Each method requires disclosure of the transition approach and the impact on financial statements under ASC 250.

Conclusion

ASU 2025-06 represents one of the most significant updates to internal-use software cost accounting in nearly three decades. By replacing the outdated stage-based model with a modern, principle-driven framework, the FASB has aligned accounting standards with the realities of today’s fast-paced, agile software development environment.

While the update provides greater flexibility, it also demands greater judgment, transparency, and internal control discipline. Entities should begin evaluating their capitalization policies, internal documentation, and software development processes well before the 2027 effective date to ensure a seamless transition.

Kim Garcia
Partner, Advisory & IT Risk Leader
kgarcia@socorropartners.com
+1.954.729.5680
Ian Shapiro
Partner, Assurance
ishapiro@socorropartners.com
+1.561.289.0455

Glossary of terms

View all terms →

Abbreviation

Full name

ASU
Accounting Standards Update
FASB
Financial Accounting Standards Board
GAAP
Generally accepted accounting principles
PP&E
Property, Plant, and Equipment
Our latest content,
straight to your inbox.
Read about our privacy policy
Thank you.
Oops! Something went wrong while submitting the form.