Sage 100

Customer on Sage 100 Advanced 2014.06 having an issue with Avalara where they are having to ""commit"" each invoice in their system manually. Avalara support is pointing fingers at a Sage bug. Has anyone else run into this?

@PhilMcIntosh I have seen reports on this but I have seen problems where Avatax returns 31 characters per line when customer addresses are updated and confirmed. This in turn causes problems with another 3rd party app. Just a heads up. I have a couple Sage 100 customers on Avatax. I will check to see if they are having challenges but I pretty sure they are all on v 2015.

Did avalara have any more detailed info other than ""sage bug"" ? the nature of the sage bug etc.

Still waiting to hear back from Avalara - anyone have a direct number for anyone that cares at Avalara? (If there is such a person)

It's been a couple of years, not sure if he is still there but was helpful in resolving a case that nobody wanted to take responsibility for. Richard Johnson | Support Engineer Office: (877) 780-4848 richard.johnson@avalara.com

One of my guys, Brandon Cumby, recently worked with a tech at Avalara. I can't vouch for his depth of knowledge but it was with Sage 100. Lars White | Support Engineer Office: (877) 780-4848 x 2 support@avalara.com

@BrandonCumby - Good hire!!!

He said he was your proxy @ShawnSlavin and I must say, he did an excellent job. It was a pleasure getting to know him.

Finally heard back from Avalara support that they are reading the invoices (created via Shipping Data Entry) as SALES ORDER, not SALES INVOICE. Avalara support person does not know what field they are reading in Sage 100 to determine this (back to dev for answer). Anyone else seen this or know what field I should look at?

I can second reaching out to Richard Johnson, he fixed our client's issue with Avalara as well.