> 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/kot-reprint-audit.md).
# KOT Reprint Audit
The **KOT Reprint Audit** report is used to monitor and review instances where Kitchen Order Tickets (KOTs) have been reprinted. This report helps ensure that KOT reprints are properly authorized and used only for genuine operational requirements.
## Steps to View KOT Reprint Audit
Step 1: Navigate to the **Point of Sale** module and click the **Advanced Reports** menu.
1. Select **KOT Reprint Audit**.
* The KOT Reprint Audit screen will open.
Step 2: Apply Sorting Options
1. Use the available **sorting options** based on your requirement.
2. Select the necessary filters to organize the report data.
These options help users generate a more accurate and customized report.
Step 3: Generate the Report
1. After selecting the required options, click on the **Display** button.
2. The system will generate and display the **KOT Reprint Audit Report**.
The report will show all KOT reprint details for review and analysis.
* If you want to export the report to Excel:
1. Click on the **Excel Export Icon** available on the report screen.
2. The report will be downloaded in Excel 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/point-of-sale/point-of-sale-module/advanced-reports/kot-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)
