|
|
|
|
|
by patio11
4700 days ago
|
|
And it’s not just Massachusetts developers that have to deal with this. It’s anyone who has clients who have “software” that is being “used” in Massachusetts. Talk to your lawyer if you doubt me on this one, but Quill vs. North Dakota means that it is the well-settled law [+] of the United States that you cannot be liable for sales or use taxes enacted by a state which you don't have a "nexus" in. What exactly constitutes a "nexus" can be hazy, but the punchline for the overwhelming majority of HNers is that if you do not have an employee who performs work for you within Massachusetts you almost certainly do not have a nexus there. Theoretically HN users who are also Massachusetts residents will have to start remitting use tax to the state to cover purchases of covered which they made from out-of-state merchants. It is an open secret that compliance in the US with use taxes is nearly zero. + Well, until they pass that threatened Internet tax legislation. |
|
If you're a consultant who does work on-site for an MA client, that may also establish a nexus. In some cases it can do so even if you don't physically travel to MA, since the services can be deemed to have been rendered in the client's location. But others are deemed to have been rendered in the consultant's remote location. It's a little conceptually (and legally) unclear where remote services "happen", and seems to depend on the state and the service and the precise consulting relationship.