R&D tax credit documentation requirements

Documentation is the claim.

A credit is only worth what you can prove. Qualification is decided on the facts you recorded while the work was happening - organized by business component, tied to named people and real dollars, and written so an examiner can follow it without your engineers in the room. Here is what that file contains, what the rules actually require, and what the IRS asks for when it looks.

Get your free R&D credit assessment Back to the §41 guide

Two machined aluminum flange parts resting on their own engineering drawings — The record usually exists before anyone calls it documentation: sketches, dated sheets, and the working notes behind a design decision.Photo by EnCata PD on Unsplash

What the rules actually require

Two provisions do the work. IRC §6001 requires every taxpayer to keep records sufficient to establish the items shown on the return. Treas. Reg. §1.41-4(d) adds the credit-specific version: a taxpayer claiming the research credit must retain records in sufficiently usable form and detail to substantiate that the expenditures claimed are eligible.

Notice what is not there. No form of log is prescribed. No template is blessed. The 2001 proposed regulations would have imposed a specific contemporaneous-documentation requirement, and that requirement was not carried into the final 2003 regulations - which is why any vendor telling you the regulations mandate a particular documentation product is selling, not citing.

The practical standard is stricter than the written one anyway. Records made while the work was happening are believed. Reconstructions made two years later have to be corroborated by something dated, and the corroboration is where thin studies come apart. So the operating rule is simple: capture the evidence the business already generates, at the time it is generated, and organize it before you need it.

Unit of proof

The business component is the unit of proof

Not the department, not the fiscal year, not “R&D” as a line item. Every substantive question the IRS asks is asked one component at a time.

A business component is defined at §41(d)(2)(B) as any product, process, computer software, technique, formula, or invention held for sale, lease, or license, or used in your trade or business. The four-part test is applied to each one. Where a component as a whole does not qualify, the shrink-back rule at Treas. Reg. §1.41-4(b)(2) applies the test to the most significant subset of its elements - a subsystem, a module, a process step - which is often how a genuinely innovative piece of a mostly routine release survives review.

That structure is not a formality. It is the reason a study organized around projects, cost centers, or customers has to be rebuilt before it can be defended, and the reason QRE allocation should be performed component-first rather than pushed down from a department total.

Identity and dates

What the component is - product, process, software, technique, formula, or invention - who owned it, and the period during which development work ran. Dates matter: qualified research generally stops once the component is ready for commercial production.

The uncertainty at the outset

What you did not know when you started: whether the result was achievable at all, how to achieve it, or which design was appropriate. This is the fact an examiner probes first, and it has to be evidenced from the beginning of the work, not asserted at year end.

The alternatives evaluated

A process of experimentation means you considered and tested more than one path. Design reviews, trade studies, architecture decision records, formulation trials, and A/B or bench-test matrices are the natural artifacts.

The experimentation itself

Test plans and results, simulation and modeling output, prototypes and first articles, build travelers, batch records, lab notebooks, commit and ticket history - evidence that alternatives were actually evaluated rather than merely listed.

The people, by name

Who worked on this component, in what role - performing the research, directly supervising it, or directly supporting it - and how much of their year that accounted for.

The money, by category

The wages, supplies, computer or cloud rental, and contract-research amounts allocated to this component, traceable back to payroll registers, the general ledger, and the underlying invoices and statements of work.

Wages have to point at activities

Wages are usually the largest QRE category and the first one adjusted. The question is never “does this person do R&D” - it is “which component, doing what, and how do you know.”

§41(b)(2)(B) counts three kinds of qualified services: performing qualified research, directly supervising it, and directly supporting it. The three are not interchangeable. Direct supervision means first-line technical management of the researchers, not a department head two levels up. Direct support means work performed for the research itself - a technician machining a test fixture, a lab assistant running assays - not the HR, finance, or legal functions that support the company generally.

There is one simplification worth knowing. Under Treas. Reg. §1.41-2(d)(2), if substantially all of an individual’s services for the year are qualified services - 80% or more - then all of that individual’s wages for the year are treated as qualified. Below that line, wages are allocated on a reasonable basis under §1.41-2(d)(1), and the word carrying the weight is reasonable: a basis you can describe, apply consistently, and support.

Most companies already hold the raw material. Ticket systems, source control, PLM and change orders, MES travelers, and electronic lab notebooks all record who touched what and when. Mapping those systems to the business-component list is nearly always faster - and more defensible - than standing up a new timesheet regime the engineers will resent and backfill.

Time and wage substantiation approaches, from strongest to weakest
Approach	How it works	Evidentiary weight	What to watch
Contemporaneous project time	Engineers book hours to projects or tickets as the work happens, and the project taxonomy maps to business components.	Strongest	The allocation is evidence, not an estimate. Requires that the project taxonomy and the business-component list line up - the most common place this breaks.
System-derived allocation	Ticket, commit, PLM, MES, or ELN activity is attributed to components and used to allocate each person’s year.	Strong	Uses records the company already keeps for other reasons, which is why it holds up. Needs a written, consistently applied methodology and a sanity check against how people actually spent their time.
Structured interviews plus corroboration	Technical leads state allocations in recorded interviews, each one tied to dated artifacts for the same period.	Workable	Standard practice where no time system exists. The corroboration is what carries it; the interview alone is a statement, not a record.
Unsupported estimates	A flat percentage applied across a department with nothing dated behind it.	Weak	This is what gets adjusted. Courts have accepted reasonable allocation methods that rest on real records, and rejected percentages with no documentary anchor at all.

Narratives that answer the test, not the marketing

A technical narrative is not a project summary. It is an argument, one per business component, that walks the four-part test in order and points at evidence for each part: the permitted purpose the work served, why it relied on principles of engineering, computer science, or the physical or biological sciences, the specific technical uncertainty faced at the outset, and the systematic evaluation of alternatives used to resolve it.

Two things separate a narrative that holds from one that reads well. First, specificity: “improved throughput” is a claim, while “could not hold ±0.02 mm on the hardened sleeve at the required cycle time, evaluated four fixturing approaches over eleven trials” is a fact pattern. Second, traceability: every assertion should be answerable with a dated artifact you can hand over, and the narrative should say which one.

The same document also has to carry the negative screening. §41(d)(4) excludes research after commercial production, adaptation and duplication, surveys and studies, routine data collection and quality control, social sciences, research conducted outside the United States, funded research, and - via a higher threshold - most internal-use software. A narrative that never mentions why the exclusions do not apply leaves the examiner to decide that for you.

Form 6765

The December 2024 form made component detail a filing item

Substantiation used to live entirely in your files. On the revised Form 6765, part of it is reported on the return itself.

The IRS finalized a substantially revised Form 6765 in December 2024. Alongside the familiar credit computations, it added Section E (other information), Section F (a consolidated QRE summary), and Section G - business component information, reported component by component.

Section G is the one that changes behavior. For each reported component you supply its name or identifier, its type, whether software is internal-use, a description of the information sought to be discovered (currently required only on amended returns), and the QREs assigned to that component broken out by category - direct research wages, direct supervision, direct support, supplies, computer rental, and contract research. Components are reported in descending order by QRE until you have covered 80% of total QREs, capped at 50 components.

Section A

Regular Credit

The 20% computation over the fixed-base amount, for filers using the Regular Credit method.

Section B

Alternative Simplified Credit

The ASC computation - 14% over 50% of the prior three-year average, or 6% of current-year QREs where there is no qualifying base.

Section C

Current-year credit

Where the elected method lands, and how the credit carries into the general business credit.

Section D

QSB payroll tax election

The qualified small business election under §41(h) - the gateway to Form 8974 and the payroll-tax offset.

Section E

Other information

A short set of questions including the number of business components generating QREs, officers’ wages in the claim, whether a major portion of a trade or business was acquired or disposed of, and whether QREs were determined under the ASC 730 directive.

Section F

QRE summary

Wages, supplies, computer rental, and contract research totaled in one place, feeding the computation in Section A or B.

Section G

Business component detail

The component-by-component report: name, type, whether software is internal-use, the information sought to be discovered (amended returns only, currently), and the QREs assigned to that component split by category.

Who has to complete Section G, and when. Under the current instructions, Section G is optional for tax years beginning before 2026 and applicable for tax years beginning after 2025. As the instructions stand, two groups are excepted: qualified small businesses under §41(h)(3) that check the box to claim the reduced payroll tax credit, and taxpayers with total QREs of $1.5 million or less - determined at the controlled-group level - and gross receipts of $50 million or less, claiming the credit on an originally filed return. Thresholds and phase-in dates have already been revised more than once; confirm against the current-year form instructions before you rely on an exception.

The practical consequence is the same either way. A study that already resolves to the business component populates Section G directly. A study built on department totals has to be taken apart first - and the component detail it produces under pressure is exactly the detail an examiner will test.

What the IRS asks for

An examination of the research credit opens with document requests. The specific wording varies; the shape rarely does.

Quantitative requests

Payroll registers and wage detail for every employee in the claim, with titles
The time records or written allocation methodology behind each qualified percentage
General-ledger detail for supply accounts, plus invoices for a sample of items
Contracts, statements of work, and purchase orders for claimed contract research
Invoices supporting computer and cloud rental included as QREs
Prior-year gross receipts and QREs supporting the base-period computation
Organization charts and job descriptions for the claimed population
The credit computation, reconciled line-for-line to the filed Form 6765

Technical requests

The business-component list with QREs assigned to each
The technical narrative for each sampled component
Dated evidence of the uncertainty that existed at the outset
Evidence of the alternatives evaluated and how they were tested
Test plans, results, travelers, batch records, notebooks, tickets, commits
Records tying named individuals to named components
Grant agreements and customer contracts for the funded-research screen
Evidence of when each component reached commercial production

Amended returns carry an extra burden

A research credit claimed on an amended return is a refund claim, and the IRS requires specified information for the claim to be valid - identifying the business components the claim relates to, the research activities performed for each, and the total qualified wage, supply, and contract-research expenses for the year. Two earlier items, naming the individuals who performed each activity and the information each sought to discover, were waived for refund claims filed on or after June 18, 2024. This guidance has been revised repeatedly, including the window allowed to perfect a deficient claim; check current IRS guidance before filing. A study built to component level satisfies the substance of the requirement as a by-product.

One safe harbor, for a narrow population

Certain larger taxpayers that follow U.S. GAAP and report R&D as a separate line item in certified audited financial statements may use the IRS’s ASC 730 directive to treat an adjusted book R&D figure as QREs for examination purposes - which is why the revised Form 6765 asks whether you did. It is an administrative convenience for a specific profile, not a general alternative to substantiation, and most companies reading this page will not qualify for it.

Built as evidence, not assembled as a defense

The difference between a study that survives review and one that does not is usually decided months before anyone asks.

The Ricerca platform is organized around the business component from intake forward. Payroll, general-ledger, and project data are mapped to components; each component is evaluated against the four-part test and screened against every §41(d)(4) exclusion before a dollar is counted; wages are allocated with a stated, consistently applied methodology; and each narrative is written against the test with its supporting artifacts referenced. The software will not pass a component that is missing its substantiation, which is a deliberately inconvenient design decision.

Our R&D experts review qualification decisions, allocations, and narratives, and finalize every study before it is issued. What you receive is the study report, the QRE workpapers, per-component narratives, and filing-ready forms - Form 6765 including the Section G detail, Form 8974 where the payroll offset applies, and a pro-forma Form 3800 - in an organized audit file your preparer can file from and an examiner can read. See how a study runs end to end.

If the IRS examines the credit, Audit Protection is included with every study: Ricerca prepares the audit response, assembles the documentation the examiner requests, and defends the technical positions in the study, working alongside your tax preparer. Representation before the IRS, where it is needed, is performed by credentialed practitioners. Coverage is limited to the R&D study and the related federal credits, under the terms of your engagement agreement, and depends on the accuracy and completeness of the information you provide.

Illustrative view of a study package. What a given engagement includes depends on the elections made and the forms its return actually needs.

What the audit file looks like from the outside

An examiner does not read a study; they open it at the exhibit they asked for. This is the shape of an audit-defense binder index - structure only, with no company, no figures, and no engagement behind it.

Audit-defense binder - index

Illustrative - synthetic data

Exhibit 1 Study report and scope of the engagement
Exhibit 2 Business component register, with QREs assigned to each component
Exhibit 3 Technical narrative, one per reported business component
Exhibit 4 Four-part-test determination and §41(d)(4) exclusion screening, by component
Exhibit 5 Wage QRE workpaper: payroll register tie-out, roles, and qualified percentages
Exhibit 6 Allocation methodology and the time or system evidence behind it
Exhibit 7 Supplies workpaper: general-ledger detail and supporting invoices
Exhibit 8 Contract research workpaper: agreements, statements of work, rights-and-risk determination
Exhibit 9 Computer and cloud rental workpaper, with the allocation method stated
Exhibit 10 Credit computation, reconciled line-for-line to the filed Form 6765
Exhibit 11 Form 6765 package including the Section G component detail
Exhibit 12 Form 8974 package, where the §41(h) payroll offset was elected

Index, page 1

Why an index is the test

Every line above answers a request on the quantitative or technical list further up this page. If a request has no exhibit, the file is not finished - and that gap is easier to see in an index than in a folder.

The order also matters. Component register, then narratives, then the workpapers that carry the dollars to each component, then the computation reconciled to the form: that is the order the questions arrive in.

Two exhibits are conditional rather than standard. Section G detail rides with the Form 6765 package, and the Form 8974 package exists only where the §41(h) payroll offset was elected.

Read the primary sources

Everything above is summary. The statute, the regulations, and the current form instructions govern.

Documentation questions we get most

Does §41 require contemporaneous documentation?

Not as a prescribed format. What binds is IRC §6001, which requires records sufficient to establish the items shown on the return, and Treas. Reg. §1.41-4(d), which requires records in sufficiently usable form and detail to substantiate that the expenditures claimed are eligible. The 2001 proposed regulations would have imposed a specific contemporaneous-documentation requirement and it was not carried into the final 2003 regulations. Contemporaneous records are an evidentiary advantage, not a statutory rule - and that distinction is worth stating precisely.

What is the unit a study has to document?

The business component, defined at §41(d)(2)(B) as any product, process, computer software, technique, formula, or invention held for sale, lease, or license, or used in your trade or business. The four-part test is applied to each one, and where a component as a whole does not qualify, the shrink-back rule at Treas. Reg. §1.41-4(b)(2) applies the test to the most significant subset of its elements. A study organized around projects, cost centers, or customers has to be rebuilt before it can be defended.

Our engineers do not track time. Can the wages still be substantiated?

Usually, but not with a flat percentage. Contemporaneous project time is the strongest evidence; a system-derived allocation built from ticket, commit, PLM, MES, or ELN activity is strong because it uses records the company already keeps for other reasons; structured interviews tied to dated artifacts for the same period are workable where no time system exists. A flat percentage applied across a department with nothing dated behind it is what gets adjusted.

What does Form 6765 Section G actually report?

For each reported component: its name or identifier, its type, whether software is internal-use, a description of the information sought to be discovered (currently required only on amended returns), and the QREs assigned to that component broken out by category. Components are reported in descending order by QRE until 80% of total QREs is covered, capped at 50 components. Thresholds and phase-in dates have been revised more than once, so confirm against the current-year instructions.

What does the IRS request when it examines the credit?

An examination opens with document requests, and the shape rarely varies: on the quantitative side, payroll registers and wage detail, the time records or written allocation methodology behind each qualified percentage, general-ledger detail and invoices for supplies, contracts and statements of work for contract research, and the computation reconciled line-for-line to the filed Form 6765; on the technical side, the business-component list with QREs assigned, the narrative for each sampled component, dated evidence of the uncertainty and of the alternatives evaluated, and records tying named individuals to named components.

Who defends the documentation if the credit is examined?

Audit Protection is included with every study: Ricerca prepares the audit response, assembles the documentation the examiner requests, and defends the technical positions in the study, working alongside your tax preparer. Representation before the IRS, where it is needed, is performed by credentialed practitioners. Coverage is limited to the R&D study and the related federal credits, under the terms of your engagement agreement, and depends on the accuracy and completeness of the information you provide.

Next: the four-part test, which is what each narrative has to prove - or Audit Protection, which is what happens if the IRS examines the credit.

Filing soon? The Form 6765 guide walks the form line by line, and what changed for 2026 covers the year Section G stops being optional. On the blog: what examiners actually ask for and Form 6765 Section G: who must file and who is exempt.

Have the file before you need it

Tell us about your R&D and your systems. We’ll scope a study that produces component-level substantiation as a by-product of the work - filing-ready forms, technical narratives, and an organized audit file, backed by Audit Protection.

[email protected] We typically reply within one business day.

Get your free R&D credit assessment Talk to our team