> 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-material-receipt.md).
# Material Receipt
Steps to perform a material request reprint
A **Material Receipt Note (MRN)** is a document used to record the receipt of materials from a supplier into the inventory system. It serves as proof that the ordered materials have been received and accepted at the designated inventory location.
## Steps to Create a Material Receipt
Step 1: Navigate to **Transactions** in the **Inventory** module.
1. Select **Material Receipt**.
* The Material Receipt screen will be displayed.
Step 2: Click **Add** button.
* Fill the following details:
1. In the **Basis** field, select the appropriate receipt basis.
2. In the **PO Type** field, select the required Purchase Order type.
3. In the **PO Number** field, choose the Purchase Order against which the materials are being received.
* These details will help the system identify the corresponding Purchase Order and the materials to be received.
Step 3: Once the Purchase Order is selected, the available PO items will be displayed.
1. Select the required Purchase Order item(s) to be received.
Step 4: Click the **Save** button.
* The Material Receipt Note (MRN) will be created and saved successfully in the system.
---
# 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-material-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.
