Tax Rate Setup based on User Location?
Mike C. Fletcher
What is the approved mechanism for setting up taxation rates on a per-user-location basis?
In Canada, for instance, I have to collect different tax rates
for each Canadian province based on the location of the buyer, but
I do not have to collect taxes from US (or really any other
country's) customers. This is, the mapping:
{
'Alberta': 5.0,
'British Columbia': 12.0,
'Manitoba': 5.0,
'New Brunswick': 13.0,
'Newfoundland and Labrador': 13.0,
'Northwest Territories': 5.0,
'Nova Scotia': 15.0,
'Nunavut': 5.0,
'Ontario': 13.0,
'Prince Edward Island': 5.0,
'Quebec': 5.0,
'Saskatchewan': 5.0,
'Yukon': 5.0
} defines what our company (based in Ontario) needs to collect from a client in each of these Canadian Provices.
Is it necessary to create N (identical) plans in CheddarGetter, each with a different VAT rate for each of these territories and then pre-qualify the client according to their territory of residence for each plan? Or is there some other mechanism to using territorial information to assign a VAT rate? For our current product, creating N plans is not horribly burdensome, but if we were to have a product with M "real" plans, each of which needed to be maintained in parallel, that would seem to become somewhat unwieldy.
Discussions are closed to public comments.
If you need help with Cheddar please
start a new discussion.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Marc Guyer on Jan 09, 2012 @ 04:11 PM
Hi Mike -- We've had this request before from Canadian merchants. Unfortunately it seems that this is specific to Canada and wasn't on our radar when implementing our tax support. In the past, we've considered enabling the
customers/newandcustomers/editAPI calls to accept the tax rate per customer. This way you would have one plan for all tax rates and the customer record would hold the tax rate.We would, of course, need to make some changes to support this. Would you be interested in using this feature?
2 Posted by Mike Fletcher on Jan 12, 2012 @ 08:15 PM
It sounds like it would be workable; we can have an extra step in our signup that requests the information before we redirect the customer to the CC signup or the Paypal redirect.
3 Posted by stacey.feero on Mar 20, 2012 @ 03:31 PM
Have changes been made to support this? I'm also a Canadian merchant with the same issue.
4 Posted by simon on Mar 30, 2012 @ 08:08 PM
Is adding the ability to configure this on a per-customer basis in your roadmap? There does not seem to be a way in which to charge different VAT rates on a per-plan basis, and hiding the taxes in the products is not a best practice here.
Support Staff 5 Posted by Marc Guyer on May 08, 2012 @ 12:36 PM
Hi guys -- Sorry for the delay. We're evaluating a couple of options here. One, is to simply add per-customer tax settings. The other, and likely would be built upon the first is to involve a tax reporting service to add some automation to the processed (including annual remittance and reporting). We're looking for development partners on the project. Participating would come with some service credit and the ability to influence the functionality. Please let me know if you're interested or would like more information.
6 Posted by simon on May 09, 2012 @ 06:40 PM
Yes, I would be interested. Keep in mind that tax rates change over time,
so the rates at the time an invoice is billed should likely be recorded.
For instance, Ontario, Canada transitioned from two separate taxes (PST +
GST) to a single tax (HST) recently.
Dean closed this discussion on Jan 22, 2013 @ 10:35 PM.
Dean re-opened this discussion on Aug 22, 2013 @ 03:11 PM