Software capitalization vs Section 174A: why the same engineering hours give two numbers

In brief

Why the same engineering labor is capitalized under ASC 350-40 but deducted or amortized under Sections 174A and 174, and the time records IT finance needs.

Steve Elliott

Steve Elliott · · 6 min read


On this page
  1. What does each rulebook ask about the same labor?
  2. How did we get here?
  3. Book vs tax, side by side
  4. A worked example (illustrative)
  5. What does this mean for time capture?
  6. What should IT finance do now?
  7. Sources

Book and tax give you two numbers because they sort the same engineering hours by different tests. For financial reporting, ASC 350-40 asks whether the work builds an internal-use software asset once funding is committed and development uncertainty is resolved. For US federal tax, the question is whether the cost is a research or experimental expenditure, which by statute includes any software development cost, and whether the research happened in the United States.

Since the 2025 tax law, software development labor performed in the United States and capitalized on the books is generally deductible at once for tax. Work done outside the United States is still amortized over 15 years, even where the books expense it. This post walks through the rules, an illustrative example and the labor records that support both. It is not tax or accounting advice; confirm how these rules apply to you with your tax and accounting advisers.

What does each rulebook ask about the same labor?

Software capitalization for internal-use software sits in ASC 350-40. Under ASU 2025-06, effective for annual periods beginning after December 15, 2027, capitalization starts when management authorizes and commits to funding the project and completion is probable, which it isn't while significant development uncertainty exists. Eligible costs include payroll for employees directly involved in the project, to the extent of their time on it. Training, data conversion, overhead and general and administrative costs are expensed. Our ASU 2025-06 post covers the book side in detail.

The tax side is a separate code. New Section 174A, added by Public Law 119-21 (enacted July 4, 2025), allows a deduction for domestic research or experimental expenditures. It applies to amounts paid or incurred in taxable years beginning after December 31, 2024. Section 174A(d)(3) treats "any amount paid or incurred in connection with the development of any software" as such an expenditure. Domestic means not foreign research, which the statute defines by reference to the research credit as research conducted outside the United States, Puerto Rico or a US possession. Foreign expenditures stay under amended Section 174 and are amortized ratably over 15 years, starting at the midpoint of the taxable year.

Two consequences follow. Book capitalization depends on where a project stands. Tax treatment depends on what the activity is and where it was performed. Neither test looks at the other.

How did we get here?

For taxable years beginning after December 31, 2021, the Tax Cuts and Jobs Act required companies to capitalize research or experimental expenditures, including software development. Domestic costs were amortized over five years and foreign costs over 15. For three tax years, many companies were in the opposite position from today: software labor they expensed on the books had to be capitalized for tax.

The 2025 law reversed that for domestic work and left foreign work where it was. In its interim guidance on the old rules, Notice 2023-63, the IRS described software development broadly: planning, designing, building a model, writing source code and testing, with upgrades and enhancements included. Corrective maintenance to fix programming errors, and training employees on new software, were outside it. Ask your tax advisers how far that guidance carries over to Section 174A. In September 2026, Rev. Proc. 2026-32 expanded the automatic method-change procedures for R&E expenditures. Further guidance under Sections 174 and 174A is on the Treasury-IRS 2026-2027 priority guidance plan, published September 29, 2026.

Book vs tax, side by side

Book: ASC 350-40 (as amended by ASU 2025-06)Tax: Section 174A (domestic)Tax: Section 174 (foreign)
EffectiveAnnual periods beginning after Dec 15, 2027; early adoption permittedTaxable years beginning after Dec 31, 2024Taxable years beginning after Dec 31, 2021 (15 years retained by the 2025 law)
What qualifiesEligible costs of internal-use software once funding is committed and significant development uncertainty is resolvedResearch or experimental expenditures; software development is included by statuteThe same, for research conducted outside the US, Puerto Rico and US possessions
Default treatmentCapitalize, then amortize from when the software is ready for intended useDeduct as paid or incurredAmortize over 15 years from the midpoint of the taxable year
OptionsPolicy choices (for example, useful life)Elect to amortize over at least 60 months (174A(c)), or over 10 years (Section 59(e))None; 15-year amortization is required
Labor in early, uncertain workExpensedGenerally R&E: deductedGenerally R&E: amortized
Bug-fix maintenance, trainingExpensedExcluded under the 2023 interim guidance (status under 174A not yet confirmed)Same
What decides itProject status and type of costActivity typeActivity type and location

Two interactions matter for the tax number. If you claim the research credit, you must reduce domestic R&E expenditures by the credit amount, or elect a reduced credit on a timely filed return. And because the immediate deduction for domestic work changes book-tax differences, it flows into deferred taxes under ASC 740.

A worked example (illustrative)

Take a calendar-year US company in 2028, its first year under ASU 2025-06. It spends $5 million of engineering labor on one internal-use system. US staff account for $4 million and a team outside the United States for $1 million. Assume no tax elections and no research credit, and assume the company follows Notice 2023-63's treatment of maintenance and training. All figures are illustrative.

ActivityUS laborNon-US laborBook, 2028Tax deduction, 2028
Feature build after uncertainty resolved$2.4M$0.6MCapitalize $3.0M$2.4M (US) + $20,000 (non-US, 15 years, half year)
Prototyping while uncertainty unresolved$0.6M$0.2MExpense $0.8M$0.6M (US) + $6,667 (non-US)
Bug-fix maintenance$0.5M$0.2MExpense $0.7MTreated as outside 174A and 174 (per the assumption); other rules apply
Training$0.5MnoneExpense $0.5MTreated as outside 174A and 174 (per the assumption); other rules apply

Three things stand out:

  • Book capitalizes $3.0 million. Tax deducts $3.0 million of domestic R&E at once, but it is a different $3.0 million: it includes $0.6 million of prototyping the books expensed and excludes the $0.6 million of non-US feature work the books capitalized.
  • The $0.2 million of non-US prototyping is expensed on the books but recovered over 15 years for tax, about $6,667 in the first year.
  • Location moves the tax answer and doesn't move the book answer. A reorganization that shifts work offshore changes the tax deduction, not the capitalized asset.

The point is that one set of hours gets classified twice, on two axes.

What does this mean for time capture?

In our view, the practical risk isn't the rules. It's a time-capture design built for one of them. A capitalization process built for the books records project, phase or uncertainty status, and capitalizable hours. A tax R&E study needs activity type and location. If those fields aren't captured when the work happens, someone often rebuilds them from interviews and org charts at year end.

A labor record that supports both treatments carries, at minimum:

  • Person and employment type. Employee or contractor, and the cost center.
  • Project or product. Tied to the funding decision the books rely on.
  • Activity type. New functionality or enhancement, maintenance, training, data conversion, support.
  • Work location. Where the work was performed. This drives the domestic or foreign split.
  • Uncertainty status and date. When significant development uncertainty was resolved, with a link to the record that shows it.
  • Hours and loaded cost. At a level finance can reconcile to payroll and the general ledger.

In our view, none of this requires a separate tax timesheet. It requires agreeing the fields with the controller and the tax team before the year starts, so one capture serves both. We think that where engineers work in sprints, the product backlog is a natural place to carry activity type, and that location, which usually sits in HR systems, should be joined to time records rather than re-entered.

What should IT finance do now?

  1. Sit down with the tax team and the controller and confirm which treatments and elections the company uses for 2025 onward, including any transition choice for 2022 to 2024 balances.
  2. Map current time codes to both tests. Flag any code that mixes capitalizable and non-capitalizable work, or domestic and foreign work.
  3. Add work location and activity type to time capture where they are missing, sourced from HR and delivery systems where possible.
  4. Keep the evidence for when uncertainty was resolved with the labor records it governs.
  5. Run one product line through both treatments as a dry run and reconcile the two numbers.
  6. Plan for book capex and tax deductions to diverge, and make sure forecasts and cash tax estimates don't assume they match.

We think the companies that handle this well treat labor data as part of the operating model, captured once with enough detail to answer finance, tax and portfolio questions alike.

Sources

Frequently asked questions

Is software development deductible for US federal tax in 2025 and later?

Yes, for domestic work. Section 174A allows a deduction for domestic research or experimental expenditures paid or incurred in taxable years beginning after December 31, 2024, and treats software development costs as such expenditures. Taxpayers can instead elect to amortize over at least 60 months. Software development performed outside the United States must still be amortized over 15 years.

What happens to software costs capitalized for tax from 2022 to 2024?

Taxpayers choose among three options: keep amortizing domestic amounts over the remaining five-year period, deduct the unamortized balance in the first taxable year beginning after December 31, 2024, or deduct it ratably over the two taxable years starting with that year. For calendar-year companies the choice belongs to the 2025 return. Rev. Procs. 2025-28 and 2026-32 set out the procedures; confirm your company's choice with your tax advisers.

Could small businesses apply the new rules to earlier years?

Yes, with a deadline that has now passed. Taxpayers meeting the gross receipts test ($31 million for 2025) could apply Section 174A to years beginning after December 31, 2021. Under Rev. Proc. 2025-28, an election by amended return had to be filed by the earlier of July 6, 2026, or the refund claim deadline. Method-change routes had separate rules.

Does the tax treatment change how software is capitalized on the books?

No. Book capitalization follows ASC 350-40 and, from annual periods beginning after December 15, 2027, ASU 2025-06. Tax elections don't change the capitalized asset. They change taxable income and therefore deferred taxes under ASC 740. The practical link between the two is the labor data, which has to support both classifications.

Free playbooks

In-depth guides for product and operations leaders.

Browse the playbooks
Steve Elliott

Steve Elliott

Published November 22, 2026

More on TBM & IT Financial Management

Cost pools, towers, showback, unit cost.