Currency note: This article reflects federal rules as of June 2026 and covers tax year 2025 (the 2026 filing season), with notes on tax year 2026. It also flags state differences in general terms. Tax law changes often — confirm current figures with a licensed professional before you file.
Quick Answer
Yes. Most software development qualifies for the federal R&D tax credit (IRC Section 41) when the work passes the IRS four-part test. For tax year 2025, qualifying wages, contractor costs, and cloud computing can generate a dollar-for-dollar credit, often 6%–10% of eligible spending.
Software development is one of the most common — and most overlooked — sources of the federal research credit under Section 41. If your team writes code to build a new product, fix technical unknowns, or make software faster, more secure, or more capable, you are likely doing “qualified research” in the eyes of the IRS. The immediate consequence of not knowing this: you may be handing the government tax dollars you never owed, year after year.
The stakes are real, and the timing matters. Roughly $30 billion in federal R&D credits are claimed each year, yet most go to large firms — small software shops and startups routinely leave money on the table. Worse, the credit is mostly claimed on a timely filed return, so a missed year can be hard or impossible to recover. This guide shows you exactly who qualifies, how the math works, and how to claim it without triggering an audit.
Here is what you will learn:
- 🧩 How the IRS four-part test decides whether your code qualifies — in plain English
- 💵 A fully worked example showing real dollars saved on a $400,000 dev payroll
- 🚀 How pre-revenue startups can offset up to $500,000 in payroll taxes per year
- ⚖️ How the 2025 OBBBA law changed Section 174 expensing and why it matters for the credit
- 🛡️ The 7 mistakes that get software R&D claims reduced or denied — and how to avoid them
Which Situation Applies to You?
The right path depends on who you are and what your business looks like. Find yourself below, then read the section that fits.
- Pre-revenue or early startup (under 5 years of gross receipts, under $5M this year): You likely cannot use an income-tax credit because you have no tax. Jump to the payroll-tax offset section — this is your path to up to $500,000 a year.
- Profitable small or mid-sized software company: You use the credit against income tax. Focus on the four-part test, the worked example, and Form 6765.
- Custom software shop or agency building for clients: Your eligibility depends on who bears the financial risk and who owns the rights. Read the “funded research” mistake closely.
- Company building internal tools (HR, accounting, internal dashboards): You face an extra, tougher test for internal-use software. Read the IUS section before you claim.
- A CPA or CFO assembling the claim: Focus on the four-part test, the revised Form 6765 Section G, and the documentation rules.
What the R&D Tax Credit Is
The R&D tax credit is a dollar-for-dollar reduction of your federal income tax bill, created under Section 41 of the Internal Revenue Code. It is not a deduction that lowers your taxable income — it is a credit that lowers the actual tax you owe, which makes it far more valuable per dollar. Congress created it in 1981 to reward U.S. companies for taking technical risk, and it was made permanent in 2015.
The credit rewards qualified research expenses (QREs). These fall into four buckets: taxable wages for employees doing or directly supporting research, 65% of payments to U.S. contractors who perform research, the cost of supplies used in research, and — important for software teams — cloud computing and rental of computers used to host development and testing.
The consequence of misunderstanding this is costly. Many founders assume the credit is “only for labs and scientists” and never claim it. The result is a permanent overpayment of tax. What you should do: if your team writes code and solves technical problems, treat the credit as a default opportunity to investigate, not a long shot.
There are two ways to compute the federal credit. The Regular Credit equals 20% of QREs above a base amount tied to your history, and the Alternative Simplified Credit (ASC) equals 14% of QREs above 50% of your average QREs from the prior three years (or 6% of current QREs if you had none in those years). Most small and newer companies use the ASC because it needs less historical data.
The IRS Four-Part Test for Software
Every activity you claim must pass all four parts of the test in Section 41(d). Fail one part, and that activity does not qualify. The test is the heart of every software R&D claim, so understand each part and what it means for code.
Part 1 — Permitted Purpose
The work must aim to create a new or improved business component — a product, process, software, technique, formula, or invention — that improves function, performance, reliability, or quality. For software, this covers building a new application, adding a major feature, rebuilding an architecture for scale, or improving algorithm speed. Cosmetic changes, such as a new color scheme or simple copy edits, do not count.
The consequence of skipping this part: routine maintenance and pure styling work get pulled out of your claim, and including them invites IRS adjustments. A common misconception is that any coding qualifies — it does not. What to do: tie each project to a concrete technical improvement you were trying to achieve, and write that goal down before the work starts.
Part 2 — Technological in Nature
The work must rely on principles of a hard science — for software, that means computer science and engineering. Writing code, designing data structures, and building algorithms clearly rely on computer science, so software development usually clears this part with ease. Market research, graphic design choices, and business strategy do not qualify because they are not grounded in hard science.
The consequence of ignoring this: non-technical work mixed into a claim weakens the whole filing. A misconception is that “creative” front-end work never qualifies — it can, if it solves a technical problem like rendering performance. What to do: keep claimed activities tied to engineering decisions, not business or design taste.
Part 3 — Elimination of Uncertainty
At the start, you must not know whether you can achieve the result, or how to achieve it, or the best design to use. This is the part software teams underestimate. If your engineers faced unknowns — Will this scale? Which architecture works? Can we integrate these systems? — you have technical uncertainty. If the solution was already known and you just typed it in, you do not.
The consequence of failing here: the IRS treats the work as routine implementation and denies it. A misconception is that uncertainty means “we might fail commercially” — no, it means technical doubt about capability, method, or design. What to do: document the open technical questions at the start of each sprint or project.
Part 4 — Process of Experimentation
You must evaluate alternatives through a process of testing — modeling, simulation, trial and error, prototyping, or systematic A/B testing. Software development does this naturally: building prototypes, running test suites, refactoring after load tests, and iterating on failed builds all count. The work must be a methodical search, not a one-shot guess.
The consequence of weak documentation here: even genuine experimentation gets denied if you cannot show the process. A misconception is that you need a formal lab notebook — you do not, but you do need some contemporaneous record. What to do: keep your normal artifacts — Git history, Jira tickets, design docs, test logs — because they prove experimentation for free.
What Software Activities Qualify
Many everyday engineering tasks meet the test. The point is the technical work, not the job title. Below are activities the IRS and practitioners widely accept as qualifying, drawn from guidance on software development credits.
- Developing new applications, platforms, or SaaS products from scratch
- Designing and testing new algorithms, data models, or system architectures
- Building integrations between systems where the method is uncertain
- Improving performance, scalability, or security through experimentation
- Developing and testing AI and machine-learning models
- Creating prototypes, proofs of concept, and minimum viable products
- Resolving technical defects that require investigation, not routine fixes
Each of these involves a technical goal, real uncertainty, and iterative testing. The consequence of not mapping your work to these categories is an under-claim — you leave eligible wages out. What to do: review your last 12 months of sprints and tag the work that fits.
What Software Activities Do NOT Qualify
Just as important is knowing what to exclude. Section 41(d)(4) lists excluded activities, and claiming them is a top audit trigger.
- Routine maintenance, bug fixes, and debugging that need no investigation
- Cosmetic or aesthetic changes, like reskinning a user interface
- Data entry, content updates, and routine configuration
- Adapting an existing product to a single customer’s needs without technical uncertainty
- Research conducted outside the United States (foreign work is excluded)
- Reverse engineering of an existing product
- Work funded by a customer who bears the financial risk and keeps the rights
The consequence of including these is real: the IRS removes them and may apply penalties for the overstatement. A misconception is that “any work on a software product” counts — it does not. What to do: separate qualifying technical work from routine upkeep in your time tracking.
Internal-Use Software Faces a Harder Test
If you build software mainly for your own internal operations — like an internal HR portal, an accounting tool, or a back-office dashboard — it must clear a higher bar. This is called the internal-use software (IUS) rule, and it adds a “high threshold of innovation” test on top of the standard four-part test. The rule exists because Congress did not want every company’s routine internal IT work to qualify.
Under the final IUS regulations, internal-use software must meet three extra conditions: it must be innovative (offer a meaningful economic improvement), involve significant economic risk, and not be commercially available for purchase or license without major modification. All three must be true.
The consequence of misjudging this is a denied claim plus the cost of defending it. A key misconception: software you sell or that customers directly use is not internal-use software and skips this harder test entirely. Customer-facing apps, SaaS products, and software embedded in a product you sell are exempt from the IUS rules. What to do: classify each project as customer-facing or internal before you claim, because the test you apply changes.
| Software Type | Test That Applies |
|---|---|
| SaaS product, mobile app, customer-facing platform | Standard four-part test only |
| Software sold or licensed to customers | Standard four-part test only |
| Internal HR, accounting, or back-office tools | Four-part test plus the three-part IUS high-innovation test |
How Section 174 Interacts (and the 2025 OBBBA Change)
The credit under Section 41 is separate from the deduction rules under Section 174, but software teams must understand both. Section 174 governs how you write off “research or experimental” (R&E) costs, and software development costs are treated as R&E costs. From 2022 through 2024, a tax-law change forced companies to capitalize and amortize these costs over five years for domestic work, which hurt software firms badly.
That changed in 2025. The One Big Beautiful Bill Act (OBBBA), signed July 4, 2025, enacted new Section 174A, which permanently restores full, immediate expensing of domestic R&E costs paid or incurred after December 31, 2024. So for tax year 2025, you can again deduct your U.S. software development costs in the year you spend them.
The consequence for the credit: because you both expense the cost (Section 174A) and earn a credit on it (Section 41), you must reduce your deduction by the credit amount — unless you make the Section 280C reduced-credit election to take a smaller credit and keep the full deduction. A misconception is that 174 and 41 are the same rule; they are not — one is a deduction, the other a credit. What to do: ask your CPA whether the 280C election helps your specific tax position.
There is also relief for the painful 2022–2024 period. Under Revenue Procedure 2025-28, eligible small businesses can elect to retroactively expense domestic R&E costs back to 2022, and others can accelerate any remaining unamortized amounts. Foreign R&E costs still must be amortized over 15 years — that did not change. What to do: if you capitalized software costs in 2022–2024, ask about amending or accelerating before the deadlines pass.
A Fully Worked Example
Here is the math, step by step, using the Alternative Simplified Credit for a profitable software company in tax year 2025. Assume “DevForge LLC” has these qualified research expenses for the year.
- Developer and engineer wages (qualified portion): $400,000
- U.S. contractor payments (65% counts): $100,000 paid → $65,000 counts
- Cloud computing for development and testing: $35,000
- Total current-year QREs: $500,000
DevForge had average QREs of $300,000 over the prior three years. The ASC base is 50% of that, or $150,000. So the credit applies to QREs above the base: $500,000 − $150,000 = $350,000.
The ASC rate is 14%, so the gross credit is $350,000 × 14% = $49,000. If DevForge makes the Section 280C reduced-credit election, the net credit is roughly $49,000 × (1 − 21%) = $38,710, and it keeps its full deduction. Either way, this is a direct reduction of tax owed — not just taxable income — so it is real cash kept in the business.
Now compare a first-time claimant with no QREs in the prior three years. That company uses the startup ASC rate of 6% on current QREs. On the same $500,000, the credit is $500,000 × 6% = $30,000. The lesson: claiming every eligible year builds your base and increases future credits.
Three Common Scenarios
Below are the three situations software businesses hit most often, each shown as a quick map from your situation to the likely tax outcome.
Scenario 1 — Profitable SaaS company
| Your Situation | Tax Outcome |
|---|---|
| $500K in dev QREs, owes income tax | Credit offsets income tax dollar-for-dollar, ~$30K–$49K saved for 2025 |
| Unused credit remains | Carry back 1 year, then carry forward up to 20 years |
Scenario 2 — Pre-revenue startup
| Your Situation | Tax Outcome |
|---|---|
| Under 5 yrs of receipts, under $5M, no income tax | Elect payroll-tax offset, up to $500,000 per year against payroll taxes |
| Credit exceeds quarterly payroll tax | Carries forward to the next quarter automatically |
Scenario 3 — Custom software agency
| Your Situation | Tax Outcome |
|---|---|
| Builds for clients, bears the risk, keeps IP rights | Work qualifies; agency claims the credit |
| Client pays regardless of success and owns the result | “Funded research” — agency cannot claim it |
Three Named Examples
Maya, founder of a 6-person fintech startup. Maya’s team spent 2025 building a new fraud-detection model and faced real uncertainty about which machine-learning approach would work. The company had no profit and owed no income tax, so Maya elected the payroll-tax offset on Form 6765, applied $90,000 of credit against payroll taxes through Form 8974, and cut her quarterly payroll bill — cash she reinvested in hiring.
Daniel, owner of a profitable SaaS analytics firm. Daniel’s engineers rebuilt the platform’s data pipeline to handle 10x the load, testing several architectures before one held. He claimed $420,000 in qualifying wages and cloud costs, used the ASC, and reduced his 2025 income tax by about $38,000 after the 280C election.
Priya, who runs a custom software agency. Priya’s team built an integration platform where her firm bore the cost of failure and kept the source code. Because she carried the financial risk and retained the rights, the work was not funded research, so her agency — not the client — claimed the credit on the qualifying development hours.
How to Claim It: Form 6765
You claim the federal credit on Form 6765, Credit for Increasing Research Activities, filed with your business income tax return. The form is where you compute the credit, choose the regular or simplified method, and make key elections. Filing it correctly — and on time — is what turns eligible work into real savings.
The form has several parts you must understand. Section A computes the Regular Credit, and Section B computes the Alternative Simplified Credit; you pick one. Section C handles other adjustments and the Section 280C reduced-credit election. Section D is where a qualified small business elects the payroll-tax offset, and Section E asks summary questions about your QREs and officer wages.
The IRS added a detailed Section G — Business Component Information in the revised Form 6765, which asks you to break down QREs by each business component. Per the latest IRS instructions, Section G is optional for tax year 2024 and tax year 2025, and becomes mandatory for tax year 2026 — with exceptions for qualified small businesses electing the payroll offset and for filers with QREs of $1.5 million or less and gross receipts of $50 million or less.
The consequence of missing the form or the payroll election is steep: the payroll-tax election must be made on a timely filed return, including extensions, and you cannot add it later by amending. A misconception is that you can claim the payroll offset whenever you like — you cannot. What to do: file Form 6765 with your return by the deadline, and if you want the payroll offset, make that election the first time, not after.
The Payroll-Tax Offset for Startups
This is the single most valuable rule for pre-revenue software companies, because it turns the credit into cash even when you owe no income tax. Under the qualified small business payroll-tax offset, an eligible startup can apply its R&D credit against the employer portion of payroll taxes instead of income tax.
A qualified small business (QSB) under Section 41(h) is a business with less than $5 million in gross receipts for the election year, and no gross receipts for any year before the five-year period ending with the election year. In short: young and small. The Inflation Reduction Act doubled the cap from $250,000 to $500,000 starting in tax year 2023.
Here is how the $500,000 splits: up to $250,000 offsets the employer’s 6.2% Social Security tax, and up to another $250,000 offsets the employer’s 1.45% Medicare tax. The credit applies starting the first calendar quarter after you file your income tax return, claimed quarterly on Form 8974 and reported on your Form 941.
The consequence of missing this: a startup with no income tax simply carries the credit forward and waits years for value, instead of getting cash now. A misconception is that you must be profitable to benefit — the opposite is true here. What to do: if you are under five years old and under $5M in receipts, make the election on your originally filed return.
Deadlines, Costs, and Timing
Timing controls whether you capture the credit at all. The credit is claimed with your income tax return, due March 15 for partnerships and S corporations and April 15 for C corporations (for calendar-year filers), or the extended date if you file an extension. The payroll-tax election, again, must be made on a timely return — extensions count, but late elections generally do not.
If you missed a prior year, you may be able to amend an open return (generally within three years) to claim a regular income-tax credit, though the payroll election cannot be added by amendment. Cost-wise, a DIY claim costs only your time plus tax-prep fees, while a specialist R&D study often costs a few thousand dollars or a percentage of the credit — usually worth it for larger or first-time claims. A well-run study takes a few weeks; gather your payroll, contractor, and cloud records early.
Mistakes to Avoid
Each of these errors carries a real cost — a reduced credit, a denial, or penalties. Avoid all seven.
- Claiming routine maintenance and bug fixes. These fail the four-part test and get removed, shrinking your credit and flagging your return.
- Including foreign development. Work performed outside the U.S. is excluded; claiming it can trigger penalties for an overstated credit.
- Ignoring the funded-research rule. If a client bears the risk and owns the result, you cannot claim that work — claiming it invites disallowance.
- Skipping documentation. Without Git logs, tickets, or design docs, even real R&D gets denied for lack of proof.
- Missing the payroll-tax election deadline. The election must be on a timely filed return; miss it and a startup loses the cash benefit for that year.
- Mishandling internal-use software. Treating internal tools like customer software skips the harder IUS test and risks denial.
- Forgetting the Section 280C election. Failing to plan the deduction-versus-credit interaction can cost you part of either benefit.
Do’s and Don’ts
Do’s
- Do track engineering time by project, because wage-based QREs are your biggest claim driver.
- Do keep contemporaneous records like Git history and tickets, since they prove experimentation cheaply.
- Do claim every eligible year, because it builds your ASC base and raises future credits.
- Do separate qualifying R&D from routine upkeep, so your claim survives scrutiny.
- Do make the payroll-tax election on time if you are a startup, because it cannot be added later.
Don’ts
- Don’t claim cosmetic or aesthetic-only changes, because they fail the technological test.
- Don’t include foreign labor, since it is statutorily excluded.
- Don’t assume you are too small, because there is no minimum size for Section 41.
- Don’t guess at the four-part test, because one failed part disqualifies the activity.
- Don’t skip professional help on a first or large claim, because the rules and Form 6765 are technical.
Pros and Cons
Pros
- Dollar-for-dollar tax savings, because a credit beats a deduction in real value.
- Cash for startups, because the payroll offset works even with no income tax.
- Carryforward up to 20 years, so unused credit is not lost.
- Rewards work you already do, because normal engineering often qualifies.
- State credits may stack, because many states offer their own R&D credit on top.
Cons
- Documentation burden, because you must prove each activity and expense.
- Audit risk if overclaimed, because aggressive claims draw IRS attention.
- Complex calculations, because the ASC, base, and 280C interactions are technical.
- Strict deadlines, because the payroll election cannot be made late.
- Professional fees, because a solid study often needs an expert.
Does Your State Follow This?
Start with the federal rule, then check your state — conformity varies a lot. Many states, including California, offer their own R&D credit that often mirrors the federal four-part test but uses different rates and rules. Some states are more generous, some less, and a few offer no R&D credit at all.
A few important contrasts. States with no income tax, such as Texas, Washington, and Florida, do not offer an income-tax R&D credit — though Texas provides an alternative franchise-tax credit or sales-tax exemption for research. The consequence of assuming your state copies federal law is a wrong claim or a missed state benefit. What to do: look up your specific state agency’s R&D credit page and confirm the rate, base, and forms before you file.
What to Do Next
Take these steps in order to capture the credit for tax year 2025 and set up future years.
- List every software project from the year and tag the work that meets the four-part test.
- Gather your records: payroll by employee, contractor invoices, cloud bills, Git logs, and tickets.
- Decide your method — the Alternative Simplified Credit is usually best for small or newer firms.
- If you are a qualified small business with no income tax, plan to elect the payroll-tax offset.
- Complete Form 6765 and, for the payroll offset, Form 8974, and file with your return by the deadline.
- Check your state’s separate R&D credit and file any state form.
- For a first or large claim, hire a CPA or R&D specialist to run a documented study.
This article is educational and not a substitute for advice from a licensed tax professional for your specific situation. A claim becomes complex enough to warrant a CPA or tax attorney when you have significant contractor work, internal-use software, prior capitalized 174 costs, or any uncertainty about funded research — that help usually involves a documented study, a defensible QRE calculation, and audit-ready records.
FAQs
Does all software development qualify for the R&D tax credit?
No. Only software work that passes the four-part test qualifies. New features, algorithms, and architectures with technical uncertainty count, but routine maintenance, bug fixes, and cosmetic changes do not, even within the same product.
Can a startup with no profit claim the R&D credit?
Yes. A qualified small business — under $5 million in gross receipts and within five years of its first receipts — can elect to offset up to $500,000 per year of payroll taxes for tax year 2025, even with no income tax.
How much is the R&D credit worth for software?
About 6%–10% of qualified spending. The Alternative Simplified Credit is 14% above a base, or 6% for first-time claimants with no prior QREs, so the effective benefit usually lands in that range for 2025.
What software costs count as qualified research expenses?
Wages, contractors, supplies, and cloud computing. For tax year 2025, you count qualified developer wages, 65% of U.S. contractor payments, supplies, and rented or cloud computing used for development and testing.
Does the credit cover offshore or foreign developers?
No. Research performed outside the United States is excluded from Section 41. Only U.S.-based software development work counts toward the federal credit, regardless of where your company is headquartered.
What form do I use to claim the credit?
Form 6765. You file Form 6765 with your business income tax return to compute the credit and make elections, and startups also file Form 8974 to apply the payroll offset.
Is internal company software eligible?
Yes, but it is harder. Internal-use software must also pass a high-innovation test — innovative, significant economic risk, and not commercially available. Customer-facing software skips this extra test entirely.
Did the 2025 OBBBA law change software R&D taxes?
Yes. OBBBA’s new Section 174A permanently restored immediate expensing of domestic R&E costs starting in 2025, reversing the 2022–2024 five-year amortization rule for U.S. software development costs.
Can I claim the credit for past years?
Yes, with limits. You can generally amend an open return — usually within three years — to claim a regular income-tax credit, but the payroll-tax offset election cannot be added by amending a prior return.
Do I need a formal lab notebook to prove R&D?
No. The IRS accepts contemporaneous business records. Git history, project tickets, design documents, and test logs are usually enough to show technical uncertainty and a process of experimentation.
Will my state give me an R&D credit too?
It depends. Many states offer their own R&D credit that often follows the federal four-part test with different rates, while no-income-tax states like Texas and Washington do not provide an income-tax credit.
Does using AI tools to build software qualify?
Yes, if it passes the test. Developing and training AI or machine-learning models with technical uncertainty qualifies. Simply using an off-the-shelf AI tool to write routine code does not, on its own, count.