> 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/nc-kot-charge-to-accounts.md).
# NC KOT Charge To Accounts
The **NC KOT Charge to Account** screen is used to create and manage charge-to account details for NC KOT (Non-Chargeable Kitchen Order Ticket) transactions.\
Using this screen, users can define a Charge ID and Charge Name, which can be used for accounting and billing purposes.
## Steps to Open NC KOT Charge to Account
Step 1: Navigate to the **Point of Sale** module and select **Masters1**.
1. Click on **NC KOT Charge to account**.
* The NC KOT Charge to Account screen will open.
Step 2: In the NC KOT Charge to Account screen, click on the **New** button.
* A new entry form will appear to create a charge account.
Step 3: Enter Required Information
1. Enter the following details in the respective fields:
* **Charge To ID**
* **Charge To Name**
Ensure the details are entered correctly before saving.
Step 4: After entering all required information, click on the **Save** button.
* The NC KOT Charge to Account details 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/nc-kot-charge-to-accounts.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.
