How to Depreciate Purchased Software on Schedule C: §179, 100% Bonus, or 36-Month Amortization

Published: September 14, 2026 · Reading time: 9 min

TL;DR: Buy — not rent — business software, and IRC §167(f)(1) defaults you to 36-month straight-line amortization, because §197(e)(3)(A) carves nearly all standalone software purchases out of the 15-year intangible regime. You can accelerate that to a single year two ways, and they aren't the same test: Section 179, per §179(d)(1)(A)(ii), only reaches software that is "described in section 197(e)(3)(A)(i)" — publicly available, nonexclusively licensed, unmodified for you. 100% bonus depreciation under §168(k)(2)(A)(i)(II) has no such restriction — it reaches any software eligible for the §167(f) default, off-the-shelf or not — and it's been permanently 100% (not phasing down) since the One Big Beautiful Bill Act, for property acquired after January 19, 2025. What doesn't help: the $2,500 de minimis safe harbor, which Treas. Reg. §1.263(a)-1(f)(1) limits to "a unit of tangible property" — software is intangible, so there's no small-dollar shortcut around any of this. And software bundled into buying an entire existing business skips all of the above for §197's mandatory 15-year amortization instead — unless it's independently off-the-shelf, which stays excluded from §197 regardless of the acquisition.

Freelancers who've internalized "equipment over $2,500 gets depreciated, everything else gets expensed" often assume software works the same way. It doesn't — software isn't tangible property, so the usual small-purchase shortcuts don't apply to it at all, and the rules that do apply run through three different Internal Revenue Code sections that don't all require the same thing. Here's what each one actually says, verified against the statute itself.

Four Ways You Pay for Software, Four Different Treatments

Before anything else, place your purchase correctly — everything below turns on how you acquired the software:

This post is about the middle two rows — the two ways a freelancer actually buys software as a standalone purchase. The first row (subscriptions) is already covered in the Line 22 supplies and software guide; the last row (whole-business acquisitions) is covered in full in the client-list amortization guide, which establishes the same "no de minimis shortcut for intangibles" point this post relies on below. That last row has its own exception, covered next: off-the-shelf software bundled into a business purchase actually behaves like row two, not row four.

Why Software Escapes the 15-Year Intangible Regime

Most purchased business intangibles — a client list, a covenant not to compete, goodwill — get the harsh treatment under IRC §197: mandatory 15-year straight-line amortization, no election out, no shortcut, regardless of how long you actually expect to use the thing. Software gets a specific statutory exception. IRC §197(e)(3)(A) carves it out:

"Any— (i) computer software which is readily available for purchase by the general public, is subject to a nonexclusive license, and has not been substantially modified, and (ii) other computer software which is not acquired in a transaction (or series of related transactions) involving the acquisition of assets constituting a trade or business or substantial portion thereof."

Two independent branches, either one is enough to escape §197. Branch (i) is the "off-the-shelf" test. Branch (ii) is broader — it excludes essentially any software you buy as a standalone purchase, off-the-shelf or not, as long as you're not buying it bundled into an entire business. For a solo freelancer, almost every software purchase clears branch (ii) even when it fails branch (i). "Computer software" itself is defined narrowly and functionally in §197(e)(3)(B): "any program designed to cause a computer to perform a desired function" — a definition that matters later, because it's the same one bonus depreciation borrows.

Escaping §197 doesn't mean escaping amortization entirely — it means falling into a different, much shorter rule.

One acquisition-context wrinkle worth naming precisely: buying an entire existing business, software included, is exactly the kind of transaction branch (ii) excludes — so branch (ii) fails for it. But branch (i) carries no such condition. Software that independently clears the off-the-shelf test — readily available to the general public, nonexclusively licensed, unmodified — stays excluded from §197 even when it arrives bundled into a business acquisition. Treas. Reg. §1.197-2(c)(4), Example 2, confirms this directly: a buyer who acquires all of a business's assets, including rights to publicly available, unmodified software, is "not a section 197 intangible" despite the business-acquisition context, because branch (i) doesn't ask how you acquired it. The 15-year trap in the table above only actually catches business-acquisition software that also fails the off-the-shelf test — proprietary, negotiated-license, or customized software is where it bites.

The Default: 36 Months, Straight-Line, No Election Needed

IRC §167(f)(1)(A) is what actually governs software excluded from §197:

"If a depreciation deduction is allowable under subsection (a) with respect to any computer software, such deduction shall be computed by using the straight line method and a useful life of 36 months."

No election, no form to file just to get this treatment — it's simply what happens if you buy qualifying software and do nothing else. Compare that to a purchased client list's mandatory 15-year (180-month) amortization under §197(a): software's default period is one-fifth as long, even before either acceleration option below comes into play.

Worked Example: An Off-the-Shelf License, Left on the Default

A freelance real estate appraiser buys a $3,400 perpetual license to a mainstream appraisal-software product — sold to anyone off a public price list, nonexclusive terms, no customization. It's placed in service in March 2026, so 10 months of the 36-month schedule fall in the 2026 tax year.

node -e "
const cost = 3400, totalMonths = 36, monthsInService2026 = 10;
const monthlyRate = cost / totalMonths;
const defaultYear1 = monthlyRate * monthsInService2026;
console.log('monthlyRate', monthlyRate.toFixed(2));
console.log('defaultYear1', defaultYear1.toFixed(2));
console.log('section179Year1', cost.toFixed(2));
console.log('bonusYear1', cost.toFixed(2));
"

monthlyRate 94.44
defaultYear1 944.44
section179Year1 3400.00
bonusYear1 3400.00

Left on the default, only $944.44 is deductible in 2026, with the remaining $2,455.56 spread over the next 26 months. Because this license is genuinely off-the-shelf, the appraiser doesn't have to accept that — both acceleration options below get the full $3,400 into 2026 instead.

Option 1: Section 179 — Only for Software That Passes the Off-the-Shelf Test

IRC §179(d)(1)(A)(ii) defines "section 179 property" to include:

"computer software (as defined in section 197(e)(3)(B)) which is described in section 197(e)(3)(A)(i) and to which section 167 applies"

Read that cross-reference carefully: it points to §197(e)(3)(A)(i) only — the "readily available for purchase by the general public... nonexclusive license... not substantially modified" branch. It does not cross-reference branch (ii), the broader one that most standalone software purchases actually rely on to escape §197 in the first place. That gap is the whole trap: software can be perfectly ordinary, perfectly deductible-eventually, fully excluded from §197 — and still be ineligible for §179, simply because it isn't sold to the general public on off-the-shelf terms.

Like any §179 election, it's also capped at your business income for the year (it can't create or deepen a loss) and reported item-by-item on Form 4562 Part I — see the Section 179 freelancer guide for the annual dollar cap and phase-out mechanics, which apply to software exactly the same way they apply to a laptop or a truck.

Option 2: 100% Bonus Depreciation — Reaches Software §179 Can't Touch

This is the option that actually matters for the software §179 leaves behind. IRC §168(k)(2)(A)(i)(II) defines "qualified property" eligible for bonus depreciation to include:

"computer software (as defined in section 167(f)(1)(B)) for which a deduction is allowable under section 167(a) without regard to this subsection"

No off-the-shelf test. No "readily available to the general public" requirement. No nonexclusive-license condition. The only gate is the same one that got the software out of §197 in the first place and into §167(f)'s 36-month default — branch (i) or branch (ii), either one. So proprietary, negotiated-license, customized-for-you software that Section 179 flatly cannot reach is still fully bonus-eligible.

And the rate genuinely is 100%, not a phased-down figure. Before the One Big Beautiful Bill Act, §168(k)(1)(A) allowed "the applicable percentage" of basis, which was scheduled to keep sliding down from its 2017 peak. Pub. L. 119-21, §70301(b)(1)(A) struck "the applicable percentage" and substituted "100 percent," and §70301(c) made the change apply "to property acquired after January 19, 2025" — permanently, with no future sunset written back into the statute. Unlike §179, bonus depreciation has no dollar cap and no business-income limit, so it can push a Schedule C into a loss. See the bonus depreciation guide for the full §280F and loss-year mechanics that apply broadly, not just to software.

Worked Example: Proprietary Software That §179 Can't Reach

A freelance structural engineer buys an $18,000 perpetual license to a specialized load-analysis platform. It's sold only through negotiated annual contracts directly to engineering firms — never available for self-service purchase by the general public — so it fails §197(e)(3)(A)(i)'s off-the-shelf test outright, even though it still clears branch (ii) and gets the standard §167(f) treatment. It's placed in service January 2026, and the engineer's Schedule C shows $9,000 of net profit before this deduction — a slow year with one large purchase in it.

node -e "
const cost = 18000, netProfitBeforeDeduction = 9000, totalMonths = 36, monthsInService2026 = 12;
const monthlyRate = cost / totalMonths;
const defaultYear1 = monthlyRate * monthsInService2026;
console.log('monthlyRate', monthlyRate.toFixed(2));
console.log('defaultYear1 (36-month default, 12 months in 2026)', defaultYear1.toFixed(2));
console.log('netProfitAfterDefault', (netProfitBeforeDeduction - defaultYear1).toFixed(2));
console.log('section179Eligible', false);
console.log('bonusYear1', cost.toFixed(2));
console.log('scheduleCResultUnderBonus', (netProfitBeforeDeduction - cost).toFixed(2));
"

monthlyRate 500.00
defaultYear1 (36-month default, 12 months in 2026) 6000.00
netProfitAfterDefault 3000.00
section179Eligible false
bonusYear1 18000.00
scheduleCResultUnderBonus -9000.00

Left on the default, the engineer deducts $6,000 and carries $12,000 forward across the next two years. Section 179 simply isn't an option here — this software was never "readily available for purchase by the general public." Bonus depreciation is what actually gets the full $18,000 into 2026, turning a $9,000-profit year into a $9,000 Schedule C loss that can offset other income on the 1040.

Why the $2,500 De Minimis Safe Harbor Doesn't Help Here

Freelancers who know the $2,500 de minimis safe harbor for small equipment purchases sometimes assume a cheap software purchase — a $150 utility, a $400 one-time app license — can be waved through the same way. It can't, and the regulation says so in its own opening words. Treas. Reg. §1.263(a)-1(f)(1) describes what the safe harbor covers:

"...any amount paid in the taxable year for the acquisition or production of a unit of tangible property nor treat as a material or supply under § 1.162-3(a) any amount paid in the taxable year for tangible property..."

Software is intangible by its own statutory definition (§197(e)(3)(B): "any program designed to cause a computer to perform a desired function") — there's no physical unit to point to. So by the letter of the regulation, there is no dollar threshold, however small, at which a purchased software license can simply be expensed as a supply the way a $150 tool or accessory can. This mirrors exactly what the client-list amortization guide already establishes for purchased intangibles generally: no de minimis shortcut, at any price.

The practical sting is small, though. Because 100% bonus depreciation applies automatically to qualifying software with no dollar floor, a $150 purchase still gets fully deducted in the year you buy it — it just travels through Form 4562 and Schedule C Line 13 instead of Line 22, a paperwork distinction more than a tax-bill one.

Common Mistakes to Avoid

• Assuming any software purchase is a 15-year §197 intangible. That's true only for software bundled into buying an entire existing business and that also fails the off-the-shelf test — nearly all standalone software purchases, and even off-the-shelf software acquired inside a business purchase, are excluded from §197 by §197(e)(3)(A) and default to 36 months instead.
• Assuming §179 and bonus depreciation require the same test. §179 needs the software to be "described in section 197(e)(3)(A)(i)" specifically — off-the-shelf, public, nonexclusive, unmodified. Bonus depreciation under §168(k)(2)(A)(i)(II) has no such requirement.
• Expensing a small software purchase on Line 22 under the de minimis safe harbor. Treas. Reg. §1.263(a)-1(f)(1) is textually limited to tangible property; software doesn't qualify regardless of price. Use bonus depreciation on Form 4562 instead to get the same full-year deduction.
• Citing a stale bonus depreciation percentage. It's a permanent 100% since the One Big Beautiful Bill Act for property acquired after January 19, 2025 — not a phased-down figure from the pre-2025 TCJA schedule.
• Applying this post's rules to a custom-development contract. Paying someone to build new software from scratch is governed by §174's research-and-experimental-expenditure rules, not the acquisition rules covered here.
• Forgetting the §179 business-income cap when the software purchase is what caused a slow year. If income is tight in the year of the purchase, bonus depreciation — not §179 — is what actually gets the full deduction, since only bonus can create a loss.

Frequently Asked Questions

I bought a $200 app outright. Can I just expense it like office supplies, or do I have to amortize it?

Technically no — the de minimis safe harbor is limited by its own text to tangible property, and software is intangible. It defaults to §167(f)(1)'s 36-month amortization, but 100% bonus depreciation reaches it with no dollar floor, so it's still fully deductible in year one on Form 4562/Line 13 instead of Line 22.

What's the actual difference between the 36-month default and electing Section 179 on software?

The 36-month default under §167(f)(1)(A) applies automatically to any qualifying software with no election. Section 179, per §179(d)(1)(A)(ii), only reaches software described in §197(e)(3)(A)(i) — off-the-shelf, public, nonexclusive, unmodified. Software that fails that test still gets the 36-month default (or bonus depreciation) but not §179.

If software doesn't qualify for Section 179, can bonus depreciation still write it off in one year?

Yes. §168(k)(2)(A)(i)(II) defines bonus-eligible software using §167(f)(1)(B)'s definition with no off-the-shelf requirement, so it reaches proprietary and negotiated-license software §179 can't touch — with no business-income cap, unlike §179.

Does any of this apply to a monthly or annual software subscription?

No. A SaaS subscription is an ordinary business expense under §162 for ongoing access, not an acquisition — it's deducted in full the year paid on Schedule C Line 22, with no amortization question at all.

What if the software came bundled into buying an entire existing business, not as a standalone purchase?

Branch (ii)'s exclusion doesn't apply, since that's exactly the transaction it excludes from covering. But branch (i) doesn't ask how you acquired the software — so if it's independently off-the-shelf (publicly available, nonexclusively licensed, unmodified), it still escapes §197 and gets the ordinary 36-month default or bonus depreciation, per Treas. Reg. §1.197-2(c)(4), Example 2. Only software that's both bundled into a business purchase and fails the off-the-shelf test falls under §197(a)'s mandatory 15-year amortization — the same regime as a purchased client list, reported via Form 4562 Part VI to Schedule C Line 27b instead of Line 13.

I paid a developer to build custom software from scratch for my business. Is that the same as "purchased" software under this post?

No. That's a development contract, governed by IRC §174's separate research-and-experimental-expenditure rules, not the acquisition rules covered here. Confirm which framework actually applies before picking a depreciation method.

Authoritative References

• Cornell Law School Legal Information Institute — 26 U.S.C. §167(f) (36-month computer software amortization)
• Cornell Law School Legal Information Institute — 26 U.S.C. §179 (section 179 property, including the software cross-reference in (d)(1)(A)(ii))
• Cornell Law School Legal Information Institute — 26 U.S.C. §197 (amortizable intangibles and the computer software exception in (e)(3))
• Cornell Law School Legal Information Institute — 26 U.S.C. §168(k) (bonus depreciation, qualified property, and the OBBBA amendment history)
• Cornell Law School Legal Information Institute — 26 CFR §1.263(a)-1 (de minimis safe harbor, limited to tangible property)
• Cornell Law School Legal Information Institute — 26 CFR §1.197-2 (Example 2 in (c)(4) — off-the-shelf software stays excluded from §197 even when acquired as part of a business)
• Public Law 119-21 (One Big Beautiful Bill Act), §70301 — the amendment restoring 100% bonus depreciation, fetched from Cornell's amendment notes to 26 U.S.C. §168

Every Software Purchase, Filed on the Right Line

Whether it's a $200 utility or an $18,000 industry platform, the question of "Line 22 or Line 13" — and which depreciation method to use if it's Line 13 — is exactly the kind of decision that gets guessed at under deadline pressure. CentSense scans the purchase invoice, tags the expense, and keeps your software purchases organized separately from your recurring subscriptions so nothing gets miscategorized when your CPA asks for the detail behind Form 4562. Start free with 10 AI receipt scans a month, no credit card required; the Solo plan ($5/month) adds unlimited scans, mileage tracking, and a CPA-ready CSV export.

Start free →

This article is educational and not tax or financial advice. Consult a qualified tax professional about your specific situation.