# Planning your integration

Source: https://developer.avalara.com/invoice_services_en/before_you_begin/planning_your_integration/

# Planning your integration

This section provides an overview of the badge certification requirements for the **E-Invoice for Services** connector necessary to become a certified partner.

Review this section to help plan your integration.

**Advice:** Before starting your integration, it is important to scope out the requirements listed for this certification program.

Administration and utilities

The table below presents a list of requirements ranging from user experience to application best practices.

**Condition**

**Requirements**

**Notes**

**Level**

Mandatory

[Set up Avalara credentials](/invoice_services_en/user_experience/setup_credentials)

The best practice is to enhance the UI for easy entry of Avalara credentials including:

\- Client ID Token

\- Secret Token

UI

Mandatory

[Test authentication connection - ping the service](/invoice_services_en/user_experience/test_connection)

There is one method available for service availability/PING

UI

Mandatory

[Comprehensive logging](/invoice_services_en/user_experience/logging)

Given that all transactions are based on request/response JSON, the connector should provide logs of the transactions for troubleshooting, if necessary. Partners can define the time necessary to keep those data within the system

UI

Mandatory

[Select environment option](/invoice_services_en/user_experience/select_environment)

Provide environment option to allow the key user to switch between sandbox and production environment

UI

Suggested

[Electronic Invoice control panel](/invoice_services_en/user_experience/electronic_invoice)

Provide an electronic invoice issuance control cockpit, which allows the customer to consult an authorized electronic invoice, cancel an electronic invoice, perform a fixed letter, and other functions that are necessary to execute the electronic invoice issuance, in compliance with the Brazilian Tax Authority

UI

Mandatory

[Checking environment](/invoice_services_en/user_experience/check_environment)

Provide evidence that demonstrates which environment (production or sandbox) the client/partner is operating

UI

Suggested

[Set timeout for API calls](/invoice_services_en/user_experience/timeout_calls)

Set a timeout for the API calls, as per your best practices

Hide configuration

Mandatory

[API base URL](/invoice_services_en/user_experience/api_base)

The URLs should be system settings

Hide configuration

Mandatory

[Version](/invoice_services_en/user_experience/version-compatibility)

Inform the compatibility of the ERP version with the connector

Documentation

Mandatory

[User implementation guide](/invoice_services_en/user_experience/user-guide)

Your implementation must include a user guide that contains screenshots and steps describing how to configure the connector through Avalara's application.

Documentation

Mandatory

[Architecture](/invoice_services_en/user_experience/architecture)

Inform the connector architecture, as well as the prerequisites for operation, either on Premise or in the cloud

Documentation

Electronic Invoice Transactions (NFS-e)

The table below presents a list of Electronic Invoice (NFS-e) transactions.

**Condition**

**Scenarios**

**Transactions**

**Point of Attention**

Mandatory

[Service sales within origin company city](/invoice_services_en/transactions/service_sales_within_company)

Sales

Mandatory

[Services sales outside of the origin company city](/invoice_services_en/transactions/service_sales_out)

Sales

CEPOM ID

Suggested

[Export services](/invoice_services_en/transactions/export_services)

Sales

Mandatory

[Service sales with deductions](/invoice_services_en/transactions/service_sales_with_deductions)

Sales

Mandatory

[Construction sector](/invoice_services_en/transactions/construction-sector)

Sales

Different layout

[Previous](/invoice_services_en/before_you_begin/about_the_program)

[Next](/invoice_services_en/before_you_begin/additional_resources/swagger_doc)