A cloud-based business workflow connects two office buildings through employee records, financial tools, and a progress tracker.
Microsoft has put a modest but telling item on its roadmap for Dynamics 365 Project Operations. It is meant to make the tax treatment of intercompany expenses predictable, whichever legal entity's tax setup is in play. The item is listed as "In development" under roadmap ID 580462. It covers the Web platform in the Worldwide (Standard Multi-Tenant) cloud. Preview is estimated for March 2027 and general availability for July 2027.

Microsoft's roadmap carries the usual caveat: dates are estimates and everything is subject to change. Treat the dates as intentions, not promises.

A cloud-based business workflow connects two office buildings through employee records, financial tools, and a progress tracker. What Microsoft says it is fixing​

The roadmap description targets customers who use Dynamics 365 Finance & Operations for project-based expense management. These customers need taxes on intercompany expenses processed "correctly and consistently". That should hold whether intercompany tax posting is configured in the source or the destination legal entity. The stated aim is to reduce inconsistencies that depend on configuration.

The entry does not say how this will be done. It does not mention a new setting. It does not say whether existing configurations will behave differently, or whether source or destination will become a universal default. Anyone planning around it should wait for Microsoft's release plan or documentation.

Background: how intercompany expense tax works today​

An intercompany expense lets a worker employed by one legal entity record expenses for work done for another. The employing entity is the loaning entity. The entity the work was done for is the borrowing entity. Microsoft's planning guidance gives an example. An employee of entity A does project work for entity B and incurs travel costs. With intercompany expenses enabled, the expense report posts the expense to B while A pays the employee.

Tax posting is where configuration matters. According to Microsoft Learn:

  • Setting Legal entity for intercompany tax posting to Source, with Apply sales tax taxation rules set to No, makes the system use the tax combination for the loaning legal entity.
  • Setting the same parameter to Destination makes the system use the tax combination for the borrowing legal entity.
  • For U.S. legal entities using Source, you must also configure the Sales tax receivable field on the new Ledger posting groups page.
  • Microsoft describes the behavior as consistent for expense lines posted with or without a project.

Older Dynamics AX 2012 documentation shows the setting has long existed. It describes the choice as posting the tax amount either where the transaction originates or where the expense or revenue is distributed. It also notes that, for journals not covered by the setting, tax amounts post to the destination entity.

Why consistency is the hard part​

Two things can go wrong in a multi-entity setup like this. The first is configuration collisions. A community thread describes a company with US and Canadian entities. Destination posting worked for use tax but pulled destination tax settings on expense reports entered against Canadian projects, which caused posting errors. Switching to Source required turning off the sales tax taxation rules. That in turn broke use tax entries in invoice journals. This is one user's account, not Microsoft's, but it shows how the choice can trade one problem for another.

The second is defects. A Dynamics 365 Community support article reports that

 

References

  1. Dynamics 365 Project Operations: Intercompany Expenses in Expense Management Microsoft 365 Roadmap 2026-11-17T18:36:41.967573Z
  2. Intercompany expenses | Microsoft Learn learn.microsoft.com
  3. Microsoft Copilot Roadmap | Microsoft 365 microsoft.com