> 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-passing.md).
# Purchase Bill Passing
**Purchase Bill Passing** is the process of verifying, validating, and approving a supplier's purchase invoice against the corresponding Purchase Order (PO) and Goods Receipt. This process ensures the accuracy of invoice details and compliance with company policies before the bill is posted to the accounting system for payment.
## Steps to Perform Purchase Bill Passing
Step 1: Navigate to the **Transactions** menu in the **Bill Passing** module.
1. Click on **Purchase Bill Passing**.
* The **Purchase Bill Passing** screen will be displayed.
Step 2: The system will display a list of available receipts.
1. Select the required **Receipt** for which the supplier invoice needs to be processed.
* After selecting the receipt, proceed to the next step.
Step 3: Once the receipt is selected, the Purchase Bill Passing details screen will appear.
1. Ensure that the invoice details match the corresponding receipt and purchase order.
Step 4: After verifying all details, click the **Save** button.
* The system will validate the information and process the transaction.
---
# 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-passing.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.
