Skip to main content

Connect Avalara AvaTax

Prerequisites

  • You have the account ID and the license key of your Avalara account. You also have the company code of the Avalara company.
  • The credentials belong to the matching Avalara environment. A sandbox Zenskar organization needs Avalara sandbox credentials. A production Zenskar organization needs Avalara production credentials.
  • The Zenskar business entity does not have another third-party tax engine connected.
  • Your role has the permissions in the following table.
If the Avalara company has no nexus in a jurisdiction, Avalara returns no tax for that jurisdiction. Neither Avalara nor Zenskar shows an error. Before you select Avalara as the tax engine of a served country, set up nexus in the Avalara company for every jurisdiction where you collect tax.
  1. Go to More > Integrations.
  2. Click the Avalara card. To find the card, you can filter by Sales Tax. The Avalara card on the Integrations page, with the Sales Tax filter
  3. Click NEW CONNECTION. The Avalara page with NEW CONNECTION NEW CONNECTION is unavailable while an Avalara connection has no Zenskar business entity. In that case, click Select Business Entity on that connection. Then continue from step 6. An Avalara connection without a business entity, with Select Business Entity
  4. Enter the credentials:
    • In License Key, enter the license key of your Avalara account.
    • In ACCOUNT ID, enter the account ID of your Avalara account.
    • In Company Code, keep DEFAULT, or enter the company code of the Avalara company.
    The Avalara connection form
  5. Click Connect. If Avalara accepts the account ID and the license key, the Avalara Setup page opens at the Connect step. If Avalara rejects them, Zenskar shows an error.
  6. In Select Zenskar Entity, select the Zenskar business entity. Cedar does not use Tax on Invalid Address. Leave it as it is.
  7. Click Save & Continue. Zenskar rejects a Zenskar business entity that already has another third-party tax engine connected.
  8. On the Countries Serving step, add or edit the served countries of the Zenskar business entity. For each served country that Avalara should tax, select Avalara in Tax Engine. See Manage served countries. The Add Country panel with Tax Engine set to Avalara
  9. Click Continue.
  10. On the Tax Categories step, set the Avalara Tax Code of each Zenskar tax category that your Zenskar products use. To look up codes, click Browse Avalara tax codes. See Map a Zenskar tax category to an Avalara tax code.
  11. Click Finish Setup. The Connections tab of the Avalara page opens.

Edit an Avalara connection

Editing an Avalara connection changes the served countries of its Zenskar business entity. It also changes the Avalara tax codes of the Zenskar tax categories. The Zenskar business entity of a connection cannot change.

Prerequisites

  • The Avalara connection has a Zenskar business entity.
  • Your role has the permissions in the following table.
  1. Go to More > Integrations.
  2. Click the Avalara card.
  3. Click the Connections tab. Each connection on the tab shows its Account ID, Connected Entity, Connected On, Last Updated On, and Status. The status is Configured after the connection has a Zenskar business entity. Before that, it is Pending Configuration. A configured Avalara connection on the Connections tab
  4. On the connection, click Edit. The Avalara Setup page opens at the Connect step. Select Zenskar Entity shows the Zenskar business entity of the connection. You cannot change it.
  5. Click Continue. To go to a step directly, you can also click the step at the top of the page.
  6. On the Countries Serving step, add or edit the served countries. See Manage served countries.
  7. Click Continue.
  8. On the Tax Categories step, change the Avalara Tax Code of the Zenskar tax categories. See Map a Zenskar tax category to an Avalara tax code.
  9. Click Finish Setup.
Changes on these steps take effect as you make them. Finish Setup only returns to the Connections tab.

Map a Zenskar tax category to an Avalara tax code

Prerequisites

  • Avalara is connected. The Avalara Tax Code field and column appear only after you connect Avalara.
  • Your role has the permissions in the following table.
  1. Go to Settings > Tax Configuration.
  2. On the Tax Categories tab, in the actions menu of the Zenskar tax category, click Edit. The Edit Tax Category panel opens.
  3. In Avalara Tax Code, enter the Avalara tax code. The code has up to 25 characters. The Avalara Tax Code field in the tax-category panel
  4. Click Save Changes. The Avalara Tax Code column of the tax-category list
You can also map the code in the Avalara Tax Code column of the tax-category list. Click Map Avalara code or the current code. Then enter the Avalara tax code, and click Save.
To remove the Avalara tax code of a Zenskar tax category, click × next to the code in the column.

Exempt a Zenskar customer in Avalara

Prerequisites

  • Your organization has the tax_exemption_number and entity_use_code customer custom attributes, of the text type. Every organization already has exempt_tax. See Custom attributes.
  • Your role has the permissions in the following table.
  1. Go to Customers.
  2. In the actions menu of the Zenskar customer, click Edit. The Edit Customer panel opens.
  3. Under Custom Attributes, set exempt_tax to true. While exempt_tax is true, the tax IDs under Tax Information are unavailable.
  4. Optional: in tax_exemption_number, enter the exemption-certificate number.
  5. Optional: in entity_use_code, enter the Avalara entity-use code. To look up codes, click Browse Avalara entity use codes.
  6. Click Save.
From the next invoice generation, Avalara treats the transactions of the Zenskar customer as exempt. Draft Zenskar invoices generated before the change are held at approval. To apply the exemption, regenerate them.

Check the Avalara transaction of a Zenskar invoice

Prerequisites

  • The Zenskar invoice is approved, partially paid, paid, or void. The Integrations tab appears only on these invoices.
  • Your role has the permissions in the following table.
  1. Go to Invoices, and open the Zenskar invoice.
  2. Click the Integrations tab. Under Linked Integration Objects, the Avalara ID card shows the ID of the Avalara transaction. To copy the ID, click the copy icon next to it. Under Integration Logs, each row is one sync event between Zenskar and Avalara for the Zenskar invoice. The row shows the event, its status, and its timestamp. To show only failed events, click Failed. The Integrations tab of an approved invoice
  3. In Avalara, open Transactions, and search for the ID that you copied. Avalara shows the ID as the document code. A committed Avalara transaction has the status Committed. If the integration worked, the amounts match the Zenskar invoice. The matching Avalara transaction in the Transactions list of Avalara
  4. To see the addresses and the tax of each line item, open the Avalara transaction. The detail of an Avalara transaction
To check the sync events of all Zenskar invoices, go to More > Integrations, click the Avalara card, and then click the Logs tab. The tab has the same columns and filters as Integration Logs. The Logs tab of the Avalara page

Disconnect Avalara AvaTax

Prerequisites

  • Your role has the permissions in the following table.
Disconnecting Avalara does not change the tax engine of any served country. Generating Zenskar invoices fails for served countries that still use Avalara. Before you disconnect, change the tax engine of those served countries. See Change the tax engine for a served country.
Disconnecting Avalara removes the links between Zenskar invoices and their Avalara transactions. You cannot undo this.
  1. Go to More > Integrations.
  2. Click the Avalara card.
  3. Click the Connections tab.
  4. On the connection, click Disconnect. The Delete Connector ID dialog opens.
  5. Click Delete.
Zenskar removes the Avalara connection. The Avalara transactions stay in Avalara. Draft Zenskar invoices that Avalara priced are held at approval after the disconnect. To apply the new tax engine, regenerate them.