Accounting standards
New rules for capitalizing software you build (ASU 2025-06)
November 18, 2026 · 10 min read

Quick answer
ASU 2025-06 replaces the old project-stage model for software you build for your own use (including the platform behind a SaaS product). You start capitalizing costs once management has authorized and committed to funding the project and it's probable the project will be completed and used as intended. If a key feature is novel or unproven, costs stay expensed until coding and testing resolve that uncertainty. It's effective for fiscal years beginning after December 15, 2027 for every company, so calendar 2028 for most, and you can adopt early.
Your developers work in two-week sprints: ship a feature, learn something, change the plan, ship again. The accounting rules for software you build for your own use were written for waterfall projects with a preliminary stage, an application development stage and a post-implementation stage. Fitting an agile team into that has been guesswork for years.
In September 2025 the FASB issued ASU 2025-06 to fix that. If you run a SaaS company, build your own internal tools, or pay developers to build a customer portal, it changes when you start putting development costs on the balance sheet instead of the profit and loss.
Sept 2025
When the FASB issued ASU 2025-06
FY 2028
Effective for fiscal years beginning after December 15, 2027, public and private alike
3 options
Transition: prospective, prospective with a catch-up for projects in progress, or retrospective
What software does this cover?
The rules sit in ASC 350-40, internal-use software. That's software you develop or buy for your own use and don't plan to sell or license to customers. It includes more than you might expect:
- the platform behind a SaaS product, where customers log in but never receive the software
- internal tools: a custom CRM, pricing engine or data warehouse
- your website and customer portal (website guidance used to sit in its own subtopic, ASC 350-50, and has now moved into ASC 350-40)
Software you sell, license or otherwise market to customers is under a different subtopic (ASC 985-20), and ASU 2025-06 doesn't change it.
What changed in ASU 2025-06?
The big change: the project stages are gone. Capitalization now starts when both of these are true:
- Management, with the right authority, has authorized and committed to funding the project.
- It's probable the project will be completed and the software will be used to perform its intended function. That's the "probable-to-complete" threshold. "Probable" has its usual GAAP meaning: likely to occur.
There's a built-in brake. If a project has significant development uncertainty, it isn't probable of completion until that uncertainty is resolved. Significant development uncertainty exists when either:
- the software, or its core features or functions, are novel, unique or unproven, or
- the significant performance requirements haven't been identified yet, or are still being substantially revised.
Novel or unproven features are resolved through coding and testing that show the software can do what it needs to do. Until then, development costs go straight to expense.
Project stages
Old model
- Preliminary project stage: expense
- Application development stage: capitalize
- Post-implementation stage: expense
- You had to decide which stage an agile sprint belonged to
- Website costs had separate guidance
Probable to complete
ASU 2025-06
- Capitalize once the project is authorized, funded and probable to complete
- Novel or unproven features: expense until coding and testing resolve the uncertainty
- Stop capitalizing when the software is substantially complete and ready for use
- No need to map sprints to stages
- Website costs follow the same rules
What didn't change?
Quite a lot, which is good news for your close process:
- Which costs can be capitalized. Developer payroll and contractor costs directly on the build still qualify. Data conversion and migration, training, general and administrative costs, overhead and maintenance are still expensed as incurred.
- When capitalization stops. When the software is substantially complete and ready for its intended use.
- Amortization and impairment. You still amortize capitalized costs over the software's useful life once it's in use.
- Disclosures. The ASU clarifies that capitalized internal-use software follows the property, plant and equipment disclosures in ASC 360-10, whether you present it as an intangible or as PP&E.
The FASB had proposed a separate cash flow statement line for capitalized software costs. The final ASU dropped that.
When does it take effect?
Sept 2025
ASU issued
The FASB issued ASU 2025-06.
Now
Early adoption open
You can adopt in any annual or interim period whose statements haven't been issued or made available for issuance. Adopting in an interim period means applying it from the start of that fiscal year.
Jan 1, 2028
Required
Fiscal years beginning after December 15, 2027, including interim periods. Same date for private and public companies.
Dec 31, 2028
First required year-end
The first annual statements prepared under the new rules for a calendar-year company that didn't adopt early.
You choose one of three transition approaches:
- Prospective: apply the new rules only to costs incurred after adoption, on new and existing projects.
- Prospective with a cumulative-effect adjustment: same, but also adjust costs already capitalized on projects still in progress.
- Retrospective: restate the prior periods presented.
Prospective is usually simplest. With a big in-process project, ask your auditor about the middle option.
A worked example: a small SaaS company's 2028 development spend
Say you run a 25-person SaaS company with a December year-end. You adopt ASU 2025-06 on January 1, 2028, prospectively. During 2028 your team works on two projects.
Project A: a customer reporting dashboard. Standard technology your developers have used before. In January the team spends $15,000 sketching options before the leadership team signs off on the budget in February. From then until it goes live on October 1, development costs are $270,000. Another $15,000 goes on migrating customer data and training your support team.
Project B: an AI cash forecasting feature. Nobody's sure the forecasts will be accurate enough to ship. The project is approved and funded in January, but the team spends $150,000 on prototypes and testing until, in August, testing shows the model meets the accuracy target. From then to substantial completion on December 31, development costs are $90,000.
| Cost | Project A | Project B | Treatment under ASU 2025-06 |
|---|---|---|---|
| Before management authorized and funded the project | $15,000 | n/a | Expense |
| While a core feature was unproven | n/a | $150,000 | Expense (significant development uncertainty) |
| Development once probable to complete | $270,000 | $90,000 | Capitalize |
| Data migration and training | $15,000 | n/a | Expense |
| Total spent | $300,000 | $240,000 | |
| Capitalized | $270,000 | $90,000 | $360,000 in total |
2028 development costs: capitalized vs expensed
Two projects at a hypothetical 25-person SaaS company
- Capitalized
- Expensed
Hypothetical example. Project A: $270,000 + $30,000 = $300,000. Project B: $90,000 + $150,000 = $240,000.
Show the numbers
| Capitalized | Expensed | |
|---|---|---|
| Project A: reporting dashboard | $270,000 | $30,000 |
| Project B: AI forecasting | $90,000 | $150,000 |
Project A goes into use on October 1 and you amortize it over three years: $270,000 ÷ 36 months = $7,500 a month, or $22,500 for October to December. Project B starts amortizing in 2029.
So of $540,000 spent on development in 2028, here's what reaches your profit and loss:
From cash spent to 2028 expense
Development spending on both projects
- Adds to expense
- Moves to balance sheet
- Total
Hypothetical example. 540,000 − 270,000 − 90,000 + 22,500 = 202,500.
Show the numbers
| Spent on development | $540,000 |
| Project A capitalized | −$270,000 |
| Project B capitalized | −$90,000 |
| Project A amortization | +$22,500 |
| 2028 P&L expense | $202,500 |
The interesting one is Project B. Under the old stage model, a team that had approved and funded the project could well have argued it was in the application development stage from January and capitalized most of the $240,000. Under ASU 2025-06, the $150,000 spent proving the AI actually works stays on the P&L. The new rules ask a more honest question: did you know this would work?
How does this interact with taxes?
Book and tax are separate, and they've drifted apart. Under Section 174A, added by the 2025 tax law, domestic research and experimental costs paid or incurred in tax years beginning after December 31, 2024 can be deducted currently for federal income tax, with an option to capitalize and amortize them over at least 60 months instead. Software development costs count as research and experimental costs for this purpose. Foreign research is treated differently.
So in the example, a large part of the $540,000 may be deductible on the 2028 tax return even though only $202,500 hits the book P&L. That gap is a normal book-tax difference, not an error, and it usually means tracking deferred taxes. Which costs qualify, and whether the R&D credit applies too, are questions for your CPA.
What should you do before year-end?
Even though the rules aren't required until 2028, a few things are worth doing now:
Decide
- Early adopt or wait until 2028? Ask your auditor which is simpler for your projects
- Pick a transition approach (prospective is usually simplest)
- Agree a capitalization threshold and useful lives with your auditor
Track
- Record when each project is formally approved and funded (board minutes, budget sign-off)
- Track developer time by project in your time or ticketing system
- Flag features that are novel or unproven and note when testing resolves them
- Separate data migration, training and maintenance time
Report
- Set up a fixed asset or software asset register with in-service dates
- Book monthly amortization once each project goes live
- Brief your CPA on book vs tax treatment
Common mistakes
No evidence of authorization. "We decided in a Slack thread" isn't great support. A budget approval, a board minute or a signed roadmap gives your auditor a date to work from.
Capitalizing everything engineering touches. Bug fixes, maintenance, training and data migration are still expenses. So is time spent on things that never get built.
Treating every new feature as "novel". Significant development uncertainty is about core features or functions that are genuinely unproven, not normal engineering risk. Building a dashboard in a framework you use daily isn't novel. Overusing the label pushes costs onto the P&L that probably belong on the balance sheet.
Mixing up book and tax. Section 174A deductions don't tell you what to capitalize for GAAP, and GAAP capitalization doesn't decide your tax deduction.
When to get help
If you only have one or two developers working on maintenance, the amounts may be small enough that your auditor or reviewer is comfortable expensing them. Ask. Once you're building real product, especially as a SaaS company heading toward an audit or a raise, it pays to set up the tracking and the policy properly.
Fintrix Consulting's accounting service can set up the capitalization policy, the project tracking and the monthly amortization, and prepare the support your auditor will ask for. If you want to talk through your projects, book a call. For how capitalized costs show up on your statements, see how to read a balance sheet, and for the revenue side of a SaaS business, ASC 606 in plain English.
Frequently asked questions
Is SaaS software internal-use software?
Usually, yes. If customers access your software through a subscription and never take possession of it, the development costs generally fall under the internal-use software rules in ASC 350-40. Software you sell or license to customers falls under ASC 985-20 instead.
Do private companies get extra time?
No. ASU 2025-06 is effective for all entities for fiscal years beginning after December 15, 2027. The FASB chose one date for public and private companies.
Can we adopt it for our 2026 financial statements?
Early adoption is allowed for statements that haven't been issued or made available for issuance yet. Talk to your auditor first, especially about which transition approach to use.
Do I have to restate costs I already capitalized?
Not if you use the prospective approach, which applies the new rules only to costs after adoption. The other two approaches adjust in-progress projects or prior periods.
Are website costs covered?
Yes. Website development guidance moved from ASC 350-50 into ASC 350-40, so websites follow the same probable-to-complete rules.
The bottom line
ASU 2025-06 swaps a stage-based model nobody's developers actually follow for a simpler question: is the project funded, and is it probable you'll finish it? Proven work gets capitalized sooner, while experiments stay on the P&L until testing proves they work. You have until 2028, but the evidence your auditor will want, approvals and time by project, is easiest to collect from today. Decide on early adoption and transition with your auditor, and keep the tax side in a separate conversation with your CPA.
Sources
- Improvements to accounting for internal-use software (Grant Thornton)
- FASB issues final ASU on software cost accounting (KPMG Financial Reporting View)
- Internal-use software costs accounting guidance (EisnerAmper)
- ASU 2025-06: Targeted improvements to the accounting for internal-use software (CFGI)
- FASB unveils new rules streamlining internal software accounting (Thomson Reuters)
- Rev. Proc. 2025-28 (IRS)
This article is general information, not advice for your situation. Rules change and details matter, so talk to us or your CPA before acting on it.
More articles
- CECL isn't just for banks: the bad-debt allowance for your receivables
November 18, 2026
- Bitcoin on your balance sheet: the fair value rules (ASU 2023-08)
November 18, 2026
- New GAAP for government grants received by businesses (ASU 2025-10)
November 18, 2026
Have a question about this article?
Ask us. A real person will reply by email within one business day. Your question isn’t published.
Ready for books you can trust?
Book a free 30-minute consultation. We'll review where your finances stand today and show you exactly how we'd help.