Whether software is CapEx or OpEx depends on how you acquire it and what it does for your business. Software you purchase or build for internal use with a useful life longer than a year is generally a capital expense; monthly SaaS subscriptions, maintenance, bug fixes, and employee training are operating expenses. Internally developed software sits in between, with parts of the project capitalized and parts expensed depending on the stage of work. Getting the split right affects your reported earnings, your tax bill, and how cleanly your books hold up in an audit.
The Default Rules by Type of Software
Start with how the software reaches you, because that single fact usually decides the treatment.
Purchased software installed on your own hardware is CapEx when it has a useful life over one year. You own an asset, and its cost sits on the balance sheet and depreciates over time. A perpetual license behaves the same way.
SaaS and cloud subscriptions are OpEx by default. Under ASU 2018-15, paying monthly or annual fees for access to software someone else hosts is a service contract, not the acquisition of an asset. The fees hit the income statement as you incur them.
Internally developed software for your own operations follows ASC 350-40. Some of the project is capitalized, some is expensed, and the timing of each cost within the project decides which bucket it lands in.
Software your company builds to sell, lease, or market to customers is a separate world governed by ASC 985-20. Almost all development cost is expensed as research and development until technological feasibility is established, which for most agile shops happens very late in the cycle.
What Qualifies as a Capitalizable Software Cost
Under ASC 350-40, software qualifies as a capitalizable asset when it has a useful life longer than one year, is intended for internal use rather than sale to customers, and will deliver a future economic benefit the company can demonstrate.
Only direct costs count. That includes payments to outside developers for coding and installation, and the portion of employee salaries tied to hands-on technical work. If a developer earning $120,000 a year spends half their time writing code for the new system, $60,000 of that salary gets capitalized. General overhead, office rent, and management salaries do not qualify, even when those managers oversee the project.
Before capitalizing anything, check the de minimis safe harbor. Businesses with audited financial statements can expense software purchases up to $5,000 per invoice; businesses without audited financials have a $2,500 per-invoice threshold.1Internal Revenue Service. Tangible Property Final Regulations Below those amounts, you can treat the purchase as an immediate operating expense regardless of useful life.
Costs That Are Always OpEx
Some categories never make it onto the balance sheet, even inside a project that is otherwise capitalized.
Routine maintenance and bug fixes flow through the income statement. They keep the software running as originally designed without giving it capabilities it did not have before.
Training is the one that surprises people. Even on a multimillion-dollar system rollout, every dollar spent teaching employees how to use it is expensed immediately. Instructor fees, materials, and travel for on-site sessions all count as training. The logic is that training builds human knowledge, not a software asset.
Data conversion is expensed too. Moving records from an old database to a new one is treated as administrative work. The narrow exception: if you build or buy a piece of conversion software specifically to make the migration happen, that tool’s cost can be capitalized, but the manual work of cleaning and transferring the data cannot.
General and administrative overhead stays on the OpEx side. Allocating a share of your office lease, utilities, or executive salaries to a software project to inflate the asset value is one of the mistakes that draws auditor scrutiny.
How Project Stage Decides the Split for Internal Software
For software you build for internal use, timing within the project matters as much as the type of cost. ASC 350-40 divides these projects into three stages, and the treatment flips as you move between them.
Preliminary Project Stage
Planning-phase spending is OpEx. Evaluating vendors, comparing technology options, deciding whether to build or buy, and scoping requirements all happen here. No asset exists yet, so there is nothing to capitalize. Feasibility studies and consultant evaluations during this window reduce current-year taxable income.
Application Development Stage
Once management formally commits to funding the project and completion is probable, the capitalization window opens. Coding, configuration, hardware installation, and testing costs incurred during this phase go on the balance sheet. The window stays open until the software is substantially complete and ready for its intended purpose. A $15,000 final integration test in this stage gets added to the asset’s book value.
Post-Implementation and Operation Stage
After go-live, the accounting reverts to OpEx for ongoing support, troubleshooting, and user training. Amortization of the capitalized costs starts at this point, typically over three to seven years depending on how long the system is expected to remain in service.
There is one exception worth knowing. Significant upgrades that add genuinely new functionality can be treated as a separate capitalization event. Building a new reporting module onto an existing system follows the same rules as a new project. Routine enhancements that improve speed or fix interface issues do not qualify.
A Rule Change Is Coming
FASB issued ASU 2025-06 in September 2025, which removes all references to development stages from ASC 350-40. Capitalization will begin when two conditions are met: management authorizes and commits to funding the project, and completion for its intended use is probable.2Financial Accounting Standards Board. Accounting for and Disclosure of Software Costs The change is designed for agile development, where coding and planning happen at the same time. ASU 2025-06 takes effect for annual reporting periods beginning after December 15, 2027, with early adoption permitted at the start of any annual period. Companies still on the three-stage model should begin planning for the transition.
The Cloud and SaaS Wrinkle
The subscription itself is OpEx, but the implementation work around it often is not. When you pay developers to configure, code, or customize a cloud platform for your business, those implementation costs can be capitalized and amortized over the term of the hosting arrangement, typically three to five years. A company that spends $200,000 on custom coding to integrate a SaaS platform with internal systems puts that amount on the balance sheet even though the underlying subscription fees do not.
A cloud contract only crosses into full CapEx territory when it functions as a disguised software license. Two conditions must both be met: the contract gives you the right to take possession of the software at any time during the hosting period without a significant penalty, and it is feasible for you to run the software on your own hardware or hire a different vendor to host it. Most SaaS contracts are written specifically to prevent this, so in practice the license classification is rare. Read the contract language carefully before making the call.
How the Tax Return Treats Software Differently
The classification on your financial statements does not automatically carry over to your tax return. Tax rules for software shifted significantly with the One Big Beautiful Bill Act in 2025, and the rules that apply now differ from those in force during 2022 through 2024.
Section 174A for Domestic Development
For taxable years beginning after December 31, 2024, domestic research and experimental expenditures, including software development, can once again be fully expensed in the year paid or incurred under new Section 174A. Companies can alternatively elect to capitalize and amortize over at least 60 months when that fits their tax planning better.
Foreign development did not get the same treatment. Software developed outside the United States must still be capitalized and amortized over 15 years under the original Section 174 framework.3Internal Revenue Service. Guidance on Amortization of Specified Research or Experimental Expenditures under Section 174 The IRS looks at where the development activities are physically performed, not where the company is headquartered. Businesses with offshore development teams end up with a real split on the same return.
Bonus Depreciation and Section 179 for Purchased Software
Purchased software, as opposed to internally developed software, can qualify for accelerated first-year deductions. The One Big Beautiful Bill Act permanently restored 100 percent bonus depreciation under Section 168(k) for qualifying property, including computer software, acquired and placed in service after January 19, 2025. A company that buys a $500,000 enterprise license can potentially deduct the entire cost in year one.
Section 179 offers a separate path for off-the-shelf software. For 2026, the deduction limit is $2,560,000, with a phase-out beginning at $4,090,000 in total equipment and software purchases. Off-the-shelf software that is not custom-built qualifies. For most small and mid-size businesses, Section 179 or bonus depreciation will eliminate any need to spread purchased software costs across multiple tax years.
One nuance: bonus depreciation and Section 179 apply to purchased and licensed software treated as a capital asset. They do not apply to SaaS subscription fees, which are already fully deductible as operating expenses in the year paid. And none of this changes the GAAP treatment on your books, which follows ASC 350-40 or ASC 985-20 regardless of what happens on the tax return. Your accountant will track the resulting book-tax difference as a matter of routine.
What Happens If You Get the Classification Wrong
Misclassification is not just a bookkeeping cleanup. Expensing a cost that should have been capitalized overstates deductions and understates taxable income. Capitalizing costs that belong in OpEx overstates assets and inflates EBITDA, which can mislead investors and lenders.
On the tax side, the IRS can impose a 20 percent accuracy-related penalty on any underpayment caused by negligence or a substantial understatement of income tax.4Office of the Law Revision Counsel. 26 U.S. Code 6662 – Imposition of Accuracy-Related Penalty on Underpayments Interest accrues on top of the penalty until the balance is paid.5Internal Revenue Service. Accuracy-Related Penalty
Documentation is the best protection. Track employee hours by project phase. Keep contracts that clearly spell out whether a cloud arrangement is a license or a hosting service. Record when management formally authorized and funded the project. When the line between capitalizable development work and routine maintenance is borderline, contemporaneous records of what the work actually accomplished are what hold up in an audit.