> 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-link-revenues-to-an-outlet.md). # How do I link revenues to an outlet? To link revenues to a specific outlet, you must use the **Outlet Revenue** master tool. This allows you to group one or more revenues under a single outlet for more efficient charging. **Steps to Link Revenues to an Outlet** 1. **Navigate to the Menu:** Go to the **FRONT OFFICE** module, select **MASTERS**, and then click on **OUTLET REVENUE**. 2. **Access the Master:** Click the **OPEN** button. 3. **Select the Outlet:** Choose the desired outlet from the **Outlet ID** drop-down menu. 4. **Add the Revenue:** 1. Click the **search icon** under the revenue heading to find and select the corresponding revenue. 2. To link **additional revenues** to the same outlet, click the **plus icon (+)** to add a new row and repeat the search process. 5. **Configure Sales Type:** If you want the revenue to be available for **miscellaneous sales** (bills for non-staying guests), ensure you enable the corresponding checkbox for that row. 6. **Remove a Link:** If you need to remove a revenue from the outlet, click the **delete icon** next to the specific revenue row. 7. **Finalize:** Click the **edit/save icons** to confirm and save your changes. Once linked, these revenues will automatically appear under the selected outlet name when you are posting **Guest Charges** or performing **Miscellaneous Sales**.
--- # 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-link-revenues-to-an-outlet.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.