10% Tax On Custom Software, $100M Tax Cut For Microsoft
reifman writes "Last week, the Washington State House of Representatives passed a bill which would impose a 10% tax on custom software while all but eliminating a $100 million yearly tax obligation that some say Microsoft is wrongfully avoiding by routing large chunks of business through an office in Nevada. 'I believe we've got an issue of justice and fairness here,' said Rep. Maralyn Chase. 'Most of the custom software purveyors are small businesses. It's a question for me of how we fairly distribute the tax burden.' 'It means that a 5 person team of entrepreneurs building a cool custom software suite, or a group of system integrators, would face a 10% tax on their services while keeping the exact same project in-house would not be taxed,' wrote Rep. Reuven Carlyle. 'It would be a massive blow to the entrepreneurial community in our state.' The bill won't become law until the House and Senate work out how best to raise another $300 million in taxes. A sales tax increase on consumers is also being considered."
This is clearly is bad for the individual geek who makes their living selling simple custom programs that do only what the user wants/needs and nothing that they don't, unlike Microsoft omnibus packages. It's a case of government by large corporation over the individual if this passes.
Just so you know, the state of Michigan tried a 3% tax on gross receipts on physicians... It got shot down in the state senate after the house passed it. They're trying it again in by hiding it in a new budget bill.
I bring this up because it's in the same idea of trying to find new tax sources, that affect a small population to make it not unpopular... And it helps if that particular group is perceived to be "well off." It's poor policy to make one profession bear the burden of the masses (IMHO). It's a great way to try to drive business out of an area. It's also a great way to pass the burden onto the consumer without and claim that taxes have been raised.
Actually, that's the ticket. If by custom, they mean written against a customers specifications, then it's pretty shitty. If by custom, they mean for one and only one client, then it should be pretty easy to get around. Imagine this. Company A hires you to build a custom piece of software. Once you're done, you just need to make it available for purchase to other companies. Then it's strictly not "custom" anymore, since more than one company can use it. So it all boils down to their definition of custom...
This is nothing more than a prime example of lobbyists in action. How else could you explain that the first "community" to do this contains one of the largest "non-custom" computer engineering firms in the country? I wonder what the state congressmen (or whatever they are called up there) got in return for this sweet deal... Money? Drugs? Sex? Free Computers?
If a man isn't willing to take some risk for his opinions, either his opinions are no good or he's no good
At first I thought ... "that doesn't affect me..."
This is a very common attitude that is degrading our lives in all areas in my opinion. To me, it's like playing chess and looking just one move ahead.
I was looking over the proposed law and found some interesting information on this.
First, I'm not a lawyer or politician. Be ye forewarned.
Page 87 makes it seem that this isn't a new tax, but a removal of an exemption. From the document:
(7)(a) The term also includes the sale of or charge made for custom software and the customization of prewritten computer software to a consumer, regardless of the method of delivery to the consumer. (b) The term also includes the charge made to consumers for the right to access and use custom software and customized prewritten computer software, where possession of the software is maintained by the seller or a third party.
In other words, the following are taxable:
1) The sale of "custom software"
2) The amount paid to customize software that's already written
3) Licensing fees to access custom software
Back to the original question in this thread, it seems that FOSS could fall under 2) in my list -- developers are often paid to add specific features (thereby customizing the software) by individual or companies. As nothing is charged for the sale and licensing of FOSS (generally), 1 and 3 woudn't apply.
I will say, however, that "custom software" is not defined in said document.