> 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/purchase/purchase-module/purchase-reports/po-audit-report.md).
# PO Audit Report
The **PO Audit Report** is used to review and verify Purchase Orders (POs) to ensure accuracy, compliance, and proper authorization.
## **Steps to View PO Audit Report**
Step 1: Navigate to the **Purchase** main menu from the dashboard.
1. Click on **Reports**.
2. From the Reports menu, select **PO Audit Report**.
* After clicking **PO Audit Report**, the report screen will open.
Step 2: Select the required **PO Type** from the available options.
* The PO Type helps users filter the report based on different categories of purchase orders.
Step 3: Click on the **Advanced Filter** option available on the screen.
* The Advanced Filter helps users refine the report using specific search criteria.
Step 4: Click on the **Display** button.
* The system will generate and display the **PO Audit Report** based on the selected filters.
Step 5: To download the report, click on the **Excel** button.
* The report will be downloaded in **Excel format** for further analysis and audit documentation.
---
# 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/purchase/purchase-module/purchase-reports/po-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.
