Microsoft's own roadmap caveat applies in full. Dates and descriptions are estimates and can change, and entries may be removed once a feature ships, is cancelled or is postponed. Nothing here has shipped yet.
What the roadmap entry does and doesn't say
The entry is short. It names three things: visibility into not-ready transactions, additional billing views, and fewer manual steps. It does not say:
- what the new views are called
- which fields they add
- whether any automation is involved
- whether the existing feature flag will control the rollout
Anything beyond the three points above would be guesswork, so treat design details as unannounced.
This is an extension, not a debut
"Not ready to invoice" visibility is not new in Project Operations. Microsoft Learn's Billing hub page already has a "What's new" section. It lists visibility for Not Ready to Invoice transactions, streamlined invoice creation, instant amount calculations and notifications in select scenarios, and performance and user experience improvements. Those updates are reached by enabling the flag Enable Billing Hub updates.
So the February 2027 item looks like another step on a path Microsoft has already started. The roadmap text doesn't say how it builds on the current feature, so that reading is an inference.
How Billing hub works today
The Learn documentation is the baseline for what the new work would change. It applies to Project Operations Core and Project Operations Integrated with ERP. The default Billing hub view shows the list of active project contracts and contract lines in a nested grid. You open it from the left pane under Sales > Billing Hub.
At contract level, the hub shows these fields:
- name
- primary customer
- total amount
- spent amount
- a count of ready-to-invoice transactions
- available advances
- advances
- product-based lines
At contract-line level, it shows these fields:
- project
- billing method
- invoice schedule type
- milestones
- backlog for time, material, expense and fee
- invoiceable backlog
- spent amount
Reviewing the backlog
The documented procedure for working the invoiceable backlog goes like this:
- Open a contract line's backlog by selecting a category amount, such as Time, or the Invoiceable backlog amount.
- Select the transactions you want to change.
- Set the billing status by choosing Ready to invoice or Not ready to invoice in the subgrid options.
- Select Update Totals on the Billing hub page so the calculated fields reflect the latest status.
Why Update Totals matters
Learn says that, because of how the platform handles roll-up fields, amounts for newly added project contracts start out as NULL. Selecting Update Totals fills in the calculated values. If a contract's numbers look empty, try this action first.
Create invoice and Add to invoice behave differently
- Create invoice on the Billing hub page includes every transaction in a Ready to invoice state across all contract lines of the selected contracts.
- Create invoice from a specific backlog category (time, materials, expenses, fees or milestones) includes only the transactions you selected.
- Add to invoice puts the transaction on the single draft invoice for that contract and customer. If several drafts exist, it uses the most recently created one. If none exists, it creates a new invoice.
The first two behaviors matter for the roadmap item. A transaction left in "not ready" status stays off any invoice built from the hub page. Better visibility into those transactions therefore matters most to teams that bill in bulk from the top-level page.
Why this matters to billing teams
Billing teams often can't tell why an amount hasn't been invoiced. It might be unapproved, held back deliberately, or blocked by a not-to-exceed limit. Microsoft's description suggests the new views are meant to make that difference easier to see. This is general industry reasoning, not a detail from the roadmap. The existing documentation shows the pieces already in place: separate Ready and Not ready statuses, and an action to reevaluate not-to-exceed status.
Microsoft's billing backlog documentation also contains a warning. Project Operations doesn't function correctly when these status values are updated with custom code. Teams that script billing statuses should be careful, whatever new views arrive.
Preparing before February 2027
Because the details are unannounced, the useful steps are about preparation:
- Check your deployment type. Learn documents Billing hub for Core and for Integrated with ERP. Confirm which one you run before planning around the roadmap item.
- Find out whether the current updates are on. The Enable Billing Hub updates flag controls Microsoft's earlier enhancements. Whether the new work will use the same flag is not stated.
- Trial in a non-production environment. Run the existing Ready and Not ready flow and Update Totals there, so you can compare when new views appear.
- Review custom billing views. Learn refers to customizing Billing hub views. Customizations may need a second look once Microsoft publishes release notes.
- Watch the roadmap entry. Dates move. Microsoft says entries can be removed when features ship or are postponed.
Bottom line
This is an incremental but sensible improvement to Billing hub, which Microsoft describes as becoming the central invoicing workspace. For finance and project accounting teams, the value will depend on details Microsoft hasn't published. Treat February 2027 as a target, not a commitment. The existing Billing hub capabilities are already documented and usable now.
References
- Dynamics 365 Project Operations: Optimize Project Operations: Billing hub updates Microsoft 365 Roadmap · 2026-11-17T18:36:41.967573Z
- Create proforma project invoices with Billing hub learn.microsoft.com
- billing hub learn.microsoft.com