Software is almost always a non-current intangible asset, not a current asset or a fixed asset. The two situations where it sits in current assets are software your company builds to sell to customers (which becomes inventory once technological feasibility is reached) and prepaid SaaS subscriptions covering the next twelve months. Whether software is a current asset or a fixed asset depends on what it does for the business, whether you own it or license it, and how long you expect to benefit from it. Software is never a fixed asset in the traditional sense, because it has no physical form; the closest equivalent is a long-term intangible asset.
The Default: Internal-Use Software Is a Non-Current Intangible
Most software on a company’s books was built or bought for internal operations, and under ASC 350-40 that software is a non-current intangible asset when it provides benefits beyond one year. It has no physical form, and no one plans to convert it to cash within the normal operating cycle. It doesn’t belong in current assets, and because it isn’t tangible property it doesn’t belong with fixed assets like buildings or equipment either. It lives in its own line: long-term intangibles.
What Gets Capitalized
Not every dollar spent on internal software reaches the balance sheet. Accounting splits the work into three stages. During the preliminary project stage, when the company is still evaluating vendors and deciding whether to proceed, costs are expensed. Capitalization begins only once management commits to the project and the application development stage starts. Design, coding, configuration, and testing costs during that stage go onto the balance sheet as a long-term asset. After the software goes live, routine maintenance and bug fixes are expensed again. A significant upgrade that adds new functionality restarts the same three-stage analysis for the new work.
How It Comes Off the Books
Capitalized internal-use software is amortized on a straight-line basis over its estimated useful life. Most companies use three to five years, which reflects how quickly business applications get replaced. The amortization runs through the income statement each period and gradually reduces the asset’s carrying value. Because these assets sit in the long-term section, they don’t inflate the current ratio or mislead creditors about short-term liquidity.
When Software Is a Current Asset
There are two genuine cases where software belongs in current assets.
Software Built for Sale to Customers
Software developed to sell, lease, or license to external customers follows ASC 985-20, and the pivot point is technological feasibility. Before it, every development dollar is expensed as research and development. Technological feasibility is established when the company has finished the planning, designing, coding, and testing needed to confirm the product meets its design specifications, usually by completing a detailed program design or a tested working model. After that milestone, costs for coding, testing, and producing the software master are capitalized as inventory. Because the company intends to sell the software within the normal operating cycle, that inventory is a current asset.
Once the product is released, amortization begins on a product-by-product basis. The annual charge is the greater of the ratio of current-period revenue to total expected lifetime revenue, or straight-line amortization over the product’s remaining economic life. Companies also test for impairment at each balance sheet date by comparing carrying amount to net realizable value from forecasted revenue, writing the asset down if it exceeds what the software can realistically earn.1SEC EDGAR. Note 1 – Summary of Significant Accounting Policies: Software Development Costs
Prepaid SaaS Subscriptions
When a business pays upfront for a cloud subscription rather than owning software outright, GAAP treats the payment as a prepaid expense. The company doesn’t control the underlying code, so there is no intangible asset to capitalize. The unexpired portion of the subscription sits in current assets as a prepaid item. Each month, a slice of the balance moves from the balance sheet to the income statement as an operating expense. If the subscription runs beyond twelve months, only the portion covering the next year stays in current assets; the rest moves to long-term assets. That split matters for the current ratio, which lenders check early.
The In-Between Case: Cloud Implementation Costs
Companies often spend serious money implementing a SaaS product: configuring it, migrating data, integrating it with existing systems. ASU 2018-15 clarified that these implementation costs follow the same three-stage framework as internal-use software under ASC 350-40, even though the underlying arrangement is a service contract rather than a software license.2FASB. Accounting Standards Update 2018-15
Preliminary and post-implementation costs are expensed. Application development stage costs, such as configuration and coding work, are capitalized as a prepaid asset. Training and certain data conversion costs cannot be capitalized regardless of stage. The capitalized implementation costs are then amortized on a straight-line basis over the term of the hosting arrangement, including any reasonably certain renewals. Because the costs are treated as a prepaid rather than an intangible license, the portion covering the next twelve months sits in current assets, and the remainder in long-term assets.2FASB. Accounting Standards Update 2018-15
Software Used for R&D Never Reaches the Balance Sheet
Software used exclusively for research and development is not a current asset or a long-term asset. Under ASC 730, R&D costs are expensed immediately as incurred and never touch the balance sheet. The one exception is software with a proven alternative future use beyond the R&D project itself. If the same tool will later support commercial products or other internal functions, it can be capitalized and amortized. Without a concrete alternative use, the cost stays on the income statement.3Internal Revenue Service. FAQs – IRC 41 QREs and ASC 730 LBI Directive
Why the Classification Matters
Getting current-versus-non-current wrong distorts liquidity ratios and misleads investors and lenders. A software cost booked as a current asset when it should be long-term inflates the current ratio and overstates short-term financial health. A cost expensed when it should be capitalized can swing a quarter into a loss it wouldn’t otherwise show.
The tax side runs on separate rules. GAAP classification determines how software appears on your financial statements; the IRS decides what you can deduct and when. Since 2022, software development costs must be capitalized and amortized over five years for domestic work or fifteen years for foreign work under Section 174, with amortization beginning at the midpoint of the tax year the cost is incurred.4Office of the Law Revision Counsel. 26 USC 174 – Research and Experimental Expenditures Purchased off-the-shelf software can qualify for immediate expensing under Section 179, subject to annual limits.5Office of the Law Revision Counsel. 26 USC 179 – Election to Expense Certain Depreciable Business Assets SaaS subscription fees are generally deductible as ordinary business expenses in the period they cover, which aligns with the GAAP prepaid treatment. Book and tax classifications can diverge, so track each software dollar in a way that supports both sets of records.
Quick Reference
- Internal-use software you own or built: non-current intangible asset, amortized over three to five years.
- Software built to sell to customers: current asset (inventory) once technological feasibility is reached.
- Prepaid SaaS subscriptions: current asset for the next twelve months of coverage; anything beyond that is long-term.
- Cloud implementation costs: capitalized as a prepaid asset during the application development stage; current-year portion sits in current assets.
- R&D software: expensed immediately unless it has a proven alternative future use.
- Fixed assets: not the right category for software under any GAAP scenario, because software lacks physical form.