Page 1 of 1

tax problem

Posted: Fri Aug 07, 2009 9:49 am
by triplw
I've been having this problem with tax calculations since I've upgraded to 7.0.3. I just now figured out how to reproduce the error.

User has to be in a Group that is tax exempt.
They add items to their cart without logging in first.
They log in on the OnePageCheckout.
Sales tax is erroneously added no matter what their address is. That's people in a tax exempt group that do not reside in a state to be taxed!
Discounts for their group are applied correctly. If they add more items to their cart, no more sales tax is applied.

Can someone please help with this?

These are my settings:
Image
Image

Example of messed up invoice:
Image

Re: tax problem

Posted: Fri Aug 07, 2009 10:40 am
by jmestep

Re: tax problem

Posted: Fri Aug 07, 2009 10:46 am
by triplw
That's not what I'm talking about. The tax is wrong after registered users log in. See the invoice.

Re: tax problem

Posted: Fri Aug 07, 2009 10:58 am
by triplw
OK, I think maybe I've fixed this. I had to uncheck the tax exempt box on the User Group page.
I really never understood why the tax exempt status was on the User Group page and the Tax Rules page. Can anyone explain this?

Re: tax problem

Posted: Fri Aug 07, 2009 11:00 am
by Logan Rhodehamel
triplw wrote:I really never understood why the tax exempt status was on the User Group page and the Tax Rules page. Can anyone explain this?
I will commit to investigating this issue before the end of today. It sounds like a potential bug, and I need to see what you mean about two locations for tax exempt.

Re: tax problem

Posted: Fri Aug 07, 2009 4:21 pm
by Logan Rhodehamel
triplw wrote:I really never understood why the tax exempt status was on the User Group page and the Tax Rules page. Can anyone explain this?
I never noticed this before. On the tax rules page, you can configure to exclude certain groups. But this only applies to stores using the built in taxation rules. AbleCommerce also has the ability to support third party tax integrations (like Avalara).

The checkbox on the user group page is a total override for all taxes. If you check this box for a group, our calculate taxes code does not process any rules for either integrated tax rules or a configured third party provider.

Re: tax problem

Posted: Fri Aug 07, 2009 4:34 pm
by Logan Rhodehamel
triplw wrote:OK, I think maybe I've fixed this. I had to uncheck the tax exempt box on the User Group page.
I really never understood why the tax exempt status was on the User Group page and the Tax Rules page. Can anyone explain this?
Confirmed. You have found a bug (reported as #8288), and you have found the workaround. The tax exempt group setting is not working properly, I think as of 7.0.2. Taxes can be calculated for anonymous session but then aren't cleared out once the user logs in.

Re: tax problem

Posted: Fri Jan 22, 2010 11:03 am
by krittleb
This post would explain why my customers in KS that have a retailers license and are supposed to be "exempt" are still getting charged tax if they haven't logged in yet. Once they log-in, all future items added are not charged tax.

I don't see any way to exclude them from the KS tax without having them in the tax-exempt user group, so whatever workaround was discussed above, does not apply to us.

Please let me know if anything has been figured out on this as our KS customers are getting annoyed, especially since we told them we would change their accounts so they would not be getting charged tax. I guess I could send out an e-mail to all of them explaining that they have to log-in at the beginning of their session for the taxes to not calculate, but that is not very user-friendly.

Re: tax problem

Posted: Fri Jan 22, 2010 11:19 am
by Logan Rhodehamel
krittleb wrote:This post would explain why my customers in KS that have a retailers license and are supposed to be "exempt" are still getting charged tax if they haven't logged in yet. Once they log-in, all future items added are not charged tax.
Bug 8288 mentioned above was fixed for the 7.0.4 release. If you are not upgrading to this release, then the best suggestion I can offer is for you to create a customer service case and ask whether the solution can be patched to whatever version you have.