-
No data entity for number sequence group reference table
There are data entities in D265FO for number sequence and number sequence reference, BUT only a data entity for number sequence group and NOT for number sequence group reference. So we cannot import automatically the number sequence groups with the reference, and it is a pain to have to enter all the data manually in the system!!
-
Automaticaly update the total forecast when budget is revised
The estimates in the D365FO project process are only based from total forecast model (or one of the forecasts models), and not from a budget. As many companies in private sector use the budget to track the different revisions (not allowed in the forecast), it means that you must update manually the total forecast each time you revised your budget (the system allows to import the original budget from the forecasts, but not budget revisions). So i propose to add the option to be able for each budget revision to automaticaly add the updated cost to the category corresponding in the total forecast (at the revision date). So that, it will cancel this painfull manual copy from forecast budget revision to total forecast, to have the total forecast updated from the budget revision. In the reality, ALL the customers will do this customization, because it is clearly a missing process in D365FO Project estimates, as if you don't do that, the forecasts will not match to the budget amount! -
Estimates from a Project Budget
The current situation is that it is not possible to manage the estimates directly from a Budget, but only from Forecasts. As the business reality is to use Budgets from a Project (Approvals, trace ability,....), and not Forecasts, it is logical to give the possibility to manage the estimates directly from the Budget. -
Cost comittment on project Timesheet is posted too late
The global rules for cost commitment management in D365 Finance is that this cost is raised for a significative time before the real cost (ex: when purchase order posted, when hours costs entered in journal, when expense entered in expense report,.....). So normally, the committed cost is usefull when it is identified at the beginning of the process, to be able to identify and report this cost. For the Project Timesheet, the committed cost is raised when the timesheet is approved, that mean at the end of the process, just before the timesheet is posted (some minutes before if you use the automatic posting that is 99% the case). So this commited cost feature can never be used, because it is not at all a commited cost and is never used in companies. It is a pity not to have a normal commitment feature in this case, as it is an important process in the companies. -
Automatically batch update of "approved" status quotations to "sent" status
From a business perspective, the step of sending quotations is optional, because it is not really an important step that need to be followed in the system. It must be possible to automatize the update of this step to the next level "Sent" by batch mode for all the quotations from the "Approved" Status. It was possible in the next versions, so why not now? Normal status for Project quotations : - Created/Submitted/Approved/Sent/Confirmed So possibility to update automatically in batch from Approved to Sent. -
Add total amounts on the invoice proposal to allocate bank accounts
Currently we have no idea in the vendor payment proposal what is the total amount for the generated proposal. Mostly often, the payment proposal is allocated to a bank account according to the amount of the payment proposal. In the current proposal, we cannot evaluate this total amount, so we are not able to allocate the corresponding company bank account (it is a classical treasury business process in a payment). So the requirement is to add at minimum a total amount by currency (proposal can be multi currencies). -
Vendor financial dimension inheritance in a vendor invoice journal
The standard D365 allows only vendor financial dimension inheritance for 1 offset expense line (when you enter your invoice on a single line). If you create an invoice with more than 1 expense line in the same voucher (that is common), you need to populate manually the vendor financial dimension because the automatic inheritance is not working. There is no functional or business explanation that an invoice with multiple expense lines (for the same voucher) cannot inherit the vendor financial dimensions. Most of the time, the customer create a customization to automatize this inheritance, that is not normal. Thanks for your help. -
Cost posted before the budget are never include and never visible on the Project Budget balances
A business situation is very classical on Projets : People will registered costs before the project budget has been approved (because there is a mandatory period of time for budget approval). So when you entered costs during this period where the budget is not approved, these costs will never be allocated to the budget (so the consumed budget is not updated for these costs, and the budget balance is partial). This situation is a real pain point for all companies that managed Projects, because you cannot track all costs in your project budget! The creation of project budget should include ALL the cost posted since the beginning of project, otherwise the project budget balance can never be use to follow the budget. The current restriction in D365 to include only the cost from the creation date of the Budget is not compliant with the budget processes of any company, and causes pains into this process. -
Leave and absence actuals updated automatically from Timesheet transactions
Actually there is no link between the absence timesheet categories posted and the leave and absence current balance. It means that the time-off request is the only actual that is calculated in this balance and the real absence posted in Timesheet has no impact to the employee balance!
So when an absence request is approved and finally the employee does not use this absence, the balance is false. It is clear that the last stage "Actuals" is missing on the leave and absence evaluation, that generate unusefull manual adjustments for correcting the absence balance.
To-day many customer are customizing this part in the system, that is not normal as the effort is not very important to match this purpose.
NB: This update from Timesheet categories posted could be extended to other absence types (Illness, injuries,....).
-
Activate Feature by company
Some features are very impactant for the group organization. For example, the "Awareness between ledger settlement and year-end close" feature has a very big impact in terms of organization, because it will force ALL companies for a group to be at the same level of closing, means ALL the companies must have close the fiscal year at the same time (that is impossible in the reality).
So the big impact is that we must wait for all companies closure, before to be able to install the feature (otherwise the closing will be impossible in companies that have not already closed the fiscal year).
This behavoir is due to the feature that does not allow to process closing for cross fiscal year settlement, so we must deactivate and then reactivate but for ALL companies (the deactivate is a Microsoft advice as no other solution si provided in standard).
So it is clear that in this case, a feature activation by company will consideraly facilitate the closing process for a group that can have 30, 40 or more companies).
Thanks for your help.
You’re offline. This is a read only version of the page.
