Form 6765 Section G NetSuite tracking now matters because many taxpayers with tax years beginning after 2025 must report qualified research expenses at the business-component level. To do that well, NetSuite should tie each component to time entries, purchasing, vendor bills, and technical support. It should also keep Section 174A treatment separate from Section 41 credit eligibility. The goal is simple: give your tax adviser a clean, traceable record instead of a year-end spreadsheet rebuild.

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.

TL;DR: Form 6765 Section G pushes R&D credit tracking down to the business-component level, so finance teams need cleaner links between time, purchasing, vendor costs, and technical evidence. NetSuite can support that workflow when you separate Section 174A treatment from Section 41 credit eligibility and tag each cost to a stable business-component record. The result is a monthly register your tax adviser can review, instead of a year-end spreadsheet rebuild.

Form 6765 Section G NetSuite requirements changed for 2026

For 2026, finance teams need more than a total R&D spend number. They need to show which business component created each cost, what qualified activity it supported, and how the amount ties back to source records. OBBBA changed domestic research tax treatment, and the revised Form 6765 raised the reporting standard for the Section 41 credit. That makes component-level tracking an operating requirement, not a year-end cleanup project.

For many taxpayers with tax years beginning after December 31, 2025, Section G is generally required unless an exception applies. When it applies, taxpayers usually list business components in descending QRE order until they cover at least 80% of total QREs or reach 50 components. The remaining components may then be reported in aggregate. The IRS Form 6765 instructions explain the current rules 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. It also created transition relief for some domestic amounts capitalized in 2022 through 2024. Foreign research still follows a separate 15-year amortization rule. 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 research must be tested by business component against the four-part test: permitted purpose, technological uncertainty, process of experimentation, and technological in nature. Statutory exclusions still matter. Those include 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 force engineers to make legal judgments in every time entry. It should capture a clear evidence trail instead. That means recording the uncertainty the team worked through, the options considered, the work performed, the component involved, the people involved, and the costs incurred. Your tax adviser can then apply the legal standard to those facts. The IRS Section 41 audit guidance is a useful reference for the records and nexus the Service reviews.

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

• Information sought and the technical uncertainty

• Technological basis and the experiments or alternatives considered

• Business purpose research locations, and current status

• 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.

• Direct Research

• Direct Supervision

• Direct Support

• Non-QRE R&D / Section 174A Only

• Pending Tax Review

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 your team also needs stronger production and cost controls, read our NetSuite for Manufacturing implementation guide and NetSuite for Assembly Manufacturing guide for the operating model around work orders, costing, and shop floor data. Those controls make R&D tagging easier to govern once finance, operations, and engineering share the same process.

QRE categories mapped to NetSuite records

The biggest pain points usually show up in two places: month-end close and audit prep. Finance teams lose time when wage allocations, vendor costs, and project evidence do not roll up cleanly by business component. Leaders lose confidence when the tax team has to rebuild support from payroll exports, invoices, and interviews. If that is happening now, add the component code, activity classification, and exception reviews earlier in the process rather than waiting for filing season.

Where CFOs and controllers feel the pain first

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 with Softype. We can help your team map the component, time, AP, and documentation controls needed for a cleaner Section G workflow.

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 starts Form 6765 work, it should pull a controlled Section G register from NetSuite. It should not rebuild the year from payroll files, vendor invoices, and interviews. Softype helps teams design the business-component, time, AP, and documentation controls that make that monthly process easier to run and easier to defend.

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.

• Section G makes business-component tracking the core reporting unit for many 2026 filings.

• Keep Section 174A treatment separate from Section 41 credit eligibility in your ERP design.

• Tag wages, supplies, and contract research to a stable component code at the transaction level.

• Store technical uncertainty, experiments, and source evidence with the component record, not in a year-end workbook.

• Build a monthly Section G register so tax review starts from governed records instead of spreadsheet reconstruction.