> 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/reports/bill-reprint-audit.md).
# Bill Reprint Audit
The **Bill Reprint Audit Report** is used to track all bill reprints performed in the system. This report helps management and auditors monitor reprinted bills, identify the user who performed the reprint, and maintain proper audit control.
## **Steps to View Bill Reprint Audit Report**
Step 1: Log in to the system and navigate to the **Banquet Module**.
1. Click on the **Reports** menu.
2. Select **Bill Reprint Audit** from the list of available reports.
Step 2: After selecting **Bill Reprint Audit**, the system will open the report page.
* By default, the system displays the report based on a **predefined day/date range**.
* This view shows all bill reprint activities recorded within the selected period.
Step 3: Click on the **User** option.
* Select the required user from the list to filter the report based on a specific user.
Step 4: After selecting the user and verifying the date range, click on the **Display** button.
* The system will generate and display the **Bill Reprint Audit 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/banquet/banquet-module/reports/bill-reprint-audit.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)
