> 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/pending-receipts-for-bill.md).
# Pending Receipts For Bill
**Pending Receipts for Bill** refers to the quantity or value of goods or services that have been ordered and billed but have not yet been physically received or recorded in the system. This report helps users track pending deliveries against a purchase bill and ensures proper monitoring of outstanding receipts.
## Steps to View Pending Receipts for Bill
Step 1: Navigate to the **Reports** menu in the **Bill Passing** module.
1. Click on **Pending Receipts for Bill**.
* The **Pending Receipts for Bill** report screen will be displayed.
Step 2: Once the screen is opened, the system will display filter options.
* These filters allow users to refine the report based on requirements.
Step 3: Select the required **Type** from the available options.
1. Select the appropriate **Store** based on user requirement.
2. Ensure all selected filters are correct before proceeding.
Step 4: Click the **Display** button.
* The system will generate and display the Pending Receipts for Bill report based on the selected criteria.
Step 5: Once the report is displayed, click the **Print** button.
* The system will generate a printable version of the report.
---
# 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/pending-receipts-for-bill.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.
