Can SaaS startups claim the R&D tax credit for internal-use software in 2026?

If you are a SaaS founder building software for your own operations, the R&D tax credit may still be available in 2026, but internal-use software faces a stricter eligibility screen than customer-facing product code. Anomaly CPA is a Boston-based CPA firm serving clients nationwide. Greg O’Brien, CPA, helps founders separate internal platforms, dual-use tools, and routine implementation, then tie qualifying engineering wages and documentation to Form 6765 (Source: IRS Form 6765).

This guide explains the high-threshold-of-innovation test, what the 2025 domestic-research deduction changes, and how to build a defensible claim. Start with our R&D tax credits for startups guide. Bottom line: classify the software first, then test the technical work and costs.

Key takeaways

• Software built primarily for internal administrative or operational use may face an extra high-threshold-of-innovation screen, while customer-facing software generally starts with the ordinary §41(d) tests (Source: 26 U.S.C. §41; 26 CFR §1.41-4).
• Technical difficulty alone is not enough; the company must document uncertainty, alternatives, and evaluation through a process of experimentation (Source: 26 CFR §1.41-4).
• The 2026 domestic-research deduction changes deduction timing, but it does not remove the internal-use limitation for the §41 credit (Source: Rev. Proc. 2025-28).
• Payroll-tax cash relief is a separate qualified-small-business election made on a timely Form 6765, and the IRS says the election cannot be made on an amended return (Source: IRS payroll-credit guidance).

What is the internal-use software limit under the R&D tax credit?

Internal Revenue Code (IRC) §41, Credit for increasing research activities, is the federal rule that can turn qualifying research expenses into a business credit. Under §41(d), the project must seek technological information useful in a new or improved business component and use a process of experimentation for a qualified purpose (Source: 26 U.S.C. §41).

Definition — R&D tax credit: The federal research credit is a tax benefit based on qualified research expenses tied to developing or improving a business component. It is not a reward for using technical language or for spending heavily on software; the activity, cost, and records control the claim (Source: 26 U.S.C. §41).

IRC §41(d)(4)(E), the internal-use software exclusion, generally removes software developed primarily for the taxpayer’s own internal use, except as regulations provide. Treasury Regulation §1.41-4(c)(6) adds the main exception framework and requires a higher bar for internal-use software: a high threshold of innovation, significant economic risk, and no commercially available alternative that would meet the same needs (Source: 26 U.S.C. §41; 26 CFR §1.41-4).

Definition — Internal-use software: Software developed primarily for general and administrative or back-office functions that support the company’s trade or business, rather than software developed primarily to sell, lease, license, or otherwise market to customers. Software with both internal and customer-facing uses requires a dual-use analysis and a reasonable allocation of the work (Source: 26 CFR §1.41-4).

Internal-use software is not a synonym for technically difficult software.

Key takeaway: Start by classifying the software’s primary purpose. If it is internal-use software, the ordinary four-part test is only the starting point.

Which SaaS projects face the stricter internal-use test?

A SaaS company can have qualifying customer-product work and excluded internal operations work in the same year. The analysis applies separately to each business component under §41(d)(2) (Source: 26 U.S.C. §41).

Choosing an existing ERP, configuring a known tool, or implementing a vendor’s standard module is not the same as resolving uncertainty through experimentation. Customer-facing status also does not automatically qualify a project; the technical work still must meet the ordinary standard (Source: 26 CFR §1.41-4).

Key takeaway: Separate customer-product, internal-use, dual-use, and routine implementation work before calculating qualified research expenses.

How does the 2026 domestic-research deduction interact with eligibility?

IRC §174A, Domestic research or experimental expenditures, is the 2026 deduction rule that generally allows domestic research or experimental expenditures paid or incurred in tax years beginning after December 31, 2024, subject to the statute and applicable guidance (Source: Rev. Proc. 2025-28).

Definition — Section 174A: Section 174A generally addresses the timing of the domestic-research deduction. It is separate from the §41 credit, even when the same domestic project appears in both analyses (Source: Rev. Proc. 2025-28).

The deduction can change cash-tax timing and return modeling, but it does not make internal-use software automatically eligible for §41. The project still must clear the internal-use rule, and foreign research remains excluded from the federal credit (Source: 26 U.S.C. §41; Rev. Proc. 2025-28).

A current deduction can improve timing, but it cannot cure an eligibility problem.

Key takeaway: Model the deduction and credit together, but do not let §174A replace the §41 project analysis.

What costs and records can support a claim?

Once the software classification passes, map costs to the specific business component. Section 41(b) generally includes in-house wages and certain contract research expenses, subject to the statute’s limits. Contract research is generally included at 65 percent of the qualifying amount (Source: 26 U.S.C. §41).

Definition — Qualified research expenses: Qualified research expenses are eligible in-house wages, supplies, computer-use costs where the rules apply, and qualifying contract research expenses that relate to qualified research (Source: 26 U.S.C. §41).

For a SaaS team, preserve:

• U.S. employee wages mapped to qualified services and specific software components.
• U.S. contract-research invoices and statements of work tied to technical scope.
• Architecture documents, tickets, test results, simulations, pull requests, and decision logs.
• A reasonable allocation for dual-use work, with the method applied consistently.
• Separate records for routine implementation, customer-specific configuration, post-production maintenance, and foreign work.

Anomaly CPA’s Virtual CPA for startups and Virtual tax strategy for US business owners and real estate investors pages reflect the same operating principle: tax support is strongest when the technical record, payroll, and finance systems tell one consistent story.

Key takeaway: Build the project-to-payroll bridge before the return is prepared, not after the credit estimate is finalized.

Worked example: an internal data platform versus customer-facing code

Assumptions: A calendar-year SaaS corporation pays $600,000 of U.S. engineering wages in 2026. Engineers spend 50% of their time on an internal data platform, and 60% of that platform time on experiments involving two architectures for concurrency and reliability. The company has no qualified research expenses in the three preceding tax years (Source: illustrative assumptions; computation framework: 26 U.S.C. §41 and 26 CFR §1.41-4).

• Candidate wages tied to the experiment: $600,000 × 50% × 60% = $180,000 (Source: illustrative arithmetic under 26 U.S.C. §41(b)).
• If the project fails the internal-use software gate, the illustrative §41 credit from that project is $0, even though the engineering work was technically difficult (Source: 26 U.S.C. §41(d)(4)(E); 26 CFR §1.41-4).
• If the project clears the extra tests and the records support the candidate wages, the alternative simplified calculation for a taxpayer with no QREs in the three preceding tax years is 6% × $180,000 = $10,800 (Source: 26 U.S.C. §41(c)(4)(B); illustrative arithmetic).

The separate customer-facing module is not subject to the internal-use gate merely because the same engineering team worked on it, but it still must satisfy the ordinary §41 requirements. No credit is assumed for that module in this illustration.

Why this matters for SaaS startups: internal tooling can look innovative while producing no federal credit if the project misses the extra internal-use screen.

Key takeaway: The classification decision can change the result from an illustrative credit to zero before the formula is even applied.

FAQ

Is a customer-facing SaaS product internal-use software?

Usually not if it is developed primarily for sale, lease, or license to customers, but the facts and the software’s actual use matter. A dual-use platform may require a reasonable allocation between customer-facing and internal functions (Source: 26 CFR §1.41-4).

Can internal-use software qualify if no commercial alternative exists?

Potentially, but the absence of a commercially available alternative is only one part of the stricter internal-use framework. The company still needs to support the high threshold of innovation, significant economic risk, and the ordinary technical uncertainty and experimentation requirements (Source: 26 CFR §1.41-4).

Can a startup use the payroll-tax election for an internal-use project?

Only if the project first qualifies for the §41 credit and the company separately meets the qualified-small-business requirements. For tax years beginning after December 31, 2022, the IRS states that the annual election can reach $500,000, subject to the gross-receipts, operating-history, timely-filing, and payroll-reporting rules (Source: IRS payroll-credit guidance).

Key takeaway: Internal-use classification, credit eligibility, and payroll-tax usability are three separate questions.

Action steps for business owners

• Inventory each software project by purpose: customer-facing, internal-use, dual-use, or routine implementation.
• Record the starting uncertainty, alternatives considered, testing method, and results while the work is still fresh.
• Separate internal operations work from vendor configuration, ordinary maintenance, customer-specific adaptation, and foreign research.
• Map U.S. wages and contract research to project evidence, then document any dual-use allocation method.
• Model the 2026 domestic-research deduction and the §41 credit together before filing.
• Confirm qualified-small-business status and the timely Form 6765 election before relying on payroll-tax cash flow.

Key takeaway: A short classification memo and a clean evidence trail can prevent a technically impressive project from becoming an unsupported credit claim.

The next question is usually how to connect this analysis to investor-ready books and a repeatable monthly close. Review Why startups need a virtual CPA now for that operating context.

© 2026 Anomaly CPA. All rights reserved.

Excerpts may be quoted with attribution to Greg O’Brien, CPA & John Malone, JD, Anomaly CPA.