New feature included in the solution to have a special mileage tax calculated by the add-on in SAP, not by Avalara.
This tax has to be calculated on a specific state (i.e. California), and must apply over Items with a matching value in a customizable UDF.
The calculated tax is not calculated by Avalara. It’s calculated in the SAP side, and is added to the document as an Item Line, for all of the calculations modes.
Configuration
CertCapture. Fix for customers creating or updating module.
DGW. Improved consolidation logic and document discount calculation.
Included changes for DI behavior on drafts on SAP 10.
No visual or user behavior has changed.
This release includes a new feature regarding the ShipEasy integration.
A new setting was added:
Upgraded all component of the solution: Avatax Add-on, Avatax Event Service and Avatax webUI app to use the latest available Avatax REST API connector version (v20.12.1).
This let’s the SAP B1 solution components support the latest available functionalities and calculation responses returned from Avatax.
New functionalities were added to ShipEasy integration logic. This behavior applies when creating new documents using the Document Generation Wizard.
When Add ShipEasy Expense Amount as a Freight is enabled, the value setted in the base document header UDF U_TWBS_UPSExpense is copied to the target document, and set to the selected Freight for ShipEasy expense amount additional expense.
Performance improvements focused on external calculation mode on documents with several lines and draft documents.
A new customization is available to user a Sales Document Header field value, SAP native or UDF, as a Reference when sending the document to Avalara.
The value is sent in the Reference field of the Avalara transaction, and it’s visible from the Avalara web console.
If you intend to use this feature, you must check the box to enable it, and complete the marketing document field name you intend to use.
As requested by Avalara, the connector is updated to NOT send by default address geo coordinates: latitude and longitude in tax calculations.
This is due to the Streamlines Sales Tax (SST) functionalities implemented by Avalara, that require not including geo coordinates in regular tax calculations, and only request calculations using street level information.
It is now possible to use any of the Business Partner Master Data User Defined Field value as the Avalara Customer Code for tax transactions.
The field can be selected from the Avatax Settings: