> ## Documentation Index
> Fetch the complete documentation index at: https://zenskar.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Reference

## Avalara page

To open the Avalara page, go to **More** > **Integrations**, and click the **Avalara** card. To find the card, you can filter by **Sales Tax**.

| Element | Description |
| - | - |
| **NEW CONNECTION** | The button opens the connection form. It is unavailable while an [Avalara connection](/docs/20260301/product-modules/settings/glossary.md#avalara-connection) has no Zenskar [business entity](/docs/20260301/product-modules/settings/glossary.md#business-entity). |
| **Connections** | The tab lists the Avalara connections of your organization. See [Connections tab](#connections-tab). |
| **Logs** | The tab lists the sync events of all Zenskar invoices. See [Logs tab](#logs-tab). |

## Connection form

**NEW CONNECTION** on the [Avalara page](#avalara-page) opens the connection form.

| Field | Required | Description |
| - | - | - |
| **License Key** | Yes | The field takes the license key of your Avalara account. |
| **ACCOUNT ID** | Yes | The field takes the account ID of your Avalara account. |
| **Company Code** | No | The field takes the company code of the [Avalara company](/docs/20260301/product-modules/settings/glossary.md#avalara-company). The field contains `DEFAULT` until you change it. |

**Connect** checks the account ID and the license key with Avalara. If Avalara accepts them, the [Avalara Setup page](#avalara-setup-page) opens at the **Connect** step. If Avalara rejects them, Zenskar shows an error. The credentials must belong to the Avalara environment that matches the type of your Zenskar organization.

## Avalara Setup page

The **Avalara Setup** page opens after **Connect** on the [connection form](#connection-form). It also opens from **Select Business Entity** and **Edit** on the [Connections tab](#connections-tab). Opening the page needs **Can Read Integration Config**.

The steps after **Connect** become available after the connection has a Zenskar business entity. Then you can also click a step at the top of the page to go to it.

| Step | Content | Main button |
| - | - | - |
| **Connect** | The step shows **Select Zenskar Entity**. There, you select the Zenskar business entity of the connection. After the connection has one, the field shows it. The field is then unavailable. The step also shows **Tax on Invalid Address**. Cedar does not use this setting. | **Save & Continue** saves the Zenskar business entity of a connection that has none. Otherwise, **Continue** goes to the next step. |
| **Countries Serving** | The step shows the [served countries](/docs/20260301/product-modules/settings/glossary.md#served-country) of the Zenskar business entity. It also shows the [tax engine](/docs/20260301/product-modules/settings/glossary.md#tax-engine) of each served country. See [Manage served countries](/docs/20260301/product-modules/settings/tax-configuration/how-to-guides.md#manage-served-countries). | **Continue** goes to the next step. |
| **Tax Categories** | The step shows the Zenskar [tax categories](/docs/20260301/product-modules/settings/glossary.md#tax-category) with their **Avalara Tax Code**. **Browse Avalara tax codes** opens the list of [Avalara tax codes](/docs/20260301/product-modules/settings/glossary.md#avalara-tax-code). See [Map a Zenskar tax category to an Avalara tax code](/docs/20260301/third-party-integrations/tax-automation/avalara-avatax/how-to-guides.md#map-a-zenskar-tax-category-to-an-avalara-tax-code). | **Finish Setup** opens the **Connections** tab. |

## Connections tab

The **Connections** tab of the [Avalara page](#avalara-page) lists the Avalara connections of your organization.

| Element | Description |
| - | - |
| **Account ID** | The detail shows the Avalara account of the connection. |
| **Connected Entity** | The detail shows the Zenskar business entity of the connection. |
| **Connected On** | The detail shows the date on which the connection was created. |
| **Last Updated On** | The detail shows the date on which the connection last changed. |
| **Status** | The detail shows **Configured** after the connection has a Zenskar business entity. Before that, it shows **Pending Configuration**. |
| **Select Business Entity** | The button appears on a connection without a Zenskar business entity. It opens the [Avalara Setup page](#avalara-setup-page) at the **Connect** step. |
| **Edit** | The button opens the Avalara Setup page of the connection. See [Edit an Avalara connection](/docs/20260301/third-party-integrations/tax-automation/avalara-avatax/how-to-guides.md#edit-an-avalara-connection). |
| **Disconnect** | The button opens the **Delete Connector ID** dialog. See [Disconnect Avalara AvaTax](/docs/20260301/third-party-integrations/tax-automation/avalara-avatax/how-to-guides.md#disconnect-avalara-avatax). |

## Exemption custom attributes

The **Edit Customer** panel shows these custom attributes under **Custom Attributes**. See [Exempt a Zenskar customer in Avalara](/docs/20260301/third-party-integrations/tax-automation/avalara-avatax/how-to-guides.md#exempt-a-zenskar-customer-in-avalara).

| Key | Type | Description |
| - | - | - |
| `exempt_tax` | Boolean | When the value is true, Avalara treats the transactions of the Zenskar customer as exempt. Every organization has this custom attribute. |
| `tax_exemption_number` | Text | Zenskar sends the value as the exemption-certificate number. When the value is empty, Zenskar sends `exempt`. |
| `entity_use_code` | Text | Zenskar sends the value as the Avalara entity-use code. **Browse Avalara entity use codes** opens the list of codes. |

## Integrations tab of a Zenskar invoice

The **Integrations** tab appears on a Zenskar invoice that is approved, partially paid, paid, or void. Opening the Zenskar invoice needs **Can Read Invoice**.

| Element | Description |
| - | - |
| **Avalara ID** | The card is under **Linked Integration Objects**. It shows the ID of the [Avalara transaction](/docs/20260301/product-modules/settings/glossary.md#avalara-transaction) of the Zenskar invoice. The copy icon next to the ID copies it. |
| **Integration Logs** | The table lists the sync events between Zenskar and Avalara for the Zenskar invoice. Each row shows the event, its status, and its timestamp. **Failed** shows only the failed events. |

## Logs tab

The **Logs** tab of the [Avalara page](#avalara-page) lists the sync events of all Zenskar invoices. It has the same columns and filters as **Integration Logs**. See [Integrations tab of a Zenskar invoice](#integrations-tab-of-a-zenskar-invoice). The tab needs no specific permission.

## IDs in Avalara

Zenskar names each Avalara transaction and each Avalara customer. Avalara shows the transaction ID as the document code.

| Object | ID in Avalara |
| - | - |
| Avalara transaction | The ID has the form `{Zenskar invoice ID}:`, followed by eight characters. |
| [Avalara customer](/docs/20260301/product-modules/settings/glossary.md#avalara-customer) | The customer code is the Zenskar customer ID. When a Zenskar invoice has a payer, the customer code is the ID of the payer. |

## Permissions

| Action | Permission | Group |
| - | - | - |
| Enter the credentials of a new connection | None | |
| Open the **Avalara Setup** page | **Can Read Integration Config** | **INTEGRATION\_CONFIG** |
| Select the Zenskar business entity of a connection | **Can Read Integration Config** | **INTEGRATION\_CONFIG** |
| Select the Zenskar business entity of a connection | **Can Create Integration Config** | **INTEGRATION\_CONFIG** |
| Set the served countries and the Avalara tax codes in the setup | **Can Update Organisation Config** | **ORGANISATION\_CONFIG** |
| Map a Zenskar tax category to an Avalara tax code | **Can Update Organisation Config** | **ORGANISATION\_CONFIG** |
| Create the exemption custom attributes | **Can Create Organisation Config** | **ORGANISATION\_CONFIG** |
| Exempt a Zenskar customer in Avalara | **Can Read Customer** | **CUSTOMER** |
| Exempt a Zenskar customer in Avalara | **Can Update Customer** | **CUSTOMER** |
| Check the Avalara transaction of a Zenskar invoice | **Can Read Invoice** | **INVOICE** |
| View the **Logs** tab | None | |
| Disconnect Avalara | None | |

## API reference

Avalara connections have no API. The Zenskar API has no operations specific to Avalara.

## Troubleshooting

| Problem | Cause | Solution |
| - | - | - |
| **NEW CONNECTION** is unavailable. | An Avalara connection has no Zenskar business entity. | On that connection, click **Select Business Entity**. Then [finish the setup](/docs/20260301/third-party-integrations/tax-automation/avalara-avatax/how-to-guides.md#connect-avalara-avatax). |
| **Connect** shows an error. | Avalara rejected the account ID and the license key. The values can be wrong, or they can belong to the other Avalara environment. | Check both values in Avalara. Use credentials from the environment that matches your Zenskar organization. |
| **Save & Continue** shows an error about another tax engine. | The Zenskar business entity already has another third-party tax engine connected. | Disconnect the other tax engine, or select another Zenskar business entity. |
| The tax-category panel has no **Avalara Tax Code** field. | Avalara is not connected. | [Connect Avalara](/docs/20260301/third-party-integrations/tax-automation/avalara-avatax/how-to-guides.md#connect-avalara-avatax). |
| An [Avalara tax code](/docs/20260301/product-modules/settings/glossary.md#avalara-tax-code) cannot be saved. | The code is longer than 25 characters. | Enter a valid Avalara tax code. |
| A Zenskar invoice has no tax for a jurisdiction. | The Avalara company has no nexus in the jurisdiction. | Set up nexus in the Avalara company. |
| Avalara taxes an exempt Zenskar customer. | The `exempt_tax` custom attribute of the Zenskar customer is not true. | [Exempt the Zenskar customer](/docs/20260301/third-party-integrations/tax-automation/avalara-avatax/how-to-guides.md#exempt-a-zenskar-customer-in-avalara). |
| A draft Zenskar invoice is held at approval after an exemption change. | Zenskar generated the draft invoice before the change. | Regenerate the Zenskar invoice. |
| Generating Zenskar invoices fails after a disconnect. | A served country still uses Avalara as its tax engine. | [Change the tax engine of the served country](/docs/20260301/product-modules/settings/tax-configuration/how-to-guides.md#change-the-tax-engine-for-a-served-country). |
| A draft Zenskar invoice is held at approval after a disconnect. | Avalara priced the draft invoice before the disconnect. | Regenerate the Zenskar invoice. |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.