Comment by aarondf
3 years ago
(I put this in a reply further down, but bringing it to the top)
Previously if a company has a million dollars in revenue and spends a million dollars on the salaries of software developers, this is how their taxable income might look:
1,000,000 Revenue
- 1,000,000 Salary expense
-----------
0 Profit
The new law would instead work like this:
1,000,000 Revenue
- 200,000 1/5th Salary expense
-----------
800,000 Profit
Now the company must pay taxes on 800,000 of profit because "R&D salaries," which includes software devs, must be amortized over five years. Obviously the company has no wherewithal to pay, given that they made a million and spent a million. That's the problem.
There's a lot of attacking in this thread from people who haven't bothered to think about the math. It's an existential risk to some companies, and one that wasn't more widely planned for because it wasn't even believed to be intended to actually occur.
Most tax experts considered the removal a budget gimmick so that the 2017 December republican majority could quickly pass a new budget using the budget reconciliation process, which can't be used to increase the deficit after a 10-year period so they had to add a time limit to a bunch of benefits "on paper" to use the reconciliation process. There appeared to be broad support for fixing it later, but the bipartisan spending bill expected to include it fell apart because they couldn't get agreement on other parts of it.
To the best I can tell this isn't tech companies complaining about paying fair tax; it's a congressional oversight that is quadrupling the taxes of small business out of nowhere which nobody in power has bothered to fix.
I understand the arguments for it, and maybe even on net it’s beneficial because it prevents other bad things from happening, but the amount of byzantine dysfunction that’s downstream of the United States Senate Filibuster rule is really something to behold.
To the extent that the filibuster's beneficial, I'd say it's only so because of our bad electoral system that stabilizes at only two viable parties, and sometimes results in minority rule.
244 replies →
The filibuster is fine, in its original form. Manipulate the parliamentary process to push the date close to the end of session, then have some windbag with sufficient endurance read the phone book for a few days.
The current version, where you declare yourself filibustered, is too cheap. In the old days, they just filibustered stuff like voting rights, not procedures for borrowing money to support the adopted budget.
5 replies →
The filibuster continues to exist each new day because a simple majority of senators continue to want it to exist. Don’t let that majority off the hook for anything by pointing to a rule they could remove at will.
7 replies →
What other bad things does this prevent from happening? I can't think of anything, unless you think double-taxing income is good.
1 reply →
It may have been beneficial on net at some point in the past, but it's just bad at this point.
Thank you for providing the actual political context. It is much more helpful to know who did this and why then to complain about an amorphous and unchanging "Congress".
I read the message you are replying to three times and I still don’t understand who did this and why? Can elaborate more?
3 replies →
The thing that is most striking to me about your explanation is that the change was made six years ago; it seems that anyone responsible for a company's tax position and cashflow (CFO, accountant, etc) should have been planning for this between then and now. Much like the SVB panic, a great deal of this seems to be people running companies without either paying attention to things that could have a significant impact, or hiring someone who does.
When I took tax law, one of the things that blew my mind is that it can be retroactive.
An exemption might expire, but then be retroactively reinstated. This happens all the time.
There is the tax law that applies to your 2022 income now, and then there's the tax law that will apply to your 2022 taxes in five years.
They have been. Large companies have been engaging with Congress since 2019 on this, reminding them that they intended to revert this before it took effect. CFOs wrote a letter to Congress in November. https://investinamericasfuture.org/Communications/letters/
1 reply →
I don’t know why you’d think it was an oversight. After all, they pushed SALT, which raised the taxes of any homeowner living in a high cost of living state, and further transfers wealth to flyover country and the south.
It gets worse, we do not reach true majorities in the House and Senate until 2030. Thus until then budgets get passed under budget reconciliation.
This whole thing sounds so shady to me, can't believe this is how they are running a country.
[flagged]
What does any of this have to do with libertarians?
1 reply →
[flagged]
IMHO the solution is really more simple than people are making it out to be and it’s weird politics among CPAs causing all the distress. To people wiling to challenge their CPAs style of doing things: don’t classify your core expenses as “research and development”. I believe this follows the letter and spirit of the law. R&D is extra stuff you do on top of an already profitable business. When you’re building a product you’re implementing. It’s entirely a semantic problem that has happened because we call the job function “software development” and the tax code uses “research and development” (a different function) as the language. The CPA thing is caused by there being a central source of “doing things” that all the CPAs follow because they’re not qualified to be a tax lawyer and think for themselves. So everyone is stuck in whatever rut their guild’s status quo tax setup for #startups has caused.
You know, this is pretty clearly the right answer. Software developer salaries are ordinary business expenses. There’s some alarming language in the section about deductibility of R&E expenses, but core business functions aren’t R&E.
Really perceptive comment.
All sw dev is considered R&E. Soo you have no choice
38 replies →
From the Section 174 text:
https://www.law.cornell.edu/uscode/text/26/174
To me it doesn't sound like classification is discretionary to me, or that splitting semantic hairs will prove effective (IANAL).
(Additionally, the R&E classification is different from R&D)
Guys, this entire section is under the ITEMIZED DEDUCTIONS FOR INDIVIDUALS AND CORPORATIONS section. Taking a deduction is never mandatory (though usually recommended if applicable). Context matters.
> In computing taxable income under section 63, there shall be allowed as deductions the items specified in this part,
Generally, these sections explaining deductions, including 174, are things you adopt. From the beginning of the section
> (a) In general
> In the case of a taxpayer’s specified research or experimental expenditures for any taxable year—
Everything that follows is subject your specified R&E. Which is all part of the itemized deductions framework which is all completely discretionary.
For instance, here’s section 162
> a) In general
> There shall be allowed as a deduction all the ordinary and necessary expenses paid or incurred during the taxable year in carrying on any trade or business, including—
> (1) a reasonable allowance for salaries or other compensation for personal services actually rendered;
You are simply carrying on business ordinarily. People don’t operate businesses on R&E expenditure. It’s just not a rational interpretation of the tax code and you don't even need to be a lawyer to read this document or form that conclusion.
https://news.bloombergtax.com/tax-insights-and-commentary/ch...
3 replies →
How do you explain the CBO scoring?
Also: this specifically singles out software development for ??? reasons.
Office Manager: 100% expense.
Software Engineer: 20% over 5 years (actually only 10% for the first year).
If they’re international then 6.67% over 15 years.
Not only that, but the effect “stacks” over the years.
By the time you get to year 5, you’ve paid tax on $2,000,000 of phantom profits you never had.
If you’re a C Corp that’s $420,000 in extra federal taxes (plus whatever state tax).
If you’re a smaller company you’re probably a S Corp and federal and state tax could be ~50% passed through to your personal return.
How any owner survives that, I’m not sure.
That sounds pretty horrible. Am I correct in assuming though that once you get over the five year hump, you're OK? Also wouldn't startups mostly be paying devs out of VC funding rather than revenue the first five years?
No, you never “catch up” unless you fire every software engineer (so income and trailing five years of amortization cancel out).
Year 5 is just a steady state of no more phantom profit taxes, but you never really get that extra tax you paid back if you want to keep operating at the same level or grow.
2 replies →
No. If you are growing and increasing expenses you’re always behind. The only case where you get ahead is if you stop growing or shrink.
5 replies →
Only if you’re not growing.
Software has a long life, like buildings and whatnot, so that is likely why it is singled out versus the office manager.
If you buy a building, you can’t depreciate the whole thing instantly, you do it over the life of the building.
What about an architect's salary? Does the firm who designs the building amortize the cost of that labor, while the purchaser of the building also amortizes the entire cost of the building? How about EEs who design the hardware? Are they included?
> If you buy a building, you can’t depreciate the whole thing instantly
The same should hold of course if you buy software.
But if you ask your employee to perform a task like writing a program you are not buying anything. You are paying the employee's salary whether the software they are writing ever gets out of the compiler or not.
So wouldn't there be a way around this by changing the titles of software developers to "software janitors" for instance ?
They get acquired by companies that have unused deductions. That is how monopolies form.
After 5 years dont you end up with some "finished" R&D project that then can be later amortized, over say next 3 (or 5 years), so you reduce your tax base by those 2 million later on?
No.
After 5 years the first years salaries are considered to be a "finished" R&D project, which means there's nothing left to amortize.
The only thing like that is that if, after a few years, you fire all your devs (or at least, all devs working on adding new features and building new products), then you can keep amortizing the last 4 years of salaries for your now-fired workers over the next few years, which reduces your tax base. But I mean, by that point, who cares? Any software business that has fired all its devs is over.
2 replies →
Software was targeted directly because they couldn't agree how to change 230. There are those who want to punish the "tech" people who were "censoring" things they didn't want censored. It was designed to be tactical retribution.
Do you have a source for that claim?
2 replies →
I don’t see any evidence of that. Care to share any?
When you lay it out like that...
Feels like this is just a move to stop companies from gaming expenses to avoid profiting. Piercing the corporate veil, if you will.
What part of it is gaming anything? They're not profiting from money they're paying to their employees as salary.
1 reply →
This also looks like it completely screws people who get government research grants for their for-profit companies (eg SBIRs). When I was thinking about one, my accountant was telling me that the grant is technically revenue, which would make it convert to taxable income less expenses. Forcing companies to capitalize R&D basically means that you have to pay tax on the grant funding first, leaving only the after-tax value of the grant for actual R&D.
I doubt most grant proposals have a 20-30% haircut built into the budget like that...
Yup, I am screwed because I got an SBIR grant in 2022. The default indirect cost rate is ~30%. In this new scenario, it should be something more like 60%, which reduces the usable funds that can be spent on actual development (IF you can even get a high rate like that approved by the govt agency)
EDIT: By "screwed" I mean that I'm facing a $100k personal tax bill because the company is an LLC taxed as an S-Corp. You can say all you want about lack of planning, etc, but the reality is that many times very small business do not have the budget for a high-end business accountant on retainer. If I were to try to "plan better" to avoid this situation, I would have just not written the grant or tried to do any of it and gotten a FT job or something instead. It's an innovation-killer.
I am personally very happy that my LLC's SBIR grant proposals in 2022 were all turned down, because I wasn't thinking about the disastrous tax consequences.
6 replies →
Which agency is this from? 30% is an insanely low indirect rate. My experience comes dominantly from DoD SBIR, where for Phase I's you propose your own indirect rate.
But yes, this law is awful for SBIR companies, because we're forced to give a giant out of pocket interest-free loan back to the gov
3 replies →
They are indeed hard hit as well. SBIR grant awardees sent their own letter to Congress about this a month ago: https://sbtc.org/sbtc-letter-to-congress-on-sec-174-tax-conc...
> I doubt most grant proposals have a 20-30% haircut built into the budget like that...
Most university research budgets do yes, and actually more than that.
Universities already have their indirect cost rate negotiated (most are like 80-120%). Default for newcomers is around 30%, until you can build up the history and wherewithal to navigate the negotiations for establishing your own rate.
When seeing it written out like this is simple math, this tax change seems absolutely insane. It would mean some (many?) small businesses will face tax bills that are far higher than any actual cash they have on hand. How did anyone ever think this was a good idea?
It is insane.
If they don’t fix it a lot of companies (and their owners) are going to go bankrupt.
Only those where CFOs are incompetent. And the owner is not responsible for the company’s debt, usually.
2 replies →
This is a topic I know very little about but doesn't this type of "absolutely insane" thing happen to other small businesses due to estate taxes too?
For example:
I might be butchering this so please correct me if I'm wrong but this feels like a system that helps larger companies because it prevents a smaller business being able to exist multiple generations.
Assuming your uncle was single and not able to leverage the double estate tax exemption for married couples, the $1,000,000 farm value is only $11.92 million short of the threshold at which estate tax would start to apply, and only to the amount above the threshold, at an initial marginal rate of 18%. It only reaches a marginal rate of 40% on the amount more than $1 million over the exemption threshold.
If, instead of being $1 million, the farm (assuming it was the whole of the estate) was worth $13.92 million, the actual estate tax would be $345,800. Assuming the same ratio of annual profit to value in your hypothetical, the annual profit would be $278,400; so if you had no other assets to pay the tax, you’d probably need to borrow against the profits, but that shouldn’t be too hard given their magnitude.
> Federal estate tax is due if an estate's value exceeds the estate tax exemption amount, which is $12.92 million for deaths in 2023
The numbers are much, much larger than a simple $1m family farm.
Also, remember, that cap is a exemption from the value. If you have a farm worth $14m, you will have to pay approximately $400,000 in estate tax (NOT 5.6 million like you would naively calculate). At that point, if the farm doesn't generate (effectively) any revenue, and it's not mortgageable or you can't secure a personal loan, it's probably best for everyone that it be sold. You certainly wouldn't be able to e.g. pay property tax on a property that size.
The estate tax is the most widely misrepresented thing in the tax code. It's designed to prevent multimillionaires and billionaires from passing down their entire fortune to the next generation intact. It almost never affects anyone but the top 0.5% wealthiest people in the country, and only then if they do absolutely no estate planning whatsoever.
Thomas Jefferson argued strenuously for the estate tax and for inheritances (without a will) to be divided evenly among the children. In Europe the law of primogeniture put inheritances in the hands of the firstborn male which guaranteed that a dynasty could always be preserved! Ick!
1 reply →
> it prevents a smaller business being able to exist multiple generations.
In addition to what everyone else says, if you have a multi-generational business the owner should be bringing their child(ren) in as executives and part owners of the business. The estate tax would only apply to the part of the business the original owner still owned at their death, not the part of the business owned by the child(ren).
If this is true then the system is clearly made to funnel these lands into the hands of the ruling oligarchs.
1 reply →
It was written to fuck over smaller companies. That was the point of it.
Written by whom? What was the original bill?
3 replies →
The amortization change was a deliberate part of the 2017 tax cut. One of the express purposes of the tax changes was to raise taxes on liberals, and I guess they figured that companies that take the R&D credit are run by liberals.
Is the IRS willing to let companies make payments of the tax over years? Would would the IRS want to put companies out of business?
Is it mandatory for software companies to classify engineer salaries as "R&D"? I haven't yet gotten an answer for this each time this issue comes up.
I know it used to be advantageous due to the R&D amortization period, and I feel this was abused in cases were there was effectively no research or development (in the traditional sense). How is your example materially different from a furniture shop that has similar revenue & salary numbers, but previously wasn't able to amortize salaries as "R&D"?
This is a complicated question.
On the one hand, Section 174 clearly stipulates: "(3)Software development 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." [1]
Section 174 R&E expenses are much more expansive than what qualifies under the R&D tax credit criteria. This article has a rundown of some of the activities included in 174. It's well beyond software or salaries -- it also includes things like market research. It also includes any expenses in connection with R&E, so for example time using a server for new features or new products would have to be amortized but maintenance (bug fixes) wouldn't. Even if a company files for R&D tax credits, they won't be able to offset this increase. [2]
Lastly, since Congress was widely expected to revert this before it took effect, the IRS didn't issue full guidance on how to implement it. They've never had to define software development before, but the interpretation that Big 4 accounting firms are taking is that it covers new products AND new features on existing commercial products, but not straight maintenance.
[1] https://www.law.cornell.edu/uscode/text/26/174 [2] https://www.forbes.com/sites/lynnmucenskikeck/2023/03/24/fiv...
> maintenance (bug fixes) wouldn't.
Link [2] lists activities related to software development and includes maintenance and debugging. As I understand it this is for the older #41?
• Programming
• Tuning and benchmarking of software
• Performing software maintenance and debugging
...
Am I understanding this correctly that there are two different things at play here: the Section 41 tax credit which works in the companies' favor by allowing them to deduce R&D expenses. Then the Section 174 that requires all expenses to be amortized and the big issue for software firms is that the definitions of R&D differes where it's narrow R&D for the credit, but very broad for #174, resulting in a cash flow problem?
Is it? "In the case of a taxpayer’s specified research or experimental expenditures for any taxable year—" is pretty clear. That means what someone wants to claim as research and experimental expenditures. "For the purposes of this section" also seems pretty clear. If you want to claim software development as R&E, it unambiguously qualifies. And now all R&E must be amortized.
I am not a tax expert, but it doesn't seem like there's any reason you have to claim software development as R&E.
5 replies →
What would a software developer do that isn't research or development? Maybe my understanding of "research and development" is wrong. Is there a formal definition that I can go by?
I still don’t understand why it has to be RnD? If I made a million dollars and spent a million in salaries, I made no profit. The government shouldn’t be taxing me on no money made. They already get taxes on the salaries I’m giving out.
16 replies →
What would a welder do that isn't research or development? I believe for both jobs certain tasks are journeyman-like, but others are legit R&D. I don't think software ought to be blanket-exempted because its done on a computer.
Here's the IRS' guidance on software: https://www.irs.gov/businesses/audit-guidelines-on-the-appli...
12 replies →
In "research and development", that typically means "research of new ideas and methods, and developing them into commercially viable products". So are there things that software engineers do that fall under R+D? Absolutely! Is adding a sorting feature to a grid in your app one of those things? Probably not!
6 replies →
Maintain services. Why was everyone expecting Twitter to go down after the layoffs if software developers only do research and development of new products?
"I haven't yet gotten the answer for this each time this issue comes up."
Asnwer: It's not mandatory.
There are various tax breaks for R&D spending - so companies try and classify lots of things that aren't R&D as R&D.
There's been a bit of stink recently in the UK around R&D tax credits and how companies have been taking the tax man for a bit of a ride.
Honestly this whole thing looks like a huge tax loophole, now being closed. I don't know of any jurisdiction (apart from the US, apparently) which allowed 100% non-amortized tax credit for loosely defined R&D salaries. No wonder everyone and their dog started software companies in the US.
What jurisdiction doesn't count employee salaries as an expense?
Salaries are already taxed as individual income. Taxing them as corporate profits and individual income is not closing a loophole, its double-taxing.
> I don't know of any jurisdiction (apart from the US, apparently) which allowed 100% non-amortized tax credit for loosely defined R&D salaries.
This is not about tax credits, this is about whether salaries are an expense. If Widget Inc makes and sells a bunch of widgets for $100m, and then they pay $20m in rent, and $30m for materials, and $40m for salaries, with $10m left over, with no other complexities (eg, interest, depreciating factory equipment, etc.), then is their profit this year:
1) $10m (or maybe a bit less, if they got any tax credits)?
2) Some other larger number closer to $50m?
You'd be hard pressed to find many jurisdictionns where the answer isn't option 1. I certainly don't know any offhand.
It is not. If I pay a worker to frame up a house it is an expense. If I pay a swe to frame up a mobile app it is R&D. Again NOT a loophole.
8 replies →
Maybe it was the point? Didn't you notice that the US gained certain lead in software technologies?
The developers, who are paid rather handsomely, also pay rather large amounts of taxes from their salaries. (If fired and jobless, they stop doing that.)
1 reply →
Well, salaries are expenses though. And software development is not necessarily R&D, so if 99% of software development has to be classified as such, that's a problem.
We are not talking about a tax credit here, but a deduction.
This is misinformation. You owe this tax even if you do not claim any R&D tax credit.
https://www.grantthornton.com/insights/articles/tax/2023/sec...
Uhhhhh… every single one up until this change.
100%
IANAA, but very important to remember that:
1) R&D classification of a single employee should be a percentage. Accountants don't list employees one by one on a tax return, they're grouped together and a percentage of their wages can be allocated to different functions of a business outside of R&D.
2) A lot of things do not qualify as "R&D". For example...
- Fixing bugs
- Maintaining existing features
- Improving existing features (even enhancing functionality)
- Building a feature because sales promised it to a customer
- Refactoring code
- Anything related to devops/infrastructure, upgrading servers, updating dependencies
- Anything related to customer support, onboarding or retention
- Anything related to helping Sales/Marketing close new business or get more leads
- Anything related to supporting day-to-day business operations
I'm not an expert, but I think it will be relatively easy for accountants to do some magic behind the scenes by classifying only a small percent of wages toward R&D.
I think the average engineer spends less than 20% of their time on "true" R&D, and if that's the case, 80% of wages can be deducted as an expense without amortizing.
Do you have a source for this? The law seems pretty clear to me:
> ANY amount paid or incurred in connection with the development of ANY software shall be treated as a research or experimental expenditure.
https://www.law.cornell.edu/uscode/text/26/174
There's a very important clause immediately before that though: "For purposes of this section".
Also the parent clause says: "In the case of a taxpayer’s specified research or experimental expenditures for any taxable year—"
So just don't specify the expenditures as research or experimental if you don't want this section to apply.
1 reply →
I guess there might be a distinction between "development" of software and "maintenance" of software (e.g., bug fixing, refactoring, etc.)?
6 replies →
> I think the average engineer spends less than 20% of their time on "true" R&D
Based on all of the items in #2, the average software engineer spends close to 0% of their time on R&D - with rare exceptions for those working on cutting edge tech, in research roles or maybe super senior engineers figuring out how to solve complex technical problems
The rest of us just write code and sit in meetings
It would be interesting if this reintroduced "10% time" with strict wording about not working on R&D in your 90% time. Just to simplify the labor involved in calculating it.
Even worse: amortization under § 174 begins at the mid-point in the year in which the expense was incurred, so it's actually 1/10th salary expense in the first year (6/60 months).
I have a favor to ask HN: is there anyone going through this that would be willing to share a redacted version of their accounting change statement[0] required to comply with this law by Rev. Proc. 2023-11? It's not at all clear to me (not a CPA or tax lawyer, but normally perfectly capable of doing bookkeeping/accounting for my single-member LLC) how specific "(D) a description of the type of expenditures included as specified research or experimental expenditures" is supposed to be. I filed an extension today because I'm now second-guessing what I wrote; my Google-fu has thus far turned up zero examples of a CPA-blessed version of this statement. (Probably because one of the other statutory requirements is that it includes the taxpayer's identification number.)
[0] Rev. Proc 2023-11: https://www.irs.gov/pub/irs-drop/rp-23-11.pdf [PDF]
This sounds like sheer madness.
Does anyone know what the situation is in other countries (in particular, in Canada) for the same situation as above?
One option companies have, if this isn't fixed, might be to re-incorporate, or relocate their company to Canada[1].
[1] Assuming Canada taxes sensibly (and allows R&D or developer salaries to be deducted).
You’d expect to run into transfer pricing issues if did that, unless you’d already structured your company avoid those problems. This problem here, and many others like it stem from the fact that corporate tax is a stupid concept. It doesn’t generate any additional tax revenue, because any tax that is paid as corporate tax will simply be used to offset taxes that would otherwise be paid as income tax. It also simply preferences operating models which are more accessible to large companies, disadvantaging SMEs. Any company can theoretically choose to not be profitable, by reinvesting all of its profits, and investors typically don’t care if their value is returned via growth or dividends. But many SME operators do, and the accounting and compliance costs associated with that place a higher burden on SMEs. But the whole debate around the topic is muddied by people who intentionally misrepresent how these systems work for their political gain, and their followers who don’t understand how these systems work (until some stupid change like this affects them, and the stupidity of the system is made clear).
"Any company can theoretically choose to not be profitable, by reinvesting all of its profits, and investors typically don’t care if their value is returned via growth or dividends. " - the Amazon model for its first 20 years :).
Amazon was founded in 1994 and it started to make profits reliably in 2016 : https://www.macrotrends.net/stocks/charts/AMZN/amazon/net-in...
In Canada, qualifying R&D spending generates a tax credit that can be worth 60% of engineers’ salaries. In other words, a company that spends $1M on engineers in Canada not only writes off the $1M in spending, but also gets a credit of $600,000.
Fine print: this is only available to Canadian-controlled entities. Foreign-controlled entities can claim R&D tax credits as well, but the rate is far less generous.
Wow, this is amazing. Do you have any links with more details on this?
It sounds like Canada is trying to make it as easy as possible for companies to set up shop in Canada.
Personally, even incorporating in Canada is so much easier. A federal corporation just costs $100 to make, and even less to maintain annually. (In contrast, in the United States, an LLC set up through Stripe Atlas costs $500, and you have an annual recurring fee $300 owed to Delaware + registered agent fees.)
1 reply →
Canadian corporate taxes are quite a bit higher than in the US - 33% vs 21%. So not an easy decision...
Yes, but have you heard of SR&ED?
Something is getting lost translation here. You can capitalize certain projects of that meet a certain threshold. I can't capitalize something as trivial as changing some colors. The capitalization is based on the expected lifespan of deliverable. Web pages is like 2 years. Bug fixes/maintenance, and project management are not capitalizable and its common to use 80/20. Public companies want to capitalize everything to improve earnings and kick up their stock price but they are kept in check by auditors.
How is this going to change?
As it relates to developer salaries, you don't have an option to decide if you're going to capitalize or immediately expense. With this bill, you must amortize over five years.
You're talking about deciding whether or not to capitalize a laptop, a piece of equipment, a vehicle, etc, and over what period. There's lots of guidance for that. This is very specifically affecting the salaries you pay software developers.
I just figured out the disconnect. This is only for tax reporting and not financials. This is going to be fun.
1 reply →
That sounds a lot like that delicious regulatory capture that giant companies like very much.
It benefits VCs because it makes it impossible to sustainably self-fund a business.
Ok, but in year five, it would look like this again:
So really, it's removing (deferring, or peanut buttering) the startup and ramp up "invent new things" subsidy, while not really affecting steady state R&D if you're not growing talent ahead of revenue.
So even in year 5, it's an adverse incentive for putting new/more talent to work.
Even big business may not be able to make as many growth project budgets work.
Startup subsidy?
This seems to be penalizing competition and new competitors, for literally no reason.
No reason? Regulatory capture is the reason.
No
Year one: You go broke. Everyone loses their jobs. You file for bankruptcy. Game over. There is no year 5.
European software companies don't go broke and AFAIK they have 0% tax credit for salaries (in most countries, I know there are some R&D schemes in UK).
8 replies →
That’s if you could have afforded to pay the tax on the $2,000,000 of phantom profit you had until this point, which no one can.
You don’t get that back unless you somehow fire everyone so you can offset income and expenses without more amortization.
You can if you raise debt or equity to pay salaries.
The lack of specificity in your little table should illuminate for you why this is such a complex issue to comprehend. I understand there is some fictional, meaningless interpretation hidden inside your head where that table is "right," but for all normal interpretations, it's wrong.
Unconstrained growth is not tolerated anywhere else, but somehow people bend over backwards to explain how actually any constraints on business growth are Very Bad And Evil.
Unsustained growth is just one type of growth though and this affects all growth so I don't see you point as relevant here.
2 replies →
Not forgetting that the government is ALSO taking money on the other side of the salary as well.
I much prefer Estonia's system of taxation. Flat 20% on share dividends. Any money that stays within the business (or gets spent on wages, other expenses) isn't taxed (aside: there are social and income taxes on wages).
Coming from Australia's system it's just so simple to be compliant. Feels designed to help businesses grow.
I have been thinking this for a while. Corporation tax creates so much work, and it would be better to tax certain inflows of money.
So my salary is taxed; my dividends are taxed; my purchases are taxed with VAT, that sort of thing.
Stop making companies employ armies of accountants to figure out all the tax credits/implications/corporate structures etc so the government doesn't take too much.
I pay the Estonian accountant (xolo.io) ~100€ a month and that covers just about everything required to keep the company in good standing. Minor amounts of admin to sign off the annual report (all done with my smart card).
1 reply →
Also, to be clear, it will eventually stack up and roughly even out as you amortize 1/5 of each of 5 years’ worth of R&D spend per year. Basically the part that sucks is that there was no 4-year phase-in period.
It doesn't even out if the company keeps growing - if your headcount is growing 50% per year you can have very significant tax drag.
I think you may have that backwards but yes. You are effectively always paying for expenses incurred 2.5 years ago.
EDIT: Nevermind, you had it the right way.
^^ This is the core issue.
This seems a silly question but are you forced to label software development as "R&D" instead of just expensing it in the first year.
I mean this is an accounting trap, it seems the best way to get out of it is to use accounting.
The law has a call out that software development costs are all R&D now. So yes according to my understanding (as one of the signers) and those who have written about this as well.
When you say "as one of the signers" do you mean you signed the federal bill which modified this tax? i.e. you are a congressperson? Surely I'm misunderstanding you; your post history is utterly incompatible with any sitting congressperson. But I can't figure out what you meant by it.
4 replies →
I think this is flawed in both directions. Sure when you’re primarily building new stuff maybe the cost of that should be amortized. What happens if you’re just maintaining a product though rather than actually developing new stuff? That doesn’t feel like R&D effort.
4 replies →
Yes. You could look at this as an indictment of the tax system, in that the plain language says what it says, but the IRS expects you to hire an account to make an "appropriate determination."
No small business accountant is incentivized to give you creative opinions, they're just going to go with whatever is the most popular practice. They don't give a fuck how much tax you actually pay.
The accounting standards forbid expensing things that should be capitalised, and if you go ahead and do it anyway your investors will wonder why your accounts show you have no assets.
Your CA would certainly prevent that from happening well before your investors look at your accounts.
It doesn’t matter what you label an expense. Accounting principles and regulations decide what category expenses fall into. That’s a major reason CAs exist, to ensure that your expenses are correctly categorized.
I am not an accountant, but I took 2 years of accounts, and learning to categorize expenses correctly was probably 75% of the classes.
How does this work with consultants/contractors? Are they still booked under R&D expenses?
So doesn't this just incentivize replacing FTE's with contracting firms when starting up?
https://www.claconnect.com/en/resources/articles/2023/a-cost...
> The amortization period is five years for domestic expenses and 15 years for foreign expenses. Additionally, for the first year of the amortization period, the expenses are “placed in service” at the midpoint of the tax year. Thus, the deduction in year one is only half the amount it will be in subsequent years.
Yes.
yes.
This calculation will apply with any level of profitability. The tax simply goes up. My questions is how the large software development companies (Google) are dealign with this? It would be $10s of billions of extra tax for each of them. We didn't hear the outcry. If they were to pay extra $10s of billions, presumably they could get the whole country up in arms quickly. Maybe this relates only to the portion of software development that us declared as an R&D expense? The regular software engineers' salaries would be the cost of goods/services sold?
It’s a cash flow issue, not a tax rate issue.
More like:
If paying salaries isn't an expense you can write off, you still have to pay all those salaries, and then pay tax on the money used for those salaries.
I don’t think you understand amortized expense accounting and income tax, you have a line item labeled tax on revenue.
What you are showing is cash flow not the income statement and also you don’t understand the tax is based on the income statement and not the salaries being paid or the revenue, but the calculated income for tax purposes.
In the 2nd year it will be 2/5ths, $200K, amortized expense of prior year plus current year, assuming same numbers, and by the 5th year would be full amount.
Your cash flow is correct and yes it becomes -$200K which is really bad. However I wanted to clarify the mechanics.
Here in Canada we have similar fractional write-offs called CCA (capital cost allowance). That's for assets though, like a company building, car or equipment.
I've written an accounting system before for business activities and successfully used its reports to win a tax dispute.
I'm not so interested in the details of this, particularly because it's in another country, but I do understand the implications of suddenly not being able to entirely write off the likely most important and large business expense.
1 reply →
Yeah that would be the cash flow, my example was taxable income. But yes, that's the whole problem!
The answer is simple: you just cut the developers' salaries to minimum wage. They'll all be happy to just have a job and will stick around, right?
It can also be positive to amortize r&d and software development costs eg. when you have no revenue this year but expect revenues the following years, you pay less taxes then and overall. In Germany software development and r&d with unknown outcomes cannot be amortized whereas you have the choice with say self developed factory equipment.
Agreed, options are great! Unfortunately this bill removes all options.
Also operating losses can be carried forward and used for 20 years, so recognizing a big loss in a single year isn't really that bad.
Isn't this all referring to the "R&D tax credit"? My understanding of the word 'tax credit" is that any labor that could be classified as R&D would essentially be funded by the government. When this came out I thought "what a scam" because companies were going to develop their next-gen products anyway, but now some of our work could qualify as "R&D" and basically be free to the company. If my interpretation was correct, that would explain why big tech companies pay so many people so well - they weren't actually paying them at all, the government was. Even though I may benefit from that, that's not how I think it should be.
OTOH, I'm not a biz guy but I was under the impression that paying employees was an expense anyway and would be deducted from revenue and not taxed. How is R&D different?
> Isn't this all referring to the "R&D tax credit"?
No. The terminology is confusing. Section 174, specifically point 3, classifies software development as R&E as of 2022 and requires amortization over 5-15 years. This prevents software engineering salaries as a standard business tax deduction. This has nothing to do with the R&D tax credit (section 41).
> Isn't this all referring to the "R&D tax credit"?
No, it is not.
>> Congress failed to extend a key tax provision last year allowing companies to fully expense research & development costs in the year incurred, a blow to big corporations that had lobbied for it.
OK, so what is it?
1 reply →
I appreciate the suddenness of the change, but aside of that, how is this different than amortizing the cost of a million dollars worth of equipment? Couldn't they borrow the money for their taxes against future profits?
Thinking about it more, perhaps it's a mistake to assume that the software being written has a service lifespan of five years.
Because you don't stop paying developers starting the second year?
But aren't you deriving value from what they developed in the first year? I mean, maybe that's my mistake.
If they spent a million, made a million, and are now back to square one, it would make more sense to not amortize the investment because it's not an investment.
2 replies →
> Couldn't they borrow the money for their taxes against future profits?
In theory, but good luck getting a loan secured against IP for a reasonable rate.
The change isn't really sudden and honestly I have a hard time having sympathy for those firms that were caught unaware. This provision was in the law since 2017 - anyone taking a chunk of VC money (including the VC lending it) should have been well aware of what would happen if Congress did not strike it before it took effect.
Honestly this is a bit like SVB all over again - poor management, in this case not knowing or understanding critical tax laws. And if you did know, shame on you for not contingency planning for Congressional ineptitude.
The only way to really plan for it, if you're running a small business with lower margins, is to raise prices, grow users or cut salary expenses. None of those are easy, even if you can see the tax bill coming.
What is the rationale for amortizing R&D expenses in general? Even outside software, what is the motivation for this?
The R&D isn't a pure expense, it typically has a result. Say you spend a million dollars developing a widget and then sell it for 10 years. The money spent in year one results in multiple years of income.
I don't have a strong enough understanding of the change to really have an opinion, but that seems to be the clearer description, the R&D spending is being treated as an investment in the business (which it probably is) that results in capital (who knows if that is true).
FWIW when I was in business school, one professor strongly argued (based on an Aswath Damodaran blog/video - he is a business school "celebrity") that R&D should generally be considered a capital expense in terms of valuing companies even when it can be considered an operational loss on an income statement. Technically, this (likely catastrophic) accounting change may be kind of correct in a pure sense.
However, the "asset" associated with software development seems pretty uniquely hard to transfer. Almost every other intangible asset has a strong marketable component (eg a patent on a widget, a copyright on a song), whereas software just doesn't have one. Licensing doesn't count here - that's not a transfer of the asset.
4 replies →
As someone who's taken a couple semesters of college-level accounting, and filed my corporate taxes correctly many years without audit (but am not an accountant/CPA), this seems broadly correct.
I'm actually surprised people are freaking out about this. Of course software is R&D. And of course you don't just get to expense it all at once. It's long-lived, like you said.
Maybe we could have some tax breaks like our friends over in real estate, but I very much think the base assumption should be that software dev is capitalized.
2 replies →
One reason is that sometimes companies claim money from the government for their R&D spend (some sort of scheme by government to incent R&D spending, presumably). In that event the government wants to prevent companies from gaming the system by simply saying that they spent all their profits each year on R&D. So rules are created that say you have to spread the spend over N years for tax purposes. Same as asset depreciation -- you're generally not allowed to depreciate a large asset in one year.
I was wondering how the end of highly paid engineers like myself would come to an end. Maybe this is it.
After 4 years are you back to where you started? With the fifth year stacking on top of the other 200K chunks from the first four years?
(If your hiring keeps accelerating I guess not, so major scaling of your team would seem to be discouraged by this change.)
At the same time, wouldn't it discourage reducing headcount (or at least headcount expenditure) for companies with roughly flat or linear revenue growth (see all the big tech layoffs), because you'd be paying more in taxes next year, etc. ?
edit: never mind, I completely misunderstood. It really only seems to harm "moonshot" companies; big tech and sustainable companies appear to be largely unaffected. If anything they may benefit as it will be more costly for upstarts to try competing
Assuming everything stays the same, this rule actually results in marginally lower tax burden (since progressive income tax means that 5 years of tax at $800k < 4 years of tax at $1 million). Assuming that it changes, no. In a worst case scenario, you may be paying a lot more if you do most of your development in a peak year and then lose the revenue stream later.
I would assume you aren't laying off your whole staff after year 1, so the comparison if costs stay the same seems like this instead?
Old:
Year 1: 0 Profit
Year 2: 0 Profit
Year 3: 0 Profit
Year 4: 0 Profit
Year 5: 0 Profit
New:
Year 1: 800K Profit
Year 2: 600K Profit
Year 3: 400K Profit
Year 4: 200K Profit
Year 5: 0 Profit
E.g. stack another amortized round of annual salary each time.
Even if revenue stays the same but costs increase, your Year 5 total for each is "X Profit" where X is the amount of revenue delta from Year 1 to Year 5?
If rapid hiring growth followed by layoff scenarios, you are worse off here: you pay the tax on the hiring boom for at least the first year or two before your revenue might drop enough to make it not matter?
If you're further away from profitability, it's maybe still a wash.
Hire up to 10 Million in salaries in 1 year, but your revenue after 2 years is just 4M - you're still under the window. You only get hit by the difference in the bill if your revenue accelerates a lot (which is an OK problem to have)?
So on one hand it seems like it could reduce poorly planned impulse hiring by spreading out the costs, but on the other hand the "run big losses until we make it" plan is less affected anyway because of the "big" in "run big losses"... so it seems to hurt the sustainable folks more in that case.
5 replies →
> (since progressive income tax means that 5 years of tax at $800k < 4 years of tax at $1 million)
This is corporate tax, not income tax, so is not progressive.
2 replies →
Do these companies have an option of moving overseas to avoid this?
>> Now the company must pay taxes on 800,000 of profit because "R&D salaries," which includes software devs, must be amortized over five years. Obviously the company has no wherewithal to pay, given that they made a million and spent a million.
So stop claiming software development as R&E and just say they're regular salaried employees. The government never should have been paying them in the first place!
It's not up to you to categorize them one way or another. This law mandates that they are r&d and thus amortized.
No, no it doesnt.
2 replies →
IANA accountant but this seems...fine? The point of writing software is typically to get some benefit from it in future years, just as GM expects to get more than one year's use out of a lathe or a sheet metal press. Of course they won't be able to cover the entire expense of buying the lathe entirely out of revenue they receive in the same tax year that they buy it. Why should they expect to be able to do the same for software?
This is backwards. Capital expenses are amortized because you purchase an asset that will give you value over multiple years. So, for example, if you buy an office building, you amortize the capital expense.
But what this does is says that if the product you created is an asset, the salaries that go into creating that asset should be treated as if it were purchasing that asset. The office building equivalent would be the builder having to treat the salary it paid its labor as a capital expense and amortizing it.
That sounds beyond insane.
That being said, it’s not a material change, if phased in properly, so companies have time to spread their expenses over a period of time.
But it looks like neither was this planned for (not surprising because it’s ridiculous on its face), nor does the legislation phase it in a manner that can be properly absorbed.
In practice companies will get hit hard the first year, but save the equivalent amount over the next 3-4 years. So after 5 years it will be a wash (ignoring the time value of money…factoring in that makes it a loss, but not as much of a loss). The problem is that it will create tremendous cash flow problems as 5 years of tax is paid in 1 year.
> Capital expenses are amortized because you purchase an asset that will give you value over multiple years. So, for example, if you buy an office building, you amortize the capital expense.
Even that seems like a pretty weak argument for what is essentially a tax penalty.
At least for a purchase of a liquid (or somewhat liquid) capital asset, one could, in principle, re-sell it. But most R&D has essentially no direct resale value and is not being done to create a salable asset. It’s done to create knowledge or IP, which, in turn, is used to create something salable.
I assume the purpose of requiring amortization of capital expenses is to prevent abuses like buying an extremely liquid asset, deducting the purchase price, and thus deferring a tax bill.
> The office building equivalent would be the builder having to treat the salary it paid its labor as a capital expense and amortizing it.
If the builder is building the thing for themself, they do in fact have to depreciate over the IRS-provided lifespan of the building.
The software equivalent to a builder is an agency. If the agency is building their own software, they now have to do the same thing. If the agency is building for someone else, they expense the labor immediatley.
>But what this does is says that if the product you created is an asset, the salaries that go into creating that asset should be treated as if it were purchasing that asset.
This is precisely what happens!!
Honestly if a company's business model revolved around getting 100% tax credits for dev salaries, that company should in fact go away. A 100% rebate on taxes on an already high margin and low expense business segment just feels wrong.
11 replies →
How closely did you read the line items?
In the example given they received a revenue that covers the entire cost of the software. The problem is that they then used that revenue for payroll which would be fine previously as if you make $X and pay $X in payroll then you pay ($X - $X) 0 in taxes and there isn't a cash flow problem.
To stick with the apples-oranges lathe example. Imagine GM got a loan of $1M for the lathe and they can only depreciate 1/5 the cost of the lathe. So come tax time, GM has to pay taxes on their 800K of "profit" since they can't fully count the cost of the lathe against the loan.
Loan example doesn't work because it's not revenue used to buy the lathe. That type of loan situation is exactly what depreciation/amortization/MACRS is for. If the company brings in $500,000 but buys a $1,000,000 lathe with a loan, they have a net cash flow of +$500,000. Their NPV isn't immediately affected by the loan liability because it's offset by the positive value of the lathe asset.
Then they pay taxes on $357,100 of adjusted earnings because under a 7-year MACRS depreciation, it's assumed the lathe lost $142,900 of value in its first year of ownership (under double-declining or straight-line methods).
Your first part is accurate though.
Anyways, this tax law is fucking terrible. W2 Wages should not be capital expenses because you generally won't be using loans to pay them.
I think I'm failing to see your point, as I cannot find one here.
If GM needs a lathe and has a reasonable business strategy, they should be able to get their accounting office and their leadership to align on how to make it make sense over 5 years. If they can't, it's a business run poorly, and according to the basic tenets of free market capitalism (which you seem to be leaning on heavily) that business would and should fail.
More generally, this seems a natural consequence of the impersonal ways that businesses treat employees, aka "human capital stock" to use the term of art. Capital stock / assets used for generating revenue should be taxed the same across the board.
9 replies →
It might be fine if that's how it long had been, maybe. What's definitely not fine is the sudden change of rules that an entire industry had been relying on for all their expense planning.
Then the argument would be "let us transition smoothly to the new mode". But all we're seeing in these threads is "bad bad no good very bad" with relatively little nuance.
The key problem here is that for 70+ years companies have had the option to amortize or expense these costs. This change was made as an accounting sleight of hand to make the 2017 tax cuts look paid for over a long-term basis, but Congress never intended for this change to take effect. They know it isn't good tax or economic policy.
So now small businesses and startups are being thrown into crisis because Congress has accidentally implemented policy that they haven't gotten around to fixing.
One potential difference is that for many things that are capital expenses (a building for example) a business is likely to take out a loan in order to buy it, so they don't have the full expense up front. A bank is probably not going to loan you money to pay your developers at the same terms they will loan you money to buy a building.
Makes sense, but why not (genuinely asking)? Is it just that the bank can repossess the building if necessary, but repossessing bespoke software is kind of pointless?
2 replies →
It really depends of your business. Sure if your are a SaaS company, SAP, Google,... that's the case.
But if you are a small shop that build software for other companies, it isn't. You write the software, get a one off paiement and you'll not be able to get more revenue from it in the future outside of a possible maintenance contract. You can't resale it to someone else.
To summarise, the work of many software companies is akind to the work of design office : you do R&D for someone else. The amortization will have to be done by your customer, not by you.
I’ve not read all the comments but I’d note that this issue becomes less serious every year as you build a pipeline of amortization. Assuming 1mm stays the same YoY in 5 years you’re paying no taxes again. Each year taxable income reduce by a further $200k until year 5. That provides no relief now but even without action it resolves eventually - except for new firms.
... growing firms are also penalized. Also, if a company goes bankrupt (like the majority of companies), those last 4 years of amortization just go into the government's pocket. Even if you could ignore the time value of money, it doesn't actually even out over the long run.
Yes. It also penalizes shrinking firms as you simply lose the benefit of amortization if you can’t use it.
2 replies →
> Assuming 1mm stays the same YoY in 5 years
That's a pretty big assumption.
But the first year is the hardest...
Are software dev salaries treated differently than regular employees. I thought 100% of salary and benefits were deductible against revenue.
I’m missing why software salaries are amortized against just straight expenses?
We are talking about an extremely lucky company if it's the first year. How many startups are able to get revenue equal to salary expenses in the first year? While they might exists, it's not very common. For all others and if it's not the first year you already have losses carried forward which will offset those 800,000 (since you didn't amortize them in the previous years, right?), so in your example if it's the first year you get any revenue you would have (years since founding) * $1,000,000 in losses. What do I miss here?
Why are you only considering the first year? My company has been around almost 20yrs and is impacted. There's no years since founding in any part of the calculation.
If we are considering a stable company the only problem is that you expensed more since 2017 than you would have normally done, i.e. you effectively paid less taxes over 5 years. Now you need to catch up. I admit it's not fun, especially if everybody expects it won't happen, but overall it's the same tax.
2 replies →
Just to clarify, if they last 5 years, then eventually it gets back to even by year 5, is that correct?
Also, if you classify the employee differently, does that change situation?
As long as you never grow.
Yes, you're correct.
What happens if they pay an 3rd party company?
Damn, what are they thinking right now?
Not an accountant But I think, they are thinking that software devs should be consultants ( unless they are researches doing something very risky, something that may not work (from technical not business sense))
This way, they are an expense to the corporation, and each one of the consultants pay their own income tax.
In that way the corporation building software for sale/SaaS is treated the same way that a corporation that's buying and then renting out real-estate, for example.
Seems like a big deal but have not heard it come up til now? Maybe cause tax season?
It's not a big deal because this change affects very few companies outside of Silicon Valley and it only affects companies at the start of the R&D process.
After 5 years, the tax impact evens out to be the same as currently expensing R&D salaries.
And generally, software companies have gotten the benefit of the R&D credit even for things would not have qualified for the R&D credit if it had not involved software, so this change was merely seen as correcting a tax loophole that the software industry has been exploiting (and arguably abusing) for several decades.
It very much affects bootstrapped companies building a software product. I'm not sure where you got the idea that it only affect Silicon Valley companies?
If you bootstrap your company to the point where you can afford one engineer's salary, you can only deduct 20% of that against your revenue. I.e. you've paid out all the cash and but you still have to pay taxes on the 80% that is not allowed to be expensed this year.
2 replies →
The R&D tax impact will NOT even out. its taxes you pay for 5 years that you don't get back. R&D tax credits is a small right-off and not worth the efforts. Lots of startups don’t even do the R&D tax credits because of the cost and time evolved to do all the necessary records, backups and reports.
This is a pretty ignorant comment.
I think you’re missing a variable here. Corporations == bad
Salaries aren’t tax deductible normally? That seems wrong.
Oh, hiring 1099 consultants now looking rather attractive
Luckily, barely any startups actually have revenue.
Huh? It's not about startups. It's about small software businesses that were moderately profitable yesterday and are potentially out of business today.
Realistically though the first year is:
So doesnt really make much difference
This has nothing to do with year one though. This is hitting companies that are in year 5, 10, 20, etc.
If you were running a small software company that make 2m in revenue and puts 200k to the bottom line, your business no longer works.
Is this applicable to different titles developing software, such as Member of Technical staff?
Wages aren’t R&D lmao
Unfortunately, the Government of the United States disagrees with you.
This is disingenuous though, because they would also have 4 other years of salaries to amortize.
If anything HN should be cheering this law since it incentivizes growing your R&D team quickly and consistently.
If you make a million and pay a million in salaries, you have no cash left, right?
But! You get to pay taxes as if you made 800k in profit. So lucky you, you have zero dollars and now you get to pay 240,000 in tax (800k * 30%) to the government.
You're now 240k in the hole. Game over, no year two, three, or four.
This doesn't affect venture funded companies as badly because they have millions in funding and they can ride out the amortization. It does, however, affect bootstrappers trying to start a thing. Perhaps you could call them small, indie hackers?
If anything, HN should not be cheering this law as it doesn't affect large incumbents and those with millions in VC funding, but crushes the little guys.
You hire consultants. You paid them a million, you also made a million on the product they produced that year.
So they were not really 'researchers', working out on unknown with high risk probabilities, instead they were building an asset that made you money the same year.
You would deduct the payment to these consultants as expense. they pay their own taxes on their salaries.
You are left with an asset that you can make money on, year after year.
That's, I think what they are thinking.
But a) you were not prepared to turn your salaried employees into consultants b) the asset requires extensive up-keep, that costs as much as money as it was to 'create it' c) the asset value without the up-keep can become zero in year d) the asset itself is very risky and may not have value later on.
So I overall agree with your sentiment.
The gov does not want to classify software dev as 'research', but yet -- they have not established how to fairly classify it.
This is a clustferfuck.
We aren’t supposed to ask direct questions on here, but you “get” that a company charges 20% of each of the past 5 years, right?
Like, we agree that’s what depreciation/amortization is, right?
So this most affects companies that have a relatively large R&D org relative to the past few years (aka my point about growing R&D ahead of other functions).
14 replies →
How can you grow your R&D team when you’re no longer in business because your tax bill is more money than you have? It makes zero sense.
It's the opposite. It disincentivizes growing all software dev (not just R&D) by front-loading taxes.
> The new law would instead work like this:
Forcing sofware dev salaries to be considered R&D then forcing all R&D expenses to be amortized over five years? There's a name for that kind of behavior.
It's theft.
There are means to offset, defer, and reduce tax burden that you also get from doing R&D, so honestly the change in the way the salary is treated is somewhat balancing these other tax benefits that startups are also taking. It's a balancing change to a larger system, not a targeted change to screw startups. A comparison over just Year #1 is disingenuous.
Let's say you have to pay 30% tax on 800,000 of profit, so now you're 240k in the hole. That's your year one! If you don't survive to take the future deductions it's kinda moot right?
Even worse for companies in high tax states like California, overall tax rate is closer to 40%.
Only a small portion of activities count as R&D for R&D tax credit purposes. R&E is a much bigger category and where the problem lies. This write up has a good graphic showing the magnitude (scroll halfway) https://www.striketax.com/journal/tcja-and-the-resulting-tax...