Capitalized software costs analysis is the practice of determining which software development expenditures a company recorded as an asset instead of an expense, testing whether that judgment follows the applicable standard, and measuring how it changes reported earnings, assets and cash flow. The core inputs are the accounting policy note, the capitalized software rollforward, the amortization disclosures and the cash flow statement. The core question is whether the capitalization pattern is consistent with the delivery the company describes in earnings calls and filings.
TL;DR
- Internal-use and cloud software fall under ASC 350-40, while software sold or licensed to customers falls under ASC 985-20. The two models differ in the trigger for capitalization and in amortization.
- Capitalization moves cost from current R&D expense into future amortization, which raises current operating income and shifts cash outflows into investing activities.
- ASU 2025-06 removes the project-stage framework from ASC 350-40 and replaces it with an authorization-and-probability threshold, effective for annual periods beginning after December 15, 2027.
- Reliable assessment depends on year-over-year comparison of capitalization rates, useful lives, impairments and any revisions to project scope or performance requirements.
Table of Contents
- 1. Which Software Costs Qualify for Capitalization
- 2. ASU 2025-06 and the Change in the Capitalization Threshold
- 3. Amortization, Impairment and Disclosure Patterns
- 4. Capex vs. Opex: Effect on Earnings, Assets and Cash Flow
- 5. Baseline Changes: How Scope and Estimate Revisions Alter Reported Costs
- 6. Is Capitalization Informative? What the Academic Evidence Shows
- 7. Perspective: Why Capitalization Belongs in a Narrative-versus-Delivery Test
- 8. A Practical Workflow for Analyzing Capitalized Software
- 9. Applying the Analysis With Lacuna Index
- FAQ
- Sources
1. Which Software Costs Qualify for Capitalization
The classification of a cost as capitalizable depends on three variables: the intended use of the software, the point in the project at which the capitalization threshold is crossed, and the nature of the cost itself.
Internal-use software under ASC 350-40
For internal-use software, eligible costs after the capitalization threshold are limited to external direct materials and services, directly attributable payroll and payroll-related costs, qualifying interest, and software that enables access to or conversion of old data. Training, physical data conversion, general and administrative costs and overhead are expensed as incurred, as are all costs incurred before the threshold.
This enumeration matters for forensic purposes because it defines what a legitimate capitalized balance should contain. A balance that grows faster than engineering headcount and external contractor spend, or one whose disclosed composition includes categories outside this list, warrants inquiry.
Software sold or licensed to customers under ASC 985-20
Software marketed externally follows a different gate. ASC 985-20 requires technological feasibility before capitalization, whereas ASC 350-40 governs internal-use and SaaS or cloud software and ties capitalization to the development stage. Because technological feasibility is typically established late in a product cycle, ASC 985-20 balances are generally smaller relative to development spend than internal-use balances at comparable companies, though the proportion varies by issuer and should be read from the filings rather than assumed.
Where cloud arrangements fall
A customer has a software license in a hosting arrangement only if it can take possession at any time during the hosting period without significant penalty and feasibly run the software on its own hardware or contract with an unrelated party to host it. Otherwise the arrangement is solely a service contract. In a service contract, ongoing hosting fees are expensed as received and qualifying implementation costs are evaluated under internal-use software guidance. An arrangement containing a license may require separate software-license accounting.
For an analyst, this distinction explains why two companies with similar cloud spend can report very different capitalized balances: one may be capitalizing implementation costs of a hosted service, the other expensing an equivalent amount.

2. ASU 2025-06 and the Change in the Capitalization Threshold
FASB's ASU 2025-06 applies to all entities subject to ASC 350-40 and removes the prescriptive references to sequential project stages. After adoption, capitalization begins when management has authorized and committed funding to the project and it is probable that the project will be completed and the software used as intended, subject to an assessment of significant development uncertainty. The amendments apply for annual periods beginning after December 15, 2027, with early adoption permitted.
Significant development uncertainty
The same ASU states that significant development uncertainty includes unresolved technological innovation or novel, unique or unproven functions, and substantially revised or unidentified significant performance requirements. Where it exists, the probable-to-complete threshold is not met and costs remain expensed. If capitalization criteria cease to be met, no further costs are capitalized and existing balances are assessed for impairment.
Disclosure consequences
The ASU specifies that PP&E disclosures under ASC 360-10 apply to all capitalized internal-use software costs regardless of balance-sheet presentation, while ASC 350-30 intangible disclosures are not required for those costs. The amendments do not affect software costs subject to ASC 985-20. During the transition period, comparability across issuers therefore weakens: early adopters, late adopters and issuers whose software falls under ASC 985-20 will report under different frameworks within the same peer set.
What the new threshold changes analytically
A stage-based model produced a recognizable timeline: preliminary project stage expensed, application development stage capitalized, post-implementation expensed. A threshold based on management authorization and probability places more weight on management judgment, because both authorization timing and the probability assessment are internal determinations. The disclosure that matters most is therefore the policy description: how the company defines authorization, how it documents probability, and how it evaluates development uncertainty. A policy note that changes wording between filings without a stated reason is a primary signal for follow-up.
3. Amortization, Impairment and Disclosure Patterns
Amortization conventions
Internal-use software is typically amortized on a straight-line basis. monday.com, for example, amortizes capitalized internal-use software straight-line over its estimated useful life and tests impairment when events or circumstances could affect recoverability.
External-use software under ASC 985-20 follows a product-by-product convention. Amortization starts at general release and uses the greater of a revenue-ratio method, based on current and anticipated future revenues, or straight-line amortization over the remaining economic life. The same handbook notes that ASC 985-20 requires unamortized software costs on each balance sheet presented and disclosure of amortization expense and net-realizable-value write-downs for the periods presented, and it points to disclosure of research-and-development costs expensed.
Reading a rollforward
An SEC-filed 2024 example illustrates the disclosure structure an analyst should expect. The filing reported $68.805 million of gross software development costs, $27.331 million of accumulated amortization and $41.474 million net at December 31, 2024. It also recognized $2.9 million of accelerated amortization after changing the estimated useful life of an abandoned project.
Several ratios can be derived from a disclosure of this kind:
| Metric | Calculation | What it indicates |
|---|---|---|
| Accumulated amortization to gross cost | $27.331 million / $68.805 million = about 39.7% | How much of the asset base has been consumed |
| Net to gross | $41.474 million / $68.805 million = about 60.3% | Remaining unamortized balance |
| Accelerated amortization to net balance | $2.9 million / $41.474 million = about 7.0% | Scale of the abandonment charge relative to the remaining asset |
The ratios are the analyst's own arithmetic on the disclosed figures. Their value lies in the trend: a rising net-to-gross ratio with flat engineering headcount indicates that additions are outpacing amortization, which may be legitimate growth or may reflect an expanding capitalization policy.
Useful lives and abandonments
A change in estimated useful life is an accounting estimate change, applied prospectively, and its effect can be material to operating income. Lengthening lives lowers annual amortization; shortening them, or abandoning a project, accelerates it. The relevant questions are whether the filing explains the change, whether it coincides with a period in which earnings targets were at risk, and whether the stated rationale appears in operational disclosures such as product roadmaps or earnings call commentary.
4. Capex vs. Opex: Effect on Earnings, Assets and Cash Flow
The capital-versus-operating-expense distinction determines where a software dollar appears in the financial statements. Capitalization reduces current R&D expense and increases net income and software assets. When capitalized costs are classified as investing outflows, operating cash flow rises, although amortization is added back in operating cash flow and therefore has no net cash-flow effect. The same research describes the shift of expense recognition from the current period into future amortization, which generally raises current assets and operating income relative to immediate expensing but creates future amortization and impairment exposure.
A worked comparison
The following illustration uses hypothetical figures to show the mechanics. It is a teaching device, not a reported result.
| Item | Fully expensed | 40% capitalized |
|---|---|---|
| Engineering spend | $100 | $100 |
| Expensed in current period | $100 | $60 |
| Capitalized to balance sheet | $0 | $40 |
| Pre-tax effect on operating income | -$100 | -$60 |
| Operating cash flow effect | -$100 | -$60 |
| Investing cash flow effect | $0 | -$40 |
| Total cash out | $100 | $100 |
Total cash is identical. The reported profit, the operating cash flow and the asset base differ. Free cash flow definitions that start from operating cash flow and subtract only purchases of property and equipment may omit capitalized software, which is why comparing software companies requires understanding their capitalization practices and adjusting operating cash flow for software development costs classified as investing.
Adjusted comparison method
- Extract capitalized software additions from the investing section of each peer's cash flow statement.
- Subtract those additions from operating cash flow to produce an adjusted operating cash flow.
- Compute capitalized additions as a percentage of total R&D (expensed R&D plus capitalized additions).
- Compare amortization of capitalized software to additions, to see whether the asset base is growing or being consumed.
- Repeat for at least three fiscal years to separate policy from project timing.
5. Baseline Changes: How Scope and Estimate Revisions Alter Reported Costs
A frequently searched question concerns baseline change manipulation: the revision of project scope, requirements or timelines in a manner that moves costs between the expensed and capitalized categories. Under the framework in ASU 2025-06, unidentified or substantially revised significant performance requirements delay capitalization until the uncertainty is resolved. A project whose requirements are reset after capitalization began creates an analytic question: were earlier capitalized costs recoverable under the new requirements, and was impairment assessed?
Patterns that warrant follow-up
- Rising capitalization rate without disclosed project change. Capitalized additions as a share of total engineering cost increase while the policy note is unchanged.
- Useful life extensions. A longer estimated life appears in a year when amortization would otherwise have pressured margins.
- Absence of impairments despite scope changes. Management describes a product pivot or restart on earnings calls, yet the filings report no impairment or accelerated amortization.
- Abandonment charges following optimistic commentary. Projects described as on track in prior calls are later written off. The forensic workflow for earnings call analysis describes how to log such statements against subsequent filings.
- Policy wording drift. Definitions of authorization, probability or development uncertainty change between periods without explanation, which is particularly relevant during ASU 2025-06 adoption.
Matching claims to records
The test is evidentiary. Each statement about product timing, readiness or scope should be traced to the filing that would reflect it if true. The MD&A tracing workflow applies the same discipline to management discussion of results, and the analysis of billings versus revenue gaps shows how a narrative claim about demand can be reconciled with reported figures. Capitalization judgments belong in the same reconciliation set.
6. Is Capitalization Informative? What the Academic Evidence Shows
Capitalization should not be dismissed as accounting noise. Aboody and Lev's study of 163 firms during 1987 to 1995 found that annual capitalized development costs were positively associated with stock returns, cumulative software assets with stock prices, and capitalization data with subsequent earnings. The result supports treating capitalization disclosures as potentially value-relevant. The analytic task is therefore discrimination: identifying when capitalization reflects investment that later produces revenue, and when it reflects a discretionary shift in the timing of expense recognition.
One practical consequence is that capitalization intensity should be read alongside delivery evidence. A company that capitalizes heavily and subsequently reports revenue growth, retention and margin expansion consistent with its description of the product has a coherent record. A company that capitalizes heavily while the described product launches slip, or while related revenue never appears, has a gap between narrative and delivery. The capital allocation spreadsheet method provides one structure for tracking this over multiple years, and the treatment of off-balance-sheet commitments covers obligations, such as outsourced development contracts, that may sit outside the capitalized balance.
Software acquired in a transaction
Capitalized software can also enter the balance sheet through acquisition rather than internal development. In that case the carrying value depends on the fair value assigned in purchase price allocation, which then determines the base from which later amortization and impairment testing proceed. Analysts should separate acquired software from internally developed software in any rollforward, since the two reflect different judgments.
7. Perspective: Why Capitalization Belongs in a Narrative-versus-Delivery Test
We treat the capitalized software balance as a record of what management committed to build, expressed in accounting terms. Every capitalized dollar implies a claim: that the project was authorized, that completion was probable, and that the resulting software will be used as intended. Those claims can be compared with what the same company said on earnings calls, in press releases and in proxy statements, and with what it subsequently delivered.
The methodology applies a consistent, evidence-based process across covered issuers, using public records only, with governance logs documenting how each score was reached. Applied to software capitalization, this means that a rising balance, a useful-life revision or an abandonment charge is read against the narrative that preceded it, rather than in isolation. The aspiration-to-execution gap is measured, not inferred.
Narrative engineering often operates through timing and omission: the unasked question about why a project's requirements changed, or why a useful life was extended. Standardized scoring across issuers makes those patterns comparable. The methodology walkthrough sets out how that process is structured, and the discussion of narrative engineering in corporate reporting addresses the valuation consequences.
Glen
8. A Practical Workflow for Analyzing Capitalized Software
The following sequence applies to a single issuer and can be repeated across a peer set.
- Identify the governing standard. Determine from the policy note whether software is internal-use (ASC 350-40), externally marketed (ASC 985-20), or both, and whether the company has early-adopted ASU 2025-06.
- Extract the rollforward. Record beginning balance, additions, amortization, impairments, abandonments and ending balance for at least three years.
- Compute intensity ratios. Capitalized additions to total R&D, additions to amortization, and net to gross.
- Adjust cash flow. Subtract capitalized software from operating cash flow to compare peers on a consistent basis.
- Review estimate changes. Note any change to useful lives, with the stated rationale and the timing relative to earnings pressure.
- Check the narrative record. Match product commentary in calls and filings against capitalization and impairment events.
- Document the evidence. Cite the specific filing and line item for each finding, so the analysis can be audited by a third party.
Sector context
Capitalization intensity differs sharply by business model, so peer selection matters. Sector-level reference points help establish what is typical before an individual issuer is judged. The free Industrials benchmarks and Financials benchmarks illustrate how execution scores are compared within a sector, which is the same logic applied to capitalization ratios within a software peer group.
9. Applying the Analysis With Lacuna Index
Sector benchmarks at Lacuna Index are free, and they provide the comparison frame for narrative-versus-delivery scoring. Per-company forensic reports, which quantify the gap between what an issuer claims and what the public record shows, are available to subscribers. The reports rely solely on public records and include audit-traceable scoring, so that a finding about capitalization, estimate changes or disclosure opacity can be followed back to its source filing.

Institutional investors, governance advocates, proxy advisors and financial journalists can review the available plans, Cohort Pulse and Sector Sweep, or see how per-company analysis is structured. Pricing is not published on those pages.
FAQ
Can software development costs always be capitalized?
No. Costs incurred before the capitalization threshold are expensed, and so are training, physical data conversion, general and administrative costs and overhead. Under ASU 2025-06, significant development uncertainty, such as unresolved technological innovation or substantially revised performance requirements, keeps costs expensed until it is resolved.
What is the difference between ASC 350-40 and ASC 985-20?
ASC 350-40 governs internal-use software, including SaaS and cloud software, with capitalization tied to the development stage (or, after ASU 2025-06 adoption, to authorization and probability of completion). ASC 985-20 governs software marketed externally and requires technological feasibility before capitalization. Amortization conventions differ as well, with the revenue-ratio or straight-line method applied product by product under ASC 985-20.
How does capitalizing software affect cash flow?
Total cash spent is unchanged. Capitalized costs classified as investing outflows raise reported operating cash flow relative to expensing, while amortization is a non-cash charge added back. Comparisons across software companies should therefore adjust operating cash flow for capitalized development costs.
Which red flags suggest capitalization is being used aggressively?
Useful signals include a rising share of R&D capitalized without a disclosed policy change, lengthened useful lives, wording changes in the policy note, and projects described as proceeding normally that are later abandoned. Each should be tested against the company's earlier statements and later results.
Sources
- 3.3 Direct and indirect costs for internal-use software, PwC Viewpoint
- ASU 2025-06, Internal-Use Software, FASB
- ASU 2025-06 full text, PwC Viewpoint
- Software development cost accounting for SaaS, cloud and other software, Deloitte
- 1.5 Cloud computing arrangements, scope, PwC Viewpoint
- monday.com internal-use software note, SEC filing
- Software development costs note, December 31, 2024, SEC filing
- Handbook: Software and website costs, KPMG
- Capitalization of software costs and operating cash flow, Georgia Tech repository
- The Value-Relevance of Intangibles: The Case of Software Capitalization, SSRN
