Avalara announced in this post an update in their REST v2 API security, that is the API used by the AvaTax connector for SAP Business One.
TLS (Transport Layer Security) protocol is used to access Avalara and consume the API for calculations. Avalara announced that using TLS version 1.2 or superior will be mandatory starting 2022, stopping support for older versions.
For Sandbox accounts since Feb 1, 2022.
Changes
Markup percentage for tax calculation on Drop Shipments
Based on customer requirements a new feature is included in the solution. The option to configure a markup percentage over the document lines when the sale is a drop ship in a specific ship-to state.
For example in the state of California, it’s required to calculate the taxes based on the sale taxable amount plus 10%. Meaning the resulting tax amount for the document will be calculated based on the document total plus 10%, while the document total before tax will remain the same in SAP.
Tax calculation on AR/Down Payments Invoice
Tax calculation in AR/Down Payments was possible, but you could usually expect the calculated tax to be zero, because the Tax Liable value for any line is fixed to No in SAP Business One.
This produces the line to be sent as Not Liable to AvaTax, resulting usually in an exempt line, without calculated tax.
Now we have included a configuration setting to ignore this field, send the lines as liable, and get the tax calculated as if the lines are liable.
Discount on freight lines
Until now, when sending freight lines as line items to AvaTax, by default the lines were considered to apply discounts.
This means when applying a document header level discount in SAP, the discount is distributed by AvaTax on all document lines that have the discounted flag.
Now there is a new setting to control if the freight lines are discounted or not. Disabling this settings will make the SAP document header discount not applied by AvaTax to the freight lines.
Starting version 21.11.03, the AvaTax add-on includes support for VAT calculation for European countries, and using European SAP B1 Company Localizations.
The AvaTax add-on is now compliant with the AvaTax API enhancements, detailed here.
AvaTax settings was updated. You need to re-select all of your freights configurations in the settings despite the tax calculation mode you are using.
Improvements for Service Layer calculation with DGW.
Support to use same SAP Tax Jurisdiction for different Avatax Jurisdictions.
Support for empty or removed Bill To in document
In previous versions reconcile will raise an error like Post failed: BillTo Bemidji – Minnesota not found for BP Code 17379 if the Bill To used in the document is modified or deleted at BP Master Data Address records.
Support for items with quotes in the ItemCode
For example ItemCode EZP-EL-18-10′-W
AvaTax Location code and empty Ship-To address
Due to known performance issues with SAP v10 when using DI-API, we implemented a new interface for using the SAP Service Layer API within the AvaTax solution for complex processes.
On this version, the External Calculation mode now supports working through Service Layer. The expected result is the same as before, but the time required to complete the process is substantially lower.