> For the complete documentation index, see [llms.txt](https://wikiedoc.guru-soft.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wikiedoc.guru-soft.com/gt/proceso-de-facturacion/manejo-de-secuenciales.md).

# Manejo De Secuenciales

En FEL Guatemala no existen rangos de facturas preautorizados por la SAT como ocurría con las facturas en papel. Cada Documento Tributario Electrónico (DTE) recibe sus identificadores en el momento de la certificación. 

## ¿Cómo funcionan los secuenciales? 

El emisor genera desde su ERP o sistema el XML, este es transmitido al certificador FEL, el certificador valida el documento y si todo está correcto devuelve el documento firmado con la asignación de los siguientes valores identificadores del DTE: 

| Campo      | Descripción                                          | Ejemplo                              |
| ---------- | ---------------------------------------------------- | ------------------------------------ |
| Serie      | Agrupador de documentos asignado por el certificador | A123BCD                              |
| Número FEL | Consecutivo dentro de la serie                       | 12548                                |
| UUID       | Identificador único global de la factura             | 4C1D7B0A-XXXX-XXXX-XXXX-XXXXXXXXXXXX |

## ¿Quién controla el consecutivo? 

#### Existen dos niveles: 

| Tipo de Secuencial     | Responsable      | Uso                                                             |
| ---------------------- | ---------------- | --------------------------------------------------------------- |
| Secuencial interno ERP | Empresa          | Número de documento interno de la factura en el ERP del cliente |
| Serie y Número FEL     | Certificador FEL | Identificación fiscal oficial ante SAT                          |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://wikiedoc.guru-soft.com/gt/proceso-de-facturacion/manejo-de-secuenciales.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.