> For the complete documentation index, see [llms.txt](https://docs.rillet.com/EjmEP4KZ9BVp9j2ho4Mh/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rillet.com/EjmEP4KZ9BVp9j2ho4Mh/reporting/budget-vs-actual/upload-a-budget-to-rillet.md).
# Upload a Budget to Rillet
Uploading a budget file into **Rillet** populates the baseline for the **Budget vs Actual** report, enabling real-time variance analysis, accountability across departments, and proactive budget management. You can upload up to 25 active budgets, such as your original plan alongside one or more forecasts, and select which one to use in the **Budget vs Actual** report, the **Income Statement**, and **Flux Analysis**.
### Upload Your Budget File
Follow these steps to upload a budget from a file, using the provided template to align with **Rillet**'s format and minimize upload errors:
{% hint style="warning" %} **Warning:**
Enter revenue and expenses as positive amounts in the template, matching how they appear on the **Income Statement**. Use negative amounts only for reductions, such as refunds or credits. Getting the sign backwards on any account throws off every report that uses this budget, including the **Budget vs Actual** report, the **Income Statement**, and **Flux Analysis**.
{% endhint %}
1. Click your **company logo** in the lower-left corner of the screen.
2. Go to **Organization Settings**.
3. Open **Reporting**, then scroll to **Budget Upload** at the bottom of the page.
4. **(Optional):** Click **Download template** to get a sample CSV file.
5. Fill out the template with your budget data, making sure each row includes the following fields:
* **Account:** Budget account code (e.g., "A0001").
* **Vendor:** Name of the vendor.
* **Department:** An optional field for the department responsible, which you can leave blank.
* **Monthly Amounts:** One column per month of the fiscal year (e.g., Jan 2025, Feb 2025) with the planned budget for that month, entered as a positive amount unless it is a reduction such as a refund or credit.
* **Field {field\_name}:** An optional custom or additional field, with the placeholder name replaced by your actual custom field's name.
6. Return to the **Budget Upload** section and click **Upload additional budget**.
7. Enter a **Budget name** to identify this version in the **Add budget** dialog, then choose your CSV file.
8. Click **Create and upload** to complete the process.
{% hint style="info" %} **Note:**
Custom fields appear in the template only if they have been configured in **Settings > Custom Fields**. The actual field names you define replace `{field_name}` in the template. If your organization has multiple entities in **Rillet**, see [**Budgets vs Actual for Multi-Entity Organizations**](/EjmEP4KZ9BVp9j2ho4Mh/multi-entity/subsidiaries/budget-vs-actual-for-multi-entity-organizations.md) for how uploads work across subsidiaries.
{% endhint %}
You can also define custom budget fields, such as Category, Phase, or Cost Type, in your system settings. Once configured, they appear as optional columns in the upload template, and your data becomes immediately available in the **Budget vs Actual** report for grouping and filtering as soon as you upload.
Rillet counts each active budget against a limit of 25 across all years, treating a budget that spans multiple years as one toward that limit and excluding archived budgets entirely. Use the **Show archived** checkbox on the Budget Upload screen to view or restore a previous version.
### Frequently Asked Questions (FAQ)
How should I enter revenue in the budget file?
Enter revenue and expenses as positive amounts, the same way they appear on the **Income Statement**. Use negative amounts only for reductions, such as refunds or credits applied against that revenue or expense.
What happens if I upload a new budget file?
Uploading a new file adds it as a separate budget version alongside any existing ones, up to 25 active budgets. Give each version a distinct **Budget name** so you can tell them apart when selecting a version in a report.
Can I upload more than one budget version?
Upload your original plan and one or more forecasts as separate named versions, then select which version to use when viewing the **Budget vs Actuals** report, the **Income Statement**, or **Flux Analysis**.
### See Also
To learn more about budgeting in **Rillet**, review these articles:
* [**Review the Budget vs Actual Report**](/EjmEP4KZ9BVp9j2ho4Mh/reporting/budget-vs-actual/review-the-budget-vs-actual-report.md)
* [**Understand Budget vs Actual Groupings**](/EjmEP4KZ9BVp9j2ho4Mh/reporting/budget-vs-actual/understand-budget-vs-actual-groupings.md)
* [**Fix Budget Upload Errors and Replace Existing Data**](/EjmEP4KZ9BVp9j2ho4Mh/reporting/budget-vs-actual/fix-budget-upload-errors-and-replace-existing-data.md)
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.rillet.com/EjmEP4KZ9BVp9j2ho4Mh/reporting/budget-vs-actual/upload-a-budget-to-rillet.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 `build a script that syncs our docs to a CMS` 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.
