Dynamics 365 Project Operations: Optimize Project Operations - Update correction journal usability
Summary
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…
- Status
- In development
- General availability target
- Mar 2027
- Preview target
- Oct 2026
- Products
- Dynamics 365 Project Operations
- Clouds
- Worldwide (Standard Multi-Tenant)
- Release phases
- General Availability, Preview
- Platforms
- Web
- Added to the roadmap
- 16 Oct 2026
- Last changed
- 16 Oct 2026 · today
More Dynamics 365 changes
All Dynamics 365 roadmap itemsWhat changed
First observed 16 Oct 2026No field changes in the recorded history.
Cite this recorded revision to keep the same title, summary, facts and links when the page changes.
A day selects the latest observation by the end of that UTC day; today's selection can change until midnight. History starts when this installation records it.