The feature addresses a practical billing problem: preparing an invoice early without making its invoice date the boundary for everything it can contain. The important catch is that the accounting date also controls the accounting period—not just which transactions appear.
What the roadmap promises—and what remains planned
Microsoft’s roadmap entry 577876, titled “Optimize Project Operations – Allow to invoice future-dated transactions,” lists these deployment targets:
- Product: Dynamics 365 Project Operations, Core and integrated deployments.
- Platform: Web.
- Cloud: Worldwide, Standard Multi-Tenant.
- Status: In development.
- Preview target: October 2026.
- General availability target: March 2027.
Those dates require care. As of November 11, 2026, the listed preview month has passed, but the entry’s status remains In development. That is not confirmation that preview access has reached a particular environment. Microsoft explicitly describes roadmap release dates as estimates and says its information can change. March 2027 should therefore be treated as a target, not a deployment commitment.
How the documented workflow works
Microsoft Learn’s modern-invoicing guidance applies to Project Operations Core and Project Operations integrated with ERP. It identifies Enable Invoice Date Driven Accounting as the required feature flag. In an environment where the capability is available and enabled, Microsoft documents this sequence:
- Set Accounting date on the invoice header.
- Select Refresh Invoice Line Transactions to bring in eligible transactions dated through that cutoff. Skip the refresh when no additional transactions are needed.
- Review the invoice, then select Confirm.
Success means the refreshed invoice includes eligible items through the chosen accounting date. It does not mean the system rewrites the underlying actuals’ transaction or document dates; Microsoft says those remain unchanged.
A later cutoff is not a billing override
“Future-dated” needs a boundary of its own. Microsoft’s invoice-management documentation ties invoice details to unbilled sales actuals and milestones associated with the relevant contract line, and requires transactions to be marked Ready to Invoice. A later cutoff should not be interpreted as permission to bill every anticipated item.
If an expected item is missing, the useful checks are whether it belongs to the relevant contract line, is ready for invoicing, and falls within the selected cutoff. The date-aware refresh instructions—not merely changing the header date—are the documented mechanism for bringing additional eligible items onto the invoice.
Review also matters before confirmation: Microsoft’s integrated-deployment guidance says draft and in-review invoices are editable, but confirmed invoices are not. It separately warns against using Dynamics 365 Sales invoices and Project Operations invoices interchangeably. This is a project-billing change, not a universal new rule for every Dynamics 365 invoice.
The practical takeaway
The operational benefit is a more flexible preparation window. The control implication is just as important: choosing the cutoff also chooses the accounting period for the resulting billed transactions. Based on that documented coupling, billing and finance teams should agree on the intended period before using a later date simply to collect more invoice lines.
It is a modest feature with a useful purpose: less friction between preparing an invoice and defining what belongs on it—without treating the accounting calendar as an afterthought.