# Returned erors

Source: https://developer.avalara.com/invoice_services_en/errors/error_returns/

# Returned erors

Unlike the common [HTTP](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes "https://en.wikipedia.org/wiki/List_of_HTTP_status_codes") error codes mentioned in the [previous section](/invoice_services_en/errors/api_error_handling),  when your company is calling us to issue an electronic invoice for services, the errors returned come from the municipality webservice. They are responsible for validating the business rules related to the sent file.

As each municipality may have its own return code and rule, we list the most common ones in the table below, which may help in the mapping.

More information about returned error codes is [available here](https://desenvolvedores.migrate.info/2016/03/codigos-de-retorno-para-nfs-e/).

**Error code**

**Description**

**100 - RPS Completed and Converted to NFS-e** 

Upon obtaining this status, it is only possible to cancel the NFS-e. Another action can not be performed.

**101 - NFS-e Canceled**

In this situation no more action is taken.

**104 and 105 - Pending and Processing Document**

In this case, you should consult the document to get the processing status of the RPS.

**110 - Denied Document**

The document was denied, due to tax irregularity of any of the CNPJs present in the document (Issuer, Recipient, Sender, Taker).

**111 - Duplicate Document**

This RPS will not be sent, as it is already in completed status ins the city hall system. A new RPS with a valid number must be sent, which has not yet been sent to the city hall system.

**204 - Document in Conflict:**

The documents are in the status In conflict, because at the time of issuance there was a failure in communication with the city hall, and as the city hall does not control this numbering, it is necessary to check if this RPS already exists in the base from the city hall before resubmitting it.

**999 - Rejected + Rejection Message Returned by the Municipality**

The action to be taken in this case must be the correction as oriented in the return message and resubmission of the document.

[Previous](/invoice_services_en/errors/api_error_handling)

[Next](/invoice_services_en/concepts/e_invoice_scenario)