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:
The Document Generation Wizard now is capable to process draft documents and create “real” documents.
When selecting the new Draft Document checkbox as the base type, the base documents will be the same type as the target type, for example base draft AR Invoices to create Invoices.
Fix to set calculated tax rate to Line UDF when multiple lines with the same ItemCode are in the document. Only affecting to Line and AdditionalExpense tax mode.
Fix to recalculate tax on some draft documents. For ExternalTax calculation mode.
The Avatax add-on, the Avatax webUI and the Avatax EventService are now compatible with SAP B1 database companies using the United Kingdom/Ireland localization.
This localization uses Sales VatGroups instead of Sales TaxCodes. The solution is able to identify this and switch the behavior based on the company localization.
Taxes can be set to the document as a Line Item or as an Additional Expense.
The Avatax configuration settings looks identical for the user.
Minor fixes included for some HANA filtering in Bulk Address Validation.
Fix for Return Request ShipTo selection error.
Fix for validating draft calculated taxes for return documents.
Document lines with negative total are now supported for tax calculation.
SAP let use some sales documents with negative totals, by setting the quantity to a negative value, the unit price as a positive value, and the total as negative.
Avatax now calculates taxes over that lines, and returns the tax calculated as negative.
You can mix negative and positive document lines in a single document without issues: