A businesswoman reviews an intercompany project invoicing dashboard showing transactions between two legal entities.
Microsoft's roadmap lists a Project Operations update called "Enhance intercompany invoicing filters and details." It targets the awkward part of intercompany billing: picking the right transactions and then tracing them afterward. It's the sort of change that rarely gets a headline, but finance teams feel it every month-end.

A businesswoman reviews an intercompany project invoicing dashboard showing transactions between two legal entities. Status and who it applies to​

Microsoft Learn says the feature is newly available with the 10.0.50 release. The roadmap entry (ID 576292) lists it as in development, with an estimated general availability of March 2027. The scope is the Web platform, the Worldwide (Standard Multi-Tenant) cloud, and Dynamics 365 Project Operations connected with ERP and manufacturing deployment types. Microsoft warns that roadmap dates and descriptions can change, so treat March 2027 as an estimate rather than a promise.

The feature is off by default. An administrator can enable or disable it in the Feature management workspace. According to the roadmap text, the path is to open Feature management, search for "Enhance intercompany invoicing filters and details," select it, and choose Enable now. That exact sequence comes from the roadmap entry. The Learn page only confirms that Feature management is where the switch lives.

Background: how intercompany project invoicing works​

Microsoft's documentation describes a lending legal entity that supplies the service or product and a borrowing legal entity that receives it. When the intercompany customer invoice is posted in the lending entity, a corresponding pending vendor invoice is created in the borrowing entity. After that, the borrowing entity posts the vendor invoice and invoices the end customer for the project work.

The lending entity's project accountant can do the invoicing manually, or set up a batch process to generate intercompany invoices on a recurring basis. The new options sit inside both of those flows.

What changes​

1. Invoicing method: invoices, credit notes, or both​

The roadmap says that when you create project intercompany customer invoices, you can choose Both, Invoices, or Credit notes. This controls whether charges and credits are processed together or separately.

Microsoft Learn spells out the selection rules and adds a fourth option the roadmap doesn't list:

  • Both puts positive and negative transactions under the normal invoice grouping. This is the default and the original behavior.
  • Invoices includes transactions whose amount is zero or greater.
  • Credit notes includes transactions whose amount is less than zero.
  • Both but Separate includes positive and negative transactions in separate invoice groupings.

So the roadmap's three-item list isn't the full set. The documentation goes further.

2. Date and balance criteria​

The roadmap says transaction-date and transaction-balance criteria help you target the transactions for a billing or financial period. Learn confirms part of this. Periodic processing gains start and end dates, matching the date criteria already available in manual processing. In the manual flow, Learn says the dates limit results by posting date. Learn doesn't separately describe a "transaction balance" control beyond the amount-based Invoicing method, so read the roadmap's balance wording with that in mind.

3. More context on invoice lines​

The roadmap says invoice lines will carry extra context about the resource and originating documents, such as expense reports and vendor invoices, where available. It adds that transactions originating in Dataverse will link to the integration journal line.

Learn documents several matching pieces:

  • An Original transaction field in Line details shows the originating document number. This replaces the need to use the button of the same name.
  • A Resource field shows the bookable resource name, so you can tell who logged the time or expense. The displayed value depends on whether the "Use employment default dimensions on integration journals" feature and its related setup are complete for the worker.
  • For a Project advanced journal line, Resource name identifies the resource in the Line details under Intercompany project.

The Learn text I reviewed doesn't mention the Dataverse integration-journal link or the expense-report and vendor-invoice source documents. Those remain roadmap claims. The roadmap's "where available" qualifier matters too. Don't expect every line to carry every field.

4. Credit notes that trace back to the original invoice​

The roadmap says credit notes generated from an intercompany transaction keep a relationship to the original free-text invoice. That lets finance teams and customizations trace credits back to the first charge. Learn describes something close. The original intercompany invoice number is shown and links back to the original intercompany invoice, and an Original invoice field identifies it in the line details. Learn also notes that creating intercompany invoices now enables Project advanced journal line by default.

Using the new filters​

Based on the documented manual flow, once the feature is enabled and live in your environment, the process in the lending legal entity looks like this:

  1. In Finance, go to Project management and accounting > Project invoices > Intercompany customer invoices, then select New.
  2. In Legal entity, select one or more borrowing legal entities. Optionally enter a project contract and project number.
  3. Enter Start date and End date to limit results by posting date.
  4. Optionally set Invoicing method to filter by balance. The default is Both.
  5. Select Search, choose the transactions to include, and select OK.
  6. Review the proposal, adding or removing lines and checking line details. Then select Post.

For batch runs, go to Project management and accounting > Periodic > Project invoices > Create intercompany customer invoices. Choose the companies and whether to create one invoice per project or per borrowing legal entity. Enter the dates and an optional Invoicing method, then use the Batch tab to schedule recurrence. Learn says the dates are saved as batch criteria.

If your organization requires review before posting, an administrator may have set up a workflow for intercompany invoices. Without one, you can post directly.

Why it matters​

This is my analysis, not a Microsoft claim, and Microsoft hasn't quantified any benefit. Still, the practical gains are easy to see:

  • Cleaner period-end billing. Separating credits from charges, and bounding runs by date, makes it easier to match what you invoice to what you intended for the period.
  • Faster investigation. Surfacing the originating document number, the resource, and the original invoice cuts down on clicking through screens when a borrowing entity queries a charge.
  • Better audit trails. Linking credits to originals helps with corrections, and it gives custom reports or extensions something stable to key on.

Before turning it on in a production environment, test it in a sandbox. Check whether any existing batch jobs or customizations assume the old grouping behavior. The feature is opt-in, and the default Both matches the original behavior.

Bottom line​

The roadmap lists this as in development with a March 2027 target, but Microsoft Learn already documents it as new in 10.0.50. It is a modest feature for a very specific audience: project accountants and ERP administrators running intercompany Project Operations. For those teams, better filters and clearer lineage are welcome. Anyone planning an upgrade should confirm which of the roadmap's extra details actually ship in their version.

 

References

  1. Dynamics 365 Project Operations: Enhance intercompany invoicing filters and details Microsoft 365 Roadmap 2026-11-17T22:45:29.907242Z
  2. Create intercompany customer and vendor invoices | Microsoft Learn learn.microsoft.com
  3. Microsoft Copilot Roadmap | Microsoft 365 microsoft.com