Is Software a Fixed Asset or Intangible Asset?

Software is a fixed asset when a business owns it outright or holds a perpetual license and expects to use it for more than one year, and because it has no physical form, it sits in the intangible-asset category rather than under Property, Plant, and Equipment. So the answer to whether software is a fixed asset or an intangible asset is that it can be both at once: an intangible type of fixed asset. Whether a particular program qualifies at all depends on how you acquired it, and the accounting answer and the tax answer often diverge for the same purchase.

Why Software Is an Intangible Fixed Asset

Fixed assets are resources a business uses in operations for longer than twelve months and does not hold for sale. Tangible fixed assets—machinery, vehicles, buildings—appear on the balance sheet under Property, Plant, and Equipment. Software lacks physical form, so it belongs to a related but separate category: intangible assets. The longevity and operational-use tests are the same. The presentation on the balance sheet is what differs.

Calling software “intangible” does not demote it from fixed-asset status. It just tells the reader where on the balance sheet to look and signals that the write-off over time is called amortization rather than depreciation.

The Ownership Test That Decides Everything

Before any capitalization question comes up, ask whether you actually own or control the software. If your company bought a copy outright or received a perpetual license to use it indefinitely, the software qualifies as an asset. Its cost goes on the balance sheet and is written off across its useful life.

If instead you pay a monthly or annual fee for access to software the vendor hosts and controls, you do not own anything. You are paying for a service, and those fees are expensed as you go. That is why Software-as-a-Service subscriptions almost never appear as assets, even when the annual bill is substantial.

Capitalization Thresholds Under GAAP

U.S. Generally Accepted Accounting Principles govern software capitalization through FASB’s Accounting Standards Codification Topic 350. Two conditions decide whether a purchase lands on the balance sheet or the income statement.

  • A dollar threshold. Most businesses set a floor, commonly between $1,000 and $5,000, below which purchases are expensed immediately regardless of useful life. Larger companies often set the threshold higher.
  • A useful life longer than one year. If the software has a determinable service life that stretches beyond the current fiscal year, the purchase price and the costs needed to get it running—installation, configuration, testing—are capitalized.

Once capitalized, the software is amortized on a straight-line basis over its estimated useful life. For internal-use software, that estimate typically falls between three and five years, though a company can justify a shorter or longer period based on how quickly it expects to replace the program.

Software Your Company Builds for Its Own Use

When a company develops software for its own operations rather than buying it, GAAP splits the project into three stages, and only the middle stage produces a capitalizable asset.

Preliminary Project Stage

Evaluating vendors, comparing technologies, and deciding whether to proceed are expensed as they happen. The project has not been formally approved, so the spending does not meet the threshold for an asset.

Application Development Stage

Once management authorizes the project, commits funding, and it is probable the software will be completed and used as intended, capitalization begins. Qualifying costs include payroll for employees directly coding, configuring, or testing the software (allocated based on time on the project) and fees paid to outside developers or consultants. Hardware installation costs tied to the software also qualify.

Post-Implementation Stage

After go-live, user training and routine maintenance are expensed as they occur. These activities keep the software running but do not add new functionality, so they do not increase the value of the asset already on the balance sheet.

FASB issued ASU 2025-06 in 2025 to remove the stage-based structure. Under the updated standard, a company capitalizes software costs whenever management has authorized and committed to funding the project and it is probable the project will be completed, regardless of stage. ASU 2025-06 does not take effect until annual reporting periods beginning after December 15, 2027, so the three-stage framework still governs calendar-year 2026 financial statements.1Financial Accounting Standards Board. FASB Issues Standard That Makes Targeted Improvements to Internal-Use Software Guidance

Software Built to Sell

If the software is a product your company markets to outside customers rather than a tool for internal use, a different GAAP standard applies (ASC 985-20). All costs before “technological feasibility”—the point at which planning, designing, coding, and testing confirm the product can meet its design specifications—are expensed as research and development. Only costs incurred after that milestone are capitalized and then amortized once the product is available for general release. The classification question ends the same way (an intangible fixed asset once capitalized), but the path to get there is not the internal-use path.

Cloud and SaaS: Usually Not an Asset

A typical SaaS arrangement is a service contract. The vendor hosts the software on its own servers, controls updates and access, and can terminate your use at the end of the term. Because your company never owns or controls the underlying code, the subscription fees hit the income statement as operating expenses in the period you pay them.

A cloud contract can contain a capitalizable software license, but only if two conditions are both met: you have the right to take possession of the software at any time without significant penalty, and it is feasible for you to run the software on your own hardware or have an unrelated party host it. Most subscription models fail this test.

Even in a pure service contract, certain implementation costs—configuring, customizing, or integrating the hosted software—can still be capitalized. FASB’s ASU 2018-15 aligned this treatment with the internal-use software rules, so the same capitalization criteria apply.2Financial Accounting Standards Board. FASB Improves the Accounting for Costs of Implementing a Cloud Computing Service Arrangement Capitalized implementation costs in a service contract are amortized over the term of the hosting arrangement, including expected renewals, not over the software’s useful life.

How the Tax Answer Can Differ

The IRS classifies software by how it was acquired, and the tax result often differs from the balance-sheet result for the same purchase. Track both.

Off-the-shelf software—commercially available, licensed on a nonexclusive basis, and not substantially modified—is not a Section 197 intangible.3Office of the Law Revision Counsel. 26 U.S. Code 197 – Amortization of Goodwill and Certain Other Intangibles You can expense it immediately under Section 179, take 100% first-year bonus depreciation on qualifying property acquired after January 19, 2025 under the One, Big, Beautiful Bill Act,4Internal Revenue Service. Treasury, IRS Issue Guidance on the Additional First Year Depreciation Deduction Amended as Part of the One, Big, Beautiful Bill or depreciate it straight-line over 36 months.5Internal Revenue Service. Publication 946 – How To Depreciate Property

Software acquired as part of buying a business is generally treated as a Section 197 intangible and amortized over 15 years, even if its practical useful life is much shorter. The exception is off-the-shelf software that meets the three tests above, which escapes Section 197 treatment even inside a business acquisition.3Office of the Law Revision Counsel. 26 U.S. Code 197 – Amortization of Goodwill and Certain Other Intangibles

For software your company develops in-house, tax years beginning after December 31, 2024 fall under Section 174A. Domestic software-development costs can be deducted in the year paid or incurred, or the taxpayer can elect to capitalize and amortize them over at least 60 months, starting in the month the taxpayer first benefits. The election is made by attaching a statement to the original federal return (including extensions) for the first year it applies.6Internal Revenue Service. Revenue Procedure 2025-28 Foreign software-development expenditures follow a 15-year amortization period.

The upshot: on the balance sheet, capitalized software is an intangible fixed asset amortized over three to five years for internal use. On the tax return, the same program might be deducted in year one, spread over 36 or 60 months, or locked into a 15-year Section 197 schedule, depending on how it landed in your hands.