Get certified

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.

To initiate a functional review:

Check that you’ve completed all the required milestones.
Contact your assigned technical resource by email and copy dg-partnerlaunch@avalara.com.

Avalara will schedule a recorded functional review call with you, during which you’ll demonstrate your integration's functionality as described below.

What to include in your demo

Include all requirements mentioned in the previous chapters in your integration.

During the functional review call, you should answer or demonstrate the following.

Installation and setup

How do you install or enable your integration?

Demonstrate how a user can perform the following tasks:

What dependencies or prerequisites are required to use your integration?
Where can a user (prospect or customer) access the user guide for your integration?

Configuration screen and authentication process:

Demonstrate how a user can complete the following actions:

View the configurations between ELR Sandbox and Production environments.
Set up Avalara API credentials.
Test an authentication connection.
- Verify success with valid credentials.
- View error messages with invalid credentials.
Enable or disable the integration.

Administration and utilities

Company Management screen and authentication process

Demonstrate how a user can complete the following tasks:

Map existing Avalara companies to your application legal entities.
Add a legal entity from your application to Avalara (via your integration).

Mandate Configuration

Demonstrate how a user can perform the following actions:

Set the logic or decision matrix used to determine when a countryMandate is used for a given document for a specific company or entity.

Selects the countryMandate from a dynamic list, powered by the GetMandates method.
Configure the frequency or event that triggers the mandate configuration logic process for an active document or aggregate report.
Shown the status of the activation process related to that mandate configuration:
- Enable a mandate configuration when activation status is Completed.
- Disable a mandate configuration until the activation status is Completed.

Document mappings

Demonstrate how a user can perform the following tasks:

View the default mappings that you have built for the integration.
View a list of the Required, Conditional, or Optional data input (UBL) fields for a given countryMandate.
Clone, edit, and save their own custom mapping.

Access guidance in the user guide for mapping customization.
Apply a custom mapping to a specific (or multiple) countryMandate processes.
Use responseKey and responseValue pairs in a UBL credit note mapping through a transformation function.

Document lifecycle management

Demonstrate how a user can trigger or configure the process to perform the following actions:
- Submit an invoice through the countryMandate GB-B2B-PEPPOL to a customer with a Peppol ID that will be communicated to you on the call (while testing, simply send to yourself)
  
  View the status, event messages and responseKey and responseValue pairs
- Be able to receive an ApplicationResponse document and display the new status on the related outbound document (for example, Rejected or Approved)
- Submit a credit note which credits the 1st invoice and includes the stored value of the "Receipt Message ID" responseKey in a ubl-creditnote field of your choice
- Be able to receive an inbound purchase document*
- Send an ApplicationResponse document approving a received inbound document*
- Import an inbound document into ERP (mapped from UBL to ERP format)*
- Downloads and stores all available formats for an outbound document and makes them to another system that could:
  - Attach it (application/xml or application/pdf) to an email and send the email
  - Include (application/png) as part of a PDF template
*Demonstrate how a user can import an inbound document into ERP (mapped from UBL to ERP format)
*Demonstrate how a user can configure the frequency at which an automated process for importing inbound documents can run

* Only applicable if your business system supports AP (purchase documents)

Server audit clarity

Demonstrate how a user can perform the following actions:

What "X-Avalara-Client" header value are you passing in each request to the ELR service?
Demonstrate how a user can access API logs that would result in an analysis of potential server-side errors
How long are the API logs persisted?

Our Partner Launch team will review all evidence submitted according to the orientation in this previous section, and get back to you with feedback as soon as possible.

Avalara E-Invoicing and Live Reporting

Get certified