Design considerations

Whether you’re 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 to become certified. We carefully crafted these UI elements to help you create an integration that's straightforward and uncomplicated for your users and to help ensure that your integration is tax compliant.

We've broken the badge requirements down into the following types:

Required: This design element is required to become certified.
Suggested: This design element isn’t 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 isn’t necessary; however we recommend that you follow these guidelines when using AvaTax APIs in your own systems.

Tip

As you design your user experience, keep in mind how the features of your ERP will work with AvaTax. If you configured your ERP for multiple filing entities, then it’s essential that you configure your AvaTax company profiles with company codes that match the filing entity identifiers in your ERP. See the Optional: Set up a hierarchy of subsidiary companies topic for more information on setting up multiple filing entities in AvaTax.