Why software development was swept into Section 174 — and what 174A changes

For tax years beginning after 2021, the Code contains a sentence with outsized consequences: any amount paid or incurred in connection with the development of any software is treated as a research or experimental expenditure. No uncertainty test, no experimentation analysis — software development is Section 174 by definition. During 2022–2024, that meant mandatory capitalization; since the OBBBA, it means domestic software work is expensed under Section 174A while foreign work stays on a 15-year schedule.

How the sweep worked, and why it hurt

Before 2022, software developers lived comfortably under Rev. Proc. 2000-50, which permitted current deduction of software development costs whether or not they satisfied the Section 174 uncertainty standard. The TCJA revoked that comfort prospectively and replaced it with the opposite categorical rule. The drafters' logic was administrative: rather than litigate which sprints involved genuine technical uncertainty, treat the whole category as research.

Combined with mandatory capitalization, the sweep produced the sharpest cash-tax shock of the amortization era. A software company's dominant cost — engineering compensation — went from fully deductible to 10% deductible in year one (five-year amortization, half-year convention). Notice 2023-63 confirmed the breadth: the capitalized pool included not just coders' salaries but allocable overhead, and covered internal-use software, websites, and apps alongside products for sale. Profitable software companies saw taxable income multiples of book income; pre-revenue startups saw taxable income appear where losses used to be. The worked numbers are in our Section 174 pillar guide.

The boundaries mattered and still do. "Development" runs from planning through testing until the software is ready for its intended use, plus later enhancements that add functionality. Outside it: routine maintenance, bug fixes without enhancement, data conversion, training, configuration of purchased software short of customization-as-development, and hosting or SaaS fees for software merely used. During the capitalization years the IRS watched for development recast as "maintenance"; those characterizations still govern the 2022–2024 balances moving through the transition rules.

What Section 174A changes — and what it doesn't

For tax years beginning after December 31, 2024, domestic software development is immediately deductible under Section 174A, with an optional election to capitalize over at least 60 months. For a U.S.-based engineering organization, the practical effect is a return to the pre-2022 cash-tax world.

Three things did not change:

• The classification itself. Software development remains statutorily an R&E expenditure. That matters because classification, not deduction timing, drives the remaining consequences.
• Foreign development. Work performed by engineers outside the United States — offshore subsidiaries, foreign contract development shops, employees working remotely abroad — remains a foreign SRE expenditure amortized over 15 years under Section 174. For distributed engineering teams, the domestic/foreign split is now the whole ballgame; see the foreign research brief.
• Credit coordination. Section 174 eligibility remains the gateway to the Section 41 research credit, but the sweep does not make all software work creditable — Section 41(d)'s four-part test, and the heightened internal-use software standards, still apply. A company's deductible software pool will exceed its credit-qualified pool, often substantially. See what the R&D credit is.

The residue of the amortization era — unamortized 2022–2024 software costs — comes back through the one- or two-year catch-up or, for small businesses, amended returns; the modeling lives in the transition rules guide.