> 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/masters-1/outlet-budget.md).
# Outlet Budget
The **Outlet Budget** screen is used to configure and maintain budget details for outlets in the system. Using this screen, users can select the financial year, enter budget values, specify cover details, and save the budget configuration.
## Steps to Open Outlet Budget
Step 1: Navigate to the **Point of Sale** module and select **Masters1**.
1. Click on **Outlet Budget**.
* The Outlet Budget screen will open.
Step 2: In the Outlet Budget screen, click on the **Open** button.
* The budget configuration window will appear.
Step 3: Click on the **Year** icon or selection field
1. A list of available financial years will be displayed.
2. Select the required year for which the budget needs to be configured.
* Ensure the correct financial year is selected before entering the budget details.
Step 4: Enter Budget Information
1. After selecting the year, enter the required:
* **Budget Amount**
* **Covers**
* The Budget field is used to define the expected financial target for the outlet.
* The Covers field is used to specify the expected customer count or service covers.
Verify all entered values carefully before saving.
Step 5: Save the Configuration
1. After entering all required details, click on the **Save** button.
* The outlet budget details will be successfully saved in the system.
---
# 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/masters-1/outlet-budget.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.
