Tax Planning Startups Bookkeeping

R&D Credit for Software Startups: The 2026 Carryforward Playbook

Published June 1, 2026 by Invisible LLC Team · 9 min read

The short version

If your startup is writing original software and burning engineering payroll, the federal R&D tax credit can convert up to $500,000 per year of that burn into a payroll tax offset — even if you have no income tax liability and no revenue yet. The credit doesn't expire when you can't use it; it carries forward for 20 years. The 2026 wrinkle is that OBBBA's new §174A interacts with the credit in ways the prior §174 capitalization regime did not, and the §280C(c)(2) election now matters more than it used to.

You're a founder, not a tax accountant. The playbook is shorter than it looks: confirm qualification, document the work as you go (not in April), elect the payroll offset on your return, and revisit the §280C choice every year.

What the R&D credit actually is

The Credit for Increasing Research Activities lives at IRC §41. It's a dollar-for-dollar federal tax credit calculated on a percentage of your qualified research expenses (QREs) — mostly engineering wages, contractor R&D, cloud compute used for development, and supplies consumed in research.

For a pre-revenue software startup the credit usually lands somewhere between 6% and 10% of qualified engineering payroll, depending on which calculation method you use (regular credit vs. Alternative Simplified Credit) and how your spend history looks. On $1M of qualified engineering payroll, that's a $60,000–$100,000 federal credit. It is not a deduction. It is not a deferral. It is cash back, applied against the employer-side payroll taxes you're already paying every two weeks.

The credit is not a loophole. It is the single piece of the U.S. tax code most directly aimed at the work an early-stage software team does every day.

The payroll offset is the whole game pre-revenue

The headline feature for seed-stage software is §41(h) — the qualified small business (QSB) payroll tax offset. The Inflation Reduction Act of 2022 doubled the cap from $250,000 to $500,000 per year starting with tax years beginning after December 31, 2022, and the cap is still $500,000 in 2026 (Journal of Accountancy).

To qualify as a QSB and elect the payroll offset, three things must be true in the credit year:

Gross receipts under $5M. Your current-year gross receipts must be below $5 million. Pre-revenue startups easily clear this.
No gross receipts in any year more than five years before the credit year. A 2026 credit year requires zero gross receipts in 2020 or earlier. Pre-incorporation idea-stage doesn't count as gross receipts; revenue does.
Elect on Form 6765, Section D. The election is annual. You make it on the original timely-filed return (extensions allowed). Miss the original return and you cannot retroactively elect the payroll offset for that year — though the underlying credit still exists and carries forward.

The offset hits the employer portion of FICA: 6.2% Social Security up to $250,000 of credit, then 1.45% Medicare up to another $250,000. So a $500,000 credit fully utilized against payroll takes roughly four to eight quarters to absorb depending on payroll size, and any unabsorbed credit rolls to the next quarter. Practically: a seed-stage company with $200K/quarter of engineering payroll will burn through a $500K credit across maybe five or six quarters.

The four-part test, in plain English

Every QRE has to clear four hurdles. The IRS calls it the four-part test; pretend it's a checklist:

Permitted purpose. The work has to be developing or improving a business component — a product, process, software, technique, or formula. Building your own SaaS is a permitted purpose. Configuring a SaaS vendor's product for your own internal admin use is not.
Technological in nature. The work has to rely on the principles of computer science, engineering, or the hard sciences. Most software development clears this trivially. UI redesigns and pure visual design work do not.
Elimination of uncertainty. At the start of the work, you didn't know whether the capability could be achieved, how to achieve it, or what the appropriate design was. Greenfield development, novel algorithms, performance optimization against unproven targets — all uncertainty. Implementing a documented vendor API the way the docs say to is not.
Process of experimentation. You evaluated alternatives — prototyping, A/B testing different approaches, modeling, simulating, iterating. Standard agile development practices typically satisfy this if you can show the iteration.

The four-part test trips up two common founder fact patterns. First, internal-use software: software your team builds to run internal ops (not to sell or to embed in a customer-facing product) has to clear a tougher "high threshold of innovation" sub-test. Most internal admin tooling doesn't qualify. Customer-facing product development does. Second, configuration vs. development: setting up Salesforce, Hubspot, Snowflake, or any other vendor platform is configuration. Building original software that integrates with those platforms — your own ETL pipelines, custom enrichment logic, novel data models — is development. The distinction matters.

If your engineering team writes original code that ships to customers and you can describe the technical uncertainty you faced, you almost certainly have QREs. The job is to document them well enough that an IRS examiner agrees three years from now.

Carryforward: the credit doesn't expire when you can't use it

This is the part founders most often miss. The R&D credit is a general business credit under IRC §39. If you generate more credit than you can use in the current year (against income tax liability or via the QSB payroll offset), the unused amount carries back one year and forward 20 years.

For pre-revenue startups this matters in two scenarios:

You generate the credit but forget to elect the payroll offset. The credit sits as a carryforward. When you become profitable in year four or year seven, you can deploy it against income tax then. You did not lose the money; you only lost the present-value benefit.
You generate more than $500,000 of credit in a single year. The excess carries forward. A heavy R&D year that produces a $700,000 credit will fully absorb the $500,000 payroll offset cap; the remaining $200,000 waits in carryforward.

The 20-year carryforward is generous, but it interacts badly with M&A. The credit doesn't follow the founders out of the company — it sits with the entity, and §382 ownership-change rules can limit how fast an acquirer can use carryforward credits post-acquisition. If an exit is on the horizon in the next 24 months, the optimal strategy is to use the payroll offset aggressively now, not bank credit for later.

How OBBBA's §174A changes the calculus in 2026

For tax years before 2022, you could expense R&D costs (under old §174) and claim the §41 credit on those same costs. The TCJA changed that for 2022–2024: domestic R&E had to be capitalized and amortized over five years, foreign R&E over fifteen. That made the credit math worse, because the §41 base was no longer fully deductible in the year incurred.

OBBBA restored immediate expensing for domestic R&E permanently, effective for tax years beginning after December 31, 2024, via new §174A. It also created a small-business retroactive election that lets eligible taxpayers (under $31M gross receipts tested against 2025) recover the 2022–2024 capitalized R&E by amending those returns — but that window closes the week of July 6, 2026 (Rev. Proc. 2025-28). For the carryforward implications of that small-business election specifically, our Section 174 retroactive election piece is the deeper read.

The piece most relevant to ongoing R&D credit work in 2026 is §280C(c)(2). Under the new regime, the §280C(c)(2) election still lets you choose between a full §174A deduction with a reduced §41 credit, or a full credit with a corresponding §174A reduction. The math is rarely intuitive, and it changes year-to-year as your tax position changes. EY's Technical Line on §174A walks through three common fact patterns; a founder running the credit in-house should model both paths annually rather than defaulting to last year's election.

Documentation: what to keep, when to keep it

Auditors lose R&D credits not because the work didn't qualify but because the documentation is reconstructed in April from memory. Three rules:

Track time at the project level, not just the engineer level. Most modern project tracking (Linear, Jira, Asana, Shortcut) already does this if you're disciplined about tagging work to projects. Pull the data quarterly, not annually.
Categorize engineering work by qualified vs. non-qualified. Bug fixes to shipped product, UI polish, vendor integration plumbing — all generally non-qualified. Greenfield product development, novel feature work, performance work against uncertain targets — qualified. Get your engineering lead in the habit of tagging.
Keep the technical narratives. For each qualifying project, write a two-paragraph narrative covering what you were trying to build, what was uncertain, and what alternatives you evaluated. Do it at the end of each quarter while memory is fresh. Three of these per quarter gives you a year-end packet your tax preparer can use without reverse-engineering.

A bookkeeper who knows the credit will track engineering payroll separately in your chart of accounts, tag QRE projects to dedicated GL classes, and reconcile the project tracker against payroll quarterly. That's the level of hygiene that makes the credit defensible. Our bookkeeping service sets up that structure as part of standard onboarding for software clients — it's not an add-on.

Common founder mistakes that cost money

A short list of avoidable losses we see when we onboard a software client mid-year:

Filing the return without Form 6765. Section D of Form 6765 is how you elect the payroll offset. If your preparer skipped Form 6765 entirely, the underlying credit still exists but you cannot retroactively elect the payroll offset for that year. The credit only converts to a payroll offset prospectively if you elect on a timely-filed return.
Misclassifying contractor R&D. Domestic contractor research is QRE-eligible at 65% of cost. Foreign contractor research is not. If you're using a Bulgarian dev shop, those costs don't qualify for the credit even though they're real R&D spend.
Letting founder salaries float un-allocated. A CTO who codes 60% of the time and runs ops 40% needs a defensible time-allocation methodology. "All of it is R&D" is not defensible at audit. Neither is "none of it."
Skipping the §280C(c)(2) analysis. Many preparers default to the same election year-over-year. The right answer changes with your tax position. Model both paths annually.
Not amending pre-PMF years. Some founders qualify retroactively for the 2022–2024 §174A small-business election but assume "we didn't have revenue, there's nothing to amend." Wrong — the amendment recovers prior capitalized R&E and can layer additional credit utility. Run the math before the July 6, 2026 window closes.

What to do in the next 30 days

If you're a software founder reading this in June 2026, three concrete moves:

Pull your engineering payroll and 1099 data for 2025 and YTD 2026. If you can't separate engineering from non-engineering by GL class or department code, fix that first.
Confirm whether you qualify as a QSB for the 2025 credit year (gross receipts test + five-year lookback). If yes, the 2025 credit can offset payroll starting the quarter after you file the 2025 return.
Decide on the §174A small-business retroactive election by mid-June. If you capitalized R&E in 2022, 2023, or 2024 and qualify under §448(c), the retroactive amendment recovers cash. The window closes the week of July 6.

If you want a second set of eyes on any of the above, our team does this work for seed-stage and post-seed software clients as part of standard monthly bookkeeping. We're not an R&D study factory — but we are the people who keep the underlying chart of accounts, payroll, and time-tracking clean enough that the credit gets claimed correctly the first time, and we partner with R&D study specialists when the credit math gets above $200K.

Publishing Brief

Hero image

Description: Close-up of a software engineer's hands at a keyboard with multiple monitors showing code; subtle overlay of dollar signs or a stylized "R&D" graphic to signal tax credit context.
Filename: rd-credit-software-startups-2026-hero.jpg
Dimensions: 1200×630
Alt text: "Software engineer coding at a multi-monitor workstation, representing R&D tax credit qualifying activities for startups."

In-body images

 — Simple flow diagram showing R&D credit → Form 6765 election → Q1 of next year → employer FICA offset on quarterly Form 941. Filename: rd-credit-payroll-offset-flow-diagram.png. Alt: "Diagram of how the R&D tax credit converts to a payroll tax offset over quarterly Form 941 filings."
 — Horizontal timeline showing credit generated year 1, used against payroll years 1–2, unused balance carried forward, deployed against income tax in year 5. Filename: rd-credit-20-year-carryforward-timeline.png. Alt: "Timeline showing 20-year R&D credit carryforward from generation through eventual deployment against income tax."

Internal links checklist

Anchor text	Destination	Body section
Section 174 retroactive election piece	/blog/section-174-small-business-retroactive-election	OBBBA §174A change section
bookkeeping service	/services/bookkeeping	Documentation section
our team	/quote	Closing CTA

Refresh checkpoints

30-day check (early July 2026): Update the post if the §174A small-business retroactive election deadline of July 6, 2026 has passed; rewrite the closing CTA to remove time-sensitive framing.
90-day check (early September 2026): Confirm $500K payroll offset cap is unchanged for the 2026 credit year; review whether IRS has issued additional procedural guidance on Form 6765 changes.
180-day check (early December 2026): Refresh QSB qualification numbers and gross-receipts thresholds against the IRS inflation adjustments for tax years beginning in 2027. Update the §280C(c)(2) framing if any 2026 case law or revenue procedures change the analysis.
Time-sensitive expiry: The "next 30 days" closing section explicitly references the July 6, 2026 §174A window. Update that section by July 7, 2026 at the latest.