The aim is straightforward: help billing teams understand an invoice without turning the review into a scavenger hunt. But this is a planned usability update—not confirmation of a release, new billing calculations, or changed posting rules.
What the invoice update would change
The roadmap description outlines four changes:
- A timeline on the invoice summary. Reviewers would gain an at-a-glance indication of where the invoice stands without leaving the summary. The precise events, statuses, and dates displayed have not been established.
- Current and future pending transactions identified separately. Pending entries would indicate whether they are current or future-dated, with current transactions appearing first. The exact date boundary behind those labels remains unconfirmed.
- Time and material transactions grouped by class. The tab would separate transaction classes such as time, expense, and material, making each type easier to review independently.
- Address details moved to the end. Amounts and transactions would receive greater prominence, while address information would remain farther down the invoice.
These changes fit the structure Microsoft already documents for modern invoicing. Microsoft Learn describes a Summary financial overview, a Details area containing information such as addresses, and a Time & Material area containing time entries, expenses, and materials. That documentation applies to Project Operations Core and Project Operations integrated with ERP; it does not independently establish delivery of this roadmap item.
The distinction matters: rearranging a review interface is not the same thing as changing which transactions qualify for billing.
Availability: the dates need careful reading
The roadmap record lists the following scope and estimates:
| Field | Listed value |
|---|---|
| Status | In development |
| Platform | Web |
| Cloud | Worldwide (Standard Multi-Tenant) |
| Preview | March 2026 |
| General availability | September 2027 |
The preview date should not be treated as proof that preview access is available. March 2026 precedes the record’s November 5, 2026 publication timestamp, yet the item remains marked In development. That combination leaves actual preview availability unresolved.
September 2027 is also a future estimate, not a deployment commitment. Microsoft explicitly says its roadmap provides estimated release dates and descriptions, and that the information is subject to change.
For administrators, the sensible interpretation is “track and prepare,” rather than “enable this now.”
Why pending transactions deserve attention
Microsoft Learn defines Pending Transactions as billable items not yet added to the current invoice. Reviewers can inspect those entries and select items to include. This is different from Edited Transactions, which exposes changes affecting invoice amounts. Microsoft also warns that pending and edited transaction calculations are not performed for invoices created before enabling the documented modern-invoicing feature.
That provides useful context for the planned date labels. As an analytical inference, distinguishing current items from future-dated ones could make a mixed pending list easier to assess. It would not, by itself, establish that an item belongs on the invoice.
There is another important distinction in the existing integrated-ERP workflow: transaction class is not billing type. Microsoft documents invoice-line groupings of Chargeable, Non-chargeable, and Complimentary. Only chargeable details contribute to the invoice-line total. Grouping time, expenses, and materials would answer “what kind of transaction is this?” rather than “does this transaction contribute to the bill?”
In short, a tidier list still needs a proper billing review.
Do not assume what “future” means
Microsoft’s modern-invoicing documentation describes a separate accounting-date capability. With Enable Invoice Date Driven Accounting enabled, the accounting date determines the financial posting period and serves as the invoice’s transaction cutoff. Eligible future-dated transactions can be included through that date. This documentation does not confirm that roadmap item 578905 uses the same mechanism for its current/future labels.
Until Microsoft connects those details explicitly, teams should avoid assuming that “current” means today, the invoice date, or the accounting date. Likewise, the accounting-date feature flag should not be presented as an activation requirement for these planned usability enhancements.
The timeline deserves similar restraint. Microsoft’s integrated-ERP documentation identifies Draft, In review, and Confirmed project invoice statuses, with editing permitted before confirmation. Those existing statuses do not prove what the new timeline will display—and certainly do not establish a draft-to-posted history.
The practical takeaway
This is a focused interface improvement with a potentially useful payoff: putting invoice context, transaction categories, and pending-item dates closer to the reviewer’s line of sight.
Once availability is confirmed, billing teams should validate the timeline’s contents, test the date-label boundary, and ensure transaction-class sections do not obscure chargeability checks. Those are recommended acceptance checks, not documented installation steps.
For now, the value is in the direction of travel: less navigation and clearer presentation. The unanswered details—especially availability, timeline contents, and date classification—remain the difference between a promising roadmap entry and a feature ready for a billing run.