About project budgets and forecasts
Important
This content is archived and is not being updated. For the latest documentation, see Microsoft Dynamics 365 product documentation. For the latest release plans, see Dynamics 365 and Microsoft Power Platform release plans.
Applies To: Microsoft Dynamics AX 2012 R3, Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012
Microsoft Dynamics AX provides two ways to manage and control your projects: project forecasts and project budgets.
You can use forecasting if your organization has an operational perspective and focuses on revenues and costs derived from specific transactions. You can use budgeting if your organization focuses more on the financial amounts.
Both methods have their advantages. We recommend that your organization consider the following points before selecting a method.
Forecasting |
Budgeting |
|
|---|---|---|
Period allocation |
Forecasting allows for no explicit period allocation. Therefore, the forecast, and the control of the forecast, is based on the life of the project. Forecasts are based on a specific date. Therefore, you must infer the period from the date. |
In project budgeting, you can allocate transactions over the total project or a fiscal period. If you allocate over a period, you can choose to carry forward unused amounts to the next fiscal period. |
Viewing transactions |
Forecast transactions can be viewed in the forecast forms, where you see the forecasts for the whole company for all projects, regardless of the hierarchy. To focus on a particular project, you must filter the data. |
In project budgeting, you can view budgeted transactions for a single project hierarchy in the Project budget balances form. This means that you can view transaction details for a parent project or its subprojects. |
Transaction variables |
Forecast transactions can be entered using every attribute that exists for an actual transaction. This allows for greater detail in the forecast. For example, you can enter details for quantities, workers, items, or line properties. |
Budget details can only be entered using amounts, categories, and activities. |
Security |
Forecasting is based on entering transactions in the forecast forms, and involves no process-control mechanism. Any worker with permissions for a forecast form can revise information without approval. |
Project budgeting uses workflow, which enables change management and makes it possible to keep a history of the revisions. |
Entry types |
Forecast transaction entries are based on number of units and cost and sales unit prices. |
Budget details are based on amounts and split between costs and revenues. |
Forms |
Forecast transactions are entered in the five forecast forms:
|
All budget details are entered in the Project budget form. |
Forecast models |
Because each forecast must be associated with a model, you can create multiple forecast models and you can set up submodels. |
Project budgeting limits the forecast models that are used for budgeting. Fewer forecast models can help increase consistency in projections. |
Cost overruns |
When you use forecasts, you can only allow or disallow entry of transactions that would cause a cost overrun. |
Project budgeting provides additional control options for users. Warnings and overruns may be allowed. |
Control |
Forecast control is performed by using forecast reduction. Actual amounts are subtracted from forecast transaction balances without any audit trail. This can make it more difficult to trace where the actual transactions occurred. |
In project budget control, actual amounts are subtracted from amounts in the remaining budget. This allows for a clearer audit trail. |
Forecast models
Both project forecasts and project budgets use forecast models to contain the projected transaction amounts. The forecast models are created in the Forecast models form.
Forecast models have a single-layer hierarchy, which means that one project forecast must be associated with one forecast model. If you use project forecasting, you can identify models as submodels, which lets you create forecasts by department, time period, or region. For example, a forecast model could be created for a year, and then submodels could be created for the Northeast, Southeast, Northwest, and Southwest region forecasts that are submitted by regional heads. By choosing different options in Microsoft Dynamics AX reports, you can view information by total forecast or by submodel.
Project budgets must be associated with an original budget forecast model and a remaining budget forecast model. Project budgets can also be associated with a carry-forward budget model if you have projects that extend over one year and carry forward remaining budget amounts at year-end to the following year. When the original budget for a project is approved, forecast transactions are created automatically, based on the associated original budget model and remaining budget model.
See also
About setting up a project budget
Configure project budget control
Create and submit an original project budget