> 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/pasos-para-habilitarse-en-facturacion-electronica.md).

# Pasos Para Habilitarse En Facturación Electrónica

### Ambiente de Calidad 

1. Completar y entregar documentación de implementación de proyectos FASE I (GS-PLI-FR004 formato interno de GuruSoft) 
2. Entregar o confirmar que se tiene el certificado de firma electrónica. 
3. Confirmar que se ha acreditado al Certificador ante la SAT 
4. Proporcionar logo de la empresa o indicar si no lo utilizan en su pdf. 
5. GuruSoft expedirá las credenciales en ambiente de calidad (QA) 

### Ambiente de Producción 

1. Confirmar que se ha acreditado al Certificador ante la SAT 
2. Entregar el certificado de firma electrónica. 
3. Completar el documento de implementación de proyectos hasta la FASE II – PASE A PRODUCCIÓN (GS-PLI-FR004 Formato interno de GuruSoft) 
4. Certificación set de pruebas, escenarios de facturación en ambiente de Calidad, mediante el documento de control de pruebas satisfactorias por empresa. 
5. Expedición de credenciales en ambiente productivo por parte de GuruSoft 


---

# 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/pasos-para-habilitarse-en-facturacion-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.