Comment by chermi
Comment by chermi 8 days ago
Can someone steelman the positives for me? I don't see how it's anything but pure regulatory capture favoring established tech firms. A small company ramping up revenue simply can't handle this amortization while a large, established company can.
That being said, I do think there's a little sloppiness in what is categorized as "R&D" in the software development. Is code maintenance R&D? Bug fixes? Performance improvements? Is it a "capital asset" no longer under R&D once it hits production? This aspect has always seemed too gray given how much money is at stake in taxes.
But again, this complexity is an advantage for more established firms with legal departments and the infrastructure in place to document everything in order to handle audits. Which, in my view, is a form of regulatory capture; this presentation of symptoms of regulatory capture is pretty common.
One potential argument I can see is that maybe this balances out since presumably the more established firms would have less "R&D" as a fraction of expenses to deduct in the first place?
Edited to fix some typos and clarity.
Doesn't this kind of make sense if software is an asset? If your company purchases a seat of Oracle or Solidworks or Windows 11 or whatever. I don't think you can expense that all at one time, you have to amortize over the useful life of the software, just like if it was a physical printing press or a backhoe. Similar if you were making a software program for sale or for use internally, there is the upfront costs associated with making the software, and then it gets used/sold for the next X number of years. And software never wears out, unlike a tractor; that's at least why physical goods are amortized over a finite life. Probably the biggest problem is that this conceptualization of software might be 20 years out of date.