Software R&D tax credits 2026 are one of the most common qualifying activities for the R&D tax credit, yet many software companies miss out because they either don’t know the rules or assume they don’t qualify. Here is what you need to know.
The Four-Part Test for Software R&D Tax Credits 2026
To qualify, your software activities must meet all four IRS requirements under IRC Section 41.
1. Permitted Purpose
Your work must aim to improve functionality, performance, reliability, or quality of the software. Small incremental improvements count—you don’t need a breakthrough.
Examples:
-
Improving processing speed
-
Reducing memory usage
-
Enhancing system reliability
-
Building new features that require novel coding techniques
2. Technological in Nature
The work must rely on computer science principles. Building a marketing funnel does not qualify; developing a novel algorithm to optimize that funnel’s performance does.
Examples:
-
Developing new algorithms or architectures
-
Creating novel data structures
-
Engineering custom APIs for complex integrations
3. Elimination of Technical Uncertainty
You must face uncertainty about capability, method, or design at the project’s outset. “Will customers buy this?” is commercial uncertainty and does not count. “Can we make this work within our performance constraints?” is technical uncertainty and does count.
What creates uncertainty:
-
Unknown whether a new approach will meet speed requirements
-
Uncertainty about which architecture will work
-
Questions about scalability at expected load
4. Process of Experimentation
You must show systematic evaluation through modeling, simulation, or trial and error. Accidentally stumbling on a solution does not count. You need documentation showing multiple approaches were tested and evaluated.
Qualifying activities:
-
A/B testing different architectures
-
Performance testing and optimization iterations
-
Prototyping and iterative design changes
Failed projects count. The IRS rewards experimentation, not just success.
Internal Use Software: The HTI Test
Software used internally for general and administrative functions (HR, finance, internal data processing) is subject to stricter rules. This is called Internal Use Software (IUS).
Internal use software faces stricter rules under software R&D tax credits 2026, including the High Threshold of Innovation test.
For IUS to qualify, it must meet the HTI test:
1. Innovative: The software must result in a significant, measurable reduction in cost or improvement in speed.
2. Significant Economic Risk: The company must commit significant resources with substantial uncertainty about recovery.
3. Not Commercially Available: The software cannot be purchased, leased, or licensed and used without significant modification.
The HTI test is difficult to meet. Most internal-use software projects do not qualify unless they are truly groundbreaking.
Third-Party Subset: The Exception
If your software allows third parties to interact with your systems, you may be able to carve out those external-facing functions and avoid the HTI test.
What qualifies: Code and development costs dedicated solely to enabling third-party interaction—like customer portals, APIs for partners, or vendor-facing platforms.
Why it matters: Successfully segregating these external functions means the associated expenses are evaluated under the standard four-part test instead of the HTI test.
Critical rule: If the third-party subset is challenged and disallowed, the entire project reverts to IUS classification and must pass the HTI test.
What Activities Qualify
Common qualifying software activities include:
Algorithm Development
-
Creating or improving machine learning models
-
Neural network development
-
Proprietary search algorithms
-
Data compression techniques
System Integration
-
Developing custom APIs for complex platform integration
-
Novel data structures for dissimilar systems
-
Integration methods not readily apparent
Operating System & Security
-
New OS compatibility layers
-
Sophisticated encryption methods
-
Unique cybersecurity protocols
Performance Engineering
-
Optimizing code and re-architecting for speed
-
Reducing memory usage
-
Improving throughput through systematic testing
UX Architecture
-
Real-time collaboration features
-
Complex data visualization requiring novel coding techniques
-
High-performance user interfaces
What Does Not Qualify
-
Routine maintenance: Bug fixes, minor updates, and ongoing maintenance do not qualify.
-
UI/UX design without technical uncertainty: Purely cosmetic design changes with no technical challenge do not qualify.
-
Customizing a CRM: Standard configuration, drag-and-drop customization, or data entry does not qualify.
-
Routine testing: Quality assurance with no technical uncertainty does not qualify.
Understanding software R&D tax credits 2026 also means knowing what does not qualify—routine maintenance and UI/UX design without technical uncertainty.
New OBBBA Rules for 2026
Immediate Expensing Is Back
For tax years beginning after December 31, 2024, software companies can once again deduct domestic R&D expenses in the year incurred. This reverses the five-year amortization requirement that took effect in 2022.
Payroll Tax Offset for Startups
Pre-revenue software companies can apply up to 500 thousand of R&D credits against payroll taxes annually. To qualify: under 5 million in gross receipts and within five years of first revenue.
Form 6765 Section G Reporting
For tax year 2026, most R&D filers must report project-level detail on Form 6765, breaking out QREs by business component. Exemptions apply for qualified small businesses electing the payroll tax credit and taxpayers with under 1.5 million in QREs and under 50 million in gross receipts.
Documentation Best Practices
The IRS expects contemporaneous records—not reconstructed studies assembled years later.
What to track:
-
Project records with technical objectives
-
Documentation of uncertainties and experimentation processes
-
Time allocation by employee and project
-
Records linking expenses to specific qualifying activities
How to track it:
-
Use project codes for R&D time
-
Quarterly surveys capture activities and time allocation better than year-end reconstruction
-
Maintain version control history and engineering notebooks
Bottom Line
R&D tax credits for software companies are real. Algorithm development, system integration, performance engineering, and even internal tools with a third-party subset can qualify.
The 2026 rules offer immediate expensing, retroactive relief for small businesses, and payroll tax offsets for startups.
Call (844) 463-2400 or email hello@indagotax.com to find out what qualifies in your software company.