Shopfy Tax Mapping on Returns

Do you have tax synchronization turned on or off?

If you have tax sync turned on you need to have a tax ID setup for each state where you charge taxes as it’s going to copy the tax logic from Shopify in the json. So “NY STATE TAX” for New York or “ME STATE TAX” for Maine would need to exist as tax IDs in Acumatica in order to import the order correctly.

We have tax sync turned on at the moment, and it works great (for the most part) at the sales order, but we are struggling with tax recalculation at the invoice leaving a balance. Rumor has it that this may be fixed in 2023 R1?

It may be best to keep tax sync turned off for now and define which tax zone that each sales order/ customer belongs to through a formula in the entities mapping. This would also allow you to continue to use your current tax IDs.

Hi folks - @VBrundage - great question. This comes up a lot with eCommerce merchants.

@brendan91 is correct. There is a challenge that these eComm platforms do not share the Tax ID’s via the API. So to match, the merchant must configure taxes in Acumatica as well. And this leads to some challenges, as you’ve found.

However, in 23R1 we have included a “tax recalculation suppression” feature allowing merchants to (per Order Type) disable tax recalculations on orders coming from the web. More info in this post - 

• How to prevent Acumatica ERP Sales Orders and Invoices from recalculating the taxes imported from external systems such as BigCommerce, Shopify, Amazon etc.,

This may resolve your issue.

Please ask your VAR to submit a case with this challenge that you’re facing. If possible, our team will offer some assistance

Thanks!

Thank you for the response.  The odd part about these transactions is it is ONLY the web returns that are getting stuck.  When our store does a return we do not have this issue. 

@brendan91 we have tax synchronization turned on.  If you don’t mind me asking what tax calculator are you using?  We currently have Avalara all of our tax locations are set up in the system as they were received from the external tax provider.

This is part of the reason why we are so confused as to why it is not working.

@brendan91 do you have formulas set up in your entity mapping?

Hi @VBrundage,

I have not used Avalara, so I don’t know what that looks like. The formula to map TaxZoneID could look something like this if you have a limited number of taxable states.

=iif([CustomerAddressData.ProvinceCode]='ME', 'MESALESTAX', 'NOTAXZONE')

You can created nested iif statements up to 10 deep, so that would cover 10 zones. There may be another way to do it with the switch formula and that would look like...

=Switch([CustomerAddressData.ProvinceCode]='ME', 'MESALESTAX', [CustomerAddressData.ProvinceCode]='PA', 'PASALESTAX', ...)

Did you add the additional tax zone and are the returns working now? It sounds like you may need to create a ticket with Acumatica support or Avalara if adding the tax zone does not fix the problem.