Skip to main content
Avalara Help Center

Avalara AvaTax Update for Microsoft Dynamics 365 for Sales Release Notes

Read the release notes to learn about the latest additions, changes, and fixes to AvaTax Update for Microsoft Dynamics 365 for Sales.

AvaTax Update for Microsoft Dynamics 365 for Sales (2019 releases)

June 21, 2019

Version 9.1, release 9.4.0.0v2  [Release notes from development]

New

  • You can now validate the bill-to address on a transaction.
  • You can now use latitude and longitude coordinates for tax calculation. 
  • You can now use the ship to address on the line level for tax calculation.
  • AvaTax Update now uses the account name as the customer code when the account number is blank.

Changed

Fixed

  • Fixed the issue that caused the "Error calculating tax'"message to display during successful tax calculations.

March 1, 2019

Version 9.0, Service Update 4, release 9.3.0.0v2  [Release notes from development]

New

  • AvaTax Update for Microsoft Dynamics 365 for Sales is now compatible with the new user interface for Microsoft Dynamics 365 for Sales Hub.
  • AvaTax Update is now compatible with Microsoft Dynamics 365 for Sales version 1710 (9.1.000.0299).

Changed

  • The AvaTax Update company code is now blank by default when you validate credentials within AvaTax Update configuration settings.
  • The AvaTax Update company code is now fetched from AvaTax Update during configuration.
  • System integration document

AvaTax Update for Microsoft Dynamics 365 for Sales (2018 releases)

November 23, 2018

Version 9.0, Service Update 4, release 9.2.0.0  [Release notes from development]

New

  • You can now perform tax calculations for write-in products.
  • You can now calculate VAT. Customization features allow you to:
    • Store invoice messages on VAT transactions.
    • Assign a Business Identification Number to a customer to allow reverse charge VAT calculation.
  • You can now select a default Avalara tax code for shipping charges during AvaTax Update configuration.
  • You can now configure a default origin address in AvaTax Update configuration.
  • You can now validate addresses on the account entity.
  • You can now enable or disable AvaTax Update address validation in AvaTax Update configuration.
  • AvaTax Update for Microsoft Dynamics 365 for Sales now uses the AvaTax Update Rest v2 API.
  • The currency code is now passed to AvaTax Update.

Changed

  • Removed the Taxable checkbox from the product entity because it's no longer necessary to select it to assign a tax code.
  • Replaced the Customer Type list with the Entity/Use Code ID list, which you can use to:
    • Select an entity/use code on the account entity.
    • Change or assign an entity/use code on the transaction entity.
    • Make custom entity/use codes.
  • Simplified the AvaTax Update Enable Logging configuration option to a checkbox.
  • Simplified the AvaTax Update Commit to AvaTax configuration option to a list.
  • You now set an account as sandbox or production by selecting a checkbox instead of entering a URL.
  • You now select the company code during configuration from a list instead of typing the code.
  • AvaTax Update now uses the default origin address as the ship-to address for will call transactions.
  • System integration document

Fixed

  • Fixed the issue that caused the "Business Process Error" message to display when calculating tax with no products selected on the transaction.
  • Fixed the issue that caused the "Business Process Error" message to display  when disabling tax calculation.
  • Fixed the issues that caused the "The specified domain does not exist or cannot be contacted" error when selecting Invoice Paid on sales invoices.

April 13, 2018

Version 9.0, Service Update 4, release 9.1.0.0  [Release notes from development]

New

  • Avalara AvaTax solution package for Microsoft Dynamics 365 for Sales is now available
  • Shipping origin is now pulled automatically from the customer/prospect record
  • Addresses can now be validated and updated on entity records

Changed

  • Country name instead of country code is now used for address validation
  • The naming convention for exemptions was changed to "Entity Use Code" from "Tax Code" in the account entity
  • You can now map to entity use "M" for educational organizations and entity use code "F" for religious organizations

Fixed

  • Corrected the date format for tax overrides
  • Fixed the issue that required the customer address and ship-to address to match in order for an exemption to be applied
  • Fixed the issue to pass product name instead of GUID's in the AvaTax Update log

January 16, 2018

Version 9.0, Service Update 4, release 9.0.1.0  [Release notes from development]

New

  • AvaTax Update is now compatible with Microsoft Dynamics 365 for Sales

Changed