---
title: "What ASU 2025-06 Means for SaaS Companies and Their Investors"
url: "https://www.lbmc.com/blog/asu-2025-06-software-capitalization/"
description: "ASU 2025-06 changes software capitalization for SaaS companies. Understand the impact on earnings, investor due diligence and adoption planning."
site: "LBMC"
type: "Post"
published: "2026-11-17"
updated: "2026-11-17"
author: "LBMC"
categories: ["Audit and Assurance", "Technology and SaaS"]
---

# What ASU 2025-06 Means for SaaS Companies and Their Investors

For years, the accounting rules for internal-use software assumed that development happens in neat, sequential stages. Anyone who has run a sprint knows that isn’t how software gets built. [ASU 2025-06](https://www.fasb.org/page/PageContent?pageId=/projects/recently-completed-projects/accounting-for-and-disclosure-of-software-costs.html), issued by the Financial Accounting Standards Board (FASB) in September 2025, replaces that stage-based model with a judgment-driven threshold that fits agile development far better.

For [SaaS and technology companies](https://www.lbmc.com/industries/technology/), and for the [private equity firms](https://www.lbmc.com/industries/private-equity/) that invest in them, the change affects when development costs land on the balance sheet versus the income statement. That, in turn, can reach reported earnings, lender conversations, and valuation. The standard applies to annual periods beginning after December 15, 2027, so calendar-year companies adopt on January 1, 2028, with early adoption permitted. That sounds distant, but transition decisions, documentation, and deal timelines mean the preparation starts now.

## What Is Changing Under ASU 2025-06?

Under legacy guidance in ASC 350-40, capitalization of internal-use software costs began once the preliminary project stage was complete. The ASU removes every reference to the software development stages. In their place, capitalization begins when two conditions are met:

- Management, with the relevant authority, has authorized and committed to funding the project.
- It is probable that the project will be completed and the software will be used to perform its intended function (referred to as the “probable-to-complete recognition threshold”).

The second condition is where the judgment sits. The threshold is not met when significant development uncertainty exists, and the amendment points to two signals:

- The software depends on novel, unique, or unproven technology, and that uncertainty has not been resolved through coding and testing.
- The significant performance requirements have not been identified, or they keep being substantially revised.

SaaS providers deserve a closer look. FASB expects capitalization to stay largely the same for most types of software. In its basis for conclusions, however, the Board indicated that it expects more costs to be expensed for software sold as part of a cloud computing arrangement, because the signals of significant development uncertainty may appear more often in that kind of development. In practice, capitalization for SaaS products may begin later than it does today.

Two smaller changes round out the amendment. Website development guidance moves into ASC 350-40, and capitalized internal-use software now follows the property, plant, and equipment disclosure requirements, regardless of how it is presented on the balance sheet.

## Three Questions Technology Companies and Investors Should Ask

Because the ASU replaces bright lines with judgment, most of the work is operational. These three questions are a good starting point for management teams, boards, and investors.

### 1. How Does Our Development Process Map to the New Threshold, and Can We Support It?

The ASU does not define a “software project,” so the unit of account is a judgment call that needs to be documented.

- Is a project a whole application, a major feature, or a set of APIs?
- Who concludes that completion is probable, and when?
- Are novel features, such as AI or machine learning components, tracked separately from routine ones?

The evidence for these conclusions will live in project management tools, backlogs, sprint documentation, test results, and governance approvals, not in the general ledger. Auditors will shift from asking which stage a project is in to evaluating whether management’s judgment is reasonable and supported.

Software capitalization is one of several [SaaS accounting and financial reporting challenges](https://www.lbmc.com/blog/saas-company-accounting-and-finance-overcoming-challenges/) that can become more demanding as a company grows.

### 2. How Will Adoption Affect Earnings, EBITDA, and Lender Conversations, and Which Transition Method Fits?

- Will capitalization start later for our SaaS products, and by how much?
- How would expensing more development cost affect EBITDA, covenant calculations, and valuation models?
- Which transition approach makes the most sense for us?

The ASU offers three approaches. A prospective approach applies the new rules to costs incurred from the start of the adoption period, including in-process projects, and leaves previously capitalized amounts on the balance sheet, subject to impairment review. A modified approach derecognizes in-process projects that no longer qualify through an adjustment to opening retained earnings. A retrospective approach recasts comparative periods. Each trades simplicity against comparability, and each affects the balance sheet differently.

Early adoption is also permitted. A company can adopt in any interim or annual period for which financial statements have not yet been issued or made available for issuance. A company that adopts in an interim period must apply the ASU as of the beginning of that annual period. For example, a calendar-year company that has not yet issued its 2026 financial statements could adopt as of January 1, 2026, while the mandatory date remains January 1, 2028.

For private equity investors, this matters well beyond the financial statements. Portfolio companies may adopt at different times, since early adoption is permitted, and by different methods. During [financial due diligence](https://www.lbmc.com/services/advisory/transaction-advisory/), teams should understand how a target’s capitalization policy affects adjusted EBITDA before they price a deal, and lenders may need a heads-up before covenant calculations move.

### 3. Are Our Systems and Controls Ready to Produce Audit-Ready Support?

- Do we have a written policy that defines what counts as a software project, and is each capitalization conclusion documented when it is made, with the date, approver, and reasoning?
- Can we pull the evidence for each project on request, such as approvals, funded budgets, requirements documents, change logs, and test results, and tie it to engineering hours and third-party costs incurred before and after the threshold?
- Is there a recurring reassessment, such as a quarterly close step, of whether each project is still probable to complete, with a clear trigger to stop capitalizing and test for impairment?

Costs incurred before the threshold is met cannot be capitalized retroactively, so the timing of that conclusion matters. A dry run on active projects before the effective date will show what the numbers look like and where the evidence gaps are. Companies that build this documentation and these controls before adoption will find the audit conversation far easier.

## Start Preparing Before the Effective Date

ASU 2025-06 may simplify some of the debate around when to start capitalizing, but it puts more weight on management judgment, governance, and documentation. A practical first step is to inventory current and planned software projects and note how each is tracked today. From there, draft a capitalization policy, estimate the impact on earnings and covenants, and choose a transition approach well before the effective date.

Have questions about how ASU 2025-06 applies to your software projects? [Talk with LBMC’s Audit and Assurance team](https://www.lbmc.com/services/audit-assurance/#contact) about your capitalization policy, supporting documentation and adoption plans.

*Content provided by LBMC Audit and Assurance professional, [Chance Bouldin](https://www.linkedin.com/in/chancellorbouldin/).*

*LBMC insights are provided as an informational and educational service for clients and friends of the firm. The communication is high-level and should not be considered as accounting, legal, or tax advice to take any specific action. Individuals should consult with their personal accounting, tax, or legal advisors before making any accounting, tax, or legal-related decisions. In addition, the information and data presented are based on sources believed to be reliable, but we do not guarantee their accuracy or completeness. The information is current as of the date indicated and is subject to change without notice.*
