# What do I include in the demo?

Source: https://developer.avalara.com/avatax-for-vat/xmp4868000397457/

# What do I include in the demo?

Learn what to include in your integration demo to meet requirements.

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.
-   Your configuration screen and authentication process, including:
    -   Demonstrate inputting your credentials.
    -   Show that your integration includes:
        -   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 defined a company code.
-   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 you send to AvaTax as the item code and description.
    -   Show that you can map items to Avalara tax codes in the platform.
-   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 AvaTax for tax calculation and when the system records a transaction to AvaTax for further reporting and remittance.
    -   Sales tax transaction scenarios:
        -   For ERP and ECom integrations:
            -   [B2B domestic sale](https://developer.avalara.com/vat-erp/test-transactions/core-vat/b2b-domestic-sale)

            -   [B2C distance sale](https://developer.avalara.com/vat-erp/test-transactions/core-vat/b2c-distance-sale)

            -   [B2C sale into the EU where the buyer is the importer of record](https://developer.avalara.com/vat-erp/test-transactions/core-vat/b2c-sale-into-eu-buyer-is-ior)

            -   [B2B domestic sale](https://developer.avalara.com/vat-erp/test-transactions/core-vat/b2b-domestic-sale)

            -   [Domestic reverse charge sale](https://developer.avalara.com/vat-erp/test-transactions/core-vat/domestic-reverse-charge-sale)

            -   [Intracommunity supply](https://developer.avalara.com/vat-erp/test-transactions/core-vat/intracommunity-supply)

            -   [Export](https://developer.avalara.com/vat-erp/test-transactions/core-vat/export)

            -   [B2C digital services sale intra EU](https://developer.avalara.com/vat-erp/test-transactions/core-vat/b2c-digital-services-sale-intra-eu)

            -   [B2C digital services sale into the EU](https://developer.avalara.com/vat-erp/test-transactions/core-vat/b2c-digital-services-sale-into-eu)

            -   [B2B services rendered outside of the EU](https://developer.avalara.com/vat-erp/test-transactions/core-vat/b2b-services-rendered-outside-of-eu)

        -   For marketplace integrations:
            -   [Avalara client as a marketplace](https://developer.avalara.com/vat-marketplace/test-transactions/avalara-client-as-a-marketplace-example)

            -   [Avalara client as a merchant](https://developer.avalara.com/vat-marketplace/test-transactions/avalara-client-as-a-merchant)

-   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 the `SalesInvoice` document type and that you don't call AvaTax multiple times for the same invoice.
    -   Confirm that orders/estimates use a document type of `SalesOrder`, `PurchaseOrder`, and so on.