For administrators, the important distinction is that this changes the integration model—not simply a maximum-line setting.
Release timing needs a careful reading
The roadmap information associated with item 577855, “Support larger invoices in Project Operations,” lists the feature as in development, with September 2025 preview availability and a December 2026 general-availability target. It identifies the web platform and Worldwide Standard Multi-Tenant cloud.
Those item-specific details were not exposed in the publicly rendered roadmap page during verification, so the dates remain roadmap metadata rather than independently confirmed availability. Microsoft’s roadmap also explicitly describes its dates as estimates subject to change. December 2026 is still a future target as of November 4, 2026—not evidence that the feature has shipped.
Microsoft Learn continues to label the invoice configuration documentation as preview and prerelease. Its broader asynchronous dual-write FAQ warns that preview features are not intended for production use.
Three connected maps—not just an invoice header
Microsoft’s configuration requires three maps to move into asynchronous processing:
- Project invoice proposal V2 (invoices): the draft invoice.
- Project Operations integration actuals (
msdyn_actuals): billed sales transactions. - Integration entity for project transaction relationships (
msdyn_transactionconnections): connections between actuals and the invoice proposal.
The documented preparation includes setting both project tracking parameters to On-Demand update, updating Dual-write Core to the latest version available for the environment, and placing the three maps into an integration job in the order above. The administrator then saves and runs the job asynchronously. Microsoft does not specify a fixed solution version in this procedure.
The documentation establishes support beyond 1,000 lines, but provides neither a replacement maximum nor measured throughput. “Larger” should not be read as “unlimited.”
Why a synchronized header is not the finish line
Microsoft’s existing invoice-integration documentation supplies useful operational context. A project manager creates and confirms a pro forma invoice in Dataverse. Its header travels one way into Finance, while confirmation also generates billing-related actuals. A periodic staging-import process creates the invoice proposal lines from billed sales actuals.
The accounts-receivable clerk or project accountant creates the customer-facing invoice; posting subsequently updates relevant Dataverse actuals with accounting details. Creating or deleting project invoice proposals directly in Finance is not supported.
The practical implication: a visible invoice header alone is not sufficient evidence of a completed billing integration. Validation should follow the related transactions and resulting proposal lines through the documented workflow. This is an operational inference from Microsoft’s integration description, not a reported test result.
The trade-off: background processing and consistency
Microsoft describes asynchronous dual-write as an eventual-consistency model: background processing sequences and transfers data instead of committing both systems at the same instant. Administrators should therefore test custom logic that assumes immediate synchronization.
Two configuration boundaries deserve particular attention:
- A transaction mixing synchronous and asynchronous entities can fail; Microsoft says its entities should use one mode, except for deletes.
- Asynchronous processing supports creates and updates. Deletes bypass that pipeline and remain synchronous.
Error handling also matters. Business-validation failures differ from retryable system failures, and outdated record versions can be skipped as nonretryable concurrency failures. Waiting longer is not a universal repair strategy.
For organizations evaluating larger Project Operations invoices, the sensible next step is a controlled preview assessment: verify environment compatibility, preserve the documented map sequence, and validate the complete billing flow before relying on the future availability target. More room for invoice lines is useful; knowing when those lines have actually reached Finance is just as important.