# Functional review

Source: https://developer.avalara.com/avatax-dm-combined-erp/functional-review/

# Functional review

Congratulations! At this point, you've completed all previous milestones, and you're 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 along with the user guide 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 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
        -   An option to disable address validation (if supported)
        -   An option to designate connecting to a Production or Sandbox environment
    -   Show that you have enabled logging
    -   Show that your company code is defined.
-   How you identify customers
    -   Show how you pass the customer identifier.
    -   Show how you exempt a customer.
-   How you identify products/services and associate tax codes
    -   Show what is sent over to AvaTax as the item code and description.
    -   Show that items can be mapped to AvaTax tax codes in the platform.
-   The AvaTax 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 Sales and Use Tax transaction scenarios:
    -   [Tax amount scenario](/avatax-dm-combined-erp/sales-tax-badge/transactions/test-tax-amount)
    -   [Discounts scenario](/avatax-dm-combined-erp/sales-tax-badge/transactions/test-discounts)
    -   [Entity use codes scenario](/avatax-dm-combined-erp/sales-tax-badge/transactions/test-entity-use-code)
    -   [Refunds scenario](/avatax-dm-combined-erp/sales-tax-badge/transactions/test-refunds)
-   The Document Management scenarios
    -   [Create a customer record](/avatax-dm-combined-erp/document-management/dm-use-cases/test-create-customer-record)
    -   [Retrieve a customer's exemption status](/avatax-dm-combined-erp/document-management/dm-use-cases/test-retrieve-exemption-status)
    -   [Request a new certificate](/avatax-dm-combined-erp/document-management/dm-use-cases/test-request-certificate)
    -   [Update a customer record](/avatax-dm-combined-erp/document-management/dm-use-cases/test-update-customer-record)
-   Additional considerations
    -   Show that the proper HTTP Headers are being sent (assuming you’re leveraging REST v2 API).
    -   Show that an address validation filter-by-country option is provided or that address validation requests are limited to only North America.
    -   Show that a reasonable API request ratio is used during invoicing.
    -   Sales invoices or requests that use document type `SalesInvoice` should not call AvaTax multiple times for the same invoice.
    -   Confirm that orders/estimates, etc. use a document type of `SalesOrder`.

[Previous](/avatax-dm-combined-erp/document-management/dm-faqs)