> 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/store-manager/manage-suppliers/viewing-supplier-invoices.md).

# View supplier invoices

This topic describes how to view supplier invoices.

1. Click **Inventory/Purchasing**.
2. Do one of the following:

* If the invoice is still open, click **Invoice**.
* If the invoice was posted, in the **History** section, click **Posted Invoices**.

3. Do one of the following:

* In the **Filter** area of the ribbon, click **Add** and build a filter to control which invoices are displayed in the list.
* Click a column heading, such as **Supplier**, **Invoice No.**, or **Invoice Date**, to sort the results in the list to make it easier to scroll down and find the desired supplier invoice.

4. Double-click the supplier invoice to open it.


---

# 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/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.
