The AvaTax Configuration Dialog Window must allow the user to specify the configuration/connection information

• Account Number
• License Key
• Environment (Sandbox/Production)
• Company Code Lookup

Test the connection to the AvaTax service and verify the AvaTax credentials. This is an important element to allow for successful troubleshooting of the AvaTax Service.

In order for this connector to be used in conjunction with other integrations to AvaTax, the user must be able to control which connector is used for recording documents to AvaTax. From a technical standpoint, simply use DocType: 'SalesOrder' on all calls and suppress any non-tax calculation calls (i.e. CommitTransaction, VoidTransaction).

The user must have an option to turn on or off the AvaTax Calculation service independent of any other Avalara product or service.

Enables detailed AvaTax transaction logging within the application including capture of round-trip processing time. We need the complete request/response for each call made to Avalara services. It does not need to run all the time as we understand the database will grow unnecessarily large – you are free to only log the last week, 30 days, custom, or have a control for the next N hours, etc. The spirit of the requirement is to assist customers and support in troubleshooting exercises, so it needs to be retrievable by an end user (or an administrator). It should be specifically Avalara service calls.

Define a timeout value for AvaTax requests.

Enable the tax inclusive flag in the tax calculation request.

When set to true: pass in UPC code into the Avalara ItemCode on the line level of the requests to our service. When UPC is unavailable, default to ItemCode. When set to false: use the default ItemCode mapping. See Product Master Management for more details.

Alternately, UPC can be enabled on the item level.

The User Implementation Guide should contain screenshots and information allowing the end user to configure for AvaTax including where the company code is entered, where the credentials are entered, where customer data is entered, and where tax codes can be mapped within the application. Click Here for a user guide template.

An Address Validation utility is present in the application.

Identify the customerCode value (number, ID) to pass to the AvaTax service.

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 entityUseCode at either the document or line level, whichever is applicable.

BevAlc customers are most likely to use “G - resale” if they are wholesalers and tax is not collected at the Supplier → WS level.

Customer record field populating exemption number in an AvaTax transaction. This is used for tracking those customers who have tax exempt transactions.

Ability to identify individual items on a transaction as exempt from tax.

Ability to identify individual items on a transaction as Taxable to an otherwise exempt customer. Functionally, you will need to pass the value 'Taxable' in the entityUseCode field at the line level.

Ability to individually identify customer, ship-to locations as Exempt, separate from the customers default address.

Represents the first and last name of purchaser associated with the transaction

The date of birth (DOB) associated with the "Bill To" recipient. Must be formatted as YYYY-MM-DD

Represents the first and last name of the recipient associated with the transaction

The date of birth (DOB) associated with the "Ship To" recipient. Must be formatted as YYYY-MM-DD

Street address of the purchaser associated with the transaction

Parameter Name: PurchaserStreetAddress

City of the purchaser associated with the transaction

Parameter Name: PurchaserToCity

State of the purchaser associated with the transaction

Parameter Name: PurchaserToState

ZIP of the purchaser associated with the transaction

Parameter Name: PurchaserToZip

Values that can come across to AvaTax as the docCode

Values that can come across to AvaTax as the docCode

Value comes across to AvaTax as the docDate

Value that comes across to AvaTax as the taxCalculationDate

Integrations must send docType values corresponding to the stages of the transaction life cycle

Value that is sent to AvaTax for Destination Address at the header level.

Value that is sent to AvaTax for Origin Address at the header level.

Value that is sent to AvaTax for PoA at the header level

Value that is sent to AvaTax for PoO at the header level.

Area at Invoice screen where end user can check box to override existing Tax Exemption for the client.

Value that is sent to AvaTax for locationCode at the header level

If the application supports multiple 'origin' addresses, locationCode must be passed with the transactions.

Value that is sent to AvaTax for exemptionNo

Required if Entity Use Code exemption functionality is not present

Value that is sent to AvaTax for the line number

Value that is sent to AvaTax for the itemCode

Value that is sent to AvaTax for the itemDescription

Value that is sent to AvaTax for the quantity

Value that is sent to AvaTax for the amount

Value that is sent to AvaTax for the Tax Code

Value that is sent to AvaTax for Destination Address at the line level.

Required if destination (shipTo) address can be managed at the item line level

Value that is sent to AvaTax for Origin Address at the line level.

Required if origin (shipFrom) address can be managed at the item line level

Value that is sent to AvaTax for PoA at the line level

Required if Point of Order Acceptance address can be managed at the item line level

Value that is sent to AvaTax for PoO at the line level.

Required if Point of Order Origin address can be managed at the item line level

Confirm that the integration is taking the Tax Amount value from the tax calculation response and using that to decorate the tax fields in the platform. Do NOT take our rate and use it to calculate the tax within the platform itself

Freight items must be sent to AvaTax as a separate line item with a configurable tax code

Ensure that invoices are processed through a logical document lifecycle

Ensure that invoices are committed/posted for reporting appropriately

When invoices are deleted/canceled, this information must be transmitted to AvaTax

If the source application supports void/delete, then the corresponding transaction on AvaTax must be updated with the current transaction status

Standard discounts included in line-level extended amount, manufacturer’s coupons and hostess credits transmitted as additional line items

Value sent to AvaTax as the purchaseOrderNo

Value sent to AvaTax for the entityUseCode at the line level

Line level exempt triggers are required if line-level exemption can be managed in the application, and should be transmitted in a manner analogous to document-level exemption

If host application captures GPS coordinates with Addresses; for US addresses, pass the Lat and Long along with address. This is especially useful in situations where a location or service site can only be pinpointed by geo location

Used to calculate taxes based on InStateDirectShipper or OutOfStateDirectShipper

We have Tax calc rules setup in Content Central where some tax rates might change if a company has claimed they are an In-state vs out-of-state shipper. (Most of our rules include both.)

Tracking number associated with a direct alcohol shipment. When multiple tracking numbers apply to a shipment, they must be separated by a semicolon (;)

Most of the time, this information is not available at the time of transaction creation, so when the product ships, the tracking number needs to be updated so the returns team can properly file returns.

Used to indicate whether a beverage alcohol product is a direct import product (directAlcoholImport)

Used to indicate the sales channel for a beverage alcohol transaction

Possible values: 3T, DTC, DTT, Pickup

DTC = Direct to consumer

3T = wholesaler

DTT = Direct to Trade

Pick up = customer pickup

The day merchandise associated with an order was shipped. Must be formatted as YYYY-MM-DD. Will default to transaction date (docDate value)

Most of the time, this information is not available at the time of transaction creation, so when the product ships, the ship date needs to be updated so the returns team can properly file returns.

Distinguishes orders that were placed onsite at a business’s location vs. offsite

Possible values: onsite, offsite. Will default to offsite

Default = offsite

Carrier code of shipment (EX, FFO, FXG, FEH, FXP, FXO, FXE, FEXA, FHA, FHD, FHE, FEXCC, GSC, GSP, GSN, GES, GSS, GPC, GPA, UP1, UP2, UP2A, UP3, UPA, UPS, UPSA, UWE, UWED, UWEP)

Most of the time, this information is not available at the time of transaction creation, so when the product ships, the carrier code needs to be updated so the returns team can properly file returns.

Name of fulfilment house (WineDirect, CopperPeakLogistics, WineServicesCoop, WineCareLogistics, WineCountryShipping, WineCountryConnect, Vinfillment, WineCountyPackAndShip, Wineshipping)

Connectors need to be able to send this information so it can be used to filed returns, but it might not be applicable to the winery if they do not use a fulfillment warehouse to store/ship their product.

For wine only, to indicate what varietal the product is classified (chardonnay)

Identify the itemCode value (number, ID) to pass to the AvaTax service.

Identify item/service/charge description to pass to the AvaTax service with a human-readable description or item name.

Association of an item to an AvaTax Tax Code to describe the taxability (e.g. Clothing-Shirts – B-to-C)

Association of a GROUP of items to an AvaTax Tax Code to describe the taxability of the group.

Pull in and surface Avalara Tax Codes within application.

See note in Administration/Utilities Integration section. If the user elects to use AvaTax UPC, ensure that the appropriate field containing UPC data is mapped to the itemCode parameter formatted as: UPC:+. Example: “UPC:1234567890000”. by formatting the value with “UPC:” identifier, our engine can pick up the UPC code, and the user can avoid mapping a tax code for that item. If no UPC data is available still default to the regular itemCode mapping.

The UPC functionality is a premium upgrade to the Avalara AvaTax subscription providing taxability decision (taxable vs. non-taxable) without requiring an Avalara Tax Code assignment.

Association of Freight/Shipping and/or Handling charge to an AvaTax Tax Code to describe the taxability.

The volume of only the item, substance, or product in question, exclusive of packaging, container, or other ancillary materials.

Possible values: Volume as a number “100 L/mL”

Intended for use where tax rate is dependent on size of container, sent as a number

Possible values: Volume as a number “100 L/mL”

Allows customer to specify, where relevant, the number of taxable items in a package, such as cigarettes in a pack or bottles in a case.

Alcohol percentage by volume, sent as a number

ex. value = 15, unit of measure = percentage

Brand name associated with the product being sold

Used to indicate whether a beverage alcohol product is a sample product (isAlcoholSample)

Used to indicate whether a beverage alcohol product is a foreign beverage alcohol product (isForeignAlcohol)

The integration must display the Avalara Shipping Verification and Registration results on the transaction summary

Upon a successful 'compliant' response from the Shipping Verification utility, add transaction to the compliance register

When Avalara Shipping Verification returns a 'non-compliant' result, function to quarantine order until merchant action is taken:

• Modify transaction and re-process Avalara Shipping Verification
• Cancel/VOID or Refund transaction
• Override the verification failure and add the transaction to the compliance register

When issuing a credit memo for a returned product, the integration must remove the returned products from the compliance register

Function to add historical transaction to the compliance registry