Dynamics 365 Project Operations Redesigns Correction Journals: Mixed Actuals, Time Splits and Rollout Dates

Under Microsoft’s AI at Work roadmap item 576880 ("Dynamics 365 Project Operations: Optimize Project Operations - Update correction journal usability"), along with corresponding Microsoft Learn release documentation, Microsoft is overhauling how project managers, billing specialists, and back-end administrators adjust approved actuals. The update replaces a strict batch-uniformity model with a staging workflow, mixed-transaction journals, a wider set of editable fields, and direct time-splitting capabilities. However, enterprise administrators tracking this rollout will also notice a glaring discrepancy between Microsoft’s public roadmap dates and its technical release notes—a classic Microsoft scheduling puzzle that requires checking your specific environment versions rather than relying on a single calendar date.

Why Fixing Project Actuals Was Such a Chore​

To appreciate why this usability update matters, you first have to understand how Dynamics 365 Project Operations guards financial integrity. According to Microsoft Learn’s documentation on Project Operations actuals, once time, expense, material usage, or invoice entries are approved, they become actuals—the official financial and schedule record of a project.

Because these records often synchronize directly with downstream accounting systems via dual-write, Project Operations strictly prohibits deleting actuals or editing them directly in the database (with the minor exception of description and external description fields). Starting with Update Release (UR) 55, Microsoft Learn notes that back-end validation actively blocks users and developers from creating or modifying actuals manually through the UI, the maker portal, JavaScript scripts, or plugins. Instead, adjustments must flow through correction journals, which preserve a clean audit trail by generating reversal lines for the original actuals and creating brand-new replacement lines.

While the accounting logic is sound, the user experience for creating those correction journals has long been a bottleneck:

• All-at-once selection: Users had to locate and select every transaction they wanted to fix at the exact same moment before generating a correction journal.
• Uniform correction rules: Every transaction placed into a single correction journal had to be corrected in the exact same way. If you had five time entries that needed to move to Project B, and three that needed a different resource role, you had to spin up separate journals.
• Separate silos by transaction class: In the legacy workflow documented on Microsoft Learn, administrators navigated separately to Approved Time, Approved Expenses, or Actuals (filtered for materials) to spawn distinct Time, Expense, or Material correction journals.
• The "recall to draft" penalty: Because the legacy correction journal only supported a narrow list of fields, fixing something like a quantity or a price—or splitting a single time entry across two different tasks—frequently forced users to recall the transaction all the way back to its draft entry state.

Section Summary: Project Operations protects financial audit trails by banning direct edits to approved actuals and requiring reversal-and-replacement correction journals. Until now, however, UX limitations forced administrators to create separate journals for every distinct type of edit.

What Changes in the New Correction Journal Experience​

Microsoft’s update directly targets the repetitive administrative overhead of the legacy workflow. Drawing from both roadmap item 576880 and Microsoft Learn’s September 2026 release documentation for Project Operations Integrated with ERP, the redesigned experience introduces several practical operational shifts:

1. Staging with "Needs Correction" in the Billing Hub​

Instead of hunting down and selecting all target transactions in a single pass, users can now flag individual transactions with a Needs correction status directly from the billing hub view. Once all the problem entries have been marked across your review session, you can gather them and generate the correction journal in one step. Furthermore, Microsoft Learn’s September 2026 release notes confirm that you can now add additional entries to an existing draft correction journal rather than starting over if you missed a line.

2. Mixed Transaction Types and Per-Group Edits​

The single biggest time-saver is the death of the one-edit-per-journal rule. The new correction journal experience supports approved time, expense, and material transactions together, allowing administrators to combine different transaction types inside a single journal. Once inside the journal, users can select specific groups of entries and apply different corrections to them using a dedicated editing side pane, while an entry-level correction status indicator clearly distinguishes modified lines from unchanged ones.

3. Expanded Field Support and Time Splitting​

Historically, Microsoft Learn’s baseline documentation for correction journals limited default edits to fields like Project, Subcontract, Project task, Subcontract line, Entry Date, Bookable resource, Resource role (for time), Expense category (for expenses), Write-in product (for materials), and custom pricing dimensions.

The updated experience significantly expands the roster of editable attributes to reduce how often transactions must be recalled to draft state. According to the September 2026 release documentation, the expanded options now include:

• Quantities
• Billing type
• Cost and sales prices
• Time splitting: Users can now split time transactions across multiple projects and tasks directly within the correction process without recalling the entry to draft state.

Section Summary: The redesigned workflow lets billing teams flag transactions asynchronously in the Billing Hub, mix time, expense, and material lines in one draft journal, edit quantities and prices via a side pane, and split time across tasks without recalling entries to draft.

The Rollout Timeline Mystery: September 2026 vs. March 2027​

If you are a Dynamics 365 administrator trying to figure out when your finance team will actually see this interface, Microsoft’s public tracking channels offer a masterclass in conflicting metadata.

Here is what the different records state:

• AI at Work Roadmap (ID 576880): The roadmap entry lists the feature status as In development for Worldwide (Standard Multi-Tenant) cloud instances on the Web platform, citing a public preview date of October 2026 and a General Availability (GA) target of March 2027, with the feature "Enabled for end users automatically."
• Archived Wave Plan & Message Center Reports: An archived Microsoft Learn 2026 release wave plan page (last updated August 27, 2026) listed General Availability as September 2026. Similarly, third-party archives of Microsoft 365 Message Center post MC1465655 (such as DeltaPulse and M365 Admin) recorded an announcement stating the feature would reach general availability on September 30, 2026.
• Official Product Release Notes: Most importantly, Microsoft Learn’s official documentation titled "What's new September 2026 - Project Operations Integrated with ERP" (updated September 21, 2026) lists the New correction journal experience as an included feature in that exact build.

Why the conflict? Microsoft’s roadmap portal explicitly notes that published dates are estimates subject to change, and roadmap entries occasionally lag behind or diverge from component-level release notes—or reflect when a feature transitions from optional to mandatory default behavior across all rings.

Notably, while the roadmap metadata says "Enabled for end users automatically," the September 2026 What’s new documentation states that the new correction journal experience is initially optional, allowing organizations to continue using the classic correction journal interface until they choose to enable the new one.

Section Summary: Despite roadmap item 576880 listing an October 2026 preview and March 2027 general availability, Microsoft Learn’s September 2026 release notes document the feature as already included—and initially optional—for Integrated with ERP deployments.

Practical Guidance for Dynamics 365 Administrators​

Because of the scheduling discrepancy between the high-level roadmap and the technical release documentation, enterprise IT and finance administrators should verify their exact environment versions rather than waiting for a calendar milestone.

1. Check Your Environment Versions: According to Microsoft Learn, the September 2026 release for Project Operations Integrated with ERP corresponds to Project Operations in a Microsoft Dataverse environment version 4.171.3551.6 and Project management and accounting in a Microsoft Dynamics 365 Finance environment version 10.0.49. Check your Power Platform admin center and Dynamics 365 Lifecycle Services (LCS) to see if your tenant is running this build or later.
2. Verify Dual-Write Map Versions: Whenever updating Project Operations Dataverse and Finance solutions, Microsoft Learn advises running the latest dual-write entity map versions and enabling all related table maps so accounting synchronizations do not break.
3. Test the "Initially Optional" Toggle in a Sandbox: Because the September 2026 documentation notes the new experience is initially optional, test enabling it in a non-production environment first. Have your project controllers test mixing time, expense, and material lines, and verify that cost price, sales price, and quantity adjustments synchronize cleanly with your Finance general ledger.
4. Respect API Boundaries for Non-Journal Fields: Remember that "a wider set of fields" does not mean unrestricted editing on the Actuals table. As detailed in Microsoft Learn’s Create or update actuals guide, specific state changes outside the journal scope still require dedicated APIs—such as msdyn_MarkActualReadyToInvoiceOrNot for Billing Status, msdyn_ReevaluateActualNotToExceedStatus for Not-to-exceed Status, and msdyn_revise for Revise operations.
5. Enforce the Preview Step: Even with a cleaner UI and entry-level status indicators, correction journals still reverse posted actuals and create replacement financial records. Train billing administrators to always use the Preview action to inspect the reversal and replacement journal lines before clicking Confirm.

For organizations running complex, resource-based engagements in Dynamics 365 Project Operations, the updated correction journal workflow removes one of the platform's most tedious daily friction points—turning a rigid, multi-journal chore into a flexible staging and review process. Just be sure to check your Dataverse and Finance build numbers first, because in the world of enterprise cloud rollouts, the code in your tenant often speaks louder than the date on the roadmap.