Tax Vendor

Last Updated: Aug 19, 2020

Tax Vendors are configured in Setup / Finance / Taxes / Tax Vendor


From this screen you can configure tax vendors that use native (LogiSense) or third party (AvaTax) tax solutions. Tax vendors added here are selected when configuring tax codes in order to specify how charges that fall under the tax code are taxed. For example, a tax code configured to use the AvaTax tax vendor will tax transactions that fall under the tax code using tax rates supplied by Avalara. Conversely, a tax code setup to use the native LogiSense tax vendor would tax based upon the tax rates that are configured on the tax code.

Tax Jurisdiction Codes

Jurisdiction codes are numerical values used by AvaTax to indicate the tax jurisdiction that an account falls under. Jurisdiction codes are determined by checking the addresses found on service contacts (or alternately, if service contacts are not used then billing account contact addresses can be configured for taxation). When a jurisdiction code is found it is added to the address details on the service/billing account contact. So long as an AvaTax vendor is active the addresses that are added or updated on these account contacts will be passed to Avalara in order to retrieve the correct jurisdiction code and update it on the contact's address details.

Batch Taxing

When utilizing an integrated tax vendor (AvaTax) transactions will be calculated in batches instead of making an API call to the tax vendor on every taxable transaction. This reduces system load, particularly in environments where usage transactions occur very frequently. By default batches are sent to Avalara when the number of transactions to tax reaches 1000 or 30 seconds have elapsed since the last bulk transmission was sent. The batch size and frequency may be adjusted from the defaults on your instance, as LogiSense will determine and configure the optimal batch taxing configuration before your environment goes live.


If you wish to configure an AvaTax tax vendor you will first need the credentials and settings supplied by Avalara.

Tax Vendor Panel

The Tax Vendor panel on the left of this screen allows you to select existing tax vendors to view and edit on the Edit Tax Vendor panel to the right. Actions are also available in this panel which are shown as icons above the Filter text box. The available actions are described below.




Deletes the tax vendor if not in use

Adds a new tax vendor

Edit Tax Vendor Panel

The information in this panel reflects the currently selected tax vendor. From here you can change vendor details (fields will display a red left border if a value is required and purple text if the field is read-only and cannot be modified).

Tax Vendor Fields:

  • Name: a descriptive name of the tax vendor

  • Active: enables or disables the tax vendor. A disabled tax vendor will not tax or perform any other integration options (e.g. if you disable an AvaTax tax vendor then tax jurisdiction codes will not be added/updated on account contact addresses)

  • Vendor: the native or external tax solution to use

Configuration tab

This tab will display configuration settings when an integrated tax vendor is selected (i.e. AvaTax).

  • Company Identifier: optional company identifier. Your company name/client company name if you are acting as a billing provider

  • URL: endpoint URL provided by Avalara

  • User Name: Avalara supplied user name

  • Password: Avalara supplied password

  • Client ID: Avalara supplied client ID number

  • Client Profile ID: optional Avalara tax profile (number) used to apply AvaTax customizations files and configurations that are setup on the profile (e.g. tax exclusions and overrides). If you have no profiles setup leave this field empty

  • Service Class: service class to indicate the primary service your organization provides (local or long distance). Only relevant in certain jurisdictions (e.g. New York)

  • Business Class: business class to indicate if your organization is an incumbent or competitive provider (CLEC or ILEC). Only relevant in certain jurisdictions (e.g. Oregon)

  • Default Account Tax Category: this option will appear during configuration after importing service tax categories. The default account tax category set here is passed to Avalara for taxation in situations where no account tax category has been set on an account. A default account tax category is particularly useful when you only use one account tax category across all accounts, as using a default will eliminate the requirement to configure an account tax category on each account

  • Default Service Tax Category: this option will appear during configuration after importing service tax categories. The default service tax category set here is passed to Avalara for taxation in situations where no service tax category has been set on a service. If you only use one service tax category then configuring it as the default will eliminate the requirement to configure the service tax category on each service in the product catalog