Improve Revenue Recognition Generation Performance for Large Volumes of Projects
Idea Description:
Currently, when generating revenue recognition entries for multiple projects, the process can experience significant performance degradation when handling large datasets. This can result in extended processing times and reduced operational efficiency, p...
Bring WIP transactions as opening balances for a Fixed Price project without running revenue recognition.
When migrating Project data from a legacy system to D365 F&O. On cutoff date, there are cost transactions of fixed price projects have not been recognized and still remain in WIP balance. We use beginning balance journal to transfer these WIP cost transactions from legacy system to F&O without...
Revenue recognition voucher should not consume multiple number sequence numbers when multiple projects share the same Revenue project ID.
The Revenue Project ID field (Project management and accounting → All projects → Project → Revenue recognition) is designed to give flexibility in how revenue is recognized. When several sub‑projects roll up under a parent project, assigning the parent’s Revenue Projec...
The revenue recognition description is not updated when the project name is updated
When a project of type Fixed Price is created then system generates the revenue recognition project and link it with the main project with the initial project name . Revenue recognition project description can be changed ...
Show Calculation Inputs for Revenue Recognition Percentage in Estimates
In the revenue recognition process for fixed-price projects using the Total forecast – actual method, D365 FO calculates a percentage of completion based on actual cost and forecasted cost. However, the system does not display the exact values used in this cal...
Automation of cost recognition principle based on percentage completion method. This automation would be same as that of revenue recognition principle
There is requirement of automation of cost recognition functionality in Project Management and Accounting, this is required when the project type selected as "Fixed Price" with revenue recognition method of "Completed percentage". This functionality is required to recognize cost based on compl...
Discount in Project Revenue Recognition for Fixed Price
We are unable to run discount on revenue recognition in fixed price contracts (Straight line method) through projects and simultaneously accounting impact on D365 F&O. Since this functionality is not available in current system as it impacting our Business, request you to prioritize this issue...
Revenue recognition batch jobs for multiple legal entities
For an organisation with a large number of legal entities, the periodic revenue recognition process requires a lot of repetitive actions in each legal entity. It would very useful to have 'global' versions of the batch jobs 'Create', 'Delete', 'Post' and 'Reverse' revenue recognition.
Estimate postings duplicate in subprojects
In the Projects module of D365, it is possible to transfer transactions between projects, which offers significant flexibility. However, there is a notable concern: these adjusted transactions are recorded as new transactions in the target projects for revenue recognition purposes. This presen...
Project Prepayment for Italian
Project Revenue Recognition does not operate according to Italian process as it considers prepayment as Revenue in the system