> 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/analysis/faq-on-analysis/how-to-find-the-po-item-rate-variance.md).

# How to find the PO Item Rate Variance?

PO Item Rate Variance refers to the difference between the rate (price) of an item specified in a purchase order (PO) and its agreed or standard rate. This tool is primarily used by the purchasing department to identify pricing discrepancies, track cost variations, or monitor changes in supplier pricing.To view and analyze these price differences in the system, follow these steps:

1. Go to the Purchase main menu.
2. Click on **Analysis > Po Item Rate Variance.**
3. Click on the Item Search icon to find and select the product you want to analyze.
4. Use the Advance Filter option to refine your search criteria.
5. Click the Display button to load the variance report on your screen.

If you want to perform further data analysis or share the details, you can download the report in Excel format by clicking the Excel button.


---

# 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/analysis/faq-on-analysis/how-to-find-the-po-item-rate-variance.md?ask=<question>&goal=<user_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.