> 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/point-of-sale/point-of-sale-module/advanced-reports/bill-reprint-audit.md).
# Bill Reprint Audit
The **Bill Reprint Audit Report** is used to track and monitor how many times a bill has been reprinted by users in the system. It provides a detailed audit of reprint activities for accountability and control.
## Steps to View Bill Reprint Audit Report
Step 1: Navigate to the **Point of Sale** module and click the **Advanced Reports** menu.
1. Select **Bill Reprint Audit**.
* The Bill Reprint Audit screen will open.
Step 2: Choose the required **Outlet** from the drop-down list.
* This ensures the report is generated for the correct outlet.
Step 3: Enable the **“User All”** checkbox if you want to filter specific users.
1. Select the required users from the list.
This helps you view reprint activity for selected users only.
Step 4: Select Date Range
1. Select the **From Date**.
2. Select the **To Date**.
This defines the period for which the report will be generated.
Step 5: Generate the Report
1. After applying all filters, click on the **Display** button.
2. The system will generate the **Bill Reprint Audit Report**.
* To **print the report directly**, click the **Print** option.
* To **save the report in Excel format**, click the **Excel Export Icon**.
---
# 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/point-of-sale/point-of-sale-module/advanced-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.
