This error message is also causing invoice to fail upon VI imports. All the Canada orders just failed for my same client. Avalara gave them the same message about being able to move past it, but its not true. This just fails these records & even if they key it in, it will not let them update them until I fix it in DFDM.
"Thank you kindly for being patient as we worked to resolve this unexpected VAT threshold prompt issue in Sage.
We have received an update from our Software Bundle Development teams at Avalara that they are working with urgency to build the solution and are targeting 9/27 to deploy a fix that will resolve this prompt.
For now they have confirmed this prompt should only be a WARNING and NOT blocking any transactional data from processing.
You should be able to simply select "ok" and proceed with processing or saving the transaction.
If you are noticing the error is blocking you from processing transactional data in any way, please kindly let us know on here and we will let our Dev teams know with the highest urgency immediately.
We will report back as soon as we hear findings and next steps from our software engineering teams.
Thank you,
Joseph OBrien | Customer Success
Office: (877) 780-4848"
------------------------------
Dana Young
Lehman Wesley & Associates
Lansing MI
------------------------------
Original Message:
Sent: 09-13-2021 12:13
From: Dana Young
Subject: Avalara issue
I also have a client getting this, they are on v2019 Premium. No upgrade or change; it just started 2 weeks ago. I also did the DFDM fix for them on the InvlaidTaxCalc field to retain the actual country data on the invoice & get it to post. They need the records to reflect correctly for history reports on sales per country/state, so just switching back to USA is not a proper fix or workaround. I had reported it to DSD & my client was opening a ticket with Avalara as well.
------------------------------
Dana Young
Lehman Wesley & Associates
Lansing MI
------------------------------
Original Message:
Sent: 09-11-2021 08:23
From: Wayne Schulz
Subject: Avalara issue
If you know:
1. Is this specific to certain Sage versions?
2. Does it only apply to updated connectors or is this something that is occurring on Avalara's side and therefore could impact any Avalara users
3. Is there anything else that has to be done after either of the mentioned workarounds ( corrections to GL or tax reporting, etc ?)
---------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990