R&D Tax Credit for Software Startups: §41, §174, and the $500K Payroll Offset

If you run a venture-backed SaaS company in San Jose or Palo Alto, are paying eight or ten engineers $200K each to write code, and have never claimed the federal R&D tax credit, you are leaving real money on the table. A pre-revenue startup with $2 million in qualifying engineering salaries can typically generate $130,000 to $200,000 in federal R&D credit. Because you are pre-profit, that credit does nothing against income tax. But under the §41(h) payroll tax election, that same credit can offset up to $500,000 per year of your employer Social Security and Medicare tax, starting the quarter after you file.

The credit has been around since 1981. Two things changed recently that make it more important to understand: the §174 capitalization rule that the Tax Cuts and Jobs Act layered in starting in 2022 (which gutted startup losses for three years), and the One Big Beautiful Bill Act (OBBBA, Public Law 119-21, signed July 4, 2025), which partially unwound it for tax years beginning after December 31, 2024. If you have not revisited your R&D position since 2024, you are likely missing both retroactive recoveries and ongoing benefit.

This guide walks through the §41 credit itself, the four-part qualification test as applied to software, the §174 capitalization rule and its 2025 rollback, the payroll offset mechanics, and the documentation an IRS exam will actually want to see. We work through this fact pattern constantly with our startup founder team at Silicon Valley Tax.

The Big Picture: §41 in Two Sentences

IRC Section 41 gives you a federal income tax credit equal to a percentage of your qualified research expenses (QREs) above a base amount. Under the Alternative Simplified Credit (ASC) method, a first-time filer with no prior-year base receives 6 percent of total QREs. As the company builds a three-year base history, the credit rises toward the statutory 14 percent of incremental QREs above 50 percent of the prior-three-year average. Most software startups land in the 6 to 10 percent range of total QREs through their first few years.

The credit is permanent (locked in by the PATH Act of 2015) and dollar-for-dollar against tax liability. For a profitable company, every $1 of credit reduces federal tax by $1. For a pre-profit startup, the credit either carries forward up to 20 years or, if you qualify as a Qualified Small Business (QSB), gets monetized against payroll tax.

The Inflation Reduction Act of 2022 amended §41(h) to double the payroll-tax offset cap from $250,000 to $500,000 per year, effective for tax years beginning after December 31, 2022. The first $250,000 still offsets the employer 6.2% Social Security portion; the second $250,000 offsets the employer 1.45% Medicare portion. Many startups still file as if the cap were $250K. It is not.

The Four-Part Test (IRC §41(d))

Every dollar of QRE has to map to a "business component" (a product, process, software, technique, formula, or invention) that passes a four-part test. Apply the test once per business component, not once per company. A typical SaaS startup will have several business components: the core platform, each major new feature, the internal data pipeline, the ML model, and so on.

1. Permitted purpose

The research must be intended to develop a new or improved business component for purposes of function, performance, reliability, or quality. Cost reduction alone counts. Aesthetic changes (rebrand, color palette, UI polish that is not performance-driven) do not.

2. Technological in nature

The work must fundamentally rely on the hard sciences: computer science, engineering, biology, chemistry, physics. Software engineering qualifies. UI/UX design as such does not, although the back-end engineering supporting a new UI usually does.

3. Process of experimentation

You must be evaluating one or more alternatives through systematic trial and error, modeling, simulation, or other methods. "We built the obvious solution and shipped it" fails. "We benchmarked three database engines, ran load tests, and iterated on the data model until p99 latency dropped below 100ms" passes.

4. Uncertainty

At the outset of the work, there must be uncertainty about capability (can this be built?), method (what approach will work?), or design (which design will achieve the requirements?). Stack already proven and documented in vendor SDK examples? Probably no uncertainty. Novel ML architecture, new distributed systems pattern, or first-of-its-kind integration? Real uncertainty.

You do not need every project to be groundbreaking. Most qualifying software work is incremental: shipping a new feature that requires new architecture, optimizing a slow query path through systematic profiling, building a new ML pipeline. The bar is "uncertainty at the outset that you resolved through experimentation," not "patent-grade novelty."

Software-Specific Gotchas

Two software-specific rules trip up startups regularly.

Internal Use Software (IUS)

Software developed primarily for the taxpayer's own internal use (back-office systems, internal data warehouses, employee-only tools) has to clear a higher three-part test on top of the §41(d) four-part test: it must be innovative, involve significant economic risk, and not be commercially available. This is a meaningful hurdle. A startup building its own ERP-like internal admin tool will struggle to claim those engineering hours.

The good news for most SaaS founders: customer-facing software (your product) is explicitly not internal use software. Dual-function software (used both internally and by customers) is split by a safe harbor under Treasury Reg §1.41-4(c)(6)(vi): if at least 10% of the use is by third parties (customers), the third-party portion escapes the IUS restriction. For a normal SaaS company shipping a product to paying customers, IUS is rarely a blocker.

Funded research

Research that is "funded" by a third party (a customer contract under which they pay you to perform research and they retain rights) generally does not qualify under §41(d)(4)(H). Two prongs: payment is not contingent on success (you get paid even if it fails) AND you do not retain substantial rights in the result. If both prongs are true, the work is funded and disqualified.

Typical SaaS pattern: ARR subscription customers who pay for product access do not "fund" your research because their payment is contingent on the product actually working, and you retain all IP. That is unfunded and qualifies. Custom dev shop contracts with milestone payments and a full IP assignment to the client? Funded, generally disqualified.

What Counts as a Qualified Research Expense

Three categories of cost roll into QREs:

1. Wages of researchers (W-2, Box 1). The biggest bucket for software startups. Includes engineers writing code, technical leads supervising research, and direct support staff (QA testing the research, data labelers feeding the ML training). Does not include sales, marketing, HR, general management, or anyone who does not directly perform, supervise, or directly support qualifying research. The "substantially all" rule of Reg §1.41-2(d)(2) lets you count 100% of an employee's wages if at least 80% of their time is on qualifying research.
2. 65% of US contractor payments. If you pay a US-based 1099 contractor to perform research, 65% of what you pay them counts as QRE. Foreign contractors do not qualify. The contractor's work must meet the §41(d) test in its own right.
3. Supplies consumed in research. Cloud compute used for ML training runs, prototype hardware, lab consumables. Does not include general operating SaaS subscriptions, office supplies, depreciable property, or land. The supplies must be consumed or used up in the research itself.

Engineer wages typically make up 85 to 95 percent of total QRE for a software startup. AWS bills used for ML training can be a meaningful fourth bucket for AI companies.

The §174 Capitalization Disaster (2022 to 2024)

For tax years beginning in 2022 through 2024, the Tax Cuts and Jobs Act required all R&D expenditures to be capitalized and amortized rather than deducted in the year incurred. Under the new IRC §174, domestic R&D had to be capitalized over 5 years (half-year convention, so you got 10% in year one) and foreign R&D over 15 years.

For startups, this was financially catastrophic. A company spending $2 million on engineering salaries used to deduct the full $2M, producing a $2M net operating loss that carried forward to offset future income. Under the post-2022 §174 rule, that same $2M generated only $200K of year-one deduction, leaving $1.8M of "phantom income" still on the books even though every dollar had been spent on payroll. Profitable-on-paper, cash-poor-in-reality startups had to pay tax on income they had already spent.

The Build Back Better Act, the EARN Act, the Tax Relief for American Families and Workers Act, and several other 2023 and 2024 bills proposed restoring immediate expensing. None made it into law in time to help the 2022, 2023, or 2024 tax years.

The OBBBA 2025 Partial Restoration

The One Big Beautiful Bill Act of 2025 finally addressed §174 for tax years beginning after December 31, 2024. The headline change:

• Domestic software R&D: full expensing restored. Software development costs incurred in the United States can again be deducted in the year incurred under amended §174A.
• Foreign R&D: still capitalized over 15 years. The foreign capitalization rule was not repealed. If your engineering is done by overseas contractors or a foreign subsidiary, those costs continue to amortize over 15 years.
• Retroactive election for small business taxpayers. Eligible small businesses (those meeting the §448(c) average gross receipts test) can elect to expense their 2022, 2023, and 2024 domestic §174 amounts by filing amended returns. The amended returns recover taxes paid on the phantom income from the prior three years.

If your startup paid federal income tax in 2022, 2023, or 2024 because of §174 capitalization, you very likely have a refund coming via amended returns. Run the §448(c) gross-receipts test (under $31 million average for the three prior years for 2025) and, if eligible, file the §174 retroactive election. We have seen six and seven-figure refunds on this.

Payroll Offset Mechanics

The payroll-tax offset is the headline benefit for pre-profit startups. Eligibility:

• Qualified Small Business (QSB): gross receipts under $5 million in the year you are claiming the offset, AND
• No gross receipts for any tax year preceding the five-tax-year period ending with the current year. In plain English: you have to be in your first five years of having any revenue at all. If you started recognizing revenue more than five years ago, you are no longer a QSB for this purpose.

The mechanics, year by year:

1. Claim the credit on Form 6765. Calculate your QREs and the resulting credit. Attach Form 6765 to your timely-filed federal income tax return (including extensions). On Form 6765, make the §41(h) election to apply some or all of the credit against payroll tax. The 2024 redesign of Form 6765 added Section G, which requires detailed business component reporting for most filers.
2. Receive Form 8974 with the credit amount. The IRS does not issue a refund check. Instead, the credit becomes available to claim on Form 8974, attached to your quarterly Form 941 employer's payroll return. The credit becomes claimable starting the first quarter after the income tax return is filed. If you file your 2025 income tax return in April 2026, the offset starts on your Q2 2026 Form 941 (the return covering April through June 2026).
3. Offset employer Social Security and Medicare. The first $250,000 of credit offsets the employer 6.2% Social Security portion until exhausted. Any remaining credit then offsets the employer 1.45% Medicare portion, up to the additional $250,000 cap. Unused credit carries forward to the next quarter, then the next year, until used.
4. Use the credit until burned through, then re-elect. The election is annual. Make it every year you remain a QSB and have qualifying credit to monetize.

A startup with $2M in QREs and a Section G-supported $200K credit can offset roughly $200K in employer payroll tax over the next four quarters, which on a 20-engineer team is real money against burn.

Documentation the IRS Will Actually Want

The R&D credit is one of the most-audited federal credits. In Siemer Milling Co. v. Commissioner, T.C. Memo. 2019-37, the Tax Court denied a substantial portion of claimed R&D credits because the taxpayer could not tie its claimed activities to specific business components, could not show the four-part test had been applied per component, and produced documentation that was largely reconstructed after the fact. The same pattern repeats across most R&D credit denials. Do not file an R&D claim without these:

• Project-level documentation: for each business component claimed, a short write-up of what was built, the uncertainty at the outset, the alternatives considered, and the experimentation performed. Engineering design docs, RFCs, and architecture review notes are exactly what the IRS wants. Pull them contemporaneously, not at audit time.
• Time tracking by project. If your engineers track time at all (Jira tickets, GitHub commits, sprint planning notes), preserve it. If they do not, implement a quarterly survey where each engineer estimates their split across qualifying projects. Verbal interviews documented in writing are acceptable but weaker than ticket-level data.
• Payroll records: W-2 Box 1 wages by employee, plus a clear mapping of which employees did qualifying work and what percentage of their time. Section G of the redesigned Form 6765 essentially requires this mapping.
• Contractor agreements: for any 65% contractor QRE, the contract itself, evidence it was unfunded research, and evidence the contractor was US-based.
• Cloud bills for supplies: for AWS, GCP, or Azure spend allocated to research, the underlying invoices and a method showing how you split research compute from production compute.

The credit is worth claiming, but only if the documentation will survive a desk audit. Filing a paper-thin Form 6765 with no project documentation is worse than not filing at all because it puts your return into the audit pool with nothing to defend.

How This Fits With Other Startup Tax Choices

R&D credit planning rarely lives alone. It interacts with your entity structure (C-corp vs. LLC vs. S-corp), QSBS planning, and how you treat founder compensation. A few overlap points worth knowing:

• Entity type: the credit is available to all entity types, but the payroll offset is most natural for C-corps and entities with W-2 employees. See our writeup on LLC to S-corp conversion for the entity decision tree.
• QSBS: if you are a C-corp founder pursuing the §1202 QSBS exclusion, the R&D credit work is complementary. QSBS shelters the exit; R&D credits ease the cash burn between now and then.
• Founder wages: founder W-2 wages count as QRE if the founder is performing qualifying research (most early CTOs are). Be deliberate about W-2 vs. distribution treatment if you are a pass-through.
• Multi-year planning: the credit has a 20-year carryforward. Even if you cannot use it now, claiming it preserves the asset. Skipping years is hard to fix later.

What Goes Wrong Without a CPA

The most common pattern we see at intake: a startup that ran a self-prepared "R&D credit calculator," took 8 to 10 percent of total engineering payroll as QRE, and filed a Form 6765 with no project-level documentation. The 2024 Form 6765 redesign forces every filer to disclose business components in Section G. A skinny disclosure paired with a generic percentage attestation puts the return into the audit pool, and the typical outcome is full disallowance plus a 20 percent accuracy-related penalty. The bill for a $200K disallowed credit including penalty and interest commonly tops $260K.

DIY filing software does not run a study, does not isolate IUS exposure on internal admin tools, does not flag funded-research contracts that disqualify portions of payroll, and does not file the §174 retroactive amended returns. Each of those items can swing the result six figures in either direction.

FAQ

Does my pre-revenue startup actually qualify for the R&D credit?

Almost certainly yes if you are building real software with engineers in the United States. The credit does not require revenue. The most common reason a pre-revenue startup does not claim it is that nobody told them about the payroll offset. If you have W-2 engineers writing code that meets the four-part test, you qualify. The credit is calculated on your QREs regardless of whether you have any income.

How much can I claim in year one?

Most software startups using the Alternative Simplified Credit get 6 to 10 percent of QREs in year one. On $2M of engineer salaries, that is roughly $120K to $200K of credit. You can convert up to $500K of credit per year to a payroll-tax offset as long as you qualify as a QSB.

What if I have been operating for years without claiming the credit?

Open tax years (generally the last three) can be amended to claim previously-missed credit. You can also claim retroactive §174 expensing for 2022 through 2024 if you meet the small-business gross-receipts test. We have seen six-figure refunds come back from this combination.

Does my offshore dev team's work qualify?

For the §41 credit itself, no. Only US-based research (W-2 employees and 65% of US contractor pay) generates QRE. For the §174 expensing rule under OBBBA 2025, foreign R&D is still capitalized over 15 years. If most of your engineering is offshore, the credit is small and the §174 capitalization continues to bite. Onshoring the engineering team has real tax consequences either way.

Will claiming the R&D credit trigger an audit?

It does not automatically trigger an exam, but the R&D credit is on the IRS's frequent-issue list. The 2024 Form 6765 redesign (Section G business-component reporting) increased disclosure substantially. If your claim is well-documented and methodologically sound, audits are defensible. If your claim is a percentage applied to total payroll with no project-level support, expect to lose at exam.

Do I have to choose between the R&D credit and the §174 expensing?

No. The credit and the deduction are separate mechanisms. For tax years after 2024, you can both expense your domestic R&D under §174A and claim the §41 credit on the qualifying portion. You do have to reduce your §174 deduction by the credit amount under §280C, or alternatively make a reduced-credit election under §280C(c). Most startups elect the reduced credit to keep deductions clean.

When to Talk to Us

R&D credit work is one of the highest-ROI tax projects available to a software startup. Done right, a pre-revenue company can recover six figures of payroll tax per year and a profitable company can shave double digits off the federal effective rate. Done wrong, it puts the return in the audit pool with no defense.

At Silicon Valley Tax, we run R&D credit studies for Bay Area software startups across the funding spectrum, including the §174 retroactive amended returns for the 2022 through 2024 capitalization period. If you have never claimed the credit, have claimed it without a study, or have not revisited your position since OBBBA 2025 passed, the marginal review is almost always worth it. See our broader services list for adjacent founder work.

Schedule a free consultation and we will walk through your engineering spend, your QSB eligibility for the payroll offset, and whether the retroactive §174 amended returns are worth filing for your situation.