> 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/pe/integraciones-y-servicios/catalogo-de-codigos/sunat/09-codigos-de-tipo-de-nota-de-credito-electronica.md).

# 09 - Códigos de tipo de nota de crédito electrónica

<table><thead><tr><th width="95">Código</th><th>Descripción</th></tr></thead><tbody><tr><td>01</td><td>Anulación de la operación</td></tr><tr><td>02</td><td>Anulación por error en el RUC</td></tr><tr><td>03</td><td>Corrección por error en la descripción o atención de reclamo respecto de bienes adquiridos o servicios prestados
<br>Corrección por error en la descripción y/o código de producto SUNAT</td></tr><tr><td>04</td><td>Descuento global</td></tr><tr><td>05</td><td>Descuento por ítem</td></tr><tr><td>06</td><td>Devolución total</td></tr><tr><td>07</td><td>Devolución por ítem</td></tr><tr><td>08</td><td>Bonificación</td></tr><tr><td>09</td><td>Disminución en el valor</td></tr><tr><td>10</td><td>Otros Conceptos</td></tr><tr><td>11</td><td>Ajustes de operaciones de exportación</td></tr><tr><td>12</td><td>Ajustes afectos al IVAP</td></tr><tr><td>13</td><td>Corrección o modificación del monto neto pendiente de pago y/o la(s) fechas(s) de vencimiento del pago único o de las cuotas y/o los montos correspondientes a cada cuota, de ser el caso</td></tr></tbody></table>


---

# 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/pe/integraciones-y-servicios/catalogo-de-codigos/sunat/09-codigos-de-tipo-de-nota-de-credito-electronica.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.