Skip to content

The Rules Changed: What Section 174A and Form 6765 Section G Mean for Software Companies

When the rules change, someone needs to review the process. For companies that build software, two rules changed at once:

  • Section 174A changed how research and development costs are deducted, starting in 2025.
  • Section G of Form 6765 changed what you report when you claim the R&D credit, starting with tax years beginning after 2025.

The first is good news for cash flow. The second raises the bar on documentation. Here’s what each one means and what to ask your tax team now.

What changed with Section 174A

From 2022 through 2024, Section 174 required companies to capitalize domestic research and experimental (R&E) costs, including software development, and amortize them over five years. Because of the mid-year convention, only about 10% was deductible in the first year. For many software companies that meant paying tax on profit they hadn’t really earned.

The One Big Beautiful Bill Act (Pub. L. 119-21, §70302) added Section 174A. For tax years beginning after December 31, 2024, qualifying domestic R&E costs can be deducted in the year they’re paid or incurred. Companies can still choose to capitalize and amortize them if that suits their tax position.

A few points that often get missed:

  • Foreign research didn’t change. R&E performed outside the U.S. is still amortized over 15 years.
  • There are transition rules for domestic costs capitalized in 2022 to 2024. Rev. Proc. 2025-28 explains how to apply them, and your tax advisor will know which options fit your situation.
  • The R&D credit is a separate question. Section 174A covers the deduction. The credit has its own four-part test under IRC §41(d). Everything that qualifies for the credit qualifies under 174, but not the other way around.

What changed with Section G

Section G is the part of Form 6765 that asks for business-component detail behind the credit. It was optional for tax years 2024 and 2025. For tax years beginning after December 31, 2025, it’s required for most filers.

For each business component (a product, process, software or technique), Section G asks for:

  • The type of component, and for software, the type of software
  • Wages split three ways: direct research, direct supervision and direct support
  • Supplies, computer rental or lease costs and contract research

You list components from largest to smallest QREs until you reach 80% of total QREs or 50 components, whichever comes first, and group the rest into one aggregate line.

Who doesn’t have to complete it

The IRS instructions include exceptions, including:

  • Qualified small businesses that elect to apply part of the credit against payroll taxes
  • Taxpayers whose controlled group has QREs of $1.5 million or less and average annual gross receipts of $50 million or less for the prior three years, filing on an original return

Even if you qualify for an exception, completing Section G voluntarily can make the claim clearer and easier to support. Ask your CPA what makes sense for you.

Why Section G is hard to do in March

Most R&D credits are still documented after the fact: surveys sent to software engineers at year end, interviews about projects that shipped months ago, time estimates rebuilt in a spreadsheet.

That approach was always fragile. Section G makes it harder, because it asks for detail that’s difficult to reconstruct: which components the work belonged to, and how each person’s time split between doing, supervising and supporting the research.

The 2026 tax year is almost over. The raw material for that return sits in your repositories and pull requests, but the context behind it fades unless it's captured as the work happens.

What to do now

  1. Sit down with your tax team before year end. Ask what information they’ll need for 2026 and how they plan to handle Section G.
  2. Map your business components. Most software companies can define them by product, platform or major feature. Agree on the list early.
  3. Look at how time is captured today. If the answer is surveys or estimates, plan for a better source of evidence.
  4. Revisit Section 174A treatment for 2025 and any transition elections with your advisor.

How CodeROI helps

CodeROI connects to your source control and engineering tools and captures development activity as it happens: who worked on what, when and on which project, with about 50 attributes per action. Fixed, deterministic rules map that activity to people, projects and wages. There's no AI in the math.

The result is a contemporaneous record your CPA can use for the credit, Section G and Section 174A, kept for seven years. Software engineers don’t fill out timesheets or surveys, and there are no workflow changes. Setup takes under an hour.

One thing to know: CodeROI doesn't look back. Capture starts the day you connect, so connect before January 1 and all of 2027 is on record.

Your CPA files the claim. We bring the proof. Book a 20-minute demo.


Sources: IRS Instructions for Form 6765; 26 U.S.C. §41, §174 and §174A; Pub. L. 119-21, §70302; Rev. Proc. 2025-28. This article is general information, not tax advice. Rules and exceptions depend on your facts. CodeROI is a software platform, not a CPA firm, law firm or financial advisor, and does not provide tax, legal, financial or accounting advice.