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

# Functional review

Congratulations! At this point, you've completed all previous milestones. If you're a technology partner, you're now ready for your integration to be reviewed.

#### How to submit

To initiate a functional review:

1. Create a recording demonstrating your integration, including the installation.
2. Send the recording to [dg-partnerlaunch@avalara.com](mailto:dg-partnerlaunch@avalara.com).
3. 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 have achieved certification.

#### What to include in your demo

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

* How do you install or enable your integration
  * Architecture diagram
* Configuration screen and authentication process
  * How to set up Avalara credentials
  * How to test authentication connection using the Health Service API (PING)
  * How to enable/disable service utilization
  * Where and how to access logs
  * Demonstrate the configurations between Sandbox and Production environments
* Send us the payloads for each of the transaction scenarios you want to have certified

**Additional considerations**

If applicable, it's important to demonstrate a control cockpit, which allows the customer to consult an authorized electronic invoice, cancel an electronic invoice (when it's allowed by the city) and other functions that are necessary to execute the electronic invoice issuance, in compliance with the Municipality Tax Authority.

[Previous](https://developer.avalara.com/invoice_services_en/transactions/construction-sector)

[Next](https://developer.avalara.com/invoice_services_en/faqs/faqs)

> **Note**
>
> Part of the **E-Invoice for Services** integration guide. [Open the full "Functional review" milestone on Avalara](https://developer.avalara.com/invoice_services_en/functional_review/) to see every page in this section.