Capitalized Software: Costs Held as a Balance Sheet Asset

Key Takeaways

• Internal-use software is capitalized under ASC 350-40; software to be sold or licensed is capitalized under ASC 985-20.
• Capitalized amounts include direct labor, third-party services, and license fees, but not research, training, or post-launch maintenance.
• Amortization typically runs straight-line over three to five years, beginning when the software is ready for its intended use.
• ASU 2025-06 modernizes ASC 350-40 by replacing project-stage gating with a principles-based capitalization trigger, effective for periods beginning after December 15, 2027.

What It Is

Capitalized software appears in non-current assets, sometimes grouped with property, plant and equipment, sometimes with other intangibles. It captures the labor, contractor fees, and license costs spent to build a working software asset that will be used internally or sold externally.

Disclosures typically include unamortized capitalized software costs, amortization expense, and writedowns to net realizable value. Materiality determines whether the line is separately stated or aggregated.

The Intuition

The matching principle says costs should be recognized in the same period as the revenue they generate. Software built for multi-year use produces benefits over years, so the cost belongs on the balance sheet and through expense gradually, not as a one-time hit when the work happens.

But not every dollar spent on a project produces a future asset. Research, planning, training, and bug fixing typically deliver no incremental capacity beyond the current period. GAAP draws a line between work that builds the asset and work that does not, and only the former is capitalized.

How It Works

Three regimes apply, depending on the use of the software:

• Internal-use software (ASC 350-40): software developed or obtained for the company's own operations. Under the current rules, costs in the application development stage are capitalized once preliminary planning is complete and management has committed to funding. Preliminary stage costs and post-implementation costs are expensed.
• Software to be sold, leased, or marketed (ASC 985-20): costs incurred between technological feasibility and general release are capitalized. Costs before technological feasibility, including most R&D, are expensed.
• Cloud computing arrangements (within ASC 350-40): implementation costs of certain hosting arrangements are capitalized and amortized over the term of the service contract.

Amortization (internal-use) = capitalized cost / useful life (typically 3 to 5 years)

Amortization begins when the software is ready for its intended use, regardless of whether it has been placed in service. The asset is tested for impairment under ASC 350 or ASC 360 when triggers arise, and is reduced to net realizable value when the carrying amount is no longer recoverable.

ASU 2025-06 updates ASC 350-40 to remove the predefined "project stage" model and replaces it with a principles-based trigger: capitalize when management has authorized and committed funding, and when it is probable the project will be completed and used as intended. The amendments are effective for annual periods beginning after December 15, 2027.

Worked Example

A retailer builds a new internal order management platform. Over 18 months, the company spends $30 million: $5 million on preliminary planning, $20 million on development labor and contractors during the build, and $5 million on training and rollout after go-live.

Under ASC 350-40, the $20 million development cost is capitalized. The $5 million preliminary planning and the $5 million post-implementation training are expensed as incurred. The capitalized asset is amortized straight-line over a 5-year useful life, producing $4 million per year of amortization expense.

If, two years after launch, the company decides to migrate to a software-as-a-service vendor and retire the internal platform, the remaining $12 million carrying value would be tested for impairment and written down to net realizable value, likely zero, with the loss running through the income statement.

Common Mistakes

1. Capitalizing planning and training costs. Only direct development costs qualify. Preliminary planning and post-launch training are expensed.
2. Confusing internal-use with sold software. The capitalization trigger and amortization start differ. Misclassifying can pull years of expense into the wrong period.
3. Treating capitalized software as cash savings. Cash already moved out the door. Capitalization just shifts the income statement charge across periods.
4. Missing the amortization start. Amortization begins when the software is ready for use, not when sales of related products start, which can advance expense earlier than expected.
5. Ignoring impairment risk on legacy platforms. Decisions to retire or migrate often produce sudden writedowns. Read the management discussion and analysis for signals.

Frequently Asked Questions

What is capitalized software in simple terms? It is software development cost that a company records as a long-lived asset on the balance sheet rather than expensing immediately. The cost then flows through the income statement as amortization over the software's useful life.

How does capitalized software affect investment decisions? Heavy capitalization can boost reported operating income today and produce higher amortization later. Investors who add back software amortization or expense all software costs get more comparable margins across peers.

What is a real-world example of capitalized software? Tech and retail companies often capitalize hundreds of millions per year for internal platforms and customer facing software. Footnotes show amortization, useful lives, and impairment charges on retired systems.

How can investors avoid being misled by capitalized software? Compare the ratio of capitalized software to total R&D spending across peers. A sudden jump in capitalization can signal earnings management.

How is capitalized software different from R&D? Most R&D is expensed under ASC 730 as incurred. Capitalized software is a narrow exception: certain development costs after a feasibility or commitment threshold can be recorded as an asset and amortized.

Sources

1. PwC Viewpoint. 8.6 Capitalized Software. https://viewpoint.pwc.com/dt/us/en/pwc/accounting_guides/financial_statement_/financial_statement___18_US/chapter_8_other_asse_US/86_capitalized_software.html
2. FASB. ASU 2025-06 Intangibles, Internal-Use Software (Subtopic 350-40). https://www.fasb.org/Page/Document?pdf=ASU+2025-06.pdf
3. Deloitte. Heads Up FASB Amends Guidance on Accounting for Software Costs. https://dart.deloitte.com/USDART/home/publications/deloitte/heads-up/2025/fasb-asu-amends-software-costs-guidance
4. AICPA and CIMA. ASU 2025-06 Changes to Accounting for Internal-Use Software. https://www.aicpa-cima.com/resources/article/asu-2025-06-changes-to-accounting-for-internal-use-software

Disclaimer

This article is educational content only and is not financial advice. Nothing here is a recommendation to buy, sell, or hold any security. Consult a licensed advisor before making investment decisions.