> 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/faq-on-transaction/how-can-i-reprint-a-bill.md).

# How can I reprint a bill?

To reprint a bill in the POS system, you must access the Bill Reprint tool within the transactions menu. Follow these specific steps:

1. **Navigate to the Menu:** Go to the Transaction Main Menu and click on Bill Reprint.
2. A**pply Filters:** Choose the correct outlet name and select the System name from the options provided on the screen.
3. **Select the Bill:** Click the Display button to load the list of bills, then select the specific bill you wish to reprint.
4. **Print:** You must enter a Reprint Reason before clicking the Print Button to generate the new copy.

**Monitoring Reprints**

For management and oversight, the system includes a Bill Reprint Audit report. This report tracks:

* The number of reprints taken for a particular bill.
* The specific user who performed the reprint.
* A distinction between the original billed date/time and the reprint date/time.

To view this audit, go to the reports section, select your outlet and date range, and apply any necessary user filters. This report can be printed directly or exported to Excel


---

# 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/faq-on-transaction/how-can-i-reprint-a-bill.md?ask=<question>&goal=<user_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.