> For the complete documentation index, see [llms.txt](https://docs.rmhpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rmhpos.com/es/store-manager/manage-suppliers/viewing-supplier-invoices.md).

# Ver facturas de proveedores

Este tema describe cómo ver facturas de proveedores.

1. Haga clic en **Inventario/Compras**.
2. Realice una de las siguientes acciones:

* Si la factura sigue abierta, haga clic en **Factura**.
* Si la factura ya se contabilizó, en la **Historial** sección, haga clic en **Facturas contabilizadas**.

3. Realice una de las siguientes acciones:

* En el **Filtrar** área de la cinta, haga clic en **Agregar** y cree un filtro para controlar qué facturas se muestran en la lista.
* Haga clic en un encabezado de columna, como **Proveedor**, **N.º de factura**, o **Fecha de factura**, para ordenar los resultados de la lista y facilitar el desplazamiento hacia abajo y la búsqueda de la factura de proveedor deseada.

4. Haga doble clic en la factura de proveedor para abrirla.


---

# 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://docs.rmhpos.com/es/store-manager/manage-suppliers/viewing-supplier-invoices.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.