Reporting expands for tax years beginning after 2025
The current Form 6765 instructions make Section G generally required for tax years beginning after 2025, with stated exceptions. The exceptions include certain qualified small businesses electing the payroll credit and certain original-return filers meeting both the qualified-expense and gross-receipts thresholds. A business should test the actual requirements rather than assume Section G remains optional because it was optional in an earlier year.
When Section G applies, the form requires business-component information under its 80 percent or top-50 framework, with remaining components reported in aggregate as directed. This reporting exercise does not replace the substantive research-credit tests. It organizes the claim around the products, processes, software, or other components to which research relates. A company that tracks development spending only by department may need an additional project-to-component mapping. Begin that work while engineers and project managers can still identify the technical work. An exception from Section G also does not eliminate the duty to substantiate the underlying credit. Keep the eligibility analysis and the reporting analysis as separate documented decisions.
Build a hypothetical component rollforward
Assume a business has $2 million of supported qualified research expenses and is required to complete Section G. Five components have expenses of $700,000, $500,000, $300,000, $200,000, and $100,000. Another twenty smaller components together account for $200,000. Listed in descending order, the first four components total $1.7 million, or 85 percent of the full pool. In this simplified case, those four satisfy the minimum 80 percent coverage, and the remaining $300,000 is addressed through the required aggregate reporting.
The example does not imply that reporting only those four components substantiates the other expenses. The complete $2 million must still be supported. Nor can management arbitrarily merge unrelated projects to reduce the number of rows. The business-component definition and form instructions control the reporting unit. If a controlled-group rule applies, the coverage and exception calculations need the relevant group information rather than a stand-alone entity total. The practical arithmetic check is straightforward: detailed rows plus the aggregate remainder must reconcile to total qualified expenses, with no overlap between the named components and the remaining pool. Any difference should be resolved before filing.
Connect technical descriptions with cost records
Give each business component a stable identifier that can connect project management, payroll allocations, vendor invoices, and the return workpaper. Document what was developed or improved, which technical uncertainty was addressed, and which activities meet the research requirements. The descriptions should be specific enough to identify the component without relying on internal shorthand known to only one employee.
Reconcile component wages, supplies, computer-use expenses where applicable, and contract research to the qualified-expense summary. Retain the allocation method for employees who work across several components. A department total can be the starting point, but it does not explain which component received the work. Track project renamings and mergers so the annual schedule does not count a component twice under different labels. Preserve exclusions, including routine rollout or foreign work, in the reconciliation to total development spending. The reporting team should be able to move in both directions: from the form row to underlying evidence and from a ledger expense to its inclusion or exclusion. This makes the completed form reviewable rather than merely populated.
Set a close process that survives staff turnover
At periodic project reviews, have technical staff confirm component names, status, and material changes in purpose. Finance should update cost allocations and flag projects with missing evidence before the year ends. An employee leaving the company should hand off the technical record, particularly where that person is the only source of information about failed experiments or abandoned approaches.
Check the latest form and instructions before filing, because reporting details can change and a form revision may apply to a different tax year than its publication date suggests. Record the basis for any Section G exception and retain the calculations. Do not decide eligibility from the credit amount alone: the exception tests use specified expense and receipt measures. Budget the reporting work as part of the claim's compliance cost, especially for businesses with many small components. The owner should receive a reconciled expense total, a documented reporting conclusion, and an evidence file that supports both named and aggregated components. That preparation makes the 2026 reporting requirement manageable without turning return preparation into an unsupported year-end reconstruction.
Sources & further reading
Consult the original guidance and its effective dates. These references support the educational discussion; their application depends on the specific facts.