A businesswoman reviews a digital workflow dashboard with task lists, timelines, and financial data on her monitor.
Dynamics 365 Project Operations is getting a way to move project costs out of the balance sheet by hand. Microsoft's roadmap lists it as "Post costs for manual transfer from the balance sheet." It lets accountants decide when long-parked work-in-progress (WIP) costs become expenses on the profit and loss (P&L) statement. It is a small feature for a very specific audience, but those readers will care about it a lot.

A businesswoman reviews a digital workflow dashboard with task lists, timelines, and financial data on her monitor. What Microsoft is adding​

The Post costs feature lets project accountants manually move project costs between balance sheet (WIP) accounts and P&L accounts. Microsoft's roadmap entry (ID 574122) frames the problem this way. Organizations run long internal or customer-facing projects. When cost and revenue profile rules post costs to the balance sheet as WIP assets, those costs eventually have to be recognized as expenses. At that point they are reclassified to the P&L.

The roadmap and Microsoft Learn describe the enhancements as follows:

  • A new Post costs form to view, select and post transactions.
  • Selection of a single transaction or several at once.
  • Filtering by transaction date and by transaction type: expense, hour or item.

The roadmap lists the version as 10.0.49. The scope is users, with admins enabling the feature.

Who gets it, and who doesn't​

This is not a feature for every Project Operations customer. Microsoft says it is specific to the Project Operations Integrated with ERP deployment type. That is the model that extends Dynamics 365 Finance and Supply Chain Management. Microsoft's deployment overview lists configurable cost and revenue profiles and WIP accounting rules among its capabilities.

Microsoft Learn also limits the feature by project type. Post costs applies to projects with time-and-material contract lines and to internal projects. It does not apply to fixed-price or investment projects. For those, Microsoft says the revenue recognition process moves costs as needed.

How it fits the accounting flows​

Microsoft's preview documentation describes four typical patterns:

  1. P&L only. Costs are recognized immediately, with no balance sheet posting.
  2. Balance sheet with manual P&L posting. Accountants use Post costs to move costs when recognition is appropriate.
  3. Balance sheet with invoice-driven P&L posting. Costs move when the customer is invoiced.
  4. Balance sheet holding. Costs already on the P&L move back to the balance sheet. Microsoft's example is exploratory work that turns into a research and development project.

The documentation says the flow depends on three settings: the Cost and revenue profile, its rule, and the line property capitalization setting. It also carries a caution that is easy to miss. Balance sheet costs don't automatically move from the balance sheet when invoiced. Post costs is the manual way to move those balances.

Post costs moves cost transactions only. Revenue is posted separately at invoicing. It is not a revenue recognition tool, and it doesn't invoice anyone.

Two details worth noting​

Revenue checks in integrated deployments. Cost and revenue are tracked as separate transaction records in integrated deployments. The Post costs process checks the corresponding revenue record before it lets a cost move from P&L to the balance sheet. Microsoft says that if revenue has already accrued or the transaction is invoiced, the cost isn't eligible. Those records won't appear in the selection window. That is documented for the P&L-to-balance-sheet direction. Don't assume the same check governs every direction.

Internal projects gain a new path. Internal projects can now post transactions directly to the balance sheet when the Cost and revenue profile is configured that way. Previously, there was no way to move costs out of the balance sheet, but now Post costs enables this flow. This depends on configuration. It doesn't mean internal project costs are capitalized by default.

Turning it on (preview guidance)​

Microsoft's preview documentation gives these steps:

  1. Go to System administration > Workspaces > Feature management.
  2. Search for Enable posting costs from the balance sheet to the income statement.
  3. Select the feature, then select Enable now.

Microsoft marks that documentation as prerelease and subject to change. Treat the steps as preview guidance, not a guarantee of tenant availability.

Timing: the dates have moved​

The roadmap entry shows status "In development." It lists preview availability as September 2026 and general availability as March 2027, for Worldwide (Standard Multi-Tenant). Microsoft's roadmap notes that all dates are estimates and subject to change.

The older 2026 release wave 1 plan listed this feature differently. That plan showed September 2026 as a public preview, with no general availability date. Microsoft has since archived the plan. It says release plans stopped being published as of October 2026. Newer capabilities are tracked on the roadmap. So the March 2027 general availability estimate is the more current one.

Microsoft also sent a message center notice, MC1462628, about the feature. It said the feature would reach public preview on September 11, 2026. Microsoft described the notice as for awareness only, with no action required.

Why finance teams might care​

Anyone who has lived through a month-end close knows that "when does this cost hit the P&L?" can hold up the whole schedule. Before this feature, community threads show accountants resorting to workarounds. One Dynamics community thread describes adjustment journals that shift expenses between line properties to move amounts out of a WIP account. A dedicated form with date and type filters is a cleaner approach. That is my reading of the documentation, not something Microsoft states.

There are reasons for caution too:

  • Narrow scope. Fixed-price and investment projects are excluded.
  • Manual means manual. Someone has to run the process on schedule, and policy and controls matter. Microsoft's material doesn't describe approval workflows or audit features for the form.
  • Preview status. Test in a non-production environment before closing real books on it.

Practical checklist​

  • Confirm you run the Integrated with ERP deployment.
  • Review your project groups and Cost and revenue profiles for time-and-material and internal projects. These determine which costs sit on the balance sheet.
  • Identify balance-sheet costs that don't move automatically at invoicing.
  • Trial the feature in a sandbox once it is available, using the Feature management steps above.
  • Document who is authorized to post costs, and how often.

The headline is modest: one new form. For project accountants, though, it fills a gap where balance-sheet costs had no built-in way out.

 

References

  1. Dynamics 365 Project Operations: Post costs for manual transfer from the balance sheet Microsoft 365 Roadmap 2026-11-17T18:36:41.967573Z
  2. Post costs for manual transfer from the balance sheet | Microsoft Learn learn.microsoft.com
  3. Microsoft Copilot Roadmap | Microsoft 365 microsoft.com