Comment by potamic
6 months ago
This is insane, how does it make sense? Employee salary expenses are no different from other expenses to run your business. Imagine they did this for raw material instead, a restaurant could only expense 20% of the food that they sell. If they purchased $100 worth of food, but could only sell $50 worth of it, they have to pay tax on that even when making a net loss overall. It just does not make any sense. There would've been a huge uproar if this was done for cost of goods. Why are employee salary expenses any different?
It makes sense when you consider that there is no minimum tax rate on businesses.
Given the choice, Amazon would rather spend 100% of its profits on itself than allow any of its profits to be paid out in taxes. Section 174 was implemented without a minimum tax on corporate profits before voluntary deductions such as research. Therefore, it’s exploitable and all companies ought to hire and fire staff to ensure their profits show as 0%.
This tax code defect is now closed by accident, but could have been done much more intelligently than it was. Oh well.
(EDIT: My first sentence is potentially confusing when I reread it later. To restate: section 174 was defective as implemented due to the uncapped 100% deduction, but the concept of a significant research exemption is still excellent. Just need to close the effective 0% corporate tax rate loophole.)
The company already pays payroll taxes on those salaries, and the employees pay income taxes. And the people hurt by this aren't the shareholders or top executives, it's the rank and file workers getting laid off, losing benefits, and being asked to work more for the same pay.
What this change effectively did was make software developers significantly more expensive, without increasing the amount those developers get paid.
The company does not pay payroll taxes. Individuals pay those taxes.
5 replies →
Software developers are already too expensive in US, so this applies some downward pressure on those salaries. Frankly the economy will be much better off when tech salaries equalize across geos, thus avoiding the deep whole US manufacturing is in (for example, manufacturing wages in Vietname are one tenth of US manufacturing wages, and thus it is better to open new plants there).
10 replies →
Don’t forget the other stakeholder - the general public.
Yes it sucks for developers, but does it make any difference for any other employee? Why does Joe’s plumbing have to pay those taxes, but Jane’s AdTech company doesn’t?
Sure, there are benefits to investing in R&D in general, and tech has fueled a lot of growth, so incentivizing it has likely paid off for the whole economy. But will that forever be true? Maybe?
5 replies →
> Given the choice, Amazon would rather spend 100% of its profits on itself
And why is this bad, exactly? Money will be spent and will go back into the economy. Amazon will have to use the funds to build new offices, datacenters, do research, whatever.
And even if execs give themselves $10^11 USD in bonuses, they will be taxed as personal income, at even higher rates than corporate income.
It is complex - is it better for the money to go back into the economy by paying high salaries to a specific group of highly-educated people? Or is it better for the money to go back into the economy through taxes, then disbursing the benefits to lower-income benefit programs?
I’m not sure what the answer is. The former is likely to drive some innovation, which I’m sure varies by company. Where the latter could also unlock innovation by giving the bottom-quartile of earners a chance to improve their situation.
17 replies →
Mostly, Amazon will do stock buybacks, so that its investor can invest into other top stocks.
1 reply →
> Given the choice, Amazon would rather spend 100% of its profits on itself than allow any of its profits to be paid out in taxes.
"on itself"???
You mean it would rather spend its profits on hiring more developers than sit on it? That sounds great, doesn't it?
That isn't a loophole. It is working exactly as was intended. Reinvesting is good.
The deal is that you can delay taxes by reinvesting (and either make the government more money at the end or lose it all if you were a fool, but you gain nothing by losing it all) but you cannot skip them when it comes to taking the profit out. The entire point of it was to promote investment into businesses which has kind of been a crucial factor in international competitiveness since the Industrial Revolution. Remember the fall of US Steel? That happened because they didn't reinvest.
after 5 years then every year is deducting a whole year's worth of R&D - as long as that investment is not too lumpy from year to year you are back where you started
Which is fine for steady companies, but perpetually drags down any rapidly growing company
1 reply →
In this theory you should tax revenue and not profit. Welcome to VAT.
There are other expenses that are also amortized.
Employee salary cost isn't always 100% an expense.
Imagine you are BigCarCo, you make cars. The salary for your factory workers that build cars to be sold is an expense, incurred in that year, to be matched against the revenues earned by selling those cars. But the cost to build the factory needs to be amortized over the lifetime of the factory - and that's true whether you buy a factory from BigFactoryCo or hire a bunch of people to build it.
Now, I'd argue that a) most software dev work is closer to the factory worker than the factory builder and b) the lifetime for most software is less than 5 years, but the idea that some cost of developing software should be amortizable is pretty reasonable.
Actually, if the company isn't selling the software they build, what their software devs do is closer to building a factory rather than working in it.
Mostly developing software is about automating things that are expensive and slow to do manually. So, to stick with the factory analogy, it makes the factory a bit better and more efficient. If you stop doing that because it is too expensive, you fall behind with your factory.
Of course the whole issue in the US is that it outsourced much of what happens in factories to China and software has become one of the main things the country runs on.
Now imagine that a restaurant buys 100 tables, 500 chairs, kitchen equipment, cutlery for 800 people, signage, a security system, and does a remodeling before opening. (Or an airline buys an airplane. Or a hotel chain builds a hotel.)
Should they be able to expense all of those items that provide value for multiple years in a single year?
Does software development provide value exclusively in the year it's done? Or over multiple years?
The reason that we require you to deduct an expense over years for some things is because they have a resale value that needs to be accounted for. It's not a pure expense because you have an asset with real value that came out of the purchase. Employee time has no resale value. Once used it's gone, so employee salaries are expenses, not investments.
The only possible justification for the Section 174 R&D changes is that employees working in R&D theoretically are producing something which does have a resale value, so there's a small tax dodge enabled by direct-expensing your R&D costs but then ending up with an infinitely-copyable asset that came out of it.
If that's what you're saying, then I'd reply to that argument by saying that paying humans to design new things has historically been a business strategy that the government has wanted to incentivize in a way that buying and holding physical assets has not been. I've seen no justification for the government deciding that from 2022 on we should actively discourage R&D, it just seems to be a mistake.
Software is like Art, it doesn't have value until sold or can be used. If they sell services based on the software, they are generating revenue and then taxation on that revenue can occur.
Same as if they sell the software, either as a copy or ownership.
But not being able to take salary as a business expense seems like as thing that would happen if software in and of itself has value, which is largely does not.
2 replies →
> I've seen no justification for the government deciding that from 2022 on we should actively discourage R&D, it just seems to be a mistake.
Removing a specific tax exemption to create a level playing field isn’t discouraging R&D.
That’s the thing, every year such exemptions exist the US taxpayers are handing out money. Just because we subsidize say EV’s or Corn doesn’t mean that’s the baseline forever more.
29 replies →
What about construction worker and other labor time to build a factory? That’s the analogy being made here by the tax code: Software whose development is a capital expense with value returned over time.
6 replies →
But the employee time that had a one time use was turned into software. That software is the thing that has value longer than "right now"
1 reply →
> I've seen no justification for the government deciding that from 2022 on we should actively discourage R&D, it just seems to be a mistake.
My understanding is that this was done in order to balance the tax bill passed by the Trump admin due to a requirement to be budget neutral. Cut tax revenue here, increase tax revenue there.
It's only shifting what year the government gets its revenue. The government should simply let the company choose how to do it, but if they choose anything other than year 1 interest will be payable at government bond rates.
It's also massively shifting the companies' cash flows. The company paid $X for R&D this year, but for tax purposes 80% of that $X expense is moved to next four years. So for this year's tax purposes, the company R&D expenses are much lower than what the company paid.
I have seen a lot of software development where what's been done has been changed beyond recognition over the course of less than a year.
Ironically I think they would want to claim that over multiple years unless they have other profitable operations under the same company. E.g. other restaurants.
They should have the choice.
If software lasted longer than 18 months or was otherwise tangible, this could also make sense.
The appropriate analogy is:
Imagine a restaurant spends money on employees to build 100 tables, 500 chairs, etc. Those tangible goods would be capital assets, so the labor costs of building them would also be capitalized.
This change to the tax code is just bringing the tax treatment of software development in line with how every other industry is treated. IOW, it was closing a loophole. A very valuable loophole, whose beneficiaries used it to get filthy rich, and bragged about how their industry was so much more valuable than everything else, even though a lot of that value was due to the exception software was getting in the tax code.
Notably, in the current version of the budget as of 6/6, the loophole is temporarily coming back, though given the Musk-Trump feud, it's very possible it will get pulled again to try to mollify the hardline deficit caucus.
If the restaurant buys e.g. a fancy oven or a delivery truck, it can't expense 100% of that cost in year 1, it has to spread that cost over the lifetime of the oven or truck.
Labor that operates the business day-to-day would be an expense, labor that creates a capital asset is more complicated.
I happen to think most employee time in software dev is more on the day-to-day operation side, and should be expensed, but I can see an argument that some should (or could) be amortized.
> If the restaurant buys e.g. a fancy oven or a delivery truck, it can't expense 100% of that cost in year 1, it has to spread that cost over the lifetime of the oven or truck.
The difference of course is that you'll have a truck or oven that can be sold. If you could count the full value in the first year then you could sell and buy one each year to reduce your taxes without actually changing anything.
Thus if we want to go that route for software the salary of the R&D employees should be counted against the value of the software they created (As in, the value were it to be sold wholesale to another company). The time spent by the employees is not an asset, once you pay the employees for their time it's gone even if they generated nothing of value. The actual value is that of the software, but that's obviously not easily assigned a value.
It's a lot easier to get financing for a tangible asset like an oven or a delivery truck, which mitigates the cash flow issue.
Sure, you can only deduct a certain percentage of the asset's value as an expense each year, but your cash expenditures to pay for it are also spread over a multi year period.
It was literally just a shot at California and New York, that’s all it was. “Own the libs” ya know
“if we aren’t rich then no one else will be”
It’s the same for movies, other intangible assets that are valuable and produce income over several years. And it’s done for many tangible goods, like servers in a datacenter, the kitchen equipment in a restaurant.
I think you may misunderstand. For most of those, you get the choice to amortize if you prefer. In this instance, you must amortize, which is a big problem for startups.
Generally it’s not a choice. Valuable assets are required to be amortized over their useful life with limited exceptions
4 replies →