Most laws aren’t retroactive. If you do the thing before it’s illegal, then you skated by. That could very easily be the answer here, especially as most all the physical automation is barely existent. If a company deploys now, they don’t pay the tax, but they will when they upgrade models.
You’ll need to provide your definition of “physical automation” for the purposes of your argument. As it stands that is NOT clear, which is part of the quagmire of all the Automation Tax approaches.
As to code automation, same rules apply. Excel macros get by, but I would apply the tax on companies that replace white collar jobs via SaaS or other applications as their core businesses model,
What does this mean? If a company is still running on-prem MS Exchange servers for company email, then the law passes, then the company switches to Office365 for email instead, does your law hit that company with an Automation tax? If so, how would the tax be applied? Amount of spend on Office365? Amount spent on salaries of former MS Exchange administrators? How long would the tax apply? A year? Forever?
What I’m also seeing is that all encumbant companies (shielded from the automation tax because they already put automation in place) would have an advantage forever against existing companies trying to make automation changes (and being hit with the tax).
Another loophole I see is companies completely liquidating or selling to a newly formed company so that there are “no jobs lost to automation, because this company from day 1 has always used automation”.
or for that line of buisness for vendors that do a lot of things. It would have to be refined as to where you draw the line, but you could.
I don’t know what this means.
Can you give a concrete example of your Automation tax? Situation before your law goes into place, the law passing, then the Automation tax a company would pay when they make a specific change in your example?
Tons of questions here, but sure I’ll give it a go.
Any autonomous or nearly autonomous hardware device would be taxed. Exceptions can apply. Maybe autonomous tractors are not taxed because food is needed, but unemployed farmers also need to be cared for.
As to the code question and m365, maybe, maybe not. It may be reasonable to tax all cloud automation as a whole, or maybe just all SaaS, leaving IaaS and PaaS out of it. Exceptions may apply.
The tax would be on the good or service forever, yes. If you displace human workers with automation, then thry need their basic needs met for human decency, but also so they don’t tear society to pieces, justifiably in my mind.
Incumbent companies using automation may have an advantage, but only until they use a new robot or new automation. That advantage goes away if they are stuck 5-10 yr behind to avoid a tax. If they want to keep avoiding it, newer companies using taxed but getting a huge productivity booster will surpass them. That will incentivise them to use the tax producing goods or services and remove any initial advantage.
I think I would also be okay with “no tax until you hit X automations” as well. You clearly can’t give tax breaks on employees, as not employing people will be the whole point of this, but you could likely work it out.
You’ll need to provide your definition of “physical automation” for the purposes of your argument. As it stands that is NOT clear, which is part of the quagmire of all the Automation Tax approaches.
What does this mean? If a company is still running on-prem MS Exchange servers for company email, then the law passes, then the company switches to Office365 for email instead, does your law hit that company with an Automation tax? If so, how would the tax be applied? Amount of spend on Office365? Amount spent on salaries of former MS Exchange administrators? How long would the tax apply? A year? Forever?
What I’m also seeing is that all encumbant companies (shielded from the automation tax because they already put automation in place) would have an advantage forever against existing companies trying to make automation changes (and being hit with the tax).
Another loophole I see is companies completely liquidating or selling to a newly formed company so that there are “no jobs lost to automation, because this company from day 1 has always used automation”.
I don’t know what this means.
Can you give a concrete example of your Automation tax? Situation before your law goes into place, the law passing, then the Automation tax a company would pay when they make a specific change in your example?
Tons of questions here, but sure I’ll give it a go.
Any autonomous or nearly autonomous hardware device would be taxed. Exceptions can apply. Maybe autonomous tractors are not taxed because food is needed, but unemployed farmers also need to be cared for.
As to the code question and m365, maybe, maybe not. It may be reasonable to tax all cloud automation as a whole, or maybe just all SaaS, leaving IaaS and PaaS out of it. Exceptions may apply.
The tax would be on the good or service forever, yes. If you displace human workers with automation, then thry need their basic needs met for human decency, but also so they don’t tear society to pieces, justifiably in my mind.
Incumbent companies using automation may have an advantage, but only until they use a new robot or new automation. That advantage goes away if they are stuck 5-10 yr behind to avoid a tax. If they want to keep avoiding it, newer companies using taxed but getting a huge productivity booster will surpass them. That will incentivise them to use the tax producing goods or services and remove any initial advantage.
I think I would also be okay with “no tax until you hit X automations” as well. You clearly can’t give tax breaks on employees, as not employing people will be the whole point of this, but you could likely work it out.