> 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/bill-passing/transactions/purchase-bill-approval.md).
# Purchase Bill Approval
**Purchase Bill Approval** is the formal authorisation process in which a verified purchase invoice is reviewed and approved by an authorised user before it is posted for payment in the accounting system. This approval ensures that the invoice has been properly verified and complies with organisational policies and procedures.
## Steps to Perform Purchase Bill Approval
Step 1: Navigate to the **Transactions** menu in the **Bill Passing** module.
1. Click on **Purchase Bill Approval**.
* The **Purchase Bill Approval** screen will be displayed.
Step 2: The system will display a list of purchase bills that are pending approval.
1. Select the required **Purchase Bill** based on your requirement.
* After selecting the purchase bill, review the details before proceeding with the approval.
Step 3: Once the purchase bill details have been verified, click the **Save** .png?alt=media)button.
* The system will process the approval and update the status of the purchase bill.
---
# 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/bill-passing/transactions/purchase-bill-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.
