> For the complete documentation index, see [llms.txt](https://videos.inforiver.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://videos.inforiver.com/reporting-matrix/planning-budgeting-and-forecasting/allocations.md).

# Allocations

With Inforiver, you can create plans & budgets in a few clicks. In this video, learn how you can 

(a) Enter at the organizational level and proportionally allocate them to its constituent products and geographies (top-down allocations) 

(b) Use various distribution options (such as driver-based or trend-based) to allocate high-level goals across business units, products, geographies, or time. E.g. costs to be allocated to various BUs based on headcount or sales. 

(c) Enter absolute values, scaled values (e.g. 5k), or increments in numbers (e.g. +2k) or percentages (+7%) 

(d) Export the entire data (to PDF or Excel)

{% embed url="<https://lumel.wistia.com/medias/thktibfcs7>" %}

> ## **Related resources**
>
> #### Feature highlights
>
> [Input and edit data in Power BI](https://inforiver.com/input-edit-data-powerbi/)
>
> #### User guide
>
> [Budgeting & allocations](https://docs.inforiver.com/working-with-inforiver/7.-planning-budgeting-and-forecasting/budgeting-and-allocations)
>
> #### Blog
>
> [5 types of manual data entry options in your Power BI table/matrix](https://inforiver.com/blog/writeback/5-types-manual-data-entry-powerbi-table-matrix/)


---

# 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://videos.inforiver.com/reporting-matrix/planning-budgeting-and-forecasting/allocations.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.