> 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-transactions/approval.md).
# Approval
The **Approval** transaction is used to review and approve Purchase Requisitions or purchase-related requests created by users. This process ensures that all purchase requests are verified and authorized before further procurement activities are carried out.
## Steps to Approve a Purchase Request
Step 1: Go to the **Purchase** main menu.
1. Click **Transaction**.
2. Select **Approval**.
* After selecting the Approval option, the Approval screen will appear.
Step 2: The system will display the list of purchase requests or requisitions that are pending approval.
* Review the displayed details carefully before approving.
Step 3: Select the required purchase request(s) or item(s) that need approval.
* Ensure the selected requests are valid and authorized for processing.
Step 4: Click the **Approve** button located at the top-right corner of the screen.
* Once approved, the request status will be updated in the system and forwarded for further purchase processing.
---
# 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-transactions/approval.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.
