Tax for Software Developers

Section 174 — Immediate Domestic R&D Expensing Restored by OBBBA

Section 174 is the single most important tax provision for software developers. The TCJA (2017) amended Section 174 to require capitalisation and 5-year amortisation of domestic R&D expenditures and 15-year amortisation of foreign R&D, effective for tax years beginning after December 31, 2021. The OBBBA reversed this, restoring immediate deductibility for domestic research and experimental expenditures for tax years beginning after December 31, 2024.

For freelance software developers, this means the cost of developing software — salaries paid to subcontractors, cloud computing costs allocable to development, and the developer's own time where it can be separately accounted for — is fully deductible in the year incurred rather than capitalised over 5 years. This eliminates the phantom income problem where developers owed tax on income they had already spent on R&D.

The critical classification question is Section 174 vs Section 162. Building a new feature for a client's existing product using established frameworks is likely Section 162 (ordinary business expense). Developing a novel algorithm, building a prototype SaaS tool, or creating experimental software is Section 174. Many developers do both — client work (Section 162) and product development (Section 174). Maintaining separate project tracking for each category is essential for audit defence.

Foreign R&D remains subject to 15-year amortisation. A developer who outsources coding to overseas subcontractors must capitalise those costs even though domestic costs are immediately deductible.

Domestic research and experimental expenditures, including software development costs, are immediately deductible in the year incurred. Foreign R&D remains subject to 15-year amortisation. (IRC §174(a) as amended by OBBBA §70302 (2025); Treas. Reg. §1.174-2)

Remote Work and Multi-State Filing Obligations

Freelance software developers routinely serve clients in multiple states while working from a single home base. Post-pandemic remote work has amplified multi-state tax exposure. The threshold question is whether the developer has income tax nexus in a client's state.

Most states follow the 'income sourcing' rule that service income is sourced to the state where the benefit of the service is received (i.e., where the client is located). A developer in Colorado building software for a California client may owe California income tax on that revenue — California aggressively asserts the 'convenience of the employer' doctrine and sources income based on where the client receives the benefit, even for remote workers who never set foot in California.

New York applies a similar 'convenience of the employer' test that can pull remote workers into NY filing obligations if they serve NY-based clients. The practical threshold is materiality — states rarely pursue small filers, but a developer billing $50,000+ to clients in a single state should investigate that state's filing requirements.

Protection: the Mobile Workforce State Income Tax Simplification Act has been repeatedly proposed in Congress but has not passed. Until it does, developers must evaluate nexus state by state. States without income tax (TX, FL, WA, TN, NV, WY, SD, NH for earned income, AK) eliminate this concern for client work sourced there.

Service income is generally sourced to the state where the client receives the benefit. Some states apply 'convenience of the employer' doctrine to tax remote workers serving in-state clients. (Cal. Rev. & Tax. Code §17951; N.Y. Tax Law §631; individual state sourcing rules)

S-Corporation Election and Reasonable Compensation

The S-Corp election under IRC Section 1362 is the most common tax-optimisation structure for software developers earning above $120,000 net. By paying yourself a reasonable W-2 salary and taking remaining profits as shareholder distributions, you avoid self-employment tax (15.3%) on the distribution portion. The IRS requires 'reasonable compensation' — a salary comparable to what you would earn in the open market for similar work.

For software developers, the IRS and Tax Court have established that reasonable compensation considers the developer's skills, experience, geographic market, and hours worked. A full-stack developer in Denver earning $155,000 net might set a reasonable salary of $85,000–$95,000 based on Bureau of Labor Statistics data for Colorado software developers. The remaining $60,000–$70,000 flows through as S-Corp distributions, saving approximately $9,180–$10,710 in SE tax.

The costs of maintaining an S-Corp include payroll processing ($1,500–$3,000/year), quarterly payroll tax filings, annual Form 1120-S preparation ($1,000–$2,500 for a CPA), and state franchise/registration fees. These costs create a breakeven point: below approximately $80,000 net, the SE tax savings rarely exceed the administrative costs. Above $120,000, the savings are almost always material.

S-Corp shareholders who are also employees must receive reasonable compensation for services performed, subject to FICA taxes. Distributions above reasonable salary are not subject to SE tax. (IRC §1362; IRC §3121(a); Rev. Rul. 74-44; Watson v. United States, 668 F.3d 1008 (8th Cir. 2012))

Equipment, Cloud Services, and the De Minimis Safe Harbour

Software developers are equipment-heavy relative to other freelancers. Laptops, external monitors, servers, networking equipment, and peripherals are core business tools. The de minimis safe harbour under Treas. Reg. 1.263(a)-1(f) allows immediate expensing of tangible property costing $2,500 or less per item per invoice (or $5,000 if the taxpayer has an applicable financial statement). Items above this threshold can be expensed under Section 179 (up to the OBBBA limit) or bonus depreciation.

Cloud computing costs — AWS, Azure, GCP, Vercel, Netlify, DigitalOcean — are ordinary business expenses deductible under Section 162 when used for client projects. Cloud costs allocable to R&D activities (Section 174) are also deductible immediately under the OBBBA restoration. The distinction matters primarily for documentation and audit trail purposes.

Software subscriptions (JetBrains, GitHub Enterprise, VS Code extensions, CI/CD tools) are deductible as ordinary business expenses. A developer spending $400/month on cloud infrastructure and $200/month on software tools deducts $7,200 annually on Schedule C. For S-Corp filers, these flow through the corporate return and reduce the income available for distribution.

Tangible property costing $2,500 or less per item may be immediately expensed under the de minimis safe harbour without capitalisation. Items above this threshold qualify for Section 179 expensing or bonus depreciation. (Treas. Reg. §1.263(a)-1(f); IRC §179; IRC §168(k))