Avalara Developer Network Developer avaTax

Chapter 8 - Summary

Because you have read this chapter, you should now know:

  • All the factors that could cause tax on a transaction to be zero
  • Which factors are company-related, which are product-related, and which are transaction-related
  • How to allow a customer to choose these factors correctly in your user interface
  • Customer Code - Identify customer code (number, ID) to pass to the AvaTax service. Typically this is an account name, customer name, or email address on file for the customer.
  • Customer Creation - Creation of an exempt customer record triggers the creation of a customer record in CertCapture.
  • Customer Updates - When exempt customer records are updated in the application, those same updates are applied to the customer record in CertCapture.
  • Request new Certificate - As exemption certificates expire, a function to send the customer a request for a new exemption certificate is required.
  • Retrieve Customer Exemption Status - Retrieve and display exemption certificate information associated with a customer record.
  • View Exemption Certificate - View an exemption certificate associated with customer record.
  • Exemption Number - Customer record field populating exemption number in an AvaTax transaction. This is used for tracking those customers who have tax exempt transactions.
  • Entity/Use Code - This is a group of codes that indicate the type of exemption. See the standard codes, but be aware that users are able to create custom codes as well.It is best to manage this value in your application’s Customer record and pass it to AvaTax as CustomerUsageType at either the document or line level, whichever is applicable. Note that either Exemption Number or Entity/Use code is required (not both). Entity/Use Code is preferred.

Test cases that must be understood to correctly handle tax exemptions, including testing for: