> This page is for Documentation, version Get certified.
> 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.

# Account Provisioning badge

### Provisioning

| Name                        | Type        | Description                                                                                                                                          | Comments                                                          |
| --------------------------- | ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------- |
| Request a new account       | Required    | Your integration must provide a way for users to provision a new Avalara account.                                                                    |                                                                   |
| Request a new entitlement   | Required    | Your integration must provide a way for users with Avalara accounts to add entitlements.                                                             |                                                                   |
| Error handling              | Required    | Your integration must provide relevant provisioning errors to users and execute a fallback method for authentication confirmation.                   |                                                                   |
| Validate password strength  | Conditional | Ensure users provide strong passwords for authentication to the provisioned Avalara service.                                                         | Required if your integration allows users to configure a password |
| Accept Terms and Conditions | Required    | Your integration must provide users with a way to view and accept relevant Avalara product terms and conditions prior to provisioning a new account. |                                                                   |
| Welcome Message             | Suggested   | Your UI should present users with a welcome message upon successfully provisioning an account.                                                       |                                                                   |
| Nexus Confirmation          | Required    | When new accounts are provisioned, users must be presented with a message confirming the Nexus settings for the companyID provided in the request.   |                                                                   |
| Tooltips                    | Required    | Your UI must provide tooltips for users during the provisioning process.                                                                             |                                                                   |

> **Note**
>
> Certification badge requirements. [View on Avalara](https://developer.avalara.com/certification/avatax/provisioning-badge/).