SETUP GUIDEHow to set it up8 sections. Choose a role to highlight what matters to you.
Everyone
1What it is and why
What it is
A setup page where you create forecast models, including the original, remaining and carry-forward budget models that project budgets use.
What you do here
Use this page to name and set up the forecast models that project forecasts and budgets are recorded against.
Example
For example, BEAT creates ORIG-26 with Budget type Original budget and REM-26 with Remaining budget, so that the 250,000.00 budget of PRJ-0042 is committed to both and actual costs reduce only REM-26.
The page in Dynamics 365. page title tab to open what to set or check
About the examples: Examples and screenshots in this guide use BEAT, a demo company in a Dynamics 365 test environment. Use your own company's codes and values instead of copying them.
Step by step, with screenshots
Set up Forecast models1 screen
Use this page to name and set up the forecast models that project forecasts and budgets are recorded against.
Screen 1
Create a forecast model
Go to Project management and accounting > Setup > Forecasts > Forecast models
Select New
Enter the model code and name
Set the project forecast options, such as the invoice date and budget type, as needed
Select Save
1Model
BEAT-FM
2Name
Forecast model
Show the full screen page title tab to open what to set or check
Steps from Microsoft
Go to Project management and accounting > Setup > Forecasts > Forecast models.
Select New, and enter a model ID and name.
Set Stopped to Yes if the forecast lines must not change.
Set Include in Cash flow forecasts to Yes if the lines should create cash flow forecasts.
Set Forecast Invoice date to Yes to use the project date as the invoice date.
In the Budget type field, select Original budget, Remaining budget or Carry-forward.
Separate Original budget and Remaining budget models for budget control, with no submodels on themA budget-controlled project needs both an original and a remaining budget model, and a model used for budget control can't have or be a submodel.
PrivilegesMaintain project forecast models ProjForecastModelMaintainDutiesEnable project accounting process ProjProjectAccountingProcessEnable1 security roleProject supervisor ProjProjectSupervisorChecked in Dynamics 365
Roles to set it up and use it
To set it up or change itProject supervisor ProjProjectSupervisorGive people one of these roles. On this system, 1 role can open this page.Checked in Dynamics 365
Actions on the page
Options: Personalize, Page options, ShareChecked in Dynamics 365
ForecastModelEntity (Forecast models): loaded for each company, in Microsoft's default template 430 - Master planning.ForecastSubModelEntity (Forecast sub models): loaded for each company, in Microsoft's default template 430 - Master planning.Load order: Microsoft's default template 430 - Master planning loads Forecast models at execution unit 1, level 30, sequence 10. Lower levels load first, and entities at the same level load in sequence order.Load first: the default templates at lower levels (System setup to General ledger)Microsoft Learn
Checked in a working Dynamics 365 system, version 10.0.49: the menu item, form, table and security, the page, the demo records and the values in the screenshots.
To cite this step: PM-SETUP-330, Set up Forecast models. Beyond ERP Atlas Hub, 2026-11-11. https://www.beyonderp.cloud/atlas/step/PM-SETUP-330