UPDATE (March 28th, 2018):
Thanks everyone for your comments and great feedback!
From your insights, we can identify two basic ways of working with project budget, which one is the most demanded? A or B below, or both are equally needed? Is that possible that a company uses one or another approach depending on a project, or the approach is usually company-wise?
* Approach A, ENTER BY PERIOD. The users actually plan, approve, and enter the project budget by period, by month, for example. They want to see the reports for budget vs actual monthly to control the project.
* Approach B, ENTER TOTAL, DISTRIBUTE BY PERIOD. The users plan, approve, and enter the entire budget for a project. But, they also want to see the reports for budget vs actual monthly to control the project. They want to see the projection of the budget on the months of project execution. To see the projection, they can distribute the budget amount by periods manually, or apply a formula and make corrections later, for example distribute evenly and then correct manually. They also need to do manual corrections of the budget by month on a regular basis, at the same time the total budget must not exceed the original total. If they need to change the original total, they would do a change order, so that they approve the original budget total + approve change orders = current revised total, which should be distributed across periods for project control.
* * *
Dear partners and customers,
We need your feedback on whether this idea makes sense to you, and whether you are aware of a real business need for this functionality in the system. It would be helpful if you can share examples of user scenarios that involve this feature.
* * *
Idea: Ability to define project budget by financial period.
Once defined, how is this information used further? What are the business scenarios?
Thank you for your feedback.