> 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/faq-on-advanced-reports/how-do-i-check-kot-audit-details.md).

# How do I check KOT Audit details?

To check KOT (Kitchen Order Ticket) Audit details, follow these steps within the POS system:

1. **Navigate to the Menu:** Go to **Advance Reports > Kot Audit.**
2. **Apply Filters:** Choose any additional options you want printed in the report. You can also sort the data based on your specific requirements.
3. **Generate the Report:** Click the display button to load the audit details.

**What the KOT Audit Provides**

This report is used to monitor the lifecycle of kitchen tickets and includes the following information:

* **Identification:** KOT number and the specific outlet name.
* **Timings:** The exact time of creation as well as timing for any amendments.
* **Amendments:** Specific details regarding changes made to the ticket, with the report clearly segregating old data from amended data.
* **Cancellations:** Details regarding any cancelled KOTs.


---

# 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/faq-on-advanced-reports/how-do-i-check-kot-audit-details.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.