Avalara Developer Network Developer avaTax
Avalara Certified Solution

Avalara AvaTax Use Tax Badge Requirements


Administration/Utilities Integration

AvaTax Configuration Window - Required

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

  • Avalara Credentials
    • Account Number
    • License Key
  • Service URL (free-form or pick-list with the following)
    • Developmnet
    • Production
  • Company Code (one of two options typically)
    • User-definable
    • Inherited from client application
    • Lookup Code from AvaTax

AvaTax Test Connect Button - Required

Provide a button for a user to test the connection to the AvaTax service and verify the AvaTax credentials. This is an important element to allow for successful setup and troubleshooting of the AvaTax service. Optional: display license key expiration date upon successful connection response.

Document Committing Control - Required

A singular control must exist in the Configuration Dialog Window to turn on/off committing of documents. In order for this connector to be used in conjunction with other integration to AvaTax, the user must be able to control which connector is used for committing documents. Typically, this exists as a checkbox or radio button. From a technical standpoint

  • Suppress any non-getTax calls (i.e. cancelTax, postTax)
  • Ensure that Commit = False on all GetTax calls.

Tax Calculation Service Control - Required

A singular control must exist in the Configuration Dialog Window to turn on/off the Avalara Use Tax Calculation service independently of any other Avalara product or service. Typically, this exists as a checkbox or radio button.

User Implementation Guide - Required

The User Implementation Guide should contain screenshots and information allowing the end user to configure for Avalara Use Tax including where the company code is entered, where the credentials are entered and where tax codes can be mapped within the application.

Enable Logging - Required

The user must have an option to enable detailed AvaTax transaction logging within the application, including capture of round-trip processing time. Users should have a means to download these detailed log files.

Link to Admin Console - Required

Link to AvaTax Production Admin Console.

Enable AvaTax UPC - Required

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. NOTE: Alternately, UPC can be enabled on the item level. See Product Master Management.

Merchant/User Exemption - Required

One or the other parameter is required, although Entity/Use code is preferred.

  • Entity/Use Code:
    • Assign an Avalara Entity/Use Code to the merchant/user (an Entity/Use Code defines the reason for the sales tax exemption, Reseller, Manufacturer, Government Entity, Charitable Organization, etc.).
    • Must include our standard list and be user-definable to add additional items.
  • Exemption Number:
    • Identify a field to map the exemption certificate number of the merchant/user of the application to the “ExemptionNo” field in Avalara.


Vendor Management

Vendor Identifier Mapping - Required

Identify the vendor identifier field (typically the database key in the vendor master) to map to the “CustomerCode” field in Avalara.

Vendor Level Use Tax Assessment - Required

True/False self assessment. Implement appropriate business logic to determine when to self assess. Be sure to include the following:

  • When self assessing, ensure that transactions are committed to the Avalara Admin Console
  • When NOT self assessing, do not commit transaction to the Admin Console
In the case of Global Use Tax assessment, commit all transactions regardless of the vendor.

Entity/Use Code - Required

Provide functionality to assign either an Avalara system or custom customer usage type (entity/use code) to the vendor, indicating all purchases from this vendor are used for an exempt purpose (resale, use in manufacturing/production, etc.).

Exemption Number - Conditional

When vendor record has a dedicated exemption number field on the vendor record and/or its address records, provide functionality to assign the buyer’s exemption number to the vendor, indicating purchases made from this vendor and/or to one of the buyer’s ship-to addresses are exempt.


Product Master Management

Item Code - Required

Identify item/service/charge code (number, ID) to pass to the AvaTax service. If the customer has access to UPC, they should be able to prepend UPC to the code and have it come across in the item code field. If there is no UPC, it should fall back to SKU. (See UPC requirements in the Administration & Utilities Integration section) For Purchase Invoices not associated with a Purchase Order, you may not have access to the ItemCode from the client application. In that case, simply use the GL account number/cost center identifier.

Item Description - Required

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

Avalara Tax Code Assignment – Group - Conditional

When the Product Master provides functionality to group items/products in the product catalog. Associate an Avalara Tax Code to an item group/product group/commodity code. The Tax Code assignment becomes the default for all items/products in the group. Search for a specific tax codeDownload a list of the standard system tax codes.

Avalara Tax Code Assignment - Item/SKU - Required

Provide an attribute to associate an Avalara Tax Code to an item/SKU. Overrides default Tax Code at item/product group level. Search for a specific tax code. Download a list of the standard system tax codes.

UPC - Required

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:>+<UPC Data>. 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.

NOTE: 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.


General Ledger Account Master Management

Item Code - Conditional

When the application provides functionality permitting the user to assign a General Ledger Account Number to a line on the purchase order/invoice in lieu of an Item/SKU, pass the General Ledger Account Number to the AvaTax service.

Item Description - Conditional

When the application provides functionality permitting the user to assign a General Ledger Account Number to a line on the purchase order/invoice in lieu of an Item/SKU, pass the General Ledger Account Number description to the AvaTax service.

Avalara Tax Code Assignment - Conditional

When the application provides functionality permitting the user to assign a General Ledger Account Number to a line on the purchase order/invoice in lieu of an Item/SKU, provide an attribute to associate an Avalara Tax Code to the General Ledger Account Number.


Purchasing & Payables Document Integration

Send header level data elements for PurchaseOrder and PurchaseInvoice document types - Required

  • Document number
  • CustomerCode
  • Document Date
  • Tax calculation date
  • Document type
  • Destination address
  • Origin address
  • Exemption number
  • Entity/Use code (aka CustomerUsageType)
  • Location Code

Send line (detail) level data elements for PurchaseOrder and PurchaseInvoice document types - Required

  • Line number
  • Item code
  • Item description
  • Quantity
  • Amount (extended)
  • Tax Code
  • Entit/Use Code
  • Revenue account

    Revenue Account references for purchase order/invoices represent the general ledger account number associated with the purchase.

Send point-of-consumption of product/service purchased as Destination address - Required

Use tax is assessed, in part, based upon the location where the product is consumed or the service is rendered. The address associated with that location is to be passed as Destination address type.

In the event the location where product is consumed is not available, the delivery address can be substituted as Destination address.

Freight/Shipping Charges - Required

Freight/Shipping Items must be sent to AvaTax as a separate line item with appropriate tax code.

Discounts - Required

Either send line items with post-discounted amounts or utilize the Avalara Discount Fields.

Purchase Orders - Required

Follow basic Purchase Order workflow with required parameters and Address Validation touch points integrated. Purchase Orders are used to calculate and apply an estimated sales tax.

Purchase Invoices - Required

Follow basic Purchase Invoice workflow with required parameters and Address Validation touch points integrated. The results of purchase Invoice documents will be used to determine if taxes need to be self-assessed. The user must then be presented with options to take action based user-specific business needs. See requirement below on Self-asses workflow.

Self-Assess workflow: Purchase Invoices - Vendor-Charged Tax - Required

  • When a purchase invoice includes vendor-charged tax:
    • Vendor-charged tax must be separately stated
    • Vendor-charged tax must be captured by the tax calculation request
  • The user is provided a display including:
    • Vendor-charged tax
    • AvaTax calculated tax
    • Difference between charged and calculated tax
  • The user is presented the following options:
    • Accept the difference between AvaTax calculated tax and vendor-charged tax (only if AvaTax is a larger amount than vendor-charged tax)
    • Accept AvaTax calculated Use Tax in total
    • Edit the Use Tax amount to a desired amount, including $0.00

Self-Assess workflow: Purchase Invoices - Zero Vendor-Charged Tax - Required

AvaTax calculated tax is returned, and the user is presented with the following options:

  • Accept AvaTax calculated Use Tax in total
  • Edit the Use Tax amount to a desired amount, including $0.00

Committing Invoices for Vendor Liability Assessment: Purchase Invoices - Required

Ensure purchase invoices are committed/posted for reporting appropriately after they are finalized.

Create Use Tax accrual: Purchase Invoices - Required

Generate use tax accrual journal entry lines for completed purchase invoices.
Debit - create debit lines for each assessed line recording use tax amount and associated general ledger number sourced from purchase invoice line.
Credit - create summary credit line for total use tax assessment charged to liability (Use Tax Payable) general ledger account number.

CancelTax Call - Required

When a purchase invoice is deleted/canceled, this information must be transmitted to AvaTax.

Send optional header level data elements - Suggested

  • Purchase Order Number - for purchase order/invoice scenarios, this represents the vendor/supplier's sales order number
  • Reference Code
  • Salesperson Code

Send optional line (detail) level data elements - Suggested

  • Exemption Number - overrides header level Exemption Number
  • Reference 1
  • Reference 2

Latitude/Longitude - Suggested

Latitude/Longitude coordinates can be sent in lieu of a postal address.


Server Audit/Clarity

Pass connector identifier information via the TaxSvc.Profile.Client property - Required

Integrations must include information about the connector, such as name, version, and company name, as a signature to each transaction.EXAMPLE: TaxSvc.Profile.Client = “Dynamics AX,9.0,MyApp for AX by ACME INC,1.0”

Reasonable errors on server-side analysis - Required

There should be no errors except those that would result from normal (but invalid) user input (e.g. invalid address data). Such errors must be logged/displayed appropriately to the application.

Reasonable ratio of GetTax and address validation calls to committed documents - Required

In a normal workflow, we expect to see up to 10 tax calculations per finalized document. In a straight-forward order entry process, the number of calls should be about three to five.

Demonstrate and document installation of software – Install Shield or equivalent where applicable - Required

Customers should have an easy and trouble free installation of the software.