Computer software is a fixed asset in the general sense that a business treats it as a long-term investment, but under U.S. generally accepted accounting principles it is classified specifically as an intangible asset rather than tangible property, because it has no physical substance. A business records software this way when it owns or controls the software and expects to use it for more than twelve months. How the cost actually lands on the books depends on whether the software was built in-house, purchased, developed for sale to customers, or accessed through a cloud subscription.
Why Software Is an Intangible Rather Than Tangible Property
The Financial Accounting Standards Board defines intangible assets as “assets (not including financial assets) that lack physical substance.” Software has no physical form, so it falls under that definition rather than under property, plant, and equipment. The governing standards are ASC 350-40 for software a company builds or buys for its own operations and ASC 985-20 for software a company creates to sell to outside customers.1FASB. ITC – Recognition of Intangibles
In practice, some companies present capitalized software next to tangible fixed assets on the balance sheet, especially when it runs a specific piece of hardware. Wherever it sits on the statement, the accounting still follows the intangible-asset rules. The economic logic is the same as for a machine: the benefits stretch across years, so the cost is spread across years too.
When You Capitalize Software and When You Expense It
ASC 350-40 lets a business record internally developed or purchased software as an asset instead of an immediate expense when three conditions hold: the software is intended for the company’s own operations rather than resale, the company controls or owns it, and its expected useful life exceeds twelve months. Many organizations also set an internal dollar threshold, often between $5,000 and $10,000, below which they simply expense the purchase to keep the books clean.
Under the framework still in force for most companies, the costs you can capitalize depend on which development phase they fall into:
- Preliminary project stage — strategy, vendor evaluation, technology selection. Everything here is expensed, because the company has not yet committed to build.
- Application development stage — coding, configuration, testing, and installing the hardware needed to run the software. These costs are capitalized as part of the asset.2FASB. ASU 2025-06 – Intangibles – Goodwill and Other – Internal-Use Software (Subtopic 350-40)
- Post-implementation stage — maintenance, training, and minor bug fixes after go-live. Expensed as incurred.
A few categories are always expensed regardless of when they occur. Training is one. Data conversion — cleaning old records or migrating information into the new system — is another, even when it happens in parallel with capitalizable coding work. Companies that capitalize software need clean records of employee time; if an engineer spends part of a week on preliminary research and the rest on production coding, only the coding hours can be capitalized.
Ongoing costs after the software is live generally cannot be added to the asset. Routine patches, bug fixes, and vendor maintenance fees hit the income statement as they are incurred. An upgrade that adds genuinely new functionality can be capitalized on its own if it meets the same criteria as the original project. A tweak that just preserves existing functionality cannot.
The 2025 Rule Change to Watch
In 2025 the FASB issued Accounting Standards Update 2025-06, which removes the three-stage model. Under the new approach, capitalization starts when management has authorized and committed funding for the project and it is probable the project will be completed and the software will perform as intended.3FASB. FASB Issues Standard That Makes Targeted Improvements to Internal-Use Software Guidance If the project involves novel or unproven technology, capitalization waits until the uncertainty is resolved through coding and testing.
ASU 2025-06 takes effect for annual periods beginning after December 15, 2027, with early adoption permitted for any interim or annual period whose financial statements have not yet been issued. Businesses using agile or non-linear development will find the update easier to apply, since costs no longer need to be mapped to a rigid stage.
Software Built to Sell to Customers
Different rules apply when a company builds software to sell, lease, or market to outside customers. ASC 985-20 draws a sharp line at “technological feasibility.” Every dollar spent before that point is research and development expense and goes straight to the income statement. Feasibility is established either by completing a detailed program design covering the specific configuration and coding requirements, or by producing a working model that shows the software operates as intended.
Once feasibility is established, development costs are capitalized. Capitalization stops when the product is available for general release to customers. From there, the capitalized amount is amortized using the greater of the ratio of current revenue to total expected revenue or the straight-line method over the product’s remaining economic life.
Cloud Subscriptions Are Not a Fixed Asset
If your business accesses software through a cloud subscription — a Software-as-a-Service arrangement — it does not sit on the balance sheet as an asset at all. Because the company never takes possession of the underlying code, the arrangement is treated as a service contract. Subscription fees are operating expenses recorded as incurred, similar to a utility bill.
Implementation costs are the one exception. Guidance introduced in ASU 2018-15 allows costs that would qualify for capitalization under the internal-use software rules — configuring the platform, building custom integrations — to be capitalized separately and then amortized over the term of the hosting contract. Data conversion, training, and routine setup remain immediate expenses.
Amortizing Capitalized Software
Once software is placed in service, its recorded value is reduced through amortization, the intangible-asset counterpart to depreciation. Most companies use the straight-line method. A $50,000 software license with a five-year useful life produces $10,000 of amortization each year. Useful lives typically run three to five years because technology moves quickly, and stretching the period too long risks overstating the asset if the software becomes obsolete.
When circumstances change — a product is discontinued, a newer platform replaces the software early, or expected revenue from a product built for sale drops sharply — the remaining book value may need to be written down through an impairment charge. Impairment reduces the asset to fair value (or net realizable value for software held for sale) and records the difference as a loss.
Tax Treatment Runs on a Separate Track
The tax rules for software operate independently from the GAAP book treatment, and they often let a business recover the cost faster than the amortization schedule on the financial statements.
Purchased Software
For off-the-shelf or separately acquired software that is not a Section 197 intangible (most purchased business software falls outside Section 197), the IRS requires straight-line recovery over a 36-month useful life.4Internal Revenue Service. Instructions for Form 4562 (2025) Because 36 months is shorter than a typical GAAP amortization period, book and tax records often diverge.
Section 179 Expensing
Off-the-shelf computer software — software available for purchase by the general public, subject to a nonexclusive license, and not substantially customized — qualifies for the Section 179 expense election.5Office of the Law Revision Counsel. 26 USC 179 – Election to Expense Certain Depreciable Business Assets The election lets a business deduct the full cost in the year of purchase. For tax years beginning in 2026, the maximum Section 179 deduction is $2,560,000, phasing out once qualifying property placed in service exceeds $4,090,000.
100 Percent Bonus Depreciation
The One Big Beautiful Bill Act permanently restored 100 percent first-year bonus depreciation for qualifying property, including computer software, acquired after January 19, 2025.6Internal Revenue Service. Treasury, IRS Issue Guidance on the Additional First Year Depreciation Deduction Amended as Part of the One Big Beautiful Bill Before that law, the TCJA phase-down had cut bonus depreciation to 60 percent for 2024 and 40 percent for 2025. A business can now write off the full cost of qualifying software in the year it is placed in service, with no dollar cap.7Internal Revenue Service. One Big Beautiful Bill Provisions
Software Developed In-House
Costs to develop software internally are treated as research or experimental expenditures for tax purposes. For tax years beginning after December 31, 2024, the OBBBA added Section 174A, which allows domestic research and experimental expenditures — including software development costs — to be deducted in the year paid or incurred. This is a change from the prior TCJA rule, which required domestic software development costs to be amortized over five years. A business may elect instead to capitalize the expenditures and amortize them over at least 60 months if spreading the deduction is more useful.8Internal Revenue Service. Revenue Procedure 2025-28