> 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/masters-1/sales-day-book-nc-kot-report-settings.md).
# Sales Day Book / NC KOT Report Settings
The **Sales Day Book / NC KOT Report Settings** screen is used to configure report settings for Sales Day Book and NC KOT reports in the system. Using this screen, users can select the required report type and save the settings for future report generation.
## Steps to Open Sales Day Book / NC KOT Report Settings
Step 1: Navigate to the **Point of Sale** module and select **Masters1**.
1. Click on **Sales Day Book / NC KOT Report Settings**.
* The report settings screen will open.
Step 2: In the Sales Day Book / NC KOT Report Settings screen, click on the **Open** button.
* The settings configuration window will appear.
Step 3: In the settings window, locate the **Report Type** section.
1. Select the required report type from the available options.
* The report type determines how the Sales Day Book or NC KOT report will be generated and displayed.
Step 4: View and Configure the Settings
1. After selecting the report type, the corresponding settings screen will appear.
2. Review the available configuration options carefully.
3. Modify the settings as required.
* Ensure all settings are properly configured before saving.
Step 5: Save the Configuration
1. After completing the required settings, click on the **Save** button.
* The report settings will be successfully saved in the system.
---
# 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/masters-1/sales-day-book-nc-kot-report-settings.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.
