> 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/eventos-del-proceso-de-emision.md).

# Eventos Del Proceso De Emisión

## Anulación 

Evento que consiste en anular un documento electrónico. El mismo solamente puede ser solicitado por el emisor de la FE; por este motivo, la solicitud debe ser firmada utilizando un certificado digital. 

Serán rechazados los pedidos de anulación de FE si: 

1. El Numero de Autorización del documento a anular no coincide con ningún DTE registrado y vigente en la SAT, si tiene asociado uno o más DTE del tipo “NDEB”, “NCRE”, “CIVA” o “CAIS” con estado Vigente.  
2. El NIT Emisor no coincide con el que aparece registrado en la SAT de acuerdo con el valor de la casilla “Número de Autorización del Documento a Anular 
3. El ID Receptor no coincide con el que aparece registrado en la SAT de acuerdo con el valor de la casilla “Número de Autorización del Documento a Anular 
4. La fecha de emisión del documento a anular no coincide con la registrada en la SAT. 
5. La fecha de anulación excede la fecha de vencimiento del período de la declaración mensual del IVA al que corresponde el documento a anular. 


---

# 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/eventos-del-proceso-de-emision.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.