Details

      Description

      Background

      We need to add a field to the account object that will allow administrators to set the exemption code for their customer. This exemption code will be used to determine their tax liability for the orders that the customer places.

      Updated Requirements

      1. We need a mapping interface where a back office user can set define the entity use code for each account.
      2. In doing so, they are essentially making a relationship between the entity/use code and an account
      3. Same as before, an account can have exactly one entity/use code
      4. Same as before, an entity/use code can be related to more than one account
      5. Look at the list of OOTB codes that Avalara provides to get a sense for how long these codes are (see linked documentation)
      6. Note that Avalara customers can also create custom codes and add them to their list in Avalara. Our connector will auto-sync those custom codes to Liferay Commerce and make them available in the list.

      Old Requirements

      1. The list of codes that populates the list of available codes to choose from will be automatically populated by the connector.
      2. The user can choose up to one code for any given account. They cannot select multiple codes. They can leave this field blank.
      3. Look at the list of OOTB codes that Avalara provides to get a sense for how long these codes are (see linked documentation)
      4. Note that Avalara customers can also create custom codes and add them to their list in Avalara. Our connector will auto-sync those custom codes to Liferay Commerce and make them available in the list.
      5. Needs to be designed for both the account UI that we plan to have and the account UI that we have today

      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.

      Our customers will need to create the custom codes on the avatax site (if they choose to use custom codes).
      We will just need to grab and display the results using ListEntityUserCodes API

      - Liferay Commerce - Avalara Connector Planning Spreadsheet

      Resources

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              andrea.censi Andrea Censi
              Reporter:
              corbin.murakami Corbin Murakami
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Packages

                  Version Package