I'm also confused because it seems that most of the reasoning is that companies sell the software for cheap and then make the service contract expensive. I've seen this done by companies like Autodesk and National Instruments for sure, so I can see why they'd dislike it. I design custom equipment, and I'd be tempted to do the same (charge at close to cost for equipment and charge as a service for labor). But this seems like an incredibly poorly conceived way to fix the problem that will cause more issues than it will address, and it's surely not limited to software. I could pull the same trick in any kind of contract work.
If the software is cheap, it is expensive to service it.
However the "Sell software cheap and then charge for service" is the OPEN SOURCE MODEL, where the software is given FREELY, and if you need professional help you have to pay, that is certainly not the model Autodesk uses.
I don't see how it being the open source model is relevant. I'm not judging the validity of the practice, this is literally what the representatives claimed the logic was.
The proposal was to replace all provincial sales taxes with the GST, and to apply GST to everything, to keep it super-simple to implement. Well the provinces hated the idea, and the tinkerers just had to have exemptions added for various reasons. The result was that there were two sales taxes in Ontario, each with a complex set of exemptions. The popular example was that buying five donuts was taxable, because that was "dining", but buying six was exempt, because that was "groceries".
Not quite easy but if your business turns over more than £79k then you will have registered for VAT in the UK.
A US state VAT system would, presumably, result in a matrix multiplier (52 by 52 or whatever the number of different rates are) and require companies to track transactions in the various states.
In the EU, if you're British and buying from Germany, you pay German, not British, VAT rates - they should copy that.
Agreed though, that British VAT isn't as simple as it could be (whole categories exempt, etc.)
The rule of thumb is that VAT is a tax on consumers, not businesses. Of course there are hundreds of exceptions to that.
If you are a British company buying services from Germany then the seller shouldn't charge you a penny, then you charge the British VAT on the purchase and then deduct it if only the purchase is related to _your_ taxable sale(s).
But if you are a British consumer then the seller should charge you the German VAT.
That's the general case, there are exceptions to that and exceptions to exceptions so don't bite me please :)
By the way, the national VAT bills have to be complex simply because they are meant to mirror the EU directive: http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=CELEX:...
http://taxfoundation.org/article/state-tax-collections-capit...
Part of that is having both a sales and an income tax. Some states have one or the other.
Per capita income minus dollars taxed or the ratio of the two might be a better measure than either of ours for what you're trying to get at.
Point being, the rates are low and could easily be added to without dumb-ass industry specific things like this.
This sort of software is in something of a hazy middle ground between shrink-wrapped software on the shelf and IT consulting services. Taxing it may seem dumb to us when compared with other states, but probably seems like a reasonable move to at least consider to most.
This minefield of regulations about what's taxable and what isn't will just make it much more expensive to sell things, as people pay for lawyers/accountants to figure out what "tax" to add to every outgoing invoice. Since this will decrease consumption, it will reduce other tax revenues, as well as making this pot smaller.
Mad. Stark Raving.