Dynamics 365 Project Operations: Optimize Project Operations - Update correction journal usability Beta
Data as of 2 hours ago (26 October 2026)
Description
Correcting transactions after they’ve been processed can be a complicated and difficult process. Currently in Project Operations, you must select all the transactions you want to correct at the same time to create the journal, and all transactions added to the journal must be corrected in the same way. This leads to significant repeat work, where you need to create multiple journals to be able to make different corrections on different transactions. This feature updates that process with the following changes: Transactions can be marked with Needs correction from the billing hub view, then once all required transactions have been marked, you can create the journal. This simplifies the journal creation process. Different transactions added to the same correction journal can be corrected in different ways, reducing the number of journals that need to be created. A wider set of fields is available for correction, limiting the number of transactions that need to be recalled to the draft entry state (a more complicated process) to complete the required changes. Time transactions can be split across multiple projects and tasks without recalling the draft entry state. A UI overhaul will be done to make the corrections process easier and simpler to follow. Overall, these changes make corrections easier, minimize mistakes that can lead to major problems, and reduce frustration with the interface. Business Value: Correcting previously processed transactions is a difficult process that’s made harder by UX limitations. The changes in this feature update let you make different corrections within the same journal, correct a wider range of fields, and easily select transactions that need correction. With the new experience, a larger volume of transactions can be corrected at once to reduce repetitive work while simultaneously making the process clearer and simpler. This reduces mistakes made during the corrections process, which in turn minimizes the more costly and problematic billing errors. Enabled for: Enabled for end users automatically
Change history
Added to the roadmap 16 October 2026. Tracked here since 16 October 2026. Earliest target we recorded: March 2027 (since tracked — Microsoft may have moved it before we started watching).
Nothing has changed on this item since tracking began on 16 October 2026. Changes appear here as Microsoft updates the feed.