Appearance
Scenario workspace
PlanningScenariosScenario workspacePermission:
planning.scenario.viewAlso known as
- budget version
- driver-based
- drivers
- plan lines
- formula
- recalculate
- P&L plan
- submit budget for approval
- publish budget
- copy scenario
The workspace is where you build a scenario: plan lines by account and month, the drivers that formula lines use, and the resulting P&L. From here you submit the scenario for approval and publish the approved budget to Finance.
The header shows the number, kind, fiscal year and entity, and Calculated {when} (or Not calculated). The side panel shows the Stage rail, Totals (revenue, cost of sales, gross profit, operating expenses, net income) and Details: code, Source (how the scenario started, with its adjustment) and Finance budget once published. Attachments and the activity feed are below.
Enter amounts on the Plan tab
The Plan tab lists one line per P&L account, grouped by section (revenue, cost of sales, operating expenses, other income, other expenses), with a subtotal per section and a column per month, the Total and Last year.
- Input lines have a box per month: type the amount.
- Formula lines (marked Formula) are calculated from drivers and other lines. Turn on Show formulas to see the formula under the account.
- Type amounts in the input cells. The header shows {count} unsaved cells.
- Select Save cells. The message Saved appears.
- If drivers or inputs changed, the banner "Inputs changed since the last calculation. Recalculate to update the formula lines." appears. Select Recalculate. The message Recalculated {count} formula lines appears.
Amounts use the natural sign: revenue and expenses are both positive. Net income = revenue − cost of sales − operating expenses + other income − other expenses.
Add or change a plan line
- Select Add account (or select an account name in the grid to edit its line).
- Fill in the dialog and select Save. Remove line deletes the line (not possible while a formula uses it).
| Field | What to enter | Required / default |
|---|---|---|
| Account | A P&L account without a line yet (revenue or expense, posting accounts). | Required |
| Method | Input (amounts typed per month) or Formula (calculated each month). | Input |
| Formula | With Formula: the expression, for example units_furniture * price_furniture. The dialog lists the drivers and accounts the formula uses. | Required for a formula line |
| Notes | Why the line has this value. | Optional |
Formula language
A formula is evaluated once per month of the fiscal year.
| You write | It means |
|---|---|
12, 1250.5, 5% | Numbers (5% is 0.05). |
units, price | Driver codes of the scenario: the driver's value for the month, else its default. |
[4100] | The plan amount of account 4100 in the same month. |
month, wf_cost, wf_headcount | Built-ins: fiscal month 1–12; workforce plan cost and headcount of the month. |
+ - * / ^, < <= > >= == != | Arithmetic and comparisons (a comparison gives 1 or 0). |
min(), max(), abs(), round(x, digits), if(cond, a, b), safediv(a, b) | Functions. safediv gives 0 when b is 0. |
prev(units, 1), prev([4100], 12) | A driver, built-in or account n months earlier. |
actual([4100]), ly([4100]) | The actual of the same month, or of the same month last year. |
Examples: [4100] * cogs_pct / 100, ly([6100]) * 1.03, wf_cost. Unknown drivers, accounts without a line, division by zero and lines that refer to themselves (directly or in a loop) are errors; saving checks the formula and Recalculate names the line that failed.
Maintain drivers
Drivers are the assumptions behind formula lines: headcount, units, prices, growth rates. The Drivers tab lists them with a value per month and the Total.
- Select Add driver, or the pencil on a driver row to edit it (Delete driver removes one that no formula uses).
- Fill in the dialog and select Save.
- Type monthly values in the grid, select Save cells, then Recalculate.
| Field | What to enter | Required / default |
|---|---|---|
| Code | The name used in formulas, for example units_sold: lower-case letters, digits and _, starting with a letter. Built-in names (month, wf_cost, wf_headcount) are not allowed. Renaming a code that formulas use is refused. | Required |
| Name | A readable name. | Required |
| Kind | headcount, units, price, growth pct, rate, amount or other. | other |
| Unit | For example pcs, USD, %. | Optional |
| Default | Used for months without a value. | 0 |
| Description | How the driver is set. | Optional |
Read the P&L
The P&L tab shows the plan as a statement: revenue, cost of sales, gross profit, operating expenses, operating income, other income and expenses and net income by month. To print or send it, open the More actions menu (⋯) and select P&L PDF (by quarter).
Copy a scenario
Permission:planning.scenario.manage- Select Copy scenario.
- Enter Name, optionally Code and Kind, the Adjustment % for input amounts and, under Driver adjustments %, a percentage per driver code ("Applied to the copied driver values and defaults").
- Select Copy scenario. The message Copy {number} created appears; open the copy from the list.
The copy takes the drivers, lines, formulas and the workforce plan and is recalculated. Use it to build the optimistic and pessimistic cases from the base.
Submit, approve and publish
Save your cells and recalculate, then select Submit for approval (not possible while cells are unsaved).
⚑ Approval
Submitting starts the approval workflow for Planning scenario. When a rule in Approval rules matches, the scenario waits In review for the approver, who acts in Approvals or on the scenario (Approve in the header, Reject in the ⋯ menu). When no rule matches, the scenario is approved at once. Users with Permission:
planning.scenario.approvecan also approve an in-review scenario that has no pending request.While In review, the submitter can Recall it from the ⋯ menu (back to Draft); an approver can Reject it (back to Draft) or Approve it.
When Approved, select Publish to finance budget (Permission:
planning.scenario.publish). Every non-zero line × month is written to the finance budget for the entity and year with the version = the scenario's code, created or replaced, and approved. The message Published to finance budget {budget} appears. A scenario without amounts cannot be published.After changes, Reopen the scenario (back to Draft), edit, approve again and select Republish to finance.
Publishing does not post to the ledger: it fills the finance budget used by budget-vs-actual reports and budget checks.
Statuses
| Status | Meaning | What you can do next |
|---|---|---|
| Draft | Being prepared; the only editable status. | Edit, Recalculate, Submit for approval, Copy scenario, Archive, Delete scenario (drafts that were never published). |
| In review | Waiting for approval. | Approve, Reject (approver); Recall (planner). |
| Approved | Approved budget. | Publish to finance budget, Reopen, Archive. |
| Published | Written to the finance budget. | Republish to finance, Reopen, Archive. |
| Archived | Retired, read-only. The stage rail shows it as stopped. | — |
A non-draft scenario shows "This scenario is {status}. Reopen it to change the plan." Delete scenario asks to confirm: "This deletes the draft scenario {number} with its drivers, lines and workforce plan."
Differences by role
- Finance (demo) holds all planning permissions.
- Permission:
planning.scenario.manageedits drafts, copies, submits and recalls;Permission:planning.scenario.approveapproves, rejects, reopens and archives;Permission:planning.scenario.publishpublishes. View-only users see the grid without input boxes.
Related
- Scenarios
- What-if: compare this scenario with others (What-if in the header)
- Workforce: the positions behind
wf_cost(Workforce in the header) - Variance: the primary scenario against actuals
- Budgets
- Close and report
- Approvals, Documents and their states, Attachments, Audit trail
