We are now live with Tax Connect and I’m not sure that I’ve done all of our cut over correctly.
I had tax liabilities in our ship to in the customer maintenance for all that applied. We removed all of the liabilities from the ship to’s at cut over. Now, as I’m looking at invoices to see that the tax is calculating I’ve noticed that we have open sales orders that still have tax liabilities linked to them.
Can anyone advise if I should be removing these liabilities from the open sales orders as well and if so, can I do it in bulk?
Invoices for Shipments will use the Tax Category specified on the order lines, and combine them with the ship to of the packer.
We use AvaTax, and have about 13 different Tax Categories. This is because some tax authorities have rates that vary by the item/service.
Our most used one is “Tangible Personal Property”. Avalara assigned the code P0000000 for this.
We don’t specify the tax rates in the Product Tax Cat maintenance. AvaTax determines the rate based on the code and the taxable address (typically the ship to).
So you might be able to just remove all the tax rates from the various Tax Cat’s and AvaTax will fill in the right ones.
Yes, we did build in Product Tax Categories also using the Ava Tax codes.
When you built your tax categories, did you leave your existing tax categories or just add the Ava Tax codes to them?
We turned on Avatax a few years back when we were on 8.03. So I don’t remember all the details related to “going live”.
We didn’t do a conversion to E10, but rather did a fresh install and imported select records. This was mostly to cleanup the poor implementation for Vista 4 that we converted to V8 -which carried all the bad things from 4 to 8.
You may have to go back into any of those “Open” orders, and recalc the tax using Avatax.
(I say “open” as the order closes when shipped, but it’s still needed for billing)
Whether doing it manually or in bulk, you’ll need the query to identify the orders and lines to change.
If you have DMT, you could do it en-mass.
But be careful either way (manually or DMT). Some changes to header fields will automatically propagate to lines and possibly releases. For example; changing customer on the OrderHed will often reset any pricing in existing OrderDtl records. (I know that’s not your case. It was just an example of how a change to the header can propagate to lines)
Before you do any updates, make sure to do a full query the OrderHed, OrderDtl, and OrderRel tables for orders you are going to change. Then save the results from each into an excel file, so you have a backup of pre-update values.