Skip to main content
Avalara Help Center

Avalara AvaTax for Salesforce Sales Cloud Release Notes

This article applies to:AvaTax for Salesforce Sales Cloud

Read the release notes to learn about the latest additions, changes, and fixes to AvaTax for Salesforce Sales Cloud.

AvaTax for Salesforce Sales Cloud (2020 releases)

July 10, 2020

Release 4.0  

Before you upgrade to this version from an earlier version, make sure you have Avalara AvaTax Salesforce Mapper 1.60 or later.

New

  • Salesforce Sales Cloud now integrates directly with CertCapture and Exemptions, letting you manage customer exemption records and certificates from within Salesforce Sales Cloud
  • The Order object now has a separate field for shipping and handling charges, as well as a field for shipping and handling tax that calculates based on it
  • The AvaTax Mapper now integrates with Workbench, making it easier to integrate custom objects

Changed

January 9, 2020

Release 3.0  

New

  • GST and PST rates now display separately for Canadian transactions
  • You can now validate header-level origin addresses
  • You can now validate line-level ship-to addresses
  • You can now configure entity/use codes at the line level
  • You can now configure the origin address at the header level on opportunities, quotes, and orders
  • You can now configure ship-to addresses at the line level
  • You can now validate addresses in bulk
  • The tax code field now checks the Avalara service before displaying tax code values
  • You can now update Avalara tax codes on products in bulk
  • You can now validate subsidiary addresses

Changed

Fixed

  • Fixed an issue with automatic tax calculation workflows on the Opportunity, Quote, and Order objects
  • Fixed an issue with Process Builder not triggering the commit tax feature

AvaTax for Salesforce Sales Cloud (2019 releases)

June 7, 2019

Release 2.0  

New

  • The AvaTax Mapper now has a graphic user interface
  • Added multi-entity configuration capabilities
  • AvaTax triggers can now be disabled through the AvaTax bundle configuration

Changed

Fixed

  • Fixed the issue that prevented the company address from validating when credentials weren't saved

March 1, 2019

Release 1.0  

New

  • Salesforce Sales Cloud consolidates and replaces Opportunities, Orders, and Quotes. Current users should upgrade to this version and migrate their data to continue to receive new features.

Changed

  • The custom AvaTax fields in Salesforce Sales Cloud now clear when you clone a transaction
  • The transaction now shows as voided in AvaTax when you delete it
  • Opportunities and Quotes no longer post to AvaTax as committed transactions
  • If a shipping address is not present on an order, AvaTax uses the billing address to calculate taxes
  • If the shipping address is blank on the customer account associated with an order, AvaTax uses the billing address to calculate taxes
  • You can now select Commit Tax to commit orders to AvaTax
  • You can now override tax amounts on the line level
  • You can now enter the business identification number and the importer of record on individual transactions and the customer account for VAT calculations
  • Authentication, transaction committing, and address validation settings are now all on the same settings tab
  • You can now override an entity/use code on a transaction
  • System integration document

AvaTax for Salesforce Sales Cloud Opportunities

This integration package is in "sustaining" mode. This means there are no new versions planned, and current versions won't be enhanced. Any issues identified will only be fixed on an as-needed basis.

August 8, 2018

Release 5.27.0.0 

New

  • Added a custom setting to disable trigger

Changed

  • Moved "Use Billing address for Tax Calc" to Tax calculation section on configuration page
  • Removed deprecated fields from configuration page

Fixed

  • Fixed an issue where currency in Salesforce (Opportunity/Quote/Order) did not match with currency in AvaTax
  • Deprecated 'Create Company' page from the package
  • Fixed an issue where Line Number in AvaTax document was starting at 0 instead of 1

 

  • Was this article helpful?