Usage Type on Customer Order
Starting with v908.2400, users will be able to set the Usage type on a per Customer Order basis. This will take precedence over any usage type(s) that may be set on a Customer (or it’s alternate shipping address if one is being used).
In Customer Order Entry, there will be a new tab labeled “Avalara”. Within that tab, will be a drop down labeled “Usage Type” in which users can select the reason for the exemption on customer orders.
Once selected and saved, this code will be sent over to Avalara as it’s usage type for the order, shipment, and invoice.
Please note that this field is editable to give users the ability to “clear” this selection if they selected a type in error. As a result, invalid entries can also be placed in here. However, if the invalid entry is not recognized by Avalara, the usage type will be ignored and the order, shipment, and invoice will be taxed accordingly.
Related Articles
Order Import Tool - User Guide
Administration Installing Use the following link to download the setup file. Once downloaded follow these steps to install. Install using Run As Administrator Run OrderImportSetup.exe Click Next Select your version of Visual; Single Site = VM 7.0 or ...Order Import Tool - Release Notes
2025.03.05 Version v1100.1003 - When getting customer orders whose customer id came from the customergroup table the data was not being pulled properly this is now fixed. - Update support libraries to current version. 2025.01.07 Version v1000.1002 - ...Copied Order shows original lines in SRI_TaxOrderLine
An order was copied with lines \ Order Lines removed and Tax recalculated Here No Tax and no Total which is correct But the SRI_TaxOrderLine table still has records from when the order was copied this will be resolved in the REST update to Synergy ...Open Purchase Order - Missing POs without any lines
If you find in the View included with SmartViews called "Open Purchase Order" that you are not seeing Purchase Orders with no line-level Desired Recv Dates, this can be resolved by replacing the highlighted instance of PURC_ORDER_LINE with ...XML Error when running the Order Total w/ Tax macro for Colorado orders (possibly other states)
Issue: When taxing orders in Colorado, you may receive the following error due to a Tax Name containing an ampersand (&): Cause: This issue occurs because XML does not allow unescaped ampersands. If a tax name includes an &, it must be correctly ...