Internal-Use Software R&D Credit: Tests, Expenses, and Form 6765

Software your company builds for its own back-office operations can qualify for the federal R&D tax credit, but the internal-use software R&D credit sits behind a higher bar than other research: the project has to clear the standard four-part research test and then satisfy a separate three-prong “high threshold of innovation” test. Get the classification and the evidence right and the credit is worth up to 20 percent of qualifying spend over a base amount, or 14 percent under the alternative simplified method.¹

What Counts as Internal-Use Software

Treasury regulations treat software as “internal use” when its primary function supports general and administrative activities: financial management, payroll, bookkeeping, human resources tracking, and similar back-office work.²

Several categories sit outside that label and only need to pass the standard four-part test. Software developed to be sold, leased, or licensed to customers is not internal-use software. Neither is software that enables the company to interact with third parties or lets customers initiate functions and review data on the company’s system.² A customer portal, an e-commerce platform, and an API that connects to outside partners generally escape the internal-use label entirely.

The classification is where the most money is usually at stake in a study. If the software truly is internal-use, the high threshold of innovation test applies on top of everything else.

The Four-Part Test Every Project Must Pass First

Before the internal-use question is even reached, any research activity claiming the credit has to satisfy four requirements under Section 41(d).¹

Permitted purpose. The research must aim to develop a new or improved business component in terms of function, performance, reliability, or quality. Style, taste, and seasonal design factors do not count.
Technological in nature. The process of experimentation must rely on principles of physical or biological science, engineering, or computer science. Software development generally satisfies this through computer science.³
Elimination of uncertainty. At the outset there must be genuine uncertainty about whether the desired result can be achieved, what method will work, or the appropriate design.
Process of experimentation. Substantially all of the research activities must involve a systematic evaluation of alternatives to resolve that uncertainty. Trying one thing and moving on is not enough.

The four elements work as a single gate. Failing any one disqualifies the project no matter how impressive the software.

The High Threshold of Innovation Test

Internal-use software has to satisfy three additional prongs, all at once.²

Innovation. The software must produce a result that is substantially and economically significant, such as a major reduction in cost or a meaningful improvement in speed. A modest efficiency gain from upgrading an existing system does not clear this bar.
Significant economic risk. The company must commit substantial resources without any guarantee the project will succeed. If the outcome was reasonably certain at the start, the risk element is missing.
No commercial alternative. The software cannot be commercially available for purchase, lease, or license at the time of development.

The “no commercial alternative” prong trips up companies more than any of the others. The IRS looks for evidence of a genuine market search before custom development began. A cursory look at one or two vendors will not hold up under examination.

The Dual-Function Safe Harbor

Many systems serve both internal operations and outside users. An order platform that runs internal inventory while letting customers track shipments is a common pattern. When the third-party portions of the software cannot be separated from the internal-use portions, the regulations let the company include 25 percent of the project’s qualified research expenses in the credit calculation without meeting the high threshold of innovation test.²

Two conditions apply. The research still has to satisfy the standard four-part test on its own merits, and the software’s third-party use must be reasonably anticipated to account for at least 10 percent of overall usage. Usage should be estimated through an objective, reasonable method appropriate to the industry, such as processing time, volume of data transferred, or the number of user interface screens. The 25 percent figure is conservative by design, but it provides a reliable path to some credit on projects that would otherwise be shut out entirely.

Activities That Still Do Not Qualify

Even software that passes every test above can lose eligibility if the specific work falls into a statutory exclusion.¹

Research after commercial production. Once the software is in production use, further work on that version generally stops qualifying. Bug fixes and routine maintenance after launch are not creditable.
Adapting existing software. Customizing a system for a particular customer without resolving new technical uncertainty is excluded.
Duplicating existing components. Rebuilding software from existing specifications or publicly available information does not count.
Surveys and management studies. Efficiency surveys, market research, routine data collection, and ordinary quality-control testing are all excluded.
Foreign research. Work performed outside the United States, Puerto Rico, or U.S. possessions cannot be included.
Funded research. Work paid for by a grant, contract, or another party is excluded to the extent of the outside funding.

The post-production exclusion matters for teams running agile cycles. New feature development that introduces genuine technical uncertainty can still qualify after launch, but incremental improvements to existing features usually cannot.

What Expenses Count

The credit is built from three cost categories, and every dollar of qualifying expense flows into the calculation.

Employee wages are the largest bucket on most software projects. Wages include all taxable compensation on Form W-2 for employees performing qualified research, including bonuses and stock option income, and compensation for employees providing direct supervision or direct support to the technical team also counts.⁴

Supplies consumed in the research process are eligible. For software work, this most often means server costs and cloud computing resources allocated to development environments rather than production.

Contract research is treated differently. When an outside contractor performs qualified research, only 65 percent of the fees count toward the credit, and payments must relate to actual technical development work. Fees for project management, general consulting, or administrative support do not qualify.⁴

How Much the Credit Is Worth

Taxpayers choose between two calculation methods.

Regular Credit

The regular credit equals 20 percent of the amount by which current-year qualified research expenses exceed a base amount.¹ The base amount comes from multiplying a “fixed-base percentage” by average gross receipts for the prior four tax years. The fixed-base percentage reflects the historical ratio of qualified research expenses to gross receipts during the 1984 through 1988 tax years and cannot exceed 16 percent. The base amount can never fall below 50 percent of the current year’s qualified research expenses.

This method produces a larger credit when the fixed-base percentage is low relative to current spending. Companies formed after 1988 often lack the historical data to compute it cleanly, and the startup rules that fill the gap carry their own complications.

Alternative Simplified Credit

The alternative simplified credit (ASC) equals 14 percent of the amount by which current-year qualified research expenses exceed 50 percent of the average qualified research expenses over the prior three tax years.¹ With no qualified research expenses in any of the three preceding years, the credit is 6 percent of current-year expenses with no base subtraction.

Most companies pick the ASC because a three-year lookback is far simpler than reconstructing 1980s records. Once elected, it applies to the current year and all future years unless the IRS grants permission to revoke it.

The Section 280C Reduced Credit Election

Federal law blocks a double benefit on the same expenses. Section 280C requires a taxpayer to reduce its Section 174 deduction by the amount of credit claimed, or to elect a reduced credit that avoids any adjustment. Under the election, the credit is multiplied by the maximum corporate tax rate (currently 21 percent) and that product is subtracted from the full credit, leaving a credit equal to 79 percent of the amount otherwise calculated.⁵ Most companies take the reduced credit because it avoids adjusting the Section 174 amortization each year. The election is made on Form 6765 and is irrevocable for the year to which it applies.⁶

One boundary worth flagging: since 2022, software development costs must be capitalized and amortized (five years for domestic work, 15 years for foreign) under Section 174 as amended by the Tax Cuts and Jobs Act.⁷ Claiming the credit does not restore an immediate deduction; the credit and the amortization run on parallel tracks.

Payroll Tax Offset for Startups

Pre-revenue and early-stage companies often have little federal income tax liability, which makes a non-refundable credit useless in the short term. Qualified small businesses can instead elect to apply up to $500,000 of the R&D credit per year against the employer portion of Social Security taxes.⁸

To qualify, a business must be a corporation (including an S corporation) or partnership that meets both of these criteria:

Gross receipts of less than $5 million for the current tax year
No gross receipts in any tax year before the five-tax-year period ending with the current year

The election cannot be made for more than five tax years total.⁶ For a software startup burning cash while building an internal platform, this offset can produce real savings well before the company is profitable.

Documentation the IRS Expects

The R&D credit is one of the most heavily scrutinized items on a corporate return, and internal-use software claims draw extra attention because of the high threshold test. Documentation has to be built as the work happens, not reconstructed after an audit notice.

An IRS Chief Counsel memorandum sets out the minimum information for a valid claim. For each business component, the taxpayer must identify every research activity performed, every individual who performed each activity, and the specific information each individual sought to discover. The claim must also include total qualified employee wages, supply expenses, and contract research expenses for the year.⁹

Examiners look for contemporaneous records: organization charts, project authorization documents, progress reports, meeting minutes, budget approvals, and contractor agreements. Payroll records need to tie individual employees to specific qualifying activities with names, job titles, compensation amounts, and the percentage of time spent on research.¹⁰

Handing over a stack of documents or a credit study is not enough. The taxpayer must provide facts in a written statement and, if documents are submitted, specify the exact pages supporting each claimed fact. Paper without a roadmap is treated as deficient.⁹ For internal-use software specifically, the file should address all three prongs of the high threshold test with concrete evidence, not conclusory language about how innovative the project was.

Filing on Form 6765

The credit is claimed on Form 6765, attached to the federal income tax return for the year the expenses were incurred. Partnerships and S corporations file the form directly; the credit flows through to partners or shareholders, who report it on Form 3800 (General Business Credit) with their own returns.⁶

The form has separate sections for the regular credit and the ASC. It asks for current-year qualified research expenses broken out by wages, supplies, and contract research, and then either the fixed-base percentage and gross receipts data (regular method) or the prior three years of qualified research expenses (ASC).¹¹

If the credit was missed on an original return, corporations amend with Form 1120-X and individuals with Form 1040-X. The window is generally three years from the date the original return was filed or two years from the date the tax was paid, whichever is later.¹² Amended claims must include the same minimum documentation, including identification of all business components and the individuals who performed the research.

1
Office of the Law Revision Counsel. 26 USC 41 – Credit for Increasing Research Activities
2
eCFR. 26 CFR 1.41-4 – Qualified Research for Expenditures Paid or Incurred in Taxable Years Ending on or After December 31, 2003
3
Internal Revenue Service. Audit Techniques Guide – Credit for Increasing Research Activities IRC 41 – Qualified Research Activities
4
Internal Revenue Service. Audit Techniques Guide – Credit for Increasing Research Activities IRC 41 – Qualified Research Expenses
5
Office of the Law Revision Counsel. 26 USC 280C – Certain Expenses for Which Credits Are Allowable
6
Internal Revenue Service. Instructions for Form 6765 (Rev. December 2025)
7
Office of the Law Revision Counsel. 26 USC 174 – Amortization of Research and Experimental Expenditures
8
Internal Revenue Service. Qualified Small Business Payroll Tax Credit for Increasing Research Activities
9
Internal Revenue Service. IRC 41 Research Credit Refund Claims (LAFA 20214101F)
10
Internal Revenue Service. Audit Techniques Guide – Credit for Increasing Research Activities IRC 41 – Substantiation and Recordkeeping
11
Internal Revenue Service. Form 6765 – Credit for Increasing Research Activities
12
Internal Revenue Service. Instructions for Form 1120-X – Amended U.S. Corporation Income Tax Return