Of course, Congressional budget negotiations have been an unproductive circus show for a while, so this never actually happened and the thing that was never actually intended to go in place went in effect. With the current razor-thin majority in the House constantly getting derailed over budget negotiations, this is unlikely to resolve any time soon.
Since Obama became president, all legislation basically needs 2/3rds of the senate to pass if it's remotely controversial and every tax change is controversial. There is one exception though: if the bill is of a budgetary nature, and is revenue neutral over 10 years.
Trump really wanted to pass some tax cuts in 2017. But as you'd expect, claiming that a big tax cut is revenue neutral is far more than the senate parlamentarian would believe. So instead, some tax cuts are made temporary, and some tax changes are made that would gain revenue. Then the whole thing appears to be revenue neutral over a decade, because nobody expects that the poison pills at the end will actually be allowed to happen. They tend to come in 6+ years later, as to make sure that all senators and the president might also claim said increases are not their problem.
So the expectation is that a future congress will just undo those tax changes, and push them further into the future, by again making another bill that looks revenue neutral in the long run, but is just kicking the ball down the road.
The congress since the midterms, however, is even less functional than in the Obama or Trump years: So the poison pills that are not supposed to happen are starting to happen. Other cuts that occurred, like the increase of the standard deduction, were also marked as temporary, and could come back if congress doesn't do anything.
So ultimately it's all side-effects of people trying to bypass congressional rules, because otherwise we'd not see anything other than emergency spending bills passing in congress. Changes to legislation that would make this kind of dysfunction stop happening are even harder to pass. Every incentive pushes politicians of all parties to play with fire. This time we got burned.
> In 2017, then-President, Donald Trump, signed the 2017 Tax Cuts & Jobs act, which overhauled tax codes and reduced tax – for example, it reduced the top tax bracket from 39.6% to 37%. To make the bill pass strict budgetary rules, the Senate used a process called reconciliation: adding in tax code changes that delayed tax increases. These delayed increases “balanced out” the tax reduction.
> One of these changes was Section 174, set to come into effect 5 years later, in 2022. These parts deliver the blow by making it clear that software development costs need to be amortized over 5-15 years. Most experts expected Congress to push back the Section 174 amendment to a later date, or simply remove it. But Congressional negotiations to repeal the changes fell apart at the last minute in December 2022, meaning it became law.
> Amazon, Microsoft, Intel, Ford, Lockheed Martin, and other US companies created the US R&D Coalition in 2018 to advocate in reversing this change. This group concludes... "By diminishing the near-term value of R&D expenditures, the Tax Cuts and Jobs Act will reduce incentives for companies to invest in the development of new products, ultimately hurting consumers and businesses alike.”
> What about VC-funded companies? For loss-making companies this change doesn’t make much of a difference. But the change does impact VC-funded companies near to break even. Most VC-funded companies close to breakeven have big-enough cash buffers with which to pay unexpected tax bills. However, these companies might reduce hiring – or even consider letting go staff.
My 2c are that big tech companies with large amounts of cash on hand wanted to be seen optically as fighting against this change... but those with cash on hand would also benefit from being the only ones able to weather the storm relative to their would-be competitors. It's unclear that incentives were aligned here among those companies with lobbying budgets.
I don't think there's any real logic to it, it's just a way to balance the tax budget.
For 1, presuming that all software engineering is "research or experimental" is faulty. The vast majority of software engineers are implementing known things, and the "experimental" status reflects its reliability. Most "experimental" software isn't really doing experiments to answer questions, it's just checking whether an approach works correctly. I don't think anyone could honestly call writing an Okta integration for a SaaS app "experimental". You know that it will work ahead of time, you just aren't sure if your pass implements it correctly.
For 2, this would imply insane things if applied to other fields. What is the correct period to amortize a bridge engineer's salary over? 50 years? 100? We still have some Roman bridges around, maybe we need to look in the thousands of years. Patents are good for 20 years, so any salaries that lead to a patent clearly need to be 20 year amortization. Copyright is life + 70 years, so graphical designer salaries should be amortized over at least 100 years.
I don't think there's any real logic here, it's just a way to balance the tax budget.
if I understand it correctly it means the cost of this year would be written of over 5 year each year 20%, but if you keep your employees it means in the second year you have 20% write off from that year and 20% of the previous years and so one, so 5 years in still 100% write off every year
I wonder if that would motivate companies to have a more constant number of employees or more precise a similar income bill every year.
Through it would definitely mean if you had considered layoffs this year is the year to go.
If you spent $100M on developer salaries in FY2022, you'd create an amortization for that over the next 5 years.
And then in FY2023... even if you had fired your entire software department... you'd still get to claim that year's portion of that previously created amortization.
IANAL but have filed corporate taxes many times.
but when keeping a job position (not necessary the same person tho) through overlapping writeoffs it will lead to a consistent 100% writeoff
not doing so can lead to spkies of little writeoff when increasing company size and the opposite when shrinking it. This would make new hires on a limited budged harder and in turn should motivate more long term planing when it comes to head count and that might lead to less head count fluctuations maybe
1) Tech workers are liberals
2) Liberals being owned is good if you're an administration consumed with punishing your enemies and enriching your allies
#2 is also why SALT deduction was curtailed, to punish blue states. While I think that's accidentally good policy, it made people mad enough to flip the House in 2018.