Release 21.04.09

DGW. Base document closing option

A new option is included in the Document Generation Wizard, to choose if want the wizard to close the base document after generating the new one, or not.

Default DGW behavior was to force SAP to close the base document (manual close) after generating the new document. This is usually required for customers using the tax calculated as Freight, customers processing partial invoicing, who needs to make sure the base document is closed after generating a new document, no matter if open lines or freights remains in the base document.

Release 21.03.15

Custom mileage tax calculation

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

Release 20.12.28

Upgrade to Avatax REST API connector v20.12.1

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.

Release 20.12.14

ShipEasy Integration features

Add-On

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.

Release 20.10.19

Send transaction reference

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.