ASU 2025-06 and your IT cost model: what changes before you adopt
In brief
ASU 2025-06 drops the stage model for internal-use software. What it changes for IT finance: when capitalization starts, the evidence, and the cost model.
Steve Elliott · · 4 min read
On this page
ASU 2025-06 removes the project stages from the accounting for internal-use software. Capitalization still requires that management has authorized and committed to funding the project and that completion is probable. What's new is that the "preliminary project stage" test is gone, replaced by a test for significant development uncertainty. The types of cost you can capitalize don't change. The standard is effective for annual periods beginning after December 15, 2027.
For IT finance, that shifts the question from "which phase is this work in?" to "what evidence shows funding was committed and the uncertainty was resolved?" Much of that evidence may already exist in delivery and portfolio records. This post covers what changes for the cost model, time capture and planning. It is not accounting advice; confirm how the standard applies to you with your accounting advisers and auditor.
What changed, in one table
| Before ASU 2025-06 | After ASU 2025-06 | |
|---|---|---|
| When capitalization starts | Preliminary project stage complete, funding authorized and committed, and completion probable | Funding authorized and committed, and completion probable, with no significant development uncertainty |
| What holds it back | Being in the preliminary or post-implementation stage | Significant development uncertainty |
| Fits | Sequential, waterfall-style projects | Any development method, including agile |
| Website development | Separate guidance (ASC 350-50) | Folded into ASC 350-40 |
| Disclosure | Varied with presentation (intangibles or PP&E) | PP&E disclosures (ASC 360-10) for all capitalized internal-use software |
Significant development uncertainty exists in two cases:
- The software has technological innovations or novel, unique or unproven functions or features, and that uncertainty hasn't been resolved through coding and testing.
- The significant performance requirements haven't been identified, or they continue to be substantially revised.
The effective date is the same for public and private companies. Early adoption is permitted in any period whose financial statements haven't been issued; adopting in an interim period applies from the start of that fiscal year.
Will you capitalize more or less?
It depends on how novel the work is. FASB says it expects that capitalization of internal-use software costs "generally will not change significantly for most types of software." PKF O'Connor Davies says more costs may be expensed rather than capitalized. FASB also expects capitalization could decrease for software developed to be sold as part of a cloud computing arrangement.
The difference comes down to the uncertainty test. Work close to a familiar internal build is less likely to have significant development uncertainty, so timing may barely move. Work with unproven functions or features may have to wait until coding and testing resolve them, which keeps more early development in opex. If your portfolio is shifting toward the second kind, raise it with your controller before you set next year's capex plan.
Where can the evidence for each condition come from?
This is where IT finance does the work. Each condition can draw on records that delivery, portfolio and architecture teams often keep:
| Condition or factor | Records that can show it | Typically held by |
|---|---|---|
| Funding authorized and committed | Portfolio or investment approval, funding decision, signed development contract | PMO, portfolio office, finance |
| Completion probable | Approved scope and plan, staffing commitment, delivery status | Product or project leads |
| Requirements identified and stable | Requirements baseline, change history, backlog of significant requirements | Product owners, architects |
| Novel functions or features resolved | Prototype or spike results, test results, release records | Engineering |
These are examples, not a list of what's sufficient. Your controller and auditor decide that.
The point is traceability. When the auditor asks why capitalization started in March, the answer should link a funding decision and a resolved uncertainty to dated records, not to a phase gate on a project plan. Crowe suggests keeping contemporaneous documentation of project approvals, funding and development road maps.
What changes in the IT cost model?
The capex and opex split stops following project phase and starts following a judgment made for each project or product. Three things follow.
- The start of capitalization needs a date and an owner. The model has to record when each initiative met the threshold. IT supplies the evidence and a proposed date; finance makes the accounting call.
- Product teams no longer sort work into phases. The stage test fit iterative delivery poorly. Without it, those teams don't have to classify work by phase, but they do need evidence of when each capability's uncertainty was resolved.
- Existing balances depend on the transition method. Under the prospective method, existing capitalized costs stay on the balance sheet and are tested for impairment. Under the modified method, previously capitalized costs on in-process projects that don't meet the new threshold are written off against opening retained earnings. The retrospective method recasts prior periods. Size which projects each method would touch before you decide.
What changes in time capture?
Policies built on the stage model typically tracked capitalizable time by phase. Under the new test, the relevant fact is when uncertainty was resolved for the work in question, and that comes from the delivery record rather than the calendar.
However you capture labor today, the link between delivery records and the capitalization record needs to hold up. How you measure the labor itself remains a policy decision for finance.
What changes in planning?
The funding decision was always a condition for capitalization. With the stage test gone, it carries more of the weight, alongside the uncertainty judgment. That makes the date and documentation of a portfolio approval matter to the controller, not just the PMO.
If more early-stage spend moves into opex, EBITDA moves with it. PKF O'Connor Davies recommends modeling the impact early and talking to lenders where covenants are tied to EBITDA. For IT finance, that means running next year's plan both ways for any initiative where significant development uncertainty is likely.
What to do before your adoption year
- Inventory in-process and planned internal-use software projects, and flag those with unproven functions or unsettled requirements.
- Agree with the controller who judges when the threshold is met and where that decision is recorded.
- Map funding approvals, requirements baselines and test records to the capitalization record, using the table above.
- Size the effect of each transition method, choose one, and review the choice with your auditor.
- Update the capitalization policy and the controls that review it.
- Run one product line through the new test as a dry run.
Sources
- FASB, ASU 2025-06, Targeted Improvements to the Accounting for Internal-Use Software, September 18, 2025
- Crowe, FASB Revises Internal-Use Software Cost Guidance, September 19, 2025
- Crowe, ASU 2025-06: Information for nonsoftware companies
- Deloitte, FASB Amends Guidance on the Accounting for and Disclosure of Software Costs, September 18, 2025
- EY, FASB modernizes guidance on accounting for internal-use software, September 19, 2025
- BDO, New ASU on Internal-Use Software Costs Guidance
- RSM, FASB modernizes the accounting for internal-use software costs, October 13, 2025
- PKF O'Connor Davies, FASB's Internal-Use Software Guidance: What Companies Need to Know, April 9, 2026
- EisnerAmper, Internal-use software costs accounting guidance
Frequently asked questions
When is ASU 2025-06 effective?
ASU 2025-06 is effective for all entities for annual reporting periods beginning after December 15, 2027, including interim periods within those years. Early adoption is permitted in any period whose financial statements haven't been issued. A company that adopts in an interim period applies the standard from the beginning of that fiscal year.
Does ASU 2025-06 change which software costs can be capitalized?
No. The types of costs eligible for capitalization stay the same. The standard changes when capitalization begins by removing the project stages. Capitalization starts once funding is authorized and committed and completion is probable, provided there is no significant development uncertainty about novel functions or unsettled requirements.
How does ASU 2025-06 affect agile development?
FASB removed the stage model partly because it fit iterative methods such as agile poorly. The new test applies regardless of development method. Teams no longer sort work into phases, but they need records showing when funding was committed and when significant development uncertainty was resolved through coding and testing.
Does ASU 2025-06 change accounting for SaaS implementation costs?
For customers, the model for implementation costs in hosting arrangements isn't being overhauled, according to Crowe. Because the stage test is removed, teams may need to reassess when implementation activities meet the new threshold. Separately, FASB expects capitalization could decrease for software developed to be sold through a cloud arrangement.
Steve Elliott
Published November 22, 2026
More on TBM & IT Financial Management
Cost pools, towers, showback, unit cost.
Keep reading
Project vs product funding: what changes in your IT cost model
Moving from project to product funding changes the cost object, allocation, capex evidence, budget cadence and how success is measured. What to change.
From an annual cost model to a living one: what changes and what stays hard
Usage-based cloud and AI spend outruns a TBM model rebuilt each year. What a living cost model means, what stays hard, and where AI agents help and don't.
Run, grow, transform is a budgeting convention, not a cost model
Run, grow, transform is a useful board shorthand and a weak cost model. Where the split breaks down, what the federal DME and O&M split adds, and what to do.
IT cost transparency in financial services: why resilience rules change the model
Banks, payment firms and insurers must map technology and suppliers to critical services. Why that changes IT cost transparency, and how a TBM model helps.