How Does the Software R&D Credit Work for Tech Companies in 2026?

The software R&D credit, rooted in IRC Section 41, reduces your federal income tax liability dollar for dollar rather than simply lowering your taxable income. For SaaS founders and technology operators, the primary qualifying cost is engineering wages your team is already earning, so you are capturing tax value from work already underway rather than creating new spending.

What activities actually qualify?

Every activity included in a software R&D credit claim must pass the IRS four-part test:

• Permitted purpose: The work must aim to create or improve a product, process, or software function in terms of functionality, performance, reliability, or quality.
• Technological in nature: The development process must rely on engineering principles or computer science. Software development naturally satisfies this element.
• Elimination of uncertainty: There must have been genuine technical uncertainty at the outset about whether the approach could achieve the desired result. Business uncertainty about market reception does not count.
• Process of experimentation: The team must have used an iterative process to test alternatives. Agile sprints, A/B testing, prototyping, and iterative debugging all satisfy this requirement.

Common disqualifiers include off-the-shelf software customization, purely aesthetic UI redesigns, post-release bug fixes that add no new functionality, and third-party platform configuration. Software built primarily for internal use faces an additional, higher bar: it must also be innovative, represent significant economic risk, and not be commercially available. The IRS outlines this elevated standard in Treasury Regulation 1.41-4 on internal-use software.

How is the credit calculated?

The IRS provides two approved methods, both applied to the same pool of Qualified Research Expenditures (QREs). The IRS Form 6765 instructions walk through both calculations in detail.

Regular Research Credit (RRC): Equal to 20% of QREs that exceed a calculated base amount tied to historical gross receipts. This method can produce a larger credit but requires more historical data.

Alternative Simplified Credit (ASC): Equal to 14% of QREs that exceed 50% of the average QREs from the prior three years. This is the more commonly used method for software companies that lack clean historical R&D records.

QREs for software companies typically include:

• W-2 wages paid to employees performing qualified research (usually the largest bucket)
• Domestic contractor payments, which qualify at 65% of the amount paid
• Foreign contractor payments, which qualify at 0%
• Supply costs, which are minimal for most software businesses
• Cloud computing costs, where IRS guidance continues to evolve in 2026

As a practical illustration: a SaaS company with $1 million in qualified engineering wages using the ASC method, where average prior-year QREs were $800,000, would calculate 50% of $800,000 as $400,000. The excess is $600,000, and 14% of that produces an $84,000 credit applied directly against taxes owed. According to Kiplinger's analysis of R&D credit strategies, SaaS companies typically qualify 60 to 85% of total engineering wages, and the average credit represents 7 to 10% of total engineering payroll.

For more on what counts as a qualified research expense, see our post on 5 Ways to Maximize Qualified Research Expenses in 2026.

How does the Section 174 amortization rule affect this?

Under the Tax Cuts and Jobs Act, R&D costs can no longer be fully expensed in the year incurred. They must now be amortized over five years for domestic activities and fifteen years for foreign activities. According to Treasury Department analysis of TCJA R&D provisions, this change meaningfully increased the effective tax burden on domestic research investment.

The software R&D credit does not reverse the Section 174 amortization requirement, but it operates as a separate, parallel benefit that can partially offset the increased cost. There is also an interaction to model carefully: under IRC Section 280C, claiming the full credit requires reducing your Section 174 deduction by the credit amount. Alternatively, you can elect a reduced credit equal to 87% of the calculated amount without reducing the deduction. For companies in higher tax brackets, running both scenarios before filing is worthwhile. The IRS guidance in Publication 334 covers the Section 280C reduced credit election. The AICPA's resources on Section 174 and the R&D credit address how these two provisions interact strategically.

Legislative proposals to restore immediate expensing under Section 174 have surfaced in 2026, but as of October 2026 no such restoration has been enacted.

Can startups use this credit before they are profitable?

Yes. Under the PATH Act, IRC Section 41(h) allows qualifying small businesses to apply the software R&D credit against employer payroll taxes rather than income tax. To qualify, a company must have less than $5 million in gross receipts and must be within the first five years of having gross receipts. The maximum annual payroll tax offset is $500,000.

For a pre-revenue SaaS company with $600,000 in total engineering payroll where 70% is qualified, the QRE pool is $420,000. At a 14% ASC rate, that produces approximately $58,800 in credit that can be applied against quarterly payroll tax deposits through Form 6765 and carried to Form 941. Fewer than 20% of eligible startups claim this election, which means a significant number of early-stage companies are leaving real cash on the table.

If your company qualifies, our team covers the mechanics in detail in our post on the R&D Payroll Offset for High Earners.

What mistakes most often reduce or kill the credit?

The IRS has increased audit scrutiny of R&D credit claims, and the IRS R&D Credit Audit Techniques Guide outlines exactly what agents examine. The most common problems are:

Retroactive documentation. The IRS requires contemporaneous records created during development, not reconstructed at tax time. Project narratives, sprint logs, git commits, and time-tracking records need to exist as the work happens.

Including non-qualifying activities. Post-release bug fixes with no new functionality, routine maintenance, and business feasibility analysis do not pass the four-part test. Including them exposes the entire claim to challenge.

Ignoring contractor geography. Foreign contractor payments are excluded entirely from QREs. Agreements with contract developers should explicitly specify that work is performed domestically.

Missing the internal-use software rules. Software built for internal operations faces the elevated three-part standard described above. Applying only the standard four-part test to internal tools is a frequent audit trigger.

Inflated claims from promoters. The IRS has flagged inflated R&D credit claims as an ongoing audit priority. Claims built on vague activity descriptions and unsupported time allocations carry a 30 to 40% disallowance rate on audit, according to IRS reporting.

What should you do before year-end 2026?

A few concrete steps can materially affect both the size and defensibility of a software R&D credit claim before December 31:

• Pull engineering payroll data through Q3 now and estimate your credit range rather than waiting until filing season.
• Deploy time-tracking tools such as Harvest, Toggl, or Jira time logs if your engineers are not already tracking time by project. The "substantially all" rule allows the full wage to qualify when 80% or more of an employee's time is spent on qualified research, so precise allocation records matter.
• Confirm that all contractor agreements specify U.S.-based work and exclude any offshore payments from your QRE calculation.
• Model whether the payroll tax offset election is available if your company is pre-profit and within its first five years of gross receipts.
• Assess whether amended returns for prior open tax years could generate refunds or carryforwards. Unused credits can be carried forward for up to 20 years.
• Work with a qualified tax advisor before year-end. Our team also recommends reviewing your broader year-end picture alongside the credit; the R&D Credit Claim Deadline post covers timing rules that affect when and how claims must be filed.

The software R&D credit is not self-executing. It rewards companies that plan deliberately, document throughout the year, and integrate the credit into a broader tax strategy rather than treating it as a last-minute filing exercise.