# Get certified

Source: https://developer.avalara.com/products/communications/integration-guides/communications-integration/vtw2673204291324/

Guide: Communications

# Get certified

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

## 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](https://developer.avalara.com/erp-integration-guide/functional-review/submit-integration-for-review/erp-integration-guide/functional-review/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 integrations**

-   How you install or enable your integration
-   Configuration screen and authentication process
    -   Demonstrate inputting your credentials.
    -   Show that you have a test connection button, an option to disable document recording/committing, and an option to designate connecting to a Production or Sandbox environment.
    -   Show that your company code is defined.
-   How you configure company or seller settings
    -   Show how to specify the service class and business class.
    -   Show option for specifying whether a company has facilities.
    -   Show option for specifying whether a company is a franchise.
-   How you configure customer or buyer settings
    -   Show how to specify the sale type and the customer type.
    -   Show option for specifying whether a customer is a lifeline customer.
    -   Show how to define exemptions.
-   Show reporting fields
    -   Account reference (`acct`) - Recommended
    -   Customer reference (`custref`) - Recommended
    -   Invoice number reference (`invn`) - Required if in the seller system
    -   Billing period (`bpd`) - Required
    -   Currency code (`ccycd`) - Required
-   Transaction level settings
    -   Show that transactions can include T/S pairs, including the ability to set custom service types to support bundles.
    -   Demonstrate understanding of committed vs uncommitted transactions.
    -   Show that you can handle adjustments.
-   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 is reaching out to AvaTax for a tax calculation and when the system is going to record a transaction to Avatax for further reporting and remittance.
    -   The transaction scenarios can be the same scenarios from the prior Example transactions > Core requirement examples section.
-   Additional considerations
    -   Show that the proper HTTP Headers are being sent (assuming you’re leveraging REST v2 API).
    -   Show that a reasonable API request ratio is used during invoicing.

**VoIP integrations**

-   Transaction level settings
    -   Demonstrate bundling in transactions.
    -   Demonstrate specifying the number of lines and minutes in a transaction.
    -   Demonstrate the ability to specify a private line split percentage.
    -   Demonstrate passing single- and multi-channel lines in a transaction.
-   VoIP use cases
    -   Show examples of VoIP transactions. You can include the transactions listed in the Examples > VoIP section.

**International integrations**

-   Transaction level settings
    -   Demonstrate ability to pass international PCode values.
    -   Show that you can map international products to Avalara T/S pairs.
    -   Demonstrate calculating tax-included transactions
-   International use cases
    -   Show examples of International transactions. You can include the transactions listed in the Examples > International section.