What the roadmap says is coming
Microsoft describes a modern invoice form that puts three things in one workspace:
- Contract information
- Invoice lines
- Billable transactions
Billing teams should be able to edit supported transaction details one at a time or in bulk. They should also be able to review pending charges and track adjustments next to key financial totals. Microsoft's stated aim is less navigation and repetitive work, with better visibility and accuracy before an invoice is confirmed.
Those are intentions, not measured results. The roadmap entry has no benchmarks, so any time-saving claim is Microsoft's expectation.
What the existing documentation shows
The roadmap text is short, so the Microsoft Learn documentation helps explain what the "modern invoice form" is. It is also where the limits show up.
Microsoft Learn says the modern invoicing experience gives a consolidated view of contracts, contract lines, and invoiceable transactions, and that it applies to both Project Operations Core and Project Operations integrated with ERP. Projects can bill time, expenses, materials and milestones, so one invoice cycle can hold a lot of transactions. Microsoft's own wording is that project-based organizations often manage thousands of transactions per invoice cycle.
The documented form is split into these sections:
- Summary: a high-level financial overview of the invoice.
- Details: items such as invoice addresses.
- Time & Material: time entries, expenses and materials. You can edit billing type, quantity, price, and tax directly.
- Fixed Price: milestone and progress billing.
- Advance & Retainers: applied and unapplied advances.
- Product: product-based lines.
This documentation does not prove that every item above is new in roadmap item 580480. It may describe functionality that already exists, with the roadmap item building on it. Microsoft's roadmap entry does not say which pieces are new.
Bulk edit has limits
"Bulk edit" does not mean any field on any line can be changed. The documentation says users select several invoice line details (ILDs) from the invoice grid or subgrid. They then apply supported changes in one step. What can be edited depends on the transaction type:
| Transaction type | Editable fields |
|---|---|
| Time & Material | Billing type, quantity, price, tax |
| Fixed Price | Chargeability, price, tax |
| Products | Tax only |
| Applied advances | Extended amount |
| Regular advances | Not editable |
Microsoft says bulk editing helps similar items get updated uniformly, which reduces errors. That makes sense, but a bulk change applied to the wrong selection is still wrong, only faster. Billing teams should still check their selections before confirming.
Pending and edited transactions
The form includes two review views:
- Pending Transactions: billable transactions not yet on the current invoice. Users can select time entries, milestones, and available and applied advances to include from the Pending Transactions form.
- Edited Transactions: modifications to transactions that affect the invoice amount. Microsoft lists quantity, price, billing type and tax changes as examples.
There is a limitation. For invoices created before the feature was enabled, the system doesn't calculate pending and edited transactions. Older drafts will not be retroactively populated. Teams with long-running draft invoices should expect that gap after enabling.
Financial summary
The contract financial summary includes five figures:
- Contract Value: the total value defined in the contract.
- Billed Amount: cumulative billing to date, excluding the current invoice.
- Current Invoice Amount: the amount being charged on this invoice.
- Remaining Amount: the balance left after the billed amount.
- NTE (Not-to-Exceed): the contract's maximum allowable value.
These figures let a reviewer check an invoice against prior billing and the contract ceiling without leaving the form. Microsoft's documentation does not say the form automatically blocks overbilling, so don't assume it does.
The "Enhanced proforma invoice" flag in integrated deployments
Microsoft's docs also use the name "Enhanced proforma invoice" in a related place. For integrated deployments, the invoice proposal documentation says to enable the dual-write map for the Project Operations integration invoice proposal export entity (msdyn_customerinvoices) in Finance, and to enable the feature flag Enhanced proforma invoice in Project Operations. That is documented for the integrated-with-ERP scenario. It may or may not map directly to roadmap item 580480, and Microsoft has not said. Admins on integrated deployments should read the flag name and the dual-write prerequisite as a hint to check their setup, not as confirmed rollout guidance.
Earlier phases of the same effort
This work builds on earlier invoice-editing improvements. Microsoft's 2025 release wave 1 plan listed fewer clicks to edit one or more invoice line details, and fewer clicks to bulk edit multiple fields on an invoice line detail. A later "phase 2" release plan page repeats that scope and adds a better invoice summary. That page now carries an archive notice saying its content is no longer maintained and may not reflect current plans. It is useful history, not current status.
Third-party partners have also written up the modern invoice form. Inogic's walkthrough says that after enabling the Modern Invoice feature, users open the Invoices entity in the Sales group and switch to the Modern Invoice form. That is a partner description, not Microsoft's official procedure, so check it against your own environment.
What billing and admin teams should do now
- Identify your deployment. Check whether you run Project Operations Core or the version integrated with ERP. The documentation covers both, but the integrated scenario has extra Finance-side prerequisites.
- Check the feature flags. Find out which invoicing feature flags are on in your environment, and which are still off.
- Map your transaction mix. If most of your edits are on products or regular advances, bulk edit will help less than you might hope. Product lines allow tax edits only, and regular advances can't be edited.
- Plan for older drafts. Drafts created before enablement won't show calculated pending and edited transactions, so finish or review them first where practical.
- Watch the roadmap. The item is "In development." Dates can slip or the scope can change before GA.
Assessment
On its own the roadmap entry is thin. Its value comes from the documentation behind it, which shows what the modern invoice form does today and where its edges are. The headline promise is fewer clicks and better review before confirmation, which matters to teams reviewing hundreds of lines per cycle. The documented limits deserve equal attention: field-level restrictions by transaction type, and no pending or edited calculations for pre-enablement invoices. A February 2027 GA date is a target. Billing teams should test in a sandbox when the feature reaches their tenant, not assume it will behave as the roadmap summary reads.
References
- Dynamics 365 Project Operations: Optimize Project Operations: Enhanced proforma invoice Microsoft 365 Roadmap · 2026-11-17T18:36:41.967573Z
- How to Use Modern Invoicing in Project Operations - Microsoft Dynamics 365 CRM Tips and Tricks inogic.com
- Manage a proforma project invoice with modern invoice form learn.microsoft.com