> 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/proceso-de-facturacion/descripcion-del-flujo.md).

# Descripción del Flujo

### 1. Generación Documento ERP 

#### El ERP genera: 

* Factura  
* Boleta  
* Nota Crédito  
* Nota Débito  
* Guía  

### 2. Envío API 

El ERP consume: 

* REST API  
* SOAP Service  

Enviando: 

* JSON  
* XML  
* Datos tributarios  

### 3. Validaciones Iniciales 

La plataforma valida: 

* Campos obligatorios  
* Catálogos SUNAT  
* Totales  
* Impuestos  
* Estructura  

### 4. Generación XML UBL 

Se construye el XML oficial bajo estándar UBL 2.1. 

### 5. Firma Digital 

El XML es firmado utilizando: 

* Certificado digital  
* SHA256  
* Firma XMLDSig  

### 6. Envío OSE 

El documento es enviado al OSE para: 

* Validación tributaria  
* Validación estructural  
* Validación normativa  

### 7. Validación SUNAT 

SUNAT procesa: 

* Reglas tributarias  
* Consistencia  
* Autorización  

### 8. Recepción CDR 

El sistema recibe: 

* Aceptado  
* Rechazado  
* Observado  

### 9. Actualización ERP 

El resultado es retornado al ERP junto con: 

* XML  
* CDR  
* PDF  
* Hash  
* Estado  


---

# 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/proceso-de-facturacion/descripcion-del-flujo.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.