15.1 Budget Models, Budget Codes & Allocation Terms
Key Takeaways
- A budget model is the container for budget register entries and can hold sub-models that roll up for reporting.
- Budget codes carry exactly one of six budget types: Original budget, Transfer, Revision, Encumbrance, Preencumbrance, or Carry-forward budget.
- Workflow is attached to a budget code, not to a budget type, and is optional; when present it must finish before the entry reaches Completed.
- Period allocation keys spread a line across fiscal periods and budget allocation terms spread it across financial dimension values.
- Running either allocation reverses the original budget account line and writes the allocated lines in its place.
15.1 Budget Models, Budget Codes & Allocation Terms
Quick Summary: In enterprise financial management, organizations must establish, adjust, and monitor financial targets for revenues, expenses, capital expenditures, and operational headcount. In Microsoft Dynamics 365 Finance, the Budgeting module provides a three-tiered architecture: Basic Budgeting (recording and updating budget register entries without real-time enforcement), Budget Control (programmatic real-time funds availability validation on transactional source documents), and Budget Planning (multi-scenario collaborative budget preparation and workflow modeling). This section covers the complete configuration of Basic Budgeting, budget models, budget codes, allocation terms, budget register entries, and variance reporting.
1. Basic Budgeting Architectural Framework
Dynamics 365 Finance divides budgeting functionality into three complementary pillars:
+---------------------------------------------------------------------------------------------------------+
| Dynamics 365 Finance Budgeting Architecture |
+---------------------------------------------------------------------------------------------------------+
| |
| +-----------------------------------+ +------------------------------------------------------+ |
| | Budget Planning | | Budget Control | |
| | - Multi-Scenario Modeling | | - Real-Time Funds Available Validation | |
| | - Organizational Hierarchies | | - Hard Stops, Warnings & Over-Budget Thresholds | |
| | - Top-Down / Bottom-Up Workflows| | - PRs, POs, Invoices, Expenses, GL Journals | |
| | - Matrix Layouts & Excel Add-in | | - Pooled Budget Groups across Dimensions | |
| +-----------------------------------+ +------------------------------------------------------+ |
| | ^ |
| | (Generates Approved Entries) | (Validates Entries) |
| v | |
| +---------------------------------------------------------------------------------------------------+ |
| | Basic Budgeting | |
| | - Master Budget Models & Sub-Models | |
| | - Budget Codes & the 6 Budget Types (Original budget, Transfer, Revision, etc.) | |
| | - Period Allocation Categories & Dimension Allocation Terms | |
| | - Budget Register Entries (Header, Lines, Workflows, Excel Integration) | |
| | - Budget vs. Actual Inquiries & Financial Reporting (Management Reporter) | |
| +---------------------------------------------------------------------------------------------------+ |
+---------------------------------------------------------------------------------------------------------+
Core Differences Between Budgeting Capabilities
| Functional Dimension | Basic Budgeting | Budget Control | Budget Planning |
|---|---|---|---|
| Primary Objective | Record, revise, and report budget amounts | Enforce real-time spending limits | Formulate and negotiate future budgets |
| Enforcement Style | Informational / Detective | Programmatic / Preventative | Collaborative / Workflow-driven |
| Transactional Impact | No document blocking | Blocks PRs, POs, Invoices, GL Journals | Pre-transactional planning only |
| Data Storage | Budget register entry lines | Budget source tracking / BFA cache | Budget plan scenario lines |
| Configuration Path | Budgeting > Setup > Basic budgeting | Budgeting > Setup > Budget control | Budgeting > Setup > Budget planning |
2. Budget Models & Hierarchical Sub-Models
Budget models (Budgeting > Setup > Basic budgeting > Budget models) establish the container structure for categorizing and aggregating financial estimates within a legal entity.
+---------------------------------------------------------------------------------------------------+
| Budget Model Configuration Hierarchy |
+---------------------------------------------------------------------------------------------------+
| Budget Model ID: [ FY2026_MASTER ] Description: Corporate Master Operating Budget 2026 |
| Budget Type: [ Master / Top-Level ] Cash Flow Forecast: [ Yes ] Status: [ Open ] |
+---------------------------------------------------------------------------------------------------+
| SUB-MODELS FASTTAB: |
| Sub-Model ID | Description | Cash Flow Forecast | Model Status |
| :------------- | :--------------------------------- | :----------------: | :-------------------- |
| `FY2026_CORP` | Corporate Administration Budget | Yes | Open |
| `FY2026_SALES` | Commercial Sales & Marketing | Yes | Open |
| `FY2026_OPS` | Manufacturing & Supply Chain Ops | Yes | Open |
| `FY2026_CAPEX` | Capital Expenditure Projects | No | Open |
+---------------------------------------------------------------------------------------------------+
Budget Model Configuration Parameters
- Budget Model ID & Name: Unique identifier and descriptive label.
- Sub-models FastTab: Allows linking multiple granular sub-models to a top-level parent model. When inquiries or reports are executed on the parent model
FY2026_MASTER, the system automatically consolidates budget figures across all child sub-models (FY2026_CORP,FY2026_SALES,FY2026_OPS,FY2026_CAPEX). - Cash Flow Forecast Toggle: When set to Yes, amounts posted against this budget model are automatically included in the Cash and Bank Management cash flow forecasting engine.
- Stop / Block Status (Stopped): When toggled to Yes, prevents users from creating or posting new budget register entries against the model, effectively freezing the budget.
[!NOTE] A sub-model can belong to only one parent budget model in the same hierarchy. However, you can create independent, standalone budget models for parallel scenarios (e.g.,
FY2026_OPTIMISTICvs.FY2026_PESSIMISTIC).
3. Budget Codes, Budget Types & Transaction Classification
Budget codes (Budgeting > Setup > Basic budgeting > Budget codes) classify budget register entries, determine their accounting treatment, link to specific number sequences, and enforce workflow governance.
+---------------------------------------------------------------------------------------------------------+
| Budget Codes & Budget Types Matrix |
+---------------------------------------------------------------------------------------------------------+
| Budget Code | Budget Type | Functional Description & Business Use Case | Workflow |
| :---------- | :----------------------- | :---------------------------------------------------- | :------------ |
| `ORIG_BUD` | **Original budget** | Approved baseline budget at the start of the cycle. | Optional |
| `XFER_DEPT` | **Transfer** | Zero-sum move of funds between dimension values. | Optional |
| `REV_ALLOC` | **Revision** | Increases or decreases the total authorized budget. | Optional |
| `ENCUMB` | **Encumbrance** | Commitment reserve for purchase orders (public sector).| Optional |
| `PRE_ENC` | **Preencumbrance** | Commitment reserve for purchase requisitions. | Optional |
| `CARRYFWD` | **Carry-forward budget** | Rolls unspent funds from the prior year forward. | Optional |
+---------------------------------------------------------------------------------------------------------+
Deep-Dive: The Six Budget Types
Microsoft documents exactly six budget types that a budget code can carry. Memorize the list — a favourite distractor style on MB-310 is a plausible-sounding invented type such as "Amendment", "Apportionment", "Preliminary", or "Zero-based". None of those exist in Dynamics 365 Finance.
- Original budget: The initial, baseline financial plan adopted by the board or executive management. An account combination typically receives only one original budget entry per budget cycle.
- Transfer: A zero-sum reallocation of funds between two or more financial dimension combinations or main accounts (for example, moving $15,000 from
600100-Travel-Dept10to600200-Training-Dept10). The source line carries a negative amount and the destination line an offsetting positive amount. - Revision: An adjustment that increases or decreases the total approved budget authorization, rather than moving money sideways within it (for example, the board approves an additional $500,000 for a product rollout).
- Encumbrance: The commitment reserve recorded against confirmed purchase orders, used mainly in public-sector and commitment-accounting scenarios.
- Preencumbrance: The earlier commitment reserve recorded against purchase requisitions, before a purchase order exists.
- Carry-forward budget: Used at year-end to roll remaining unspent budget balances, or outstanding encumbered purchase order balances, from the closing fiscal year into the new one.
Budget Code Parameters
- Budget Type: One of the six types above; it defines the mathematical handling and the reporting classification.
- Workflow: Attaching a workflow is optional and is done per budget code, not per budget type. If a workflow is associated with a budget code, it is enabled for every budget register entry that uses that code, and its steps must complete before the entry can reach Completed.
- Reason Code Requirement: Can be set to Mandatory or Optional, forcing users to state why a revision or transfer is being requested.
[!IMPORTANT] Governance is enforced by the workflow you hang on the budget code. There is no built-in rule that "transfers always need approval" — an unworkflowed Transfer code updates budget balances immediately.
4. Allocation Terms: Period & Dimension Spreading
To prevent manual data entry across 12 monthly periods or across multiple departments, Dynamics 365 Finance provides automated Allocation Terms.
A. Period Allocation Categories
- Configuration Path:
Budgeting > Setup > Basic budgeting > Period allocation categories - Purpose: Distributes a lump-sum annual budget amount across specific fiscal periods based on predefined percentage or weight rules.
+---------------------------------------------------------------------------------------------------+
| Period Allocation Category: [ SEASONAL_Q4 ] |
+---------------------------------------------------------------------------------------------------+
| Period / Month | Allocation Method | Percentage Allocation | Example: $120,000 Annual Budget Line |
| :------------- | :---------------- | :-------------------- | :----------------------------------- |
| **Period 1 (Jan)** | Percent | 5.00 % | $6,000.00 |
| **Period 2 (Feb)** | Percent | 5.00 % | $6,000.00 |
| **Period 3 (Mar)** | Percent | 5.00 % | $6,000.00 |
| **Period 4 (Apr)** | Percent | 5.00 % | $6,000.00 |
| **Period 5 (May)** | Percent | 5.00 % | $6,000.00 |
| **Period 6 (Jun)** | Percent | 5.00 % | $6,000.00 |
| **Period 7 (Jul)** | Percent | 10.00 % | $12,000.00 |
| **Period 8 (Aug)** | Percent | 10.00 % | $12,000.00 |
| **Period 9 (Sep)** | Percent | 10.00 % | $12,000.00 |
| **Period 10 (Oct)**| Percent | 12.00 % | $14,400.00 |
| **Period 11 (Nov)**| Percent | 12.00 % | $14,400.00 |
| **Period 12 (Dec)**| Percent | 15.00 % | $18,000.00 |
| **Total** | — | **100.00 %** | **$120,000.00** |
+---------------------------------------------------------------------------------------------------+
Common Period Allocation Methods
- Equal: Divides the line amount equally across the active fiscal periods (e.g., $120,000 / 12 = $10,000/month).
- Percent: Applies explicit user-defined percentages per period (must sum to exactly 100.00%).
- Factor / Weight: Proportions calculated based on relative integer weights (e.g., 4-4-5 retail calendar retail weights).
B. Budget Allocation Terms
- Configuration Path:
Budgeting > Setup > Basic budgeting > Budget allocation terms - Purpose: Defines the percentage of a budget register entry that is allocated to specific financial dimension values, splitting a single high-level budget line into multiple discrete dimension combinations.
[!NOTE] Do not confuse budget allocation terms with the ledger allocation rules covered in 5.5. Ledger allocation rules distribute posted ledger amounts; budget allocation terms distribute a budget register entry line.
C. Running an Allocation on a Budget Register Entry
Both allocation styles are launched from the saved line in the Budget account entries grid:
- Allocate across periods — pick a period allocation key, then select Allocate.
- Allocate to dimensions — pick a budget allocation term, then select Allocate.
In either case Dynamics 365 Finance creates a reversal entry for the original budget account line and then writes the newly allocated lines, so the grid shows the original line, its reversal, and the spread. Finish with Update budget balances.
+---------------------------------------------------------------------------------------------------+
| Dimension Allocation Terms: IT Software Licensing |
+---------------------------------------------------------------------------------------------------+
| Target Account-Dimension Combination | Percentage | Allocated Share of $100,000 Budget |
| :------------------------------------------- | :--------- | :----------------------------------- |
| `601500-Dept_001-BU_Corp (Corporate HQ)` | 40.00 % | $40,000.00 |
| `601500-Dept_002-BU_Retail (Retail Ops)` | 35.00 % | $35,000.00 |
| `601500-Dept_003-BU_Mfg (Manufacturing)` | 25.00 % | $25,000.00 |
| **Total Distributed** | **100.00 %**| **$100,000.00** |
+---------------------------------------------------------------------------------------------------+
An organization adopts an annual operational budget of $240,000 for utility expenses (Main Account 600400). Due to seasonal heating and cooling demand, corporate finance requires the annual budget to be spread across periods as follows: 15% in Q1 (5% per month), 20% in Q2, 35% in Q3, and 30% in Q4. How can the functional consultant implement this requirement with minimal manual data entry?
A company maintains separate sub-models for Marketing (SUB_MKT), IT (SUB_IT), and Facilities (SUB_FAC). The CFO wants to view consolidated actual vs. budget reports in Financial Reporting without manually combining the three models. Furthermore, the CFO wants budget numbers to automatically update the Cash Flow Forecast. What configuration is required?