15.6 Budget Planning Framework, Organization Hierarchies & Planning Processes
Key Takeaways
- Scenarios, stages, workflow stages, allocation schedules, priorities, columns, and layouts are all defined on the Budget planning configuration page; stage rules are not.
- An organization hierarchy must carry the Budget planning purpose, and be published with an effective date, before a budget planning process can select it.
- Each budget planning process binds exactly one budget cycle, one ledger, and one organization hierarchy.
- A budget planning process is activated from Actions > Activate and cannot be used until it has been.
- Plan visibility needs both a Budget clerk, contributor, or manager role and, per legal entity, an organization grant made with Grant with children.
15.6 Budget Planning Framework, Organization Hierarchies & Planning Processes
Quick Summary: Basic budgeting records a number that has already been decided, and budget control polices spending against it. Budget planning is the collaborative process that produces the number in the first place. Microsoft added Configure and manage budget planning as a brand-new skill group on the August 14, 2026 MB-310 blueprint, and one of its two bullets is explicitly "Configure budget planning process, including organization hierarchy." Expect scenario items in which a hierarchy, a workflow, or a process refuses to behave, and you must name the one missing configuration step.
1. The Budget planning configuration page
Almost every reusable building block lives on a single page: Budgeting > Setup > Budget planning > Budget planning configuration. Each tab produces an artifact that a budget planning process later consumes.
| Tab | What you define there | Why the exam cares |
|---|---|---|
| Parameters | The Security model for budget plans, plus the default financial dimensions used when a user drills into a plan amount | Choosing Based on security organizations is what makes hierarchy-driven access work at all |
| Scenarios | Named containers for one version of budget data — monetary (Previous year actuals, Budgeted) or quantity-based (FTE count, Number of sales calls) | Every allocation moves data from a source scenario to a destination scenario |
| Stages | The ordered steps a plan travels through, such as Initial, Submitted, CFO review, Final | Stages exist independently and are then arranged inside a workflow |
| Workflow stages | The budget planning workflow: an ordered set of stages plus the budgeting workflow that moves plans between them | Recommended practice is one budget planning workflow per level of the budgeting hierarchy |
| Allocation schedules | Reusable source-scenario-to-destination-scenario allocation definitions | Six allocation methods are available (detailed in 15.7) |
| Stage allocations | Bind an allocation schedule to a workflow and a stage so that it fires automatically during workflow processing | Only works if the budgeting workflow contains the Budget planning stage allocation automated task |
| Priorities | Optional categories, objectives, and ranking numbers — for example Health and safety | Priorities are selected on plans and constrained on the process |
| Columns | Budget plan columns: a scenario, optionally filtered to a period and to ledger accounts | The default ceiling is 36 columns, and it can only be raised by extending the budget planning layout |
| Layouts | The grid itself — a ledger dimension set supplies the rows, columns are added as elements, and each element is flagged editable or read-only | Generating the Excel template locks the layout, so finish the layout first |
High-value trap: stage rules are not on this page. Which stages permit Add lines and Modify lines is defined per process, on the budget planning process record itself. That separation is deliberate: one shared set of scenarios and stages can be reused by several processes that grant completely different permissions.
A second setup detail worth remembering: the Budget planning query optimization for performance feature in the Feature management workspace (under Budgeting) speeds up the Publish action when a user pushes many edited rows back from Excel, and Microsoft recommends turning it on.
2. The organization hierarchy behind a plan
Budget planning borrows the Organization administration hierarchy engine to decide two things at once: how plan amounts aggregate upward and distribute downward, and who may see which plan.
+---------------------------------------------------------------------------+
| Budget planning organization hierarchy |
+---------------------------------------------------------------------------+
| [ CFO / Executive committee ] |
| (consolidated parent plan) |
| | |
| +----------------------+----------------------+ |
| | | |
| [ VP Operations ] [ VP Commercial ] |
| | | |
| +------+------+ +-------+-------+ |
| | | | | |
| [ 020 IT ] [ 021 Mfg ] [ 030 East ] [ 031 West ] |
| child plan child plan child plan child plan |
+---------------------------------------------------------------------------+
Aggregate = children roll UP into the parent plan
Distribute = parent pushes targets DOWN into the child plans
Configuration rules that scenario questions key on:
- Assign the Budget planning purpose. On the Organization hierarchies page choose Assign purpose, select the Budget planning purpose, select Add, and attach your hierarchy. (The same purpose list is reachable at Organization administration > Organizations > Organization hierarchy purposes.) A hierarchy without that purpose never appears in the budget planning process lookup, no matter how correctly it is drawn.
- Assign the Security purpose as well when you intend to drive plan access from the hierarchy. Microsoft's own walkthrough assigns both the Budget planning purpose and the Security purpose to the same hierarchy.
- Publish it. Draw the nodes in the Hierarchy designer, then choose Publish and Close and supply an effective date. A hierarchy that exists only as a draft has no published version for a process to bind to.
- One hierarchy per process. Only one organization hierarchy can be assigned to each budget planning process.
- It need not mirror operations. The budgeting hierarchy exists to aggregate and distribute money, so it commonly groups departments differently from the operational org chart.
3. User security for budget plans
Access is a two-layer test, and candidates routinely fix only one layer.
- Role. To open the Budget plan page a user must hold Budget clerk, Budget contributor, or Budget manager.
- Organization. Set Security model to Based on security organizations on the Parameters tab, then in System administration > Users > Users select the user's role, choose Assign organizations, select Grant access to specific organizations, pick the node, and use Grant with children to cascade access down the branch.
Organization security is applied per legal entity, so the grant must be repeated in each company that participates in the plan. A department manager granted at node 020 sees only the IT plan; the VP granted with children at the Operations node sees every child plan beneath it.
4. Building and activating the budget planning process
The process (Budgeting > Setup > Budget planning > Budget planning process) is the container that binds everything together.
| Field or FastTab | Setting |
|---|---|
| Budget planning process | Identifier, e.g. DEMF budgeting FY2026 |
| Budget cycle | Exactly one cycle per process |
| Ledger | Exactly one ledger per process |
| Default account structure | The structure used for new plan lines |
| Organization hierarchy | The published, Budget-planning-purposed hierarchy |
| Budget planning process administration | Assigns a budget planning workflow to every responsibility center in the grid; Assign workflow bulk-applies one workflow to an organization type |
| Budget planning stage rules and layouts | Per stage: allow Add lines, allow Modify lines, and the default layout; Alternate layouts exposes extra layouts |
| Budget plan priority constraints | Optional list of priorities selectable on plans |
Activation is the final step, and it is a menu action, not a status field. Choose Actions > Activate; a budget planning process cannot be used until it has been activated. Two other commands on the same menu matter in practice: copying an existing process to seed next year's cycle, and View budget process status, which graphically shows every plan in the process with its workflow status, amount and unit summaries, and one-click navigation into the plan.
Exam traps in this section
- Hierarchy missing from the lookup → the Budget planning purpose was never assigned.
- Hierarchy assigned but nobody can see plans → missing Security purpose, wrong Security model, or a missing role.
- Everything configured but no plans can be created → the process was never activated with Actions > Activate.
- Layout cannot be edited → an Excel template was already generated against it.
A global enterprise has built a new organization hierarchy of departments for its annual planning cycle and published it. When the finance team opens Budgeting > Setup > Budget planning > Budget planning process and tries to select the hierarchy, it does not appear in the lookup. What configuration step was missed?
A consultant has defined scenarios, stages, workflow stages, columns, and layouts, and has created a budget planning process record with the correct budget cycle, ledger, published hierarchy, and per-stage rules. Budget managers still cannot create any budget plans for that process. What remains to be done?
Two divisions must share the same budget plan scenarios and the same stage names, but one division's contributors may add and modify plan lines at the Estimate stage while the other division's contributors may only modify existing lines. Where is that difference configured?