Reference & Data Model
Budget request (budget_request)
A budget request is an application for additional budget for a cost item; it is decided, never deleted.
Purpose
Section titled “Purpose”The Budget request documents additional need with amount and justification (project data). It hangs off the budget of a cost item and is evaluated at project, program and portfolio level.
Where in the app
Section titled “Where in the app”- Create: budget plan › context menu of the cost item „Neues Budget anfragen“ (Request new budget) or detail view › section „Budgetanfragen“ (Budget requests) › „+“ („Neue Budgetanfrage“).
- Decide: admins and owners decide in the inbox or directly on the request by approving or rejecting. The dialog „Budgetantrag“ (Budget application; double-click or link icon) shows the request; the status dropdown is gone. Tabs „Alle“ (All), „Genehmigt“ (Approved), „Offen“ (Open), „Abgelehnt“ (Rejected), „Zurückgezogen“ (Withdrawn) with a total per tab.
- Portfolio › „Budget“ › sub-view „Budgetanfragen“: all requests with project and cost item, decidable from there. Program › „Budget“: columns „Genehmigt“ and „Beantragt“ (Requested) per project.
- See Guides › Submit & decide a budget request.
Fields
Section titled “Fields”| Field | Technical | Type | Required | Meaning | Notes |
|---|---|---|---|---|---|
| Budget to request / Requested | requested_value |
Amount | yes | Requested amount | only by amending while the request is open |
| Request description / Label | description |
Text | yes (may be empty) | Justification | only by amending while the request is open |
| Status | state |
Display | yes | see States | set only by the decision |
| Requested on | requested_at |
Date | yes | Date of the request | System: current date at creation |
| Answered on | answered_at |
Date | no | Date of the last status change | System |
Relations
Section titled “Relations”| Related to | Kind | Required | On archive | On delete |
|---|---|---|---|---|
| Budget | belongs to | yes | – | deleted along |
Via the budget, the request is assigned to the cost item and thus to the project; the portfolio list resolves this chain.
States
Section titled “States”| Value | Label | Color | Set by |
|---|---|---|---|
open |
Offen (tab) / offen (badge) | blue | System at creation |
approved |
Genehmigt | green | Decision |
rejected |
Abgelehnt | red | Decision |
withdrawn |
Zurückgezogen | grey, row dimmed | Withdrawal or expiry after 14 days |
A request leaves „Offen“ exactly once. There is no way back to „Offen“. For a new outcome, submit a new request or amend the open one.
Rules & automation
Section titled “Rules & automation”- Effect of approval: with approval, Aligia increases the budget of the cost item by the requested amount in one step. Rejection, withdrawal and expiry do not change the budget. See Rule: budget request.
- Expiry: a request that stays open for 14 days shows as „Zurückgezogen“.
- Amend: an open request can be amended. It is then replaced, and earlier answers no longer count.
- Reverse: an approved request is reversed by a new request with the negated amount. It needs its own approval.
- No deletion: requests stay stored permanently in an audit-proof manner. The note below the form reads: „Nach Erstellung einer Budgetanfrage ist ausschließlich ein Zurückziehen möglich. […] Der Datensatz bleibt dauerhaft revisionssicher gespeichert.“ (After creating a budget request, only withdrawal is possible. The record remains permanently stored in an audit-proof manner.)
- „Beantwortet am“ is set when the decision is made.
Requested = Σ of all requests (including rejected and withdrawn); approved = Σ of approved requests; card „Beantragtes Budget“ (Requested budget) with share „freigegeben“ (released); portfolio card „Budgetanfragen“. See Budget KPIs.
See also
Section titled “See also”Budget · Guides › Plan the portfolio budget · Guides › Monitor the program budget