> 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-view-the-nc-kot-report.md).

# How do I view the NC KOT report?

To view the Non-Chargeable (NC) KOT reports, you can access either a detailed view or a summarized view depending on your needs. Both reports are found within the Advance module,.

**NC KOT Details Report**

This report provides specific information for each NC KOT, including the item details, KOT number, covers, table number, bill number, cost and sales values, and user remarks.

1. Navigate to **Advance Reports > NC Kot Details.**
2. Select the desired Advance Filter options to define what information you want printed in the report.
3. Click on Display to generate the outlet-wise report.
4. Optional: You can convert this report into an Excel format by clicking the Excel icon.

**NC KOT Type – Summary Report**

Use this version if you need a consolidated view of Non-Chargeable KOTs categorized by their specific type.

1. Navigate to **Advance Reports > NC Kot Type – Summary.**
2. Choose your preferred Advance Filter options.
3. Click Display to view the summarized outlet-wise report.
4. **Optional:** This report can also be exported to Excel using the provided icon.


---

# 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-view-the-nc-kot-report.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.