> 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/nc-kot-type-summary.md).
# NC KOT Type Summary
The **NC KOT Type – Summary** report provides a consolidated summary of all Non-Chargeable (NC) KOT transactions categorized by NC KOT type. This report helps users analyze NC KOT activities in a summarized format for better monitoring and reporting.
Using this report, users can generate outlet-wise NC KOT summary reports and review the total count and values associated with each NC KOT type.
## Steps to View the NC KOT Type – Summary Report
Step 1: Navigate to the **Point of Sale** module and click the **Advanced Reports** menu.
1. Select **NC KOT Type – Summary**
* The **NC KOT Type – Summary** report screen will open.
Step 2: Select Advanced Filter Options
* Users can apply advanced filters based on their reporting requirements before generating the report.
Step 3: After selecting the required filter options, click the **Display** button.
1. The system will generate the **NC KOT Type – Summary Report**.
---
# 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/nc-kot-type-summary.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.
.png?alt=media)