# SRI Cases

### docAduaneroUnico ​ ​ 

This error pops up when the DAE, AWB, HAWB is not saved in that purchase order, it must be checked on the coordination page if the data is correctly entered.

<figure><img src="/files/k8YbttirdjMYBNtfJSpv" alt=""><figcaption></figcaption></figure>

If any data is missing, it can be entered by [PRE-AUTHORIZATIONS MODIFICATIONS](/accounting/sri-electronic-transfer/sri-electronic-management/pre-authorization-modifications.md), or the SRI DATA column of each SRI FACTURA in the SRI module.

### docCustomsUnique - is not facet-valid with respect to maxLength '20' for type 'docCustomsUnique' ​ ​&#x20;

<figure><img src="/files/sRJ7TQdSmqedWbuPNrpL" alt=""><figcaption></figcaption></figure>

This means that the SRI accepts only a maximum of up to 20 characters in that field, in the case of the example there are 21 characters.&#x20;

* The DAE must be corrected in the system&#x20;
* Regenerate the XML file and resubmit ​&#x20;

### Limite de Intentos NO AUTORIZADOS POR DIA&#x20;

When there is an error in a document, and we have not corrected yet, and it has been sent for authorization more than twice before the correction, a 24-hour block prevent us from trying to authorize the document again.&#x20;

In this case, we must wait to send the same document for authorization again ( detects the consecutive number and the password)&#x20;

Error message example:

*"LIMIT OF UNAUTHORIZED ATTEMPTS PER DAY The access key 0701202201019013194700120010030000498131234567811 has exceeded the daily limit allowed for an unauthorized voucher (2 attempts), for the date: Tue Jan 11 15:40:29 GMT-05:00 2022. Correct the errors and try again the next day"*&#x20;

### tipoIdentificacionComprador&#x20;

<figure><img src="/files/BnVxBsHEIN0yhSZGqNh9" alt=""><figcaption></figcaption></figure>

This error occurs because the SRI IDENTIFICATION, which is found in the ACCOUNTING tab of the manage clients form, is not specified in the form. ​ ​&#x20;

<figure><img src="/files/61jnQQ573hx9R4kUlMJ6" alt=""><figcaption></figcaption></figure>

RUC, CEDULA, Passport, Foreign Identification, Final Consumer Sale **must always be selected .**

### Error en Diferencia

When the calculated values ​​do not coincide with the values ​​reported in the XML, a difference error occurs, in which the total of the order plus freight (if any) is not equal to what the XML contains.

<figure><img src="/files/qffd9jBwBZrwD8PbVDlp" alt=""><figcaption></figcaption></figure>

In these cases, it commonly occurs because the species is not assigned in the SKU of that order, or if the SKU has more than 1 compound, it may be that there are fewer or more stems in the compound and at the time of calculation the sum does not match.&#x20;

## Error Lugar INCOTERM

This error occurs if a PO has been billed without information of **AWB**, **HAWB** or **DAE** of that information the COUNTRY, Airport cannot be determined.

{% hint style="info" %}
*"FILE DOES NOT MEET XML STRUCTURE The following error was found in the receipt structure: cvc-minLength-valid: Value '' with length = '0' is not facet-valid with respect to minLength '1' for type 'lugarIncoTerm'..."*
{% endhint %}

<figure><img src="/files/A6giRKqUNIWtk72bwSIg" alt=""><figcaption><p> </p></figcaption></figure>

Example:

<figure><img src="/files/ZklFPK5fJUQa9Z7wSFVF" alt=""><figcaption></figcaption></figure>

To solve it can be done through: SRI DATA, filling in the fields one by one, and press the SAVE SRI button.

### DETAILS, the details content is not complete&#x20;

{% hint style="info" %}
*"Se encontro el siguiente error en la estructura del comprobante: cvccomplex-type.2.4.b: The content of element 'detalles' is not complete. One of '{detalle}' is expected..."*
{% endhint %}

This error occurs when one or more SKUs of that order do not have a species defined in the SKU configuration. ​ ​ ​ ​ ​ ​

<figure><img src="/files/RaZ94lOhuJ4Rz0v1rivL" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/6go1a1qN539msvDyiH16" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/8svzqTOxBIbQRt0cMjfA" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://manual.unosofbooks.com/accounting/sri-electronic-transfer/sri-cases.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.