Functional review

Congratulations! At this point, you’ve completed all previous milestones. If you’re a technology partner, you’re now 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.

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.

• 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:

    • B2B domestic sale

    • B2C distance sale

    • B2C sale into the EU where the buyer is the importer of record

    • B2B domestic sale

    • Domestic reverse charge sale

    • Intracommunity supply

    • Export

    • B2C digital services sale intra EU

    • B2C digital services sale into the EU

    • B2B services rendered outside of the EU

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

POS integrations

Input VAT integrations

• Demonstrate support for import and goods place or service rendered addresses.

• Demonstrate that users can specify to defer VAT.

• Transaction scenarios along with doc codes. You can show the scenarios from the Test transactions > Input VAT examples section.

  • B2B domestic purchase

  • Domestic reverse charge purchase

  • B2C distance sale with transport starting outside of the EU

  • Import sale

  • Import purchase

  • Intracommunity acquisition

  • Import VAT deferment

Triangulation integrations

• Demonstrate support for triangulation scenarios.

• Demonstrate support for middleman VAT IDs and for the goods place or services rendered address.

• Transaction scenarios along with doc codes. You can show the scenarios from the prior Test transactions > Triangulation examples section.

  • Middleman purchase

  • Middleman sale

  • End-customer purchase

  • Party A VAT ID sale (optional)

  • Party C VAT ID purchase (optional)