Software Capitalization

What is Software Capitalization?

Software capitalization is the accounting practice of recording certain software development costs as an asset on the balance sheet. The costs are then amortized over the software's useful life instead of expensed immediately.

Updated November 2026 · 2 min read


Why companies capitalize software costs

When a company builds software it expects to use for several years, part of the cost is treated like an investment in an asset, similar to buying equipment. Capitalized costs sit on the balance sheet and are spread over the software's useful life through amortization. This affects reported profit, EBITDA and tax timing, so the rules are closely watched by finance teams, auditors and investors. It is one of the main reasons the line between CapEx and OpEx matters to technology leaders.

The main accounting standards

StandardCoversWhen costs are capitalized
ASC 350-40 (US GAAP)Internal-use software, including most cloud-hosted software a company builds for itselfHistorically during the "application development stage"; changing under ASU 2025-06 (see below)
ASC 985-20 (US GAAP)Software to be sold, leased or marketedAfter technological feasibility is established
IAS 38 (IFRS)Intangible assets, including softwareIn the development phase, once six criteria such as technical feasibility and intent to complete are met

What is changing under ASU 2025-06

For decades, ASC 350-40 used three stages: preliminary project (expense), application development (capitalize) and post-implementation (expense). That model fit waterfall projects poorly and agile teams worse. In September 2025, the FASB issued ASU 2025-06, which removes the stages. Instead, capitalization starts once management has authorized and committed to funding the project and it is probable the project will be completed and used as intended, with no significant development uncertainty. The update is effective for annual periods beginning after December 15, 2027, with early adoption permitted.

Which costs can be capitalized

Usually capitalizedUsually expensed
Developer and engineer time spent building new functionalityResearch, discovery and evaluating alternatives
Directly attributable contractor costsTraining and data conversion (in most cases)
Testing during developmentMaintenance and bug fixes after go-live
Significant upgrades that add functionalityGeneral overhead and administration

An example

A retailer's product teams spend $4 million in a year building a new order management system. Finance works with engineering to tag time: $2.6 million relates to building new functionality after the project was approved, $0.9 million to discovery and prototyping, and $0.5 million to maintaining the old system. The $2.6 million is capitalized and amortized over five years, so the year's expense is lower than the cash spent. The time-tracking categories, agreed with auditors, make the split defensible.

Capitalization in agile and product teams

Continuous delivery and product-based funding make capitalization harder, because there is no single project with a clear build phase. Common approaches include tagging epics or features as capitalizable, using team-level allocation percentages backed by sampling, and aligning work tracking with finance categories. A clear capitalization policy and capitalization threshold help keep decisions consistent.

Common pitfalls

  • Capitalizing maintenance or bug-fix work, which auditors will challenge
  • Weak evidence: no time tracking or work tagging to support the amounts
  • Treating capitalization as a way to flatter results; it shifts expense, it does not remove it
  • Ignoring future amortization, which adds to run costs and KTLO-style spending in later years

Frequently asked questions

What software costs can be capitalized?

Typically, the direct costs of building new software or adding significant new functionality, such as developer salaries for time spent on that work, contractor fees and testing during development. Research, planning, training, maintenance and general overhead are usually expensed. The exact rules depend on the accounting standard and the company's policy.

How does ASU 2025-06 change software capitalization?

It removes the three project stages from ASC 350-40. Capitalization now begins when management has authorized and committed funding and it is probable the software will be completed and used as intended, without significant development uncertainty. It applies to annual periods beginning after December 15, 2027, and early adoption is permitted.

Over how many years is capitalized software amortized?

Over its estimated useful life, which companies set based on how long they expect to use the software. Three to five years is common for internal-use software, though some large systems use longer periods. Amortization usually starts when the software is ready for its intended use, typically at go-live.