> 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-the-kot-type.md). # How do I check the KOT type? To check the KOT type, you can use several reports within the system that explicitly include this information as part of their data view. **1. Bill Audit Report** The Bill Audit report allows you to view the KOT type along with bill numbers, steward details, items, amounts, and transaction timings. * **Navigation:** Go to **Advance Reports > Bill Audit.** * **Action:** Apply any necessary sorting and click Display to view the report. **2. Bill Split Audit Report** Similar to the standard Bill Audit, the Bill Split Audit is specifically designed for split transactions and includes the KOT type for each entry. * **Navigation:** Go to **Advance Reports > Bill Split Audit.** * **Action:** Click Display to load the report after applying any required filters. **3. Non-Chargeable (NC) KOT Reports** If you are specifically looking for the type of Non-Chargeable KOT, you can use the following specialized reports: * **NC KOT Details:** This provides the specific NC KOT type for individual tickets, along with item details, table numbers, and user remarks. * **Navigation: Advance Reports > NC Kot Details.** * **NC KOT Type Summary:** This is a consolidated report that summarizes transactions categorized by NC KOT type. * **Navigation: Advance Reports > NC Kot Type – Summary.** **Configuration of KOT Types** If you need to define or manage these categories, the system provides setup menus in the Master settings: * **Creating NC KOT Types:** You can define new types (including Type ID and Name) by navigating to **Master1 > NC KOT Type.** * **Report Settings:** You can configure settings for how these types appear in reports via **Master1 > Sales DayBook / NC KOT Report Settings** --- # 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-the-kot-type.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.