> 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/mr-audit-report.md).
# MR Audit Report
The **MR Audit Report** provides a detailed record of all **Material Requests (MR)** or **Store Indents** along with their operational status and transaction history.This report is primarily used for monitoring, tracking, and audit purposes, helping users review the complete life-cycle of material requests across a specific store or all stores within the organisation.
## Steps to View the MR Audit Report
Step 1: Navigate to the **Reports** menu in the **Inventory** module.
1. Select **MR Audit Report**.
* The MR Audit Report screen will be displayed.
Step 2: Click the **Advanced Filter** option.
* This filter help users retrieve specific audit records and generate more accurate reports.
Step 3: After selecting the required filter criteria, click the **Display** button.
* The system will generate and display the MR Audit Report.
Step 4: Print or Export the Report
1. Once the MR Audit Report is displayed, you can:
* Click the **Print** button to print the report.
* Click the **Excel** button to export and download the report in Microsoft Excel format.
---
# 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/mr-audit-report.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.
