> For the complete documentation index, see [llms.txt](https://help.rbsgo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rbsgo.com/material-management/material-management-module/mm-reports/mm-reports-receipt-list.md).
# Receipt List
Steps to view to receipt list
The **Receipt List Report** provides a comprehensive list of all **MRN (Material Receipt Note)** and **GRN (Goods Receipt Note)** transactions recorded in the system.
This report enables users to view received items either **Store-wise** or as a **Consolidated Report** for a selected period. Additional information such as **Supplier Name**, **Bill Number**, **Receipt Date**, and other transaction details can also be viewed.
## Steps to View the Receipt List Report
Step 1: Navigate to the **Reports** menu in the **Inventory** module.
1. Select **Receipt List**.
* The **Receipt list** screen will be displayed.
Step 2: Click the **Report Type** drop-down.
1. Choose the required report type based on your reporting needs.
Step 3: Click the **Advanced Filter** option available on the screen.
* Select the required filter criteria according to your reporting requirements.
Step 4**:** Select the required **filter options.**
1. You can filter the report by **Product**, **Product Group**, and other available criteria, as shown below.
Step 5: After selecting the required filter options, click the **Display** button.
* The system will generate and display the filtered Receipt List Report.
---
# 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://help.rbsgo.com/material-management/material-management-module/mm-reports/mm-reports-receipt-list.md?ask=&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.
