> 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/pos-transactions/reprint-bill.md).
# Reprint Bill
The **Bill Reprint** option is used to print a duplicate copy of an already generated bill. This feature helps users reprint bills when customers request another copy or when the original print is unclear or lost.
## Steps to View and Reprint a Bill
Step 1: Go to the **Point of Sale** module and select the **Transaction** menu.
1. Click on **Bill Reprint**.
* The Bill Reprint screen will appear.
Step 2: Choose the required **Outlet Name** from the list.
Step 3: Select the required **System Name** from the available list.
* The system name identifies the billing terminal or POS system from which the bill was generated.
Step 4: Click the **Display** button.
* The system will display the list of bills available for the selected outlet and system
Step 5: Choose the required bill from the displayed list.
* Verify the bill details carefully before proceeding.
Step 6: Enter the reason for reprinting the bill in the **Reprint Reason** field.
* Entering a valid reason helps maintain proper audit records.
Step 7: Click on the **Print** button.
* The selected bill will be reprinted successfully.
---
# 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/pos-transactions/reprint-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.
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)