> 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/reports/purchase-bill-receipt.md).
# Purchase Bill Receipt
**Purchase Bill Receipts** are the records of goods or services that have been physically received and acknowledged against a purchase bill. These records confirm that the items billed by the supplier have been delivered and accepted by the organisation. This report is used for verification, stock reconciliation, and audit purposes.
## Steps to View Purchase Bill Receipts
Step 1: Navigate to the **Reports** menu in the **Bill Passing** module.
1. Click on **Purchase Bill Receipts**.
* The **Purchase Bill Receipts** screen will be displayed.
Step 2: Select the required **Purchase Type** from the available options.
* Ensure all selected filters are correct before proceeding.
Step 3: Click the **Display** button.
* The system will generate and display the Purchase Bill Receipts report based on the selected criteria.
Step 4: Once the report is displayed, click the **Excel** button.
* The system will download the report in excel format.
---
# 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/reports/purchase-bill-receipt.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.
