Whether software is an asset or an expense depends on how you acquire it, how long you’ll use it, and what it costs. A perpetual license you’ll rely on for years typically goes on the balance sheet and gets amortized. A monthly SaaS subscription gets expensed the same way rent does. The tax treatment can differ from the book treatment, and within tax law you often have several ways to deduct the same purchase. Getting the classification right changes both your financial statements and your tax bill, sometimes by six figures in a single year.
What Makes Software a Capital Asset
Three factors push software toward asset treatment: useful life, ownership, and cost.
The first is duration. Under GAAP, software you expect to use for more than twelve months qualifies for capitalization. A tool that generates revenue for several years should be matched against that revenue over time rather than dumped into one period’s expenses.
The second is control. When you pay a one-time fee for a perpetual license, you own the right to use that software indefinitely. You can install it on your own servers, run it without an internet connection, and keep using it even if the vendor disappears. That level of control is what separates a capital investment from a service payment.
The third is materiality. Most organizations set a dollar threshold below which purchases get expensed automatically, regardless of useful life. The IRS supports this through its de minimis safe harbor election: businesses with audited financial statements can expense items up to $5,000 per invoice, and those without audited statements can expense items up to $2,500 per invoice.1Internal Revenue Service. Tangible Property Regulations – Frequently Asked Questions A $400 utility app gets expensed even if you use it for five years. A $50,000 ERP system clears the threshold and gets capitalized.
Once capitalized, software gradually loses value on your books through amortization, which spreads the cost over the software’s estimated useful life. This keeps your financial statements from overstating net income in the year you buy expensive tools and understating it in the years you actually use them.
What Gets Expensed Right Away
Subscription-based software almost always gets expensed. SaaS platforms, cloud-hosted tools, and any arrangement where you pay for access to someone else’s system rather than owning a license are treated as period costs. You don’t control the underlying software, you can’t take it with you if you cancel, and the vendor can change the product at any time. Economically, these payments look like rent.
The tax code backs this up. Section 162 of the Internal Revenue Code allows businesses to deduct ordinary and necessary expenses in the year they’re paid, including “rentals or other payments required to be made as a condition to the continued use or possession… of property to which the taxpayer has not taken or is not taking title.”2Office of the Law Revision Counsel. 26 USC 162 – Trade or Business Expenses That language covers SaaS subscriptions precisely.
Beyond subscriptions, any software that falls below your capitalization threshold gets expensed, even if you plan to use it for years. Routine maintenance, security patches, and minor updates to existing systems also get expensed, because they keep things running rather than adding new capabilities. The line between a maintenance fix and a capitalizable upgrade comes down to whether the work delivers genuinely new functionality.
Cloud Implementation Sits in the Middle
The subscription itself gets expensed, but the work that goes into standing up a cloud platform can be capitalized. Under FASB guidance aligned with ASC 350-40, certain implementation costs for a cloud computing arrangement that qualifies as a service contract are capitalized even though the underlying subscription is not. The rules follow the nature of the work, not the type of hosting.
Costs incurred during the build-out phase, such as configuring the system, integrating it with existing tools, and coding custom interfaces, can be capitalized and amortized over the term of the hosting arrangement, including renewal periods the company reasonably expects to exercise. Training employees on the new system, converting data from old formats, and early-stage planning done before the company commits to the project all get expensed as incurred. On the income statement, amortization of the capitalized implementation costs shows up on the same line as the hosting fees rather than lumped in with depreciation of physical equipment.
Custom Software Your Team Builds
When your team builds software in-house rather than buying it, the accounting treatment depends on how far along the project is and how certain you are that it will actually get finished.
Under ASC 350-40, you begin capitalizing development costs when two conditions are met: management has authorized and committed to funding the project, and it is probable the software will be completed and used as intended.3FASB. FASB Issues Standard That Makes Targeted Improvements to Internal-Use Software Guidance Everything before that point (brainstorming, evaluating vendors, assessing whether the project is worth pursuing) gets expensed as incurred. The same applies to post-launch costs like additional training and ongoing maintenance contracts.
The FASB recently issued ASU 2025-06, which removes references to the traditional “project stage” framework (preliminary, application development, post-implementation) that previously governed ASC 350-40. The updated guidance leans on the two conditions above rather than forcing companies to slot activities into rigid phases, which makes the standard more compatible with agile and iterative development. The new rules take effect for annual reporting periods beginning after December 15, 2027, with early adoption permitted.3FASB. FASB Issues Standard That Makes Targeted Improvements to Internal-Use Software Guidance
Capitalizable costs during active development include payroll for employees directly coding and testing the software, along with outside contractor fees tied to the build. General overhead, administrative costs, and training never qualify, even during the development period.
Maintenance Versus Enhancements
After launch, the split between an expense and a capital addition hinges on whether the work adds new functionality. Fixing bugs, applying security patches, and optimizing existing features are maintenance expenses. Building a new reporting module, adding a customer-facing portal, or integrating with a new third-party system is an enhancement, and those costs get capitalized under the same rules as the original development.
The IRS Default: 36-Month Amortization
When you capitalize purchased software for tax purposes, the IRS default recovery period is 36 months on a straight-line basis. You deduct one-third of the cost each year, starting in the month you place the software in service.4Legal Information Institute (LII). 26 USC 167(f)(1) – Computer Software That is the schedule you follow when you don’t elect any accelerated method.
One exception applies to software you acquire as part of buying an entire business. Under Section 197, software purchased in a transaction involving a trade or business gets classified as a Section 197 intangible and must be amortized over 15 years, not 36 months.5Office of the Law Revision Counsel. 26 USC 197 – Amortization of Goodwill and Certain Other Intangibles Off-the-shelf software with a nonexclusive license that you buy separately is specifically excluded from Section 197 and keeps the 36-month schedule. If you’re buying a company and its proprietary software is a significant piece of the deal value, you’re locked into a much slower deduction timeline.
Section 179 Immediate Expensing
Instead of spreading the deduction over 36 months, Section 179 lets you write off the entire cost of qualifying software in the year you place it in service. For tax years beginning in 2026, the maximum Section 179 deduction is $2,560,000, and the benefit phases out dollar-for-dollar once total qualifying property placed in service exceeds $4,090,000. The deduction disappears entirely at $6,650,000 in total purchases.6Internal Revenue Service. Depreciation Expense Helps Business Owners Keep More Money
The Section 179 deduction cannot exceed your business’s taxable income for the year, which prevents you from using it to create or deepen a net operating loss. If your business earns $200,000 and buys $300,000 in software, the Section 179 deduction stops at $200,000. The remaining $100,000 carries forward.
A business with strong current-year profits can use Section 179 to immediately offset a large software purchase and drop its tax bill. A startup expecting higher revenue in future years might skip Section 179 and use the 36-month schedule instead, preserving deductions for years when it will be in a higher bracket.
Bonus Depreciation Under the New Rules
Bonus depreciation is another accelerated option, and the rules changed with the One Big Beautiful Bill Act in mid-2025. For qualifying computer software acquired and placed in service after January 19, 2025, the bonus depreciation rate is 100 percent, and that rate is now permanent.7Office of the Law Revision Counsel. 26 USC 168(k) – Special Allowance for Certain Property
There is a transitional wrinkle. If you acquired software before January 20, 2025, but didn’t place it in service until 2026, the bonus depreciation rate is only 20 percent.7Office of the Law Revision Counsel. 26 USC 168(k) – Special Allowance for Certain Property Property acquired before that date and placed in service after 2026 gets no bonus depreciation at all. For most purchases going forward, 100 percent bonus depreciation is available.
Unlike Section 179, bonus depreciation has no dollar cap and no phase-out based on total purchases. It also isn’t limited by taxable income, so it can generate or increase a net operating loss. For a very large software investment, bonus depreciation can be more useful than Section 179. A common approach is to combine them: apply Section 179 first up to the limit, then take bonus depreciation on the remainder.
Section 174A and Domestic Development
If your company develops software in-house, a separate set of tax rules applies. Section 174A, effective for tax years beginning after December 31, 2024, permanently restores full expensing for domestic research and experimental expenditures, including software development. Companies can deduct the full cost of domestic software development in the year it’s paid or incurred, or they can elect to capitalize and amortize over at least 60 months if they prefer to spread the deduction.
Foreign software development still has to be capitalized and amortized over 15 years. If your development team is split between domestic and offshore locations, you’ll need to allocate costs between the two regimes. The IRS issued Notice 2023-63 defining which activities count as software development for these purposes, covering everything from planning and design through coding, testing, and producing final product versions.8Internal Revenue Service. Guidance on Amortization of Specified Research or Experimental Expenditures Under Section 174 (Notice 2023-63) Purchasing and installing off-the-shelf software, including configuring it for your business, does not count as software development under Section 174.
Book and Tax Treatment Don’t Always Match
The asset-versus-expense decision isn’t a single choice. A company might expense its SaaS subscriptions under Section 162, capitalize the implementation costs for those same platforms under ASC 350-40, take Section 179 on a large perpetual license, use bonus depreciation on another purchased system, and fully expense its domestic development work under Section 174A. Each category of software cost follows its own rules.
The financial statement treatment under GAAP and the tax treatment under the IRC don’t always line up. You might capitalize development costs on your balance sheet for investor reporting while fully expensing them on your tax return. That gap creates a book-tax difference your accountant tracks with deferred tax entries. Classifying each type of software cost correctly at the start prevents restatements, audit flags, and missed deductions that compound over time.