Articles

ASC 350-40 software capitalization rules after ASU 2025-06

How ASU 2025-06 removes sequential project stages, introduces significant development uncertainty, folds in website costs, and changes capitalization, amortization, and transition.

Under ASU 2025-06 (issued September 18, 2025, effective for annual periods beginning after December 15, 2027, with early adoption permitted), ASC 350-40 eliminates the legacy three-stage waterfall model and requires capitalizing internal-use software only when management commits funding and completion is probable with no unresolved significant development uncertainty. On Kestrelway Systems' flagship platform, that single shift reduces capitalization from $1,767,200 to $1,526,000, a $241,200 swing in earnings and balance sheet assets.

Worked in full in The Software Costs Accounting Handbook by Julian R. Sterling, with every figure reproduced in live Excel workbooks.Get the DRM-free PDF, $19.99 →

Why FASB replaced the three-stage model of ASC 350-40

For nearly three decades, US GAAP preparers accounted for internal-use software under ASC 350-40 by forcing every project into three sequential boxes: the preliminary project stage (expensed), the application development stage (capitalized), and the post-implementation-operation stage (expensed). That waterfall structure worked when companies wrote rigid multi-year specifications before typing code. It broke down completely in agile software organizations that release code every two weeks, run discovery and coding in parallel sprints, and iterate requirements continuously.

On September 18, 2025, as read in November 2026, FASB issued Accounting Standards Update No. 2025-06, Targeted Improvements to the Accounting for Internal-Use Software. ASU 2025-06 removes all references to sequential project stages from ASC 350-40. It also supersedes ASC 350-50 (Website Development Costs) and folds website application development directly into ASC 350-40 so internal-use applications, hosted SaaS platforms, and customer-facing web portals follow a single recognition threshold. The standard takes effect for all entities for annual reporting periods beginning after December 15, 2027 (calendar year 2028) and interim periods within those years, with early adoption permitted as of the beginning of an annual reporting period.

The two capitalization gates under ASU 2025-06

Under amended ASC 350-40-25, capitalization starts when two conditions are met simultaneously. First, management with the relevant authority must authorize and commit to funding the software project. Second, it must be probable that the project will be completed and the software will be used to perform its intended function. To evaluate that probable-to-complete threshold, preparers must explicitly test whether significant development uncertainty exists.

Significant development uncertainty prevents capitalization whenever either of two indicators is present: the software relies on novel, unique, unproven functions or technological innovations whose uncertainties have not yet been resolved through coding and testing, or the software's significant performance requirements have not been identified or continue to be substantially revised. In practice, this rule changes timing sharply for iterative product teams: coding hours spent exploring unproven algorithms or unstable feature scopes must be expensed until engineering testing resolves the uncertainty.

Worked example 1: Legacy ASC 350-40 vs. ASU 2025-06 on an agile build

Consider Kestrelway Systems, Inc., a fictional calendar-year US GAAP technology company whose full case runs through The Software Costs Accounting Handbook. In fiscal 2026, Kestrelway builds Dispatch Core 4.0, a hosted SaaS platform sold as a service (without a software license), placing it inside ASC 350-40. During Q1, engineering spends 3,200 hours on architecture scoping and proof of concept ($286,000 payroll plus $24,000 external consultants = $310,000), expensed under both frameworks. On April 1, 2026, management commits full funding for Q2 and Q3.

In Q2, the core billing and dispatch build has settled requirements (5,800 hours, $514,000 payroll, $180,000 contractors, and $36,000 for custom data-conversion software = $730,000 capitalized under both frameworks). Meanwhile, a separate Predictive Route Engine sub-module runs across Sprints 7 to 10 (2,300 hours, $211,000 payroll plus $25,000 specialist fees = $236,000) with unresolved performance requirements until prototype testing succeeds at the end of Sprint 10. Under Legacy ASC 350-40, because the overall project already entered application development, Kestrelway capitalized $236,000. Under ASU 2025-06, significant development uncertainty forces that $236,000 straight to operating expense, which also reduces ASC 835-20 capitalized interest in Q3 from $31,200 to $26,000 at Kestrelway's 6.5% borrowing rate.

Dispatch Core 4.0 ComponentLegacy ASC 350-40ASU 2025-06Impact
Q1 Preliminary scoping and proof of concept$0$0Expensed under both
Q2 Core billing and dispatch (certain)$730,000$730,000Capitalized under both
Q2 Predictive Route Engine (Sprints 7 to 10)$236,000$0Expensed under ASU 2025-06
Q3 Full build, testing, and capitalized interest$801,200$796,000Lower interest base
Total capitalized at Oct 1, 2026 go-live$1,767,200$1,526,000Difference: $241,200

When Dispatch Core 4.0 goes live on October 1, 2026 over a 36-month straight-line life, Q4 2026 amortization (three months) is $147,267 under Legacy versus $127,167 under ASU 2025-06. Across the company, adopting ASU 2025-06 reduces FY2026 Adjusted EBITDA from $4,860,000 to $4,624,000 and moves leverage from 2.47x to 2.60x against a 3.50x bank covenant (compared with 5.11x if zero software were capitalized). For a deeper look at lender adjustments, see how capitalising software development lifts EBITDA and covenant headroom.

Eligible vs. ineligible costs: payroll, stock-based compensation, and overhead

ASU 2025-06 changes when capitalization begins, not which cost types qualify under ASC 350-40-30-1. Three categories remain eligible once the threshold is cleared: (1) external direct costs of materials and services (such as third-party coding contractors), (2) payroll and payroll-related costs for employees directly associated with the project, including benefits and allocable stock-based compensation under ASC 718, and (3) qualifying interest under ASC 835-20.

Three cost categories remain strictly expensed: general and administrative overhead (ASC 350-40-30-3), training costs (ASC 350-40-25-4), and manual data conversion or cleansing (ASC 350-40-25-5, except software built specifically to convert legacy data). In Kestrelway's case, $420,000 of product management, executive oversight, and corporate G&A overhead stays completely outside the hourly rates, and Q2 manual data cleansing ($95,000) plus user training ($64,000) are expensed immediately ($159,000 combined).

Engineering BandFTEsLoaded Rate ($/hr)SBC Included ($/hr)
Senior Engineers8$110.00$9.35
Staff Engineers10$80.00$3.75
QA and DevOps Engineers4$70.00$2.90

Notice how stock-based compensation flows through the cash flow statement. Across Dispatch Core 4.0 and its Q4 Multi-Currency upgrade ($264,000), Kestrelway capitalizes $99,580 of non-cash SBC under Legacy ($85,610 under ASU 2025-06). Under ASC 230, only cash paid for internal-use software ($2,063,620 Legacy or $1,836,390 ASU 2025-06) enters investing cash outflows; capitalized SBC is a non-cash investing activity disclosed separately.

Worked example 2: standalone calculator and transition adjustment

In the free Software Cost Capitalization Model, a standalone team logging 4,000 eligible direct engineering hours at a loaded rate of $95 per hour ($380,000 payroll) plus $100,000 of external coding contractors capitalizes $480,000 once both ASU 2025-06 gates are met, producing $160,000 of annual straight-line amortization over 36 months. Flip either authorization or probable-to-complete to zero and capitalized cost immediately drops to $0.

When transitioning to ASU 2025-06 on January 1, 2028, preparers may select prospective, modified, or retrospective transition. Under prospective transition, previously capitalized balances stay intact and only new costs from January 1, 2028 forward apply the new standard. Under modified transition, any in-process project that fails the new threshold on January 1, 2028 must be derecognized through opening retained earnings. If an in-process project carried $280,000 of uncertain work on January 1, 2028 at a 25.0% tax rate, modified transition writes off $280,000, books a $70,000 deferred tax benefit, and reduces opening retained earnings by $210,000, accompanied by ASC 250-10-50-1(a) disclosures.

Finally, ASU 2025-06 aligns ongoing disclosures for all capitalized internal-use software with ASC 360-10-50 (gross carrying amount, accumulated amortization, period amortization expense, and methods), regardless of balance sheet line item. Establishing a clear capitalization policy memo early prevents year-end audit friction; for general asset threshold principles, see fixed asset capitalization thresholds.

The trap: Assuming agile sprints can be capitalized automatically once a product roadmap is approved. Under ASU 2025-06, every novel feature or unproven technical module must clear significant development uncertainty before its coding hours leave the income statement.

Questions controllers ask

When is ASU 2025-06 effective?

ASU 2025-06 is effective for all entities for annual reporting periods beginning after December 15, 2027 (calendar year 2028), including interim periods within those years. Early adoption is permitted as of the beginning of an annual period.

Can stock-based compensation be capitalized under ASC 350-40?

Yes. Under ASC 350-40-30-1(b), stock-based compensation under ASC 718 is a payroll-related cost for employees directly working on eligible software activities, though it is excluded from cash investing outflows as a non-cash addition.

What happens to ASC 350-50 website development costs under ASU 2025-06?

ASU 2025-06 supersedes ASC 350-50 and merges website application development into ASC 350-40 under the same funding commitment and probable-to-complete threshold, while marketing content and hosting remain expensed.

Did ASU 2025-06 require a new line item on the statement of cash flows?

No. Although the exposure draft proposed a separate investing cash flow line for capitalized internal-use software, FASB did not mandate a new line item in the final standard.

Read the full handbook

This guide is one chapter arc of The Software Costs Accounting Handbook. The book tracks one US GAAP company through Legacy ASC 350-40 vs. ASU 2025-06, agile sprint evidence, stock-based compensation, abandonment write-offs, cloud ERP implementation vs. IFRIC 2021, ASC 985-20 NRV testing, EBITDA covenants, transition methods and deferred taxes.

Paperback PDF edition, $19.99 Book page and companion workbooks

Free download: Software Cost Capitalization Model (Excel).

Also on this site

Illustrative figures computed by the book's model; every company, project and dollar figure is fictional. Rules checked as read in November 2026; education only, not accounting, audit or tax advice.