> 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-analysis/supplier-wise-receipt.md).
# Supplier Wise Receipt
The **Supplier Wise Receipt** report provides a detailed record of goods, materials, or services received from suppliers, organised supplier-wise. It captures information such as received quantities, delivery dates, purchase order references, receipt numbers, and other relevant transaction details.
## Steps to View the Supplier Wise Receipt Report
Step 1: Navigate to the Analysis menu in the Inventory module.
1. Select **Supplier Wise Receipt**.
* The **Supplier Wise Receipt** screen will be displayed.
Step 2: After opening the report page, apply the necessary filters to generate the desired report.
* The report supports multiple filters, allowing users to customise the information according to their business requirements.
1. Use the Funnel Filter
* The **Funnel Filter** allows users to further refine the report by applying specific search criteria.
Step 3: After selecting the required filters and grouping options, click **Display** button.
* The system will display the Supplier Wise Receipt report based on the selected criteria.
---
# 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-analysis/supplier-wise-receipt.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.
