> 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/front-office-module/fo-masters/faq-on-masters/how-do-i-create-a-new-revenue-master-in-front-office.md).
# How do I create a new revenue master in Front Office?
To create a new Revenue Master in the Front Office module, which is used to store and track the total value of sales collected through the software, follow these steps:
1. **Navigate to the Menu:** Go to the **FRONT OFFICE** module, select **MASTERS,** and then click on **REVENUE**.
2. **Enter Revenue Details:** Create the revenue entry as required for your property's needs.
3. **Assign Tax Structure:** You can assign a specific tax structure to each revenue item. This ensures that taxes are automatically calculated whenever a corresponding transaction takes place.
4. **Link Outlets:** You have the option to link specific outlets to the revenue item within this master.
5. **Finalise:** Click the **Save** icon to store the new revenue.
**Key Features of the Revenue Master**
* **Universal Applicability:** Once a revenue is created in the Front Office masters, it is applicable for use across all modules of the software.
* **Modifying Existing Entries:** If you need to change details for a revenue that has already been created, click the **OPEN** button, select the revenue you wish to amend, make your changes, and then click the **Save** icon.
---
# 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/front-office-module/fo-masters/faq-on-masters/how-do-i-create-a-new-revenue-master-in-front-office.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.
