> 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/banquet/banquet-module/queries/pending-bills.md).
# Pending Bills
The **Pending Bills** feature is used to view all unpaid or pending bills in the system. This report helps users monitor outstanding payments and generate reports for billing follow-up and financial tracking.
## Steps to View Pending Bills
Step 1: Navigate to the **Banquet** module and select **Queries** menu.
1. Click on **Pending Bills**.
* After selecting the menu, the **Pending Bills** screen will be displayed.
Step 2: On the **Pending Bills** screen, click the **Display** button.
1. The system will retrieve and display the list of all pending bills.
* The report will show the outstanding billing details available in the system.
Step 3: After the pending bills report is displayed, the report screen will appear.
1. Click one of the following buttons to generate the report:
* **Print** – To print the pending bills report.
* **Excel** – To export the report in Excel format.
The report will be generated in the selected 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/banquet/banquet-module/queries/pending-bills.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.
.png?alt=media)
.png?alt=media)
.png?alt=media)