> 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/pos-transactions/pos-transactions-bill.md).
# Billing
Steps to create a bill
Billing is the second process in the **Point of Sale (POS)** system after generating a **KOT (Kitchen Order Ticket).**In the software, the **Bill** option is referred to as **“CHECK”**.
* Once the KOT is created, the user can proceed with bill generation and settlement.
## Steps to Create a Bill (CHECK)
Step 1: First, create the required **KOT** for the selected table.
1. Ensure all ordered items are entered correctly before proceeding to billing.
Step 2: After creating the KOT, return to the table selection screen.
1. Click on the required **Table Number** for which the bill needs to be generated.
Step 3: On the KOT screen, click on the **CHECK** button located at the bottom of the screen.
Step 4: After clicking **CHECK**, the system will redirect you to the **Billing Screen**.
1. Verify all bill details carefully before proceeding.
Step 5: At the bottom of the billing screen, click on the **Print** option.
Step 6: Click on the respective **Table Number**.
Step 7: Choose the required **Settlement Mode** based on the customer’s payment method.
* After selecting the payment method, click on **SETTLE** button.
* The system will complete the billing process successfully.
---
# 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/pos-transactions/pos-transactions-bill.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.
