> 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.

# Get certified

Guide: AvaTax Excise

Learn how to submit your ATE integration for Avalara's review.

Congratulations! At this point, you've completed all previous milestones, and you're ready for Avalara to review your integration.

## How do I submit?

To initiate a functional review:

1. Create a recording demonstrating your integration, including the installation.
2. Send the recording along with the user guide to [DG-PartnerLaunch@avalara.com](mailto:DG-PartnerLaunch@avalara.com).

Avalara will review your demo and then follow up with you. During this follow-up, Avalara will either request more information from you or inform you that you achieved certification.

## What do I include in the demo?

Your integration should include all requirements mentioned in the previous chapters. Specifically, we want to see the following:

**Core integration requirements**

* How you install or enable your integration.
* Your configuration screen and authentication process, including:
  * Demonstrate inputting your credentials.
  * Show that your integration includes:
    * A test connection button
    * An option to designate connecting to a Production or Sandbox environment
  * Show that you defined a company code.
* How you identify business entities, locations, and product and mode code.
* The quote-to-cash process, including transaction scenarios along with doc codes:
  * The quote-to-cash process should specifically call out the times when the system reaches out to ATE for tax calculation and when the system records a transaction for further reporting and remittance.
* Other considerations
  * Show that your integration sends the proper HTTP headers (assuming that your integration uses the REST v2 API).
  * Show that your integration includes an address validation, filter-by-country option or that you limit address validation requests to only the US and Canada.
  * Show that your integration uses a reasonable API request ratio during invoicing.
  * Show that sales invoices use an `AvataxDocumentType` of `SalesInvoice` and that you don't call AvaTax multiple times for the same invoice.
  * Confirm that orders/estimates use an `AvataxDocumentType` of `SalesOrder` or `PurchaseOrder`.

**Tobacco, nicotine, and vape integrations**

Demonstrate that you can run the tobacco, nicotine, and vape example transactions included in this guide.

**Fuel integrations**

Demonstrate that you can run the fuel example transactions included in this guide.

> **Note**
>
> Part of the **AvaTax Excise** integration guide. [Open the full "Get certified" milestone on Avalara](https://developer.avalara.com/products/excise/integration-guides/excise/yyo7150607989444/) to see every page in this section.