What IRS Exam Teams Are Actually Requiring in R&D Credit Audits Right Now

The legal standard for what qualifies as R&D under Section 41 has not changed. The four-part test is still the four-part test. A qualified business component must involve a permitted purpose, eliminate technical uncertainty, follow a process of experimentation, and be technological in nature. None of that is new.

But IRS exam teams have shifted how they conduct examinations. Documentation that used to satisfy auditors a few years ago no longer holds up. Here’s what practitioners working active R&D credit examinations are seeing from exam teams right now.

Less Inference, More Direct Evidence

The biggest practical change is this: IRS examiners are far less willing to connect the dots for you. Under the older approach, you could present a project summary, a list of employees involved, and an allocation of wages and expenses. The examiner would then use reasonable inference to link those materials to the activities the statute requires.

That approach is breaking down. Exam teams now require direct substantiation. They want documentation that doesn’t just describe a project, but demonstrates specifically how the work satisfies the process of experimentation requirement. That means contemporaneous records: lab notebooks, design iteration logs, test results, technical reports, software commit histories with meaningful annotations, and engineering meeting notes that capture uncertainty and alternative approaches as they came up. Not reconstructions prepared after the audit notice arrived.

This marks a real shift for companies that have historically relied on employee interviews and retrospective project summaries as their primary documentation. Those approaches can still play a role in a complete study. But practitioners agree: they no longer stand on their own. Examiners are pushing back, and they’re doing it early in the examination.

The Process of Experimentation Standard

Most disputes in R&D credit examinations come down to the process of experimentation standard. The statute requires that the taxpayer systematically evaluate alternatives: try an approach, assess the results, and use that information to decide what to do next. The research must aim to eliminate technical uncertainty about the capability or method needed to develop or improve the business component.

Traditional laboratory or hardware R&D maps naturally onto this standard, since it matches the kind of records scientists and engineers produce in the normal course of work. Software development and other iterative processes have a harder time meeting it — not because the work doesn’t qualify, but because standard documentation from modern development environments doesn’t always tell the story the IRS wants.

Sprint retrospectives don’t count as process-of-experimentation documentation. A Jira ticket that says “implement authentication module” isn’t a technical uncertainty record. Companies that rely heavily on software development as their qualifying activity need someone — typically an engineer or technical project manager, not a tax professional — to articulate what the uncertainty was, what alternatives came up, and how test results shaped later decisions. That narrative has to form during the project, not get built afterward.

Individual-Level Documentation

Exam teams are also pushing harder on employee-level substantiation. Simply stating that the engineering department spent 40% of its time on qualified research no longer cuts it. Examiners want documentation of what specific individuals did, why those activities qualify under the four-part test, and how you determined each person’s time and expense allocations.

This isn’t just an administrative preference. It reflects how the IRS has built its examination approach over the years, and it now shows up directly in Form 6765 Section G, which requires wage allocations broken out by individual activity type — direct research, supervision, and support — for each business component. The examination standard and the new form point at the same requirement.

Approaches to individual-level tracking vary by industry and company size, but the principle stays consistent: you need to know what each contributor to a business component actually did, and you need to have created that record close to when the work happened. We’ve written in detail about how to find and document every QRE across different employee and expense categories.

Software Development in Financial Services

Software development claims in financial services are drawing particularly intensive examination scrutiny right now. Banks, investment management firms, and fintech companies that claim R&D credits on software development work face some of the highest examination odds, and when those examinations open, they tend to run thorough.

The core difficulty: modern financial technology development doesn’t map cleanly onto the IRS’s traditional conception of research. Agile sprint cycles, continuous integration, and iterative feature deployment don’t look like a lab notebook. But consider a two-week sprint where the team evaluates three alternative approaches to a risk calculation, chooses one, builds it, and determines in the next sprint whether the approach worked. That’s a genuine process of experimentation. The uncertainty is real. The alternatives are real. The outcome wasn’t predetermined.

That process doesn’t document itself the way laboratory R&D tends to. Building the infrastructure to capture technical uncertainty, alternative approaches, and experimental outcomes takes intentional effort, and it has to happen during development. Once an examination notice arrives, it’s too late to reconstruct it.

Amended Return Claims

Amended return claims are drawing close examination attention, too. Since June 2024, any amended return claiming an R&D credit refund must include business component identification, individual activity descriptions, and QRE breakdowns at the time of filing. Claims that skip that information come back as not perfected, with a 45-day window to supply what’s missing. The perfection transition period runs through January 10, 2027.

This matters if you’ve filed amended return claims for prior years to capture credits you originally missed. Those claims face essentially the same documentation requirements that Section G will require for original returns starting in 2026. If your amended return documentation doesn’t meet that bar, expect a perfection request.

Getting Ahead of This

Across all these shifts, one thread stays consistent: the IRS wants documentation created in real time, at the project level, with enough specificity to show that each claimed activity satisfies the four-part test — without requiring inferential leaps. That’s a higher standard than many companies have maintained historically.

Want to talk about where your documentation stands against the current exam standard? Reach out. We would love to take a look.

Stephen Whiteaker, CPA

As MASSIE’s Director of Controversy, Stephen specializes in audit risk assessment and quality review. His proficiency in navigating complex tax law makes him an essential resource in addressing tax technical challenges for clients. His exten...