> This page is for Documentation, version Integration guides (default).
> For other versions, use one of these documentation indexes:
> - Integration guides (default): https://avalara.ferndocs.com/docs/integration-guides/llms.txt
> - Refactor guides: https://avalara.ferndocs.com/docs/refactor-guides/llms.txt
> - Get certified: https://avalara.ferndocs.com/docs/get-certified/llms.txt
> - Agent to Agent (A2A): https://avalara.ferndocs.com/docs/agent-to-agent-a2a/llms.txt
> - AI use cases: https://avalara.ferndocs.com/docs/ai-use-cases/llms.txt
> - API versioning: https://avalara.ferndocs.com/docs/api-versioning/llms.txt

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://avalara.ferndocs.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://avalara.ferndocs.com/_mcp/server.

# Design the Sales and Use Tax user experience

Whether you are a technology partner working to become certified or an API customer, this section describes how you should design your AvaTax application.

**Certification for technology partners:**

What should your integration's user interface look like? What design elements should you include? For partner certification, this section describes the design elements that are necessary in order to become certified. These UI elements have been carefully crafted to help you create an integration that is straightforward and uncomplicated for your users and to help ensure that your integration is tax compliant.

The badge requirements are broken down into the following types:

* **Required**: This design element is required in order to become certified.
* **Suggested**: This design element is not required, but we recommend that your UI includes suggested elements.
* **Conditional**: Depending on your use case, this design element may be required.

**API customers:**

For API customers, following these badge certification requirements is not necessary; however we recommend that you follow these guidelines when using AvaTax APIs in your own systems.

**Advice:** As you design your user experience, you should keep in mind how the features of your ERP system will work with AvaTax. If your ERP system is confgured for multiple filing entities, it is essential that you configure your AvaTax company profiles with company codes that match the filing entity identifiers in your ERP system. See [Set up a hierarchy of subsidiary companies](https://developer.avalara.com/avatax-dm-combined-erp/common-setup/configure-your-account/erp-hierarchy "About location-based filing") for more information on setting up multiple filing entities in AvaTax.

[Previous](https://developer.avalara.com/avatax-dm-combined-erp/common-setup/design-the-user-experience/dm/batch-load-customers)

[Next](https://developer.avalara.com/avatax-dm-combined-erp/sales-tax-badge/designing/customer-code)

> **Note**
>
> Part of the **AvaTax and ECM** integration guide. [Open the full "Design the Sales and Use Tax user experience" milestone on Avalara](https://developer.avalara.com/avatax-dm-combined-erp/sales-tax-badge/) to see every page in this section.