We’ve got a non-taxable tax region code created in Epicor for non-taxable customers. In the past, they would not be taxed. Seems like something changed with Avalara - They are now getting taxed, even though the tax region code is set to the non-taxable exempt code.
One example has a sales order with no tax, but at invoicing, it got taxed (with the same exempt tax region code on both).
Epicor support is directing us to use Avalara’s Tax Exempt Certificate service going forward… We never used to have to do this, and manage the certificates ourselves.
Can you screenshot the Tax Liability setup screen? There should be a checkbox that says use tax interface or something like that. If it is unchecked then you can stop it from hitting Avalara all together
Utah - I did put in a ticket. One for our 2024.2.8 test environment where we first saw it, and thought it was an upgrade issue. Then another for a different company that we just put live on Avalara last week in our LIVE 2023.2.14 environment.
EpiCare states that the previous practice of marking customers exempt to avoid Avalara taxing is not best practice, and that we now need to use Avalara’s tax exempt certificate management service to guarantee no taxes.
If that’s the case, what’s the purpose of the “Tax Connect Calculation” checkbox in Tax Liability Entry?
It’s weird that Epicor would skip tax on the sales order, but then charge it on the invoice.
It’s super odd dude because the whole cert capture product is an add on if I am not mistaken, right Andris? It’d be like saying you can’t use AvaTax without their cert capture.
Utah - We’re on-prem 2023.2.14, upgrading to 2024.2.8 next weekend.
That’s how I’m reading it too. Hoped that I could point to some change and push back on Epicor to get it working the way it used to… This will kill us on our volume of Amazon transactions! They already capture sales tax, so we don’t need to.
And if we changed something by mistake, I don’t recall doing anything. I was hoping Epicor support could get us back to business as usual.
Latest response is asking us to use base-mode on the classic UI’s for order entry and AR invoice entry (to rule out a 4 year old customization that unhides a few fields in a grid and adds a UD field).
This really happened man? Like they are just straight up saying that we have to buy cert capture now and we have to send every transaction to them? This feels really off.
We’re on 2023.2.14, so not THAT new… I’ve got to do a bit of research with BAQ to see if it’s consistent, or a handful of glitches. Sucks when you can’t trust Epicor and have to check up on it.
Utah - Correct. The tax region code is the tax liability. We’ve got our code as ‘NTS’ for one company (Non-Taxable State) and ‘Ex01’ (Exempt) for the other one. Neither have ‘Tax Connect Calculation’ checked in the Tax Liability Entry module.
I did a BAQ to show orders with tax = Ex01 joined to invoices that have a tax amount >0.
So, all of your invoices have something there in tax liability on the invoice line and all of those invoices are bringing back tax right now when a valid cert isn’t found, is that right?
Let me ask you this, for all of the customers that this is happening to… are they set up in Cert capture?
Let me ask that a different way… for all the invoices where you are seeing this issue, do those invoices belong to a customer in cert capture with expired certs?
It would be really surprising for that checkbox to no longer work. It is there for when a company wants to use the Epicor tax engine, which is robust but needs a lot of work to maintain tax rate changes.
I suspect there is something else going on. Who from support have you been working with?
If you would like, we could do a screenshare and I can take a look. I am in Pacific time.
