# Requirements for certify calculation for services transactions

Source: https://developer.avalara.com/certification/avatax/services-calculation/

Requirements for certify calculation for services transactions

### Introduction

The connector certification requirements for services calculations are designed so that the end-user has a simple implementation process.        

 There are options to obtain certification on sales and purchase transactions.        

 The partner will need to define if they desire to implement one or both transaction types.

   Below are the minimum scenarios necessary for certification.        

### Premises

The partner can be certified at any time, but will only be considered "Launched" to the market, after two customers in production using the connector.

  The partner will be responsible for support customers in production and give the maintenance of the developed connector.

 The partner will be responsible for providing training and a guide to support customers.  

 To present an SLA (Service Level Agreement) plan.

 Present a schedule detailing development times, unit tests, and integration tests. 

 We inform the importance of our partners complying with the rules and determinations of the General Data Protection Law - LGPD (Law No. 13,709), not disclosing or exposing customer data.        

### Services Transaction

# Sales Transaction

|Mandatory Suggested | Scenarios | Transactions | Point of Attention || --- | --- | --- | --- |
|Mandatory | Service Sales Within Origin Company City | Sales |  |
|Mandatory | Services Sales Out of Origin Company City | Sales | CEPOM ID |
|Suggested | Export Services | Sales |  |
|Suggested | Service Sales with Deductions | Sales |  |

### Purchase Transaction        

|Mandatory Suggested | Scenarios | Transactions | Point of Attention || --- | --- | --- | --- |
|Suggested | Service Purchase with Deductions | Purchase |  |
|Mandatory | Services Purchase Out of Origin Company City | Purchase | CEPOM ID |
|Mandatory | Services Purchase Within Origin Company City | Purchase |  |

### Minimum Taxes        

Connectors needing certification will need to be able to prepare to receive and process the list of taxes below:

-   ISS
-   ISS-RF
-   IRRF
-   IRPJ
-   PIS
-   PIS-RF
-   COFINS
-   COFINS-RF
-   CSLL
-   CSLL-RF
-   INSS-RF
-   INSS-CPRB
-   APPROXIMATE VALUE OF TAXES - MUNICIPALITY
-   APPROXIMATE VALUE OF TAXES – FEDERAL

### Mandatory requirements to get the certification.        

As a user, I will navigate to one place on the application, and I should be able to:

|Mandatory Suggested | Use Cases | Notes || --- | --- | --- |
|Mandatory | Setup Avalara Credentials | The best practice is to enhance the UI for easy entry of Avalara credentials including: -   Client ID Token -   Secret Token -   Avalara end point URL |
|Mandatory | Test Authentication Connection - Heath Service (PING) | There are two methods available: -   One for authentication /AUTH -   another for service availability /PING |

|Suggested | Enable/Disable Service Utilization | In this case, the user can enable or disable the AvaTax BR service at any time. The flag will indicate that the service is operational. |
|Mandatory | Comprehensive Logging | Given that all transactions are based on request/response JSON, the connector should provide logs of these transactions for troubleshooting, if necessary. Partners can define the time necessary to keep those data on the system. |
|Mandatory | Set the timeout to API calls | Set a timeout to API call, as recommended by best practices. |
|Mandatory | Security Communication Protocol – HTTPS/SLL | The platform (ERP´s, middleware’s, e-commerce, etc.) that will be the API calls should be prepared to support TLS 1.2. Previous versions will be discontinued and are not recommended. |
|Mandatory | Checking Environment | Provide evidence that demonstrates which environment (Production or Sandbox) the client/partner is operating |
|Mandatory | Version | Inform version compatibility with the ERP with the connector. |
|Mandatory | Architecture | Inform the connector architecture, as well as the prerequisites for operation, either on Premise or in the cloud. |
|Mandatory | Namespaces – SAP | Exclusive for partners who will develop a connector for SAP ERP, it is mandatory to have a reserved domain within the SAP system, which must be active and licensed. |