Sage 100

Is this in Sales Order? I had a customer where we had an issue where the Sales Order History totals were not updated properly.

I believe @Brett Zimmerman reported something similar to:

Basically, if the ship-to address on the sales order is invalid, it does not properly write to the S/O History file (e.g. nontaxable and taxable are $0, although freight for example does show) – and the S/O Entry file is fine.

My customer did not have that exact issue. Similar but we could not trace it to an invalid ship-to:

We had a couple of issues:

1. If we did not go to the TOTALS tab during SO Entry then Avalara ( when using AVATAX sales tax code ) was not computing totals
2. We received an error message during VI jobs when Avalara was enabled

I would not bother to call Avalara until you've downloaded the latest connector from DSD. In each interaction we had with Avalara updating the connector was always the first 10 things suggested.....

And the connector seems to be updated frequently so even if you installed an update yesterday you'll be installing another today during your support call.

All support first goes through Avalara. I did not have especially good luck working with them.

Is this in Sales Order? I had a customer where we had an issue where the Sales Order History totals were not updated properly.

I believe @Brett Zimmerman reported something similar to:

Basically, if the ship-to address on the sales order is invalid, it does not properly write to the S/O History file (e.g. nontaxable and taxable are $0, although freight for example does show) – and the S/O Entry file is fine.

My customer did not have that exact issue. Similar but we could not trace it to an invalid ship-to:

We had a couple of issues:

1. If we did not go to the TOTALS tab during SO Entry then Avalara ( when using AVATAX sales tax code ) was not computing totals
2. We received an error message during VI jobs when Avalara was enabled

I would not bother to call Avalara until you've downloaded the latest connector from DSD. In each interaction we had with Avalara updating the connector was always the first 10 things suggested.....

And the connector seems to be updated frequently so even if you installed an update yesterday you'll be installing another today during your support call.

All support first goes through Avalara. I did not have especially good luck working with them.

Is this in Sales Order? I had a customer where we had an issue where the Sales Order History totals were not updated properly.

I believe @Brett Zimmerman reported something similar to:

Basically, if the ship-to address on the sales order is invalid, it does not properly write to the S/O History file (e.g. nontaxable and taxable are $0, although freight for example does show) – and the S/O Entry file is fine.

My customer did not have that exact issue. Similar but we could not trace it to an invalid ship-to:

We had a couple of issues:

1. If we did not go to the TOTALS tab during SO Entry then Avalara ( when using AVATAX sales tax code ) was not computing totals
2. We received an error message during VI jobs when Avalara was enabled

I would not bother to call Avalara until you've downloaded the latest connector from DSD. In each interaction we had with Avalara updating the connector was always the first 10 things suggested.....

And the connector seems to be updated frequently so even if you installed an update yesterday you'll be installing another today during your support call.

All support first goes through Avalara. I did not have especially good luck working with them.

Is this in Sales Order? I had a customer where we had an issue where the Sales Order History totals were not updated properly.

I believe @Brett Zimmerman reported something similar to:

Basically, if the ship-to address on the sales order is invalid, it does not properly write to the S/O History file (e.g. nontaxable and taxable are $0, although freight for example does show) – and the S/O Entry file is fine.

My customer did not have that exact issue. Similar but we could not trace it to an invalid ship-to:

We had a couple of issues:

1. If we did not go to the TOTALS tab during SO Entry then Avalara ( when using AVATAX sales tax code ) was not computing totals
2. We received an error message during VI jobs when Avalara was enabled

I would not bother to call Avalara until you've downloaded the latest connector from DSD. In each interaction we had with Avalara updating the connector was always the first 10 things suggested.....

And the connector seems to be updated frequently so even if you installed an update yesterday you'll be installing another today during your support call.

All support first goes through Avalara. I did not have especially good luck working with them.

Is this in Sales Order? I had a customer where we had an issue where the Sales Order History totals were not updated properly.

I believe @Brett Zimmerman reported something similar to:

Basically, if the ship-to address on the sales order is invalid, it does not properly write to the S/O History file (e.g. nontaxable and taxable are $0, although freight for example does show) – and the S/O Entry file is fine.

My customer did not have that exact issue. Similar but we could not trace it to an invalid ship-to:

We had a couple of issues:

1. If we did not go to the TOTALS tab during SO Entry then Avalara ( when using AVATAX sales tax code ) was not computing totals
2. We received an error message during VI jobs when Avalara was enabled

I would not bother to call Avalara until you've downloaded the latest connector from DSD. In each interaction we had with Avalara updating the connector was always the first 10 things suggested.....

And the connector seems to be updated frequently so even if you installed an update yesterday you'll be installing another today during your support call.

All support first goes through Avalara. I did not have especially good luck working with them.

Is this in Sales Order? I had a customer where we had an issue where the Sales Order History totals were not updated properly.

I believe @Brett Zimmerman reported something similar to:

Basically, if the ship-to address on the sales order is invalid, it does not properly write to the S/O History file (e.g. nontaxable and taxable are $0, although freight for example does show) – and the S/O Entry file is fine.

My customer did not have that exact issue. Similar but we could not trace it to an invalid ship-to:

We had a couple of issues:

1. If we did not go to the TOTALS tab during SO Entry then Avalara ( when using AVATAX sales tax code ) was not computing totals
2. We received an error message during VI jobs when Avalara was enabled

I would not bother to call Avalara until you've downloaded the latest connector from DSD. In each interaction we had with Avalara updating the connector was always the first 10 things suggested.....

And the connector seems to be updated frequently so even if you installed an update yesterday you'll be installing another today during your support call.

All support first goes through Avalara. I did not have especially good luck working with them.

Is this in Sales Order? I had a customer where we had an issue where the Sales Order History totals were not updated properly.

I believe @Brett Zimmerman reported something similar to:

Basically, if the ship-to address on the sales order is invalid, it does not properly write to the S/O History file (e.g. nontaxable and taxable are $0, although freight for example does show) – and the S/O Entry file is fine.

My customer did not have that exact issue. Similar but we could not trace it to an invalid ship-to:

We had a couple of issues:

1. If we did not go to the TOTALS tab during SO Entry then Avalara ( when using AVATAX sales tax code ) was not computing totals
2. We received an error message during VI jobs when Avalara was enabled

I would not bother to call Avalara until you've downloaded the latest connector from DSD. In each interaction we had with Avalara updating the connector was always the first 10 things suggested.....

And the connector seems to be updated frequently so even if you installed an update yesterday you'll be installing another today during your support call.

All support first goes through Avalara. I did not have especially good luck working with them.

Is this in Sales Order? I had a customer where we had an issue where the Sales Order History totals were not updated properly.

I believe @Brett Zimmerman reported something similar to:

Basically, if the ship-to address on the sales order is invalid, it does not properly write to the S/O History file (e.g. nontaxable and taxable are $0, although freight for example does show) – and the S/O Entry file is fine.

My customer did not have that exact issue. Similar but we could not trace it to an invalid ship-to:

We had a couple of issues:

1. If we did not go to the TOTALS tab during SO Entry then Avalara ( when using AVATAX sales tax code ) was not computing totals
2. We received an error message during VI jobs when Avalara was enabled

I would not bother to call Avalara until you've downloaded the latest connector from DSD. In each interaction we had with Avalara updating the connector was always the first 10 things suggested.....

And the connector seems to be updated frequently so even if you installed an update yesterday you'll be installing another today during your support call.

All support first goes through Avalara. I did not have especially good luck working with them.

Is this in Sales Order? I had a customer where we had an issue where the Sales Order History totals were not updated properly.

I believe @Brett Zimmerman reported something similar to:

Basically, if the ship-to address on the sales order is invalid, it does not properly write to the S/O History file (e.g. nontaxable and taxable are $0, although freight for example does show) – and the S/O Entry file is fine.

My customer did not have that exact issue. Similar but we could not trace it to an invalid ship-to:

We had a couple of issues:

1. If we did not go to the TOTALS tab during SO Entry then Avalara ( when using AVATAX sales tax code ) was not computing totals
2. We received an error message during VI jobs when Avalara was enabled

I would not bother to call Avalara until you've downloaded the latest connector from DSD. In each interaction we had with Avalara updating the connector was always the first 10 things suggested.....

And the connector seems to be updated frequently so even if you installed an update yesterday you'll be installing another today during your support call.

All support first goes through Avalara. I did not have especially good luck working with them.

Is this in Sales Order? I had a customer where we had an issue where the Sales Order History totals were not updated properly.

I believe @Brett Zimmerman reported something similar to:

Basically, if the ship-to address on the sales order is invalid, it does not properly write to the S/O History file (e.g. nontaxable and taxable are $0, although freight for example does show) – and the S/O Entry file is fine.

My customer did not have that exact issue. Similar but we could not trace it to an invalid ship-to:

We had a couple of issues:

1. If we did not go to the TOTALS tab during SO Entry then Avalara ( when using AVATAX sales tax code ) was not computing totals
2. We received an error message during VI jobs when Avalara was enabled

I would not bother to call Avalara until you've downloaded the latest connector from DSD. In each interaction we had with Avalara updating the connector was always the first 10 things suggested.....

And the connector seems to be updated frequently so even if you installed an update yesterday you'll be installing another today during your support call.

All support first goes through Avalara. I did not have especially good luck working with them.

Sage Case#8008269285

Avalara Case# 19822350 

Is this in Sales Order? I had a customer where we had an issue where the Sales Order History totals were not updated properly.

I believe @Brett Zimmerman reported something similar to:

Basically, if the ship-to address on the sales order is invalid, it does not properly write to the S/O History file (e.g. nontaxable and taxable are $0, although freight for example does show) – and the S/O Entry file is fine.

My customer did not have that exact issue. Similar but we could not trace it to an invalid ship-to:

We had a couple of issues:

1. If we did not go to the TOTALS tab during SO Entry then Avalara ( when using AVATAX sales tax code ) was not computing totals
2. We received an error message during VI jobs when Avalara was enabled

I would not bother to call Avalara until you've downloaded the latest connector from DSD. In each interaction we had with Avalara updating the connector was always the first 10 things suggested.....

And the connector seems to be updated frequently so even if you installed an update yesterday you'll be installing another today during your support call.

All support first goes through Avalara. I did not have especially good luck working with them.

Sage Case#8008269285

Avalara Case# 19822350 

Is this in Sales Order? I had a customer where we had an issue where the Sales Order History totals were not updated properly.

I believe @Brett Zimmerman reported something similar to:

Basically, if the ship-to address on the sales order is invalid, it does not properly write to the S/O History file (e.g. nontaxable and taxable are $0, although freight for example does show) – and the S/O Entry file is fine.

My customer did not have that exact issue. Similar but we could not trace it to an invalid ship-to:

We had a couple of issues:

1. If we did not go to the TOTALS tab during SO Entry then Avalara ( when using AVATAX sales tax code ) was not computing totals
2. We received an error message during VI jobs when Avalara was enabled

I would not bother to call Avalara until you've downloaded the latest connector from DSD. In each interaction we had with Avalara updating the connector was always the first 10 things suggested.....

And the connector seems to be updated frequently so even if you installed an update yesterday you'll be installing another today during your support call.

All support first goes through Avalara. I did not have especially good luck working with them.

Sage Case#8008269285

Avalara Case# 19822350 

Is this in Sales Order? I had a customer where we had an issue where the Sales Order History totals were not updated properly.

I believe @Brett Zimmerman reported something similar to:

Basically, if the ship-to address on the sales order is invalid, it does not properly write to the S/O History file (e.g. nontaxable and taxable are $0, although freight for example does show) – and the S/O Entry file is fine.

My customer did not have that exact issue. Similar but we could not trace it to an invalid ship-to:

We had a couple of issues:

1. If we did not go to the TOTALS tab during SO Entry then Avalara ( when using AVATAX sales tax code ) was not computing totals
2. We received an error message during VI jobs when Avalara was enabled

I would not bother to call Avalara until you've downloaded the latest connector from DSD. In each interaction we had with Avalara updating the connector was always the first 10 things suggested.....

And the connector seems to be updated frequently so even if you installed an update yesterday you'll be installing another today during your support call.

All support first goes through Avalara. I did not have especially good luck working with them.

Sage Case#8008269285

Avalara Case# 19822350 

Is this in Sales Order? I had a customer where we had an issue where the Sales Order History totals were not updated properly.

I believe @Brett Zimmerman reported something similar to:

Basically, if the ship-to address on the sales order is invalid, it does not properly write to the S/O History file (e.g. nontaxable and taxable are $0, although freight for example does show) – and the S/O Entry file is fine.

My customer did not have that exact issue. Similar but we could not trace it to an invalid ship-to:

We had a couple of issues:

1. If we did not go to the TOTALS tab during SO Entry then Avalara ( when using AVATAX sales tax code ) was not computing totals
2. We received an error message during VI jobs when Avalara was enabled

I would not bother to call Avalara until you've downloaded the latest connector from DSD. In each interaction we had with Avalara updating the connector was always the first 10 things suggested.....

And the connector seems to be updated frequently so even if you installed an update yesterday you'll be installing another today during your support call.

All support first goes through Avalara. I did not have especially good luck working with them.

Sage Case#8008269285

Avalara Case# 19822350 

Is this in Sales Order? I had a customer where we had an issue where the Sales Order History totals were not updated properly.

I believe @Brett Zimmerman reported something similar to:

Basically, if the ship-to address on the sales order is invalid, it does not properly write to the S/O History file (e.g. nontaxable and taxable are $0, although freight for example does show) – and the S/O Entry file is fine.

My customer did not have that exact issue. Similar but we could not trace it to an invalid ship-to:

We had a couple of issues:

1. If we did not go to the TOTALS tab during SO Entry then Avalara ( when using AVATAX sales tax code ) was not computing totals
2. We received an error message during VI jobs when Avalara was enabled

I would not bother to call Avalara until you've downloaded the latest connector from DSD. In each interaction we had with Avalara updating the connector was always the first 10 things suggested.....

And the connector seems to be updated frequently so even if you installed an update yesterday you'll be installing another today during your support call.

All support first goes through Avalara. I did not have especially good luck working with them.

Sage Case#8008269285

Avalara Case# 19822350 

Is this in Sales Order? I had a customer where we had an issue where the Sales Order History totals were not updated properly.

I believe @Brett Zimmerman reported something similar to:

Basically, if the ship-to address on the sales order is invalid, it does not properly write to the S/O History file (e.g. nontaxable and taxable are $0, although freight for example does show) – and the S/O Entry file is fine.

My customer did not have that exact issue. Similar but we could not trace it to an invalid ship-to:

We had a couple of issues:

1. If we did not go to the TOTALS tab during SO Entry then Avalara ( when using AVATAX sales tax code ) was not computing totals
2. We received an error message during VI jobs when Avalara was enabled

I would not bother to call Avalara until you've downloaded the latest connector from DSD. In each interaction we had with Avalara updating the connector was always the first 10 things suggested.....

And the connector seems to be updated frequently so even if you installed an update yesterday you'll be installing another today during your support call.

All support first goes through Avalara. I did not have especially good luck working with them.

Sage Case#8008269285

Avalara Case# 19822350 

Is this in Sales Order? I had a customer where we had an issue where the Sales Order History totals were not updated properly.

I believe @Brett Zimmerman reported something similar to:

Basically, if the ship-to address on the sales order is invalid, it does not properly write to the S/O History file (e.g. nontaxable and taxable are $0, although freight for example does show) – and the S/O Entry file is fine.

My customer did not have that exact issue. Similar but we could not trace it to an invalid ship-to:

We had a couple of issues:

1. If we did not go to the TOTALS tab during SO Entry then Avalara ( when using AVATAX sales tax code ) was not computing totals
2. We received an error message during VI jobs when Avalara was enabled

I would not bother to call Avalara until you've downloaded the latest connector from DSD. In each interaction we had with Avalara updating the connector was always the first 10 things suggested.....

And the connector seems to be updated frequently so even if you installed an update yesterday you'll be installing another today during your support call.

All support first goes through Avalara. I did not have especially good luck working with them.

Sage Case#8008269285

Avalara Case# 19822350 

Is this in Sales Order? I had a customer where we had an issue where the Sales Order History totals were not updated properly.

I believe @Brett Zimmerman reported something similar to:

Basically, if the ship-to address on the sales order is invalid, it does not properly write to the S/O History file (e.g. nontaxable and taxable are $0, although freight for example does show) – and the S/O Entry file is fine.

My customer did not have that exact issue. Similar but we could not trace it to an invalid ship-to:

We had a couple of issues:

1. If we did not go to the TOTALS tab during SO Entry then Avalara ( when using AVATAX sales tax code ) was not computing totals
2. We received an error message during VI jobs when Avalara was enabled

I would not bother to call Avalara until you've downloaded the latest connector from DSD. In each interaction we had with Avalara updating the connector was always the first 10 things suggested.....

And the connector seems to be updated frequently so even if you installed an update yesterday you'll be installing another today during your support call.

All support first goes through Avalara. I did not have especially good luck working with them.

Sage Case#8008269285

Avalara Case# 19822350 

Is this in Sales Order? I had a customer where we had an issue where the Sales Order History totals were not updated properly.

I believe @Brett Zimmerman reported something similar to:

Basically, if the ship-to address on the sales order is invalid, it does not properly write to the S/O History file (e.g. nontaxable and taxable are $0, although freight for example does show) – and the S/O Entry file is fine.

My customer did not have that exact issue. Similar but we could not trace it to an invalid ship-to:

We had a couple of issues:

1. If we did not go to the TOTALS tab during SO Entry then Avalara ( when using AVATAX sales tax code ) was not computing totals
2. We received an error message during VI jobs when Avalara was enabled

I would not bother to call Avalara until you've downloaded the latest connector from DSD. In each interaction we had with Avalara updating the connector was always the first 10 things suggested.....

And the connector seems to be updated frequently so even if you installed an update yesterday you'll be installing another today during your support call.

All support first goes through Avalara. I did not have especially good luck working with them.

Most recent download for v2019

Sage Case#8008269285

Avalara Case# 19822350 

Is this in Sales Order? I had a customer where we had an issue where the Sales Order History totals were not updated properly.

I believe @Brett Zimmerman reported something similar to:

Basically, if the ship-to address on the sales order is invalid, it does not properly write to the S/O History file (e.g. nontaxable and taxable are $0, although freight for example does show) – and the S/O Entry file is fine.

My customer did not have that exact issue. Similar but we could not trace it to an invalid ship-to:

We had a couple of issues:

1. If we did not go to the TOTALS tab during SO Entry then Avalara ( when using AVATAX sales tax code ) was not computing totals
2. We received an error message during VI jobs when Avalara was enabled

I would not bother to call Avalara until you've downloaded the latest connector from DSD. In each interaction we had with Avalara updating the connector was always the first 10 things suggested.....

And the connector seems to be updated frequently so even if you installed an update yesterday you'll be installing another today during your support call.

All support first goes through Avalara. I did not have especially good luck working with them.

Most recent download for v2019

Sage Case#8008269285

Avalara Case# 19822350 

Is this in Sales Order? I had a customer where we had an issue where the Sales Order History totals were not updated properly.

I believe @Brett Zimmerman reported something similar to:

Basically, if the ship-to address on the sales order is invalid, it does not properly write to the S/O History file (e.g. nontaxable and taxable are $0, although freight for example does show) – and the S/O Entry file is fine.

My customer did not have that exact issue. Similar but we could not trace it to an invalid ship-to:

We had a couple of issues:

1. If we did not go to the TOTALS tab during SO Entry then Avalara ( when using AVATAX sales tax code ) was not computing totals
2. We received an error message during VI jobs when Avalara was enabled

I would not bother to call Avalara until you've downloaded the latest connector from DSD. In each interaction we had with Avalara updating the connector was always the first 10 things suggested.....

And the connector seems to be updated frequently so even if you installed an update yesterday you'll be installing another today during your support call.

All support first goes through Avalara. I did not have especially good luck working with them.

Most recent download for v2019

Sage Case#8008269285

Avalara Case# 19822350 

Is this in Sales Order? I had a customer where we had an issue where the Sales Order History totals were not updated properly.

I believe @Brett Zimmerman reported something similar to:

Basically, if the ship-to address on the sales order is invalid, it does not properly write to the S/O History file (e.g. nontaxable and taxable are $0, although freight for example does show) – and the S/O Entry file is fine.

My customer did not have that exact issue. Similar but we could not trace it to an invalid ship-to:

We had a couple of issues:

1. If we did not go to the TOTALS tab during SO Entry then Avalara ( when using AVATAX sales tax code ) was not computing totals
2. We received an error message during VI jobs when Avalara was enabled

I would not bother to call Avalara until you've downloaded the latest connector from DSD. In each interaction we had with Avalara updating the connector was always the first 10 things suggested.....

And the connector seems to be updated frequently so even if you installed an update yesterday you'll be installing another today during your support call.

All support first goes through Avalara. I did not have especially good luck working with them.

Most recent download for v2019

Sage Case#8008269285

Avalara Case# 19822350 

Is this in Sales Order? I had a customer where we had an issue where the Sales Order History totals were not updated properly.

I believe @Brett Zimmerman reported something similar to:

Basically, if the ship-to address on the sales order is invalid, it does not properly write to the S/O History file (e.g. nontaxable and taxable are $0, although freight for example does show) – and the S/O Entry file is fine.

My customer did not have that exact issue. Similar but we could not trace it to an invalid ship-to:

We had a couple of issues:

1. If we did not go to the TOTALS tab during SO Entry then Avalara ( when using AVATAX sales tax code ) was not computing totals
2. We received an error message during VI jobs when Avalara was enabled

I would not bother to call Avalara until you've downloaded the latest connector from DSD. In each interaction we had with Avalara updating the connector was always the first 10 things suggested.....

And the connector seems to be updated frequently so even if you installed an update yesterday you'll be installing another today during your support call.

All support first goes through Avalara. I did not have especially good luck working with them.

Most recent download for v2019

Sage Case#8008269285

Avalara Case# 19822350 

Is this in Sales Order? I had a customer where we had an issue where the Sales Order History totals were not updated properly.

I believe @Brett Zimmerman reported something similar to:

Basically, if the ship-to address on the sales order is invalid, it does not properly write to the S/O History file (e.g. nontaxable and taxable are $0, although freight for example does show) – and the S/O Entry file is fine.

My customer did not have that exact issue. Similar but we could not trace it to an invalid ship-to:

We had a couple of issues:

1. If we did not go to the TOTALS tab during SO Entry then Avalara ( when using AVATAX sales tax code ) was not computing totals
2. We received an error message during VI jobs when Avalara was enabled

I would not bother to call Avalara until you've downloaded the latest connector from DSD. In each interaction we had with Avalara updating the connector was always the first 10 things suggested.....

And the connector seems to be updated frequently so even if you installed an update yesterday you'll be installing another today during your support call.

All support first goes through Avalara. I did not have especially good luck working with them.

Most recent download for v2019

Sage Case#8008269285

Avalara Case# 19822350 

Most recent download for v2019

Sage Case#8008269285

Avalara Case# 19822350 

Is this in Sales Order? I had a customer where we had an issue where the Sales Order History totals were not updated properly.

I believe @Brett Zimmerman reported something similar to:

Basically, if the ship-to address on the sales order is invalid, it does not properly write to the S/O History file (e.g. nontaxable and taxable are $0, although freight for example does show) – and the S/O Entry file is fine.

My customer did not have that exact issue. Similar but we could not trace it to an invalid ship-to:

We had a couple of issues:

1. If we did not go to the TOTALS tab during SO Entry then Avalara ( when using AVATAX sales tax code ) was not computing totals
2. We received an error message during VI jobs when Avalara was enabled

I would not bother to call Avalara until you've downloaded the latest connector from DSD. In each interaction we had with Avalara updating the connector was always the first 10 things suggested.....

And the connector seems to be updated frequently so even if you installed an update yesterday you'll be installing another today during your support call.

All support first goes through Avalara. I did not have especially good luck working with them.

Most recent download for v2019

Sage Case#8008269285

Avalara Case# 19822350 

Is this in Sales Order? I had a customer where we had an issue where the Sales Order History totals were not updated properly.

I believe @Brett Zimmerman reported something similar to:

Basically, if the ship-to address on the sales order is invalid, it does not properly write to the S/O History file (e.g. nontaxable and taxable are $0, although freight for example does show) – and the S/O Entry file is fine.

My customer did not have that exact issue. Similar but we could not trace it to an invalid ship-to:

We had a couple of issues:

1. If we did not go to the TOTALS tab during SO Entry then Avalara ( when using AVATAX sales tax code ) was not computing totals
2. We received an error message during VI jobs when Avalara was enabled

I would not bother to call Avalara until you've downloaded the latest connector from DSD. In each interaction we had with Avalara updating the connector was always the first 10 things suggested.....

And the connector seems to be updated frequently so even if you installed an update yesterday you'll be installing another today during your support call.

All support first goes through Avalara. I did not have especially good luck working with them.

Most recent download for v2019

Sage Case#8008269285

Avalara Case# 19822350 

Is this in Sales Order? I had a customer where we had an issue where the Sales Order History totals were not updated properly.

I believe @Brett Zimmerman reported something similar to:

Basically, if the ship-to address on the sales order is invalid, it does not properly write to the S/O History file (e.g. nontaxable and taxable are $0, although freight for example does show) – and the S/O Entry file is fine.

My customer did not have that exact issue. Similar but we could not trace it to an invalid ship-to:

We had a couple of issues:

1. If we did not go to the TOTALS tab during SO Entry then Avalara ( when using AVATAX sales tax code ) was not computing totals
2. We received an error message during VI jobs when Avalara was enabled

I would not bother to call Avalara until you've downloaded the latest connector from DSD. In each interaction we had with Avalara updating the connector was always the first 10 things suggested.....

And the connector seems to be updated frequently so even if you installed an update yesterday you'll be installing another today during your support call.

All support first goes through Avalara. I did not have especially good luck working with them.