Dynamics 365 Project Operations

We are trying to implement the project budget in the project accounting module, but we are facing a few issues:

1-     The system allows the project managers to add budgets with any type of control or limitation, I suggest the system have a budget ceiling like total contract value or any suggested control

2-     The system should allow for non-financial impact budget items like contingency reserve and management reserve 

When Sub module Customer & Vendor set to None under Ledger period setup then system will restrict users to enter any transactions for Vendor & Customer (Accounts receivable & Accounts Payable) but same will be allowed from General Ledger module.

Whereas in 2^nd case, when sub module Project is set to None under Ledger Period setup then system will restrict users to enter transactions from both modules Project and Accounting management & General Ledger module.

In comparison with above two scenarios customer wants to understand why there no uniformity in the functionality where Project is also an sub module and it should allow user to enter transactions from General ledger module else same logic should applicable to AP & AR modules as well.

Filtering by Invoice status on Project posted transactions form should show accurate data for on-account transactions

Business scenario: After the project is eliminated, the expectations are not to be able to post against it as it is already finished. For example: the project starts on 01 April and will end on 30 June which means it will hit 3 financial periods. It is not possible to consider the revenue and expenses per period, so the option of WIP transactions is coming here to post expenses and revenue as a WIP and after completion of the project run the estimation and elimination process for transferring from WIP to actual sales and expenses. In this stage the project is considered as a finished project, and there shouldn't be any posting related to it. But if there are received any new transactions and that must be posted, the option of “reverse elimination” will be used to re-open the project again and reverse again to WIP, pass new transactions then close the project again by estimation and elimination.

Request: Removing “set project to finished” option in elimination posting and let the stage changes automatically to Finished, which will then prevent any future postings. And in reverse elimination, changing the project stage to in process automatically.

Issue: User noticed in the “project invoices” screen, that the Name column is being populated with “Invoice” in some instances. It seems that, when the Name is blank, the invoice is generated correctly but, if a value exists in that Name field, it is being used instead of the client name.

Current design: It was concluded that this is the expected behavior of the system. The Delivery name comes to the invoice name because of the Address of the Customer.

Request: System to take the customer name instead of delivery name.

When we work with fixed price projects , WIP posting

Estimation & Elimination process is done and project must be marked as finished to prevent any new postings for the project otherwise if you post elimination without set stage of the project to finish ,system will allow posting and this is incorrect and not controlled point !

The idea here is once elimination posted ,project stage must change to be finished automatically ,and if we need to open the project again ,reverse elimination will do this action normally.

So, all what we need is to delete “set project to finished” option in elimination posting to prevent any mistakes and let the stage changes automatically ,then the behavior will prevent any postings. And in reverse elimination ,changing the project stage to in process automatically.

Wish there is option to potentially future easily transfer budget travel expenses transfer in financial summary to budget commitments, budget planning stages, or approvals entry lines.

Wish there is an option to easily schedule and priority tasks resources process transaction planned tasks as per priority or priority role origin preferences, for purpose to maintain user role, planned and priority tasks, for purpose to potentially justify main project goal (s) or feedbacks.

For complex parent-child project hierarchies, budget control at the child level is requiring that you select the parent project vs enabling budget control for the hierarchy and consuming against the parent project by default. There is an option to create the budget for the subproject. This is adding multiple clicks and posting errors if they forget to select the parent budget on the subproject.

Allow for the a production Bom (item required on project) detailed cost lines to be included in the Project Budget and Forecast, for a more integrated Project with Production reporting solution.