> 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/banquet/banquet-module/masters/plan-item.md).
# Plan Item
The **Plan Items** master is used to create and manage banquet plans. Users can define plan details such as plan ID, plan name, rate, tax structure, and revenue group mapping. These plans are used for banquet booking, billing, and financial management.
## **Steps to Create Plan Items**
Step 1: Log in to the system and navigate to the **Banquet Module**.
1. Click on the **Masters** menu.
2. Select **Plan Items** from the available options.
Step 2: After selecting **Plan Items**, the system will open the Plan Items master screen.
Step 3: Click on the **New** button.
1. A new entry screen will appear.
2. Enter the required details such as:
* **Plan ID**
* **Plan Name**
* **Rate**
* **Tax Structure**
Ensure that all mandatory fields are entered correctly before proceeding.
Step 4: After entering the plan details, select or link the appropriate **Revenue Group**.
* The revenue group mapping helps maintain accurate accounting and financial tracking for the plan item.
Step 5: Once all required information has been entered and the revenue group has been linked, click on the **Save** button.
* The system will save the Plan Item 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/banquet/banquet-module/masters/plan-item.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)
