> 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/fo-masters-revenue-creation.md).

# REVENUE

Steps to create Revenue master

**REVENUE CREATION**

Revenue is created in the software to store revenue sales happened through the software. Each of the revenue collected in the software can be created as per the revenue’s name. Revenue created holds the data of total value collected on a daily basis.

1.To create revenue in “FRONT OFFICE” go to “**FRONT OFFICE**” module MASTERS REVENUE

2\. Create the revenue required as shown in the below screenshot

![](https://4060887901-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2ktZUs9CJyincVDXEmrM%2Fuploads%2Fgit-blob-d6b73447a91533fe53f02ee820ecfac0a39f3b9b%2FScreenshot%202023-08-16%20144649.png?alt=media)

3.The revenues created here can be assigned with a tax structure which gets calculated when the corresponding transaction takes place

4.Revenues created here are applicable for all the modules of the software

5.Users can link the outlets

6.Click “**OPEN**” to amend any details of an existing revenue, and click ![](https://4060887901-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2ktZUs9CJyincVDXEmrM%2Fuploads%2Fgit-blob-bc0dfed6572f8ac189d2eb032013326045fa63ea%2F1%20\(41\).png?alt=media) to select the revenue

7.Click ![](https://4060887901-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2ktZUs9CJyincVDXEmrM%2Fuploads%2Fgit-blob-0b1eed8a340d828a739446ba698cfa4cb29f2eb3%2F10%20\(7\).png?alt=media) once changes are made


---

# 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/fo-masters-revenue-creation.md?ask=<question>&goal=<user_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.