> 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/banquet/banquet-module/queries/pending-kot-charges.md).

# Pending KOT/Charges

The **Pending KOT/Charges** feature is used to view all pending Kitchen Order Tickets (KOT) and pending charges that have not yet been settled or billed. This report helps users track outstanding food orders and additional charges efficiently.

## Steps to View Pending KOT/Charges

Step 1: Navigate to the **Banquet** module and select **Queries** menu.

1. Click on **Pending KOT/Charges**.

* After selecting the menu, the **Pending KOT/Charges** screen will be displayed.

<figure><img src="https://4060887901-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2ktZUs9CJyincVDXEmrM%2Fuploads%2Fgit-blob-5b667c661594b1d8f8b920026e4cbc23958944fd%2FScreenshot%20From%202026-05-19%2010-44-30.png?alt=media" alt=""><figcaption></figcaption></figure>

Step 2: On the **Pending KOT/Charges** screen, click the **Display** button.

1. The system will retrieve and display the list of all pending KOTs and charges.

* The displayed report will contain details of unsettled food orders and pending charges available in the system.

<figure><img src="https://4060887901-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2ktZUs9CJyincVDXEmrM%2Fuploads%2Fgit-blob-9cc66b909fffe59191e0a5cf22c8ad13d5922d79%2FScreenshot%20From%202026-05-19%2010-46-17.png?alt=media" alt=""><figcaption></figcaption></figure>


---

# 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/banquet/banquet-module/queries/pending-kot-charges.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.
