Finance | Project Operations, Human Resources, ...

Avalara GP Connector TLS change

(0) Share

Report

Posted on by Tamulis

We are on GP2018 18.00.0628. We use Avalara Tax Calculation in our Canadian Database. It was working great - never a problem. About a week ago it stopped working. We contacted Avalara and was told we probably needed to update the GP Connector because Avalara is requiring TLS 1.2 instead of TLS 1.0.

I am aware of the email issues with GP and MAPI settings if GP version is prior to October 2020 (which we are of course). We somehow averted the need to upgrade and happily e-mail from within GP to this day.

My question is - are there any GP Users in the forum running GP2018 18.00.0628 and Avalara Tax?

I just want to be certain that I don't have to get GP2018 upgraded just to maintain keep Avalara Tax functionality. I downloaded the latest GP Connector from Avalara but is sure seems to me to be the same version I am running in my current production environment (that has stopped working).

Any guidance would be appreciated. Thanks in advance.

Categories:

Microsoft Dynamics GP

I have the same question (0)

All responses (14)

Answers (0)

Suggested answer

Derek Albaugh on at

Like (0)

Report

I'm not familiar with Avalara but if it uses Web Services, Web Services won't work with TLS 1.0/1.1 disabled on the server, unless you're using a AD security store with Web Services.

Other than that, there isn't much in Dynamics GP impacted by TLS, though SQL Server requires TLS 1.2 for connection.

Hopefully someone in the Community uses Avalara and can answer more from that side of it.....

thanks

Was this reply helpful? Yes No
Suggested answer

Lisa at AonC.com 919 Super User 2025 Season 2 on at

Like (1)

Report

Confirm with Avalara, but I believe you can update Avatax to the newer version without upgrading GP (even though you should get that upgrade scheduled ... ).

[We have a GP 2016 - yes, we are trying to get them upgraded! - who doesn't email but had to update their Avatax for a different issue.]

Was this reply helpful? Yes No
Tamulis 10 on at

Like (0)

Report

Follow up - we upgraded the Avalara GP connector and actually uninstalled and reinstalled Avalara and still can't get Avalara working. Support directly from Avalara has been pitiful - they don't seem interested in our problem.

I'm just reaching out (again) to see if anyone on GP 18 .0628 (build) is using Avalara and trying to determine if I need to do anything on the Server operating system in order to get back up and running.

Thanks in advance

Was this reply helpful? Yes No
Lisa at AonC.com 919 Super User 2025 Season 2 on at

Like (0)

Report

What issues/errors are you having following the Avatax upgrade?

Was this reply helpful? Yes No
Craig Fuller 411 on at

Like (0)

Report

Yes, but we are on a slightly older version than you: Dynamics GP 2018 18.00.0496.

We had to upgrade the Avalara GP Connector a while back and it has been working. Our Systems Group actually just installed their newest release this weekend and it is working.

Have you tried installing their newest one?

Was this reply helpful? Yes No
Tamulis 10 on at

Like (0)

Report

Yes - we have downloaded and re-installed both the connector and the application to no avail.

When we 'calculate tax' - the Avalara Dictionary throws an error about

The message seems to suggest that the record (invoice) has a problem with the address and can't therefore, be validated and taxes calculated. However, in our case the same item number, same customer number and same address worked on March 23 - something changed on March 23rd - either in our environment (we're in the Amazon Cloud) or in the Avalara environment.

I don't know much about how Avalara 'magic' happens, but I think in our environment - when I click calculate tax - the connector sends the data on the invoice externally to an Avalara website or other designated website/server where the address is validated against local tax codes and taxes are calculated.

We read that Avalara switched requirements on February 2023 to TLS 1.2 - that the connection between our server and their server had to be 1.2 TLS.

Our problem started March 23rd - I assume (maybe incorrectly) it's a server to server issue and need some suggestions on what I can troubleshoot on my side.

Thanks

Was this reply helpful? Yes No
Craig Fuller 411 on at

Like (0)

Report

So on this invoice, when you drill into the Ship To Address (click blue arrow at Customer ID, then blue arrow at Ship To Address ID) and inspect the address fields in the Sales Ship To Address Entry window, everything is populated and correct? The message is indicating state or province is missing or invalid.

And something completely unrelated...I'm curious, does Perfecto Manufacturing ring a bell?

Was this reply helpful? Yes No
Tamulis 10 on at

Like (0)

Report

Yes sir - in fact I have even verified that this same item number, same customer, same price, same shipping address has been previously processed (successfully) by Avalara prior to March 23rd.

Was this reply helpful? Yes No
Lisa at AonC.com 919 Super User 2025 Season 2 on at

Like (0)

Report

Have you tried calculating in the Avatax portal?

When you have the transaction open and select Additional > AvaTax Tax Inquiry, are there any clues/messages there to help troubleshoot this?

[Have you reached out to your GP/Avalara partner to see if there is something unique in your setup that may provide insight?]

Was this reply helpful? Yes No
Tamulis 10 on at

Like (0)

Report

Thank you very much for the reply. Definitely have not tried to calculate in Avalara Tax Portal - not certain how to do that. I just used the additional tax inquiry and I get exact same message.

Was this reply helpful? Yes No