Comment by robomartin
Comment by robomartin 8 days ago
Signed.
That said, here's my perspective on 174 (which should be reverted to full deduction on the year the expense is incurred).
You do not have to amortize 100% of your engineering costs. Not even close.
Here's the key:
Development costs incurred to remove uncertainty are amortized.
All other costs are deductible during the tax year where they are incurred.
How does this work?You are going to design a new robot arm.
In January, you spend $100K to "remove uncertainty". In rough strokes, this means discovering all the things you don't know and need to know for this robot arm to become a product. This amount will be amortized over five years under 174.
Now, with uncertainty removed, you spend an additional $1.1MM from January until December for engineering implementation. No uncertainty being removed. Just building a product. This is 100% deductible that tax year.
Analogy: You want to build a new brick wall with specific properties. You spend $100K to develop a new type of brick and $1.1MM to build the wall using that brick. The $100K is amortized, the $1.1MM is deductible in one shot.
BTW, at year 6 the amortization schedule reaches steady-state and you are amortizing the full $100K every year. In other words, the impact of 174, if treated intelligently, is the time value of money until steady state is reached for the engineering costs incurred to remove uncertainty.
If it's software, you do need to amortize 100%. Section 174 (as amended by the TCJA) has specific language to this effect [1]:
> For purposes of this section, any amount paid or incurred in connection with the development of any software shall be treated as a research or experimental expenditure.
i.e. it needs to be amortized. That's the part that people find most objectionable -- software development is special-cased for unfavorable tax treatment that does not apply to other fields.
[1] https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim...