Avalara - Use Codes

Avalara - Use Codes

Release Date: 4/28/23
Updated: 1/23/24
Version: 8.6 and Above

Use codes are used to determine why a customer is exempt from taxes. Use codes can be assigned at the customer type, customer, ship-to, and order levels. When determining the use code for an order, a hierarchy will be applied. If the order contains a ship-to and a use code has been assigned to the ship-to, the use code will be assigned to the order when taxes are calculated. If no ship-to use code has been assigned or the user is not using a ship-to, the application will check for a customer use code. If the use code does not exist, the application will check for a customer type use code. The use code can also be manually defined at the order header level.


Use codes are attached to customers, customer types, and ship-to codes via the _USECODE attribute.

For example, if customer  "002035" is non-taxable, you can assign an exemption reason to the customer that is different from the code defined in the Avalara Global Setup Default Cust Exempt Use Code. Bring up the customer in Change mode Accounts Receivable-> Maintenance-> Customer File Maintenance and click on the Attribute button. The user would then click on new, choose the _USECODE attribute, and click OK.



Once the screen is displayed, the user would click on the search button.



The user would then search to find the appropriate use code. 



Choose the correct use code and click on OK or press Enter to return the value.



Click on OK to save the attribute.

Whenever an order is entered for this customer in Order Entry without a ship-to specified, the use code will be passed to Avalara and the reason will be recorded. 

In summary, the purpose of the _USECODE attribute is to determine the nature of tax exemption. For taxable customers, we do not recommend adding the _USECODE to the customer or ship-to. Instead, use the taxable flags for the customer or ship-to and set them to "Y". However, if you set the customer or ship-to taxable flag to "N", we recommend adding the _USECODE so that Avalara can determine the nature of their tax exemption. See the following KB article: 


CLS




    • Related Articles

    • The Relationship of Taxable Flag and _USECODE Attribute for Avalara

      Release Date: 06/21/2023 Last Revised: 04/25/2025 Version: 8.6 & Up Q - What is the relationship of customer, ship-to and order taxable flags vs. the _USECODE? Does the system calculate sales tax based on _USECODE or taxable flag? How is this related ...

    • Avalara Attribute Support

      Release Date: 4/28/23 Updated: 4/25/25 Version: 8.6 and Above For Elliott to work with the Avalara Sales Tax Interface, there are additional data to be stored on the Elliott side. Our implementation chooses to store these data in the following ...

    • Avalara - Attribute Enhancement File Maintenance

      Release Date: 4/28/23 Version: 8.6 and Above This feature adds AVUSECDE (Avalara Use Code) and AVGDSRVC (Avalara Tax Code) as files to the Master File list in Attribute Enhancement File Maintenance. This allows the _USECODE and _GOODSERVICES ...

    • Avalara: Documentation Roadmap

      Release Date: 4/28/23 Updated: 4/29/25 Version: 8.6 and Above Introduction Elliott Business Software previously supports Vertex for national sales tax collection. Starting Elliott V8.6, we are favoring Avalara over Vertex. Existing Vertex users ...

    • Avalara Setup Procedures - Integrity Check

      Release Date: 4/28/23 Date Revised: 6/10/24 Version: 8.6 and Above You should run Avalara integrity check on daily, weekly or monthly basis. The frequency depends on if you can commit resources for someone to look at the output of this report and ...