> 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-reports-2/pending-kot.md).
# Pending KOT
The **Pending KOT (Kitchen Order Ticket)** report displays all KOTs that have been created but are not yet billed. Each KOT is shown along with its corresponding food items that have been punched into the system.
## Steps to View the Pending KOT Report
Step 1: Navigate to the **Point of Sale** module and click the **Reports** menu.
1. Select **Pending KOT**.
* The Pending KOT report screen will appear.
Step 2: Before viewing the report, select the required details:
1. Choose the **Date**.
2. Select the **Outlet**.
3. Select the **Session** if required.
* These filters help generate the report based on specific requirements.
Step 3: After selecting the required filters, click on the **Display** button.
1. The system will display all pending KOTs.
Step 4: To view whether serve instructions have been added to the KOT, tick the **Serve Instructions** checkbox.
1. The report will display the related instructions along with the KOT details.
* This helps kitchen and service staff identify special instructions for orders.
Step 5: To print the Pending KOT report directly, click on the **Print** button.
1. The report will be sent to the configured printer.
Step 6: To convert and save the report in Excel format, click on the **Excel Export** button.
---
# 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-reports-2/pending-kot.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.
