Answer in 60 seconds: For many taxpayers with tax years beginning after 2025, Form 6765 Section G requires business-component-level reporting of qualified research expenses (QREs). NetSuite should connect each component to time entries, purchasing, vendor bills, supporting technical evidence, and a separate Section 174A/Section 41 classification. That gives your tax adviser a traceable data set—not a year-end spreadsheet reconstruction.

If you are auditing whether NetSuite can support project-level QRE capture, read our NetSuite for Manufacturing implementation guide for the broader operating model behind governed R&D data.

What changed for 2026?

The OBBBA reset the tax treatment of domestic research expenditures, while the redesigned Form 6765 raises the reporting bar for the Section 41 research credit. Finance teams now need to answer a more specific question than “How much did we spend on R&D?”: which business component generated each cost, what qualified activity did it support, and can the amount be traced to source records?

For many taxpayers with tax years beginning after December 31, 2025, Section G is generally mandatory unless an exception applies. When it is required, taxpayers generally list business components in descending QRE order until the listed components represent at least 80% of total QREs or the taxpayer reaches 50 components; remaining components may be reported in aggregate. The IRS Form 6765 instructions explain the current reporting requirements and exceptions.

A business component is a product, process, computer software program, technique, formula, or invention held for sale, lease, license, or use in your trade or business. The analysis is not satisfied by labeling an entire engineering department “R&D.” You need to connect research activities and QREs to the specific component that generated them.

There are exceptions, including a potential original-return exception for a controlled group with total QREs of $1.5 million or less and average annual gross receipts of $50 million or less for the prior three tax years, as well as an exception for certain qualified small businesses claiming the payroll-tax credit. Those thresholds are not a reason to postpone the data model. The same component-level records are valuable whether Section G is mandatory today or becomes mandatory as the business grows.

OBBBA restored domestic expensing, but it did not make every R&D cost a credit QRE

OBBBA introduced Section 174A and generally restored immediate deduction for domestic research and experimental expenditures paid or incurred in tax years beginning after December 31, 2024, subject to elections and transition rules. The law also provides relief mechanisms for certain domestic amounts capitalized in 2022 through 2024, while foreign research remains subject to a separate 15-year amortization regime. Review the IRS research credit guidance, IRS Section 174 guidance, and PwC's H.R. 1 tax summary with your advisers.

The control point is to keep Section 174A and Section 41 distinct. Section 174A addresses the treatment of domestic research or experimental expenditures. Section 41 asks whether the research and cost meet credit-specific requirements. A domestic cost that is expensed under the Section 174 fix is not automatically a QRE.

The Section 41 four-part test is the design brief for your evidence trail

For a cost to support the Section 41 credit, the underlying research generally must satisfy the familiar four-part test: permitted purpose, technological uncertainty, process of experimentation, and technological in nature. The test must be applied by business component, and statutory exclusions still matter, including foreign research, funded research, post-commercial-production work, routine testing, customer-specific adaptation, and research in the social sciences, arts, or humanities.

NetSuite should not ask an engineer to make a legal conclusion in every time entry. Its role is to retain a practical evidence trail: what uncertainty the team addressed, alternatives considered, work performed, component supported, people involved, and costs incurred. Your tax adviser can then apply the legal standard to the preserved facts. The IRS Section 41 audit guidance is a useful reference for the records and nexus the Service examines.

That evidence should sit on a stable business-component record, not only in a year-end tax study workbook. A component such as Automated Inspection Process, BC-2026-012 should state the technical information sought, the technical uncertainty, the hypothesis or alternatives tested, the owner, the activity dates, and links to specifications, test plans, tickets, prototypes, and results.

For a related view of how one governed financial data spine supports planning and analysis, see our NetSuite Planning and Budgeting guide.

Five things your ERP must do for Form 6765 Section G

1. Assign a business-component code to every relevant transaction

Create an R&D Business Component custom record and an associated custom segment. Give each component an immutable ID, such as BC-2026-012, so it remains recognizable even if a project or product name changes. Use the segment on Projects, Project Tasks, time entries, purchase orders, vendor bills, expense reports, inventory issues, and journals where relevant.

Project is not always the same as business component. One project can cover several products or processes; conversely, one component may span multiple engineering workstreams. Use Projects as an operational container and the component segment as the Section G reporting key.

2. Keep the technical-uncertainty narrative with the component

On the component master record, capture the information sought to be discovered, the technical uncertainty, the technological basis, the experiments or alternatives considered, the business purpose, research locations, and current status. Attach or link supporting evidence such as design specifications, source-control references, prototype results, test data, decision logs, and engineering tickets.

A statement such as “improve the platform” is weak. A useful record explains the uncertainty: for example, whether a proposed allocation algorithm could meet a defined response-time and concurrency threshold while preserving data consistency. The objective is to capture contemporaneous operating evidence, not to turn project managers into tax counsel.

3. Allocate engineer wages from approved, project-level time

Wages are often the largest QRE category. Section G separately reports wages for direct research, direct supervision, and direct support. Configure time entry so employees working on R&D select the business component, project or task, activity classification, work location, and a concise description of the work performed.

Use a controlled activity list: Direct Research, Direct Supervision, Direct Support, Non-QRE R&D/Section 174A Only, and Pending Tax Review. Reconcile approved qualified activity percentages to the appropriate wage base rather than substituting standard labor cost or bill rates for the final tax calculation. Contemporaneous time records supported by project artifacts are generally more defensible than annual interview-based allocations.

4. Track supplies consumed in research at the transaction line

Section G calls for qualified supplies separately. Require the business-component code and QRE cost category on R&D-related purchase orders, vendor bills, expense reports, inventory issues, and requisitions. The record should distinguish a supply consumed in testing or prototyping from indirect overhead or general department spending.

Use exception reviews to identify research accounts, departments, suppliers, or projects with missing component tags. That turns the month-end close into a correction window rather than an after-the-fact reconstruction exercise.

5. Preserve contract-research facts and the applicable credit amount

For third-party work, attach or link the master service agreement, statement of work, deliverables, payment evidence, rights-to-results terms, research location, and funding-risk analysis to the vendor bill or component record. Tag the vendor charge to the component and a contract-research work type.

Store both the gross accounting cost and a separate, reviewable Section 41 applicable amount. Qualifying contract research is often included at 65%, while different statutory rules can apply in defined circumstances such as qualified research consortium payments or certain research arrangements. Do not hard-code a conclusion across all vendors. Let tax review control the applicable percentage.

If you want the broader ERP context around production controls, costing, and manufacturing operations, see our NetSuite for Manufacturing: Complete Implementation Guide 2026 and NetSuite for Assembly Manufacturing: Production Tracking, MRP & Shop Floor Control.

QRE categories mapped to NetSuite records

Why QuickBooks plus Excel usually breaks the audit trail

QuickBooks can store accounting transactions, and Excel can assemble a calculation. The problem is maintaining a controlled, repeatable nexus between a specific business component, the qualifying activity, source evidence, and each underlying cost. When project identifiers, time allocations, vendor terms, and technical records live across disconnected systems, the year-end study often depends on manual joins and retrospective interviews.

NetSuite is not automatically audit-ready merely because it is an ERP. The advantage comes from making the business-component tag, activity classification, approval, attachment, and exception workflow part of normal operations. Projects, Time Tracking, AP, custom fields, and saved searches can create one traceable path from Section G output back to source transactions and supporting evidence.

A monthly operating workflow for QRE tracking in NetSuite

• Create or update business-component records as initiatives begin, change, commercialize, or close.

• Require component, activity classification, and meaningful work descriptions on R&D time entries.

• Review and approve time before payroll and period close.

• Tag R&D-related purchasing, AP, expense, and inventory transactions at line level.

• Attach or link technical evidence, contracts, invoices, and deliverables to the related component.

• Run exception reviews for missing tags, pending tax review, foreign work, unapproved time, and vendor charges without supporting agreements.

• Produce a monthly Section 41 register and reconcile it to payroll, AP, project costing, and the general ledger.

Form 6765 Section G documentation checklist

1. Identify the business component. Assign a stable ID, name, component type, legal entity, and owner.

2. Document the four-part-test facts. Record permitted purpose, technical uncertainty, technological basis, and experimentation evidence.

3. Code employee time. Capture component, task, activity classification, location, and work description, and retain approval history.

4. Reconcile wage data. Connect approved time allocations to the appropriate wage base and separate direct research, supervision, and support.

5. Tag supply transactions. Preserve component, cost category, item, amount, consumption purpose, and source documents.

6. Validate contract research. Retain the agreement, statement of work, rights and funding terms, domestic-location evidence, invoices, deliverables, and reviewed applicable amount.

7. Separate Section 174A and Section 41. Retain distinct tax-treatment fields and exclusion reason codes.

8. Build the Section G output. Rank total QREs by component, identify the 80% or Top 50 population, and reconcile the register to the relevant Form 6765 totals.

If you want to pressure-test your current setup before year-end, book a 30-min R&D expense tracking scoping call.

Frequently asked questions

Make NetSuite the QRE trail, not the source of another spreadsheet

Form 6765 Section G turns R&D credit reporting into a data-governance issue. The 2026 objective is not to make NetSuite decide a tax position. It is to capture the component, activity, transaction, and supporting evidence in a form that makes tax-adviser review and final reporting traceable, repeatable, and reconcilable.

When the tax team begins its Form 6765 work, it should be extracting a controlled Section G register from NetSuite, not rebuilding the year from payroll files, vendor invoices, and interviews. Book a 30-min R&D expense tracking scoping call to map the business-component, time, AP, and documentation controls needed for your environment.

This article provides general ERP-configuration information, not tax, legal, or accounting advice. Consult qualified advisers on Section 41 eligibility, Section 174 and 174A treatment, elections, controlled-group rules, and Form 6765 filing positions.