Configuration

A. Avalara Integration Settings:

        To configure this, follow the steps below:

        

B. Mapping Price Code for each Charge:

        The BluSynergy “Charges” are mapped to Avalara “Items” which can then be mapped to Avalara “Tax Codes”. The  former mapping is performed inside BluSynergy, whereas the latter mapping is performed inside Avalara. The following  table depicts a sample configuration for a web hosting enterprise that offers an annual and monthly Plan. This example  depicts how revenue for monthly storage changes (STOR) may be tracked separately from the revenue for annual storage  (STOR-PREPAID), even though they map to the same Tax code. 

             

    

            Specifically, the “Price Code” field of each Charge in BluSynergy maps to Avalara’s “Item Code” field for each Item.  Each Item has an     associated “Tax Code” field.

        

                  Let’s see the Price codes present in “Avalara product”. To do this follow below steps:

                  

                 Now let’s check this in BluSynergy,Follow the steps:

        

Fig B.1.7

                

C. Tax Exempt Customers:

         We can exempt a Customer from paying Tax for certain criteria. This can be done by selecting the “Tax types” to be  exempted in the Customer settings

              Tax Exempt types: These are loaded from the Tax configuration. To make use of this for a Customer, follow the  steps

Fig C.1.1

Fig C.1.2

Fig C.1.3