> 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-transactions/mm-transactions-receipt-return.md).
# Receipt Return
Steps to perform a Material Receipt Return
**Receipt Return** is the process of returning received materials or products back to the supplier. This transaction is used when materials are damaged, defective, incorrectly supplied, excess in quantity, or no longer required.
## Steps to Perform a Receipt Return
Step 1: Navigate to **Transactions** in the **Inventory** module.
1. Select **Receipt Return**.
* The Receipt Return screen will be displayed.
Step 2: Locate the **Basis** field.
1. Select the appropriate basis for the receipt return from the available options.
Step 3: Click on the **Vendor Name** field.
1. Select the vendor to whom the materials are being returned.
* Confirm that the correct vendor and materials have been selected for return.
* Ensure that the returned quantities do not exceed the quantities originally received.
Step 4: After verifying all details, click the **Save** button.
* The Receipt Return document will be created successfully, and the inventory records will be updated accordingly.
---
# 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-transactions/mm-transactions-receipt-return.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.
.png?alt=media)