Release timing needs a careful reading
Microsoft’s roadmap entry lists the feature as In development, with estimated general availability in November 2026. Its stated scope is the Web platform in Worldwide (Standard Multi-Tenant) and GCC cloud instances.
That is a planning window, not evidence that every eligible environment already has the capability. Microsoft explicitly describes roadmap dates as estimates and says the information can change. A General Availability release-ring label should not be mistaken for a completed rollout.
There is another useful distinction: the Microsoft Learn cancellation page carries a July 15, 2025 update date. The documented procedure therefore predates this roadmap notice; the notice alone does not establish when the functionality first became usable.
How to cancel entry-journal actuals
Microsoft scopes the procedure to Project Operations Integrated with ERP and Project Operations Core. Only actuals created through entry journals qualify; other selected actuals are ignored.
- Open Sales > Transactions > Actuals.
- Select the records to cancel.
- Select Cancel on the Action Pane.
- If at least one record qualifies, a correction journal opens and the selected actuals enter In process.
- Review the journal’s Actuals to Cancel tab.
- Select Confirm only after checking the list.
Successful confirmation creates reversing actuals marked Unadjustable, while the canceled originals become Adjusted. Confirmation is irreversible. If a selected record is missing from the journal, check its origin rather than assuming every selection qualified.
Why reversal matters more than deletion
Microsoft’s actuals overview explains the accounting rationale. Actuals represent reviewed and approved financial and schedule progress, and Project Operations prevents their deletion to preserve financial integrity and integration with accounting systems. Supported journal processes provide ways to reverse, replace, or edit transactions instead.
The practical distinction is straightforward: correcting a mistake should not erase the evidence that it happened. This workflow counteracts the original transaction while keeping its history visible—a less dramatic outcome than making a row disappear, but a considerably more useful one when reconciling records. That is the operational implication of Microsoft’s documented preservation model.
Entry journals still require restraint
Microsoft’s separate entry-journal documentation, scoped to Project Operations Core, explains why these records need particular care. Entry journals can create actuals without the usual time, expense, or material usage-log process, including for data migration or situations where individual entries are impractical. Once confirmed, the journal and its lines can no longer be edited.
The same documentation distinguishes entry-journal actuals from usage-log actuals: entry journals do not create the same transaction connections between cost and unbilled sales actuals or transaction-origin links to source records. Microsoft also says ordinary correction journals cannot correct actuals created through entry-journal confirmation. The dedicated cancellation procedure should therefore not be confused with the standard correction workflow.
Finally, Microsoft warns that entry journals do not enforce strict defaulting rules by default and recommends using standard business processes wherever possible. Its Journal line improvements feature provides a separate mechanism for enforcing journal-line rules. Cancellation is a correction path, not a substitute for careful entry and validation.