Dynamics 365 Project Operations Subscription Billing: ERP Setup, Dual-Write Maps and Auto-Posting

Microsoft is now closing that operational gap. Tracked under AI at Work roadmap ID 576737 (and announced in Microsoft 365 Message Center notice MC1472430 ), Microsoft is introducing support for subscription billing in Dynamics 365 Project Operations. While the roadmap entry targets a September 2026 preview window and a September 2027 general availability date for Worldwide Standard Multi-Tenant web environments, Microsoft Learn's September 2026 release documentation and product guides already detail the exact architecture, version requirements, and dual-write mappings needed to run it.

Before your finance team celebrates the end of manual monthly billing spreadsheets, however, it is crucial to read the architectural fine print. Microsoft Learn documentation explicitly notes that this capability is currently supported only for the Project Operations Integrated with ERP deployment type and applies specifically to fee-type transactions. Organizations running Lite deployments (Dataverse-only without Dynamics 365 Finance) are not part of this specific pipeline.

The Architectural Split: Who Owns What?​

Why didn't Microsoft just copy-paste a recurring billing calculator directly into Dataverse? Because duplicating an enterprise accounting and revenue-recognition engine in two separate databases is a recipe for audit nightmares. Instead, Microsoft kept each application as the system of record for what it already does best, using dual-write synchronization to bridge Customer Engagement (CE) in Dataverse and Finance and Operations.

According to Microsoft Learn's Subscription billing documentation, the division of labor breaks down like this:

In short: Project Operations initiates the contract line and drives the pro forma invoice preparation, while Finance handles the heavy scheduling math in the middle and the legal accounting at the end.

Roadmap Promises vs. Current Documentation​

It is worth noting a distinction between high-level roadmap goals and current implementation guides. Roadmap ID 576737 and the archived 2026 release plan highlight capabilities such as standard and tiered-based pricing, consolidating multiple billing lines into a single invoice, fee journal-based billing, subscription holds or terminations, and refund handling.

Microsoft Learn's current procedural documentation confirms how Finance manages schedule pricing, proration, holds, and terminations, and explains how subscription charges can be reviewed alongside time-and-material and fixed-price work on a single pro forma invoice. However, the current setup guide does not yet lay out step-by-step configuration procedures for tiered pricing structures or refund workflows—a reminder that with general availability slated out to September 2027, roadmap descriptions represent planned trajectory as much as immediate functionality.

Version Requirements and Dual-Write Prerequisites​

According to Microsoft Learn's What's new September 2026 - Project Operations Integrated with ERP documentation, this capability aligns with two specific component versions:

• Project Operations in Microsoft Dataverse: version 4.171.3551.6
• Project management and accounting in Dynamics 365 Finance: version 10.0.49

Because the workflow spans both systems, administrators must enable features in a strict sequence: Finance first, and Project Operations second. Why? Because the placeholder schedule generation and subscription engine that Project Operations calls upon originate inside Finance.

1. Feature Management in Dynamics 365 Finance​

In Finance Feature management, admins must enable the following switches in order:

1. Subscription billing: Activates the core billing schedule engine, lines, and detail generation.
2. Recurring contract billing: Enables billing frequencies, start/end dates, and proration logic.
3. Billing schedules and deferrals with projects: Links billing schedules and deferrals to specific projects and funding sources.
4. Subscription billing for Project Operations: Enables automatic creation of placeholder billing schedule headers from synced contract lines and enforces read-only locking once invoicing starts.
5. (Preview) Enable project fee journals to support subscription billing for Project Operations for manufacturing: Optional preview switch required only if your organization uses project fee journal-based subscription billing for manufacturing scenarios. (A related capability for production or stocked scenarios reached general availability in September 2026 via the stocked scenarios feature flag.)
6. Enable line discounts and additional fee for Project Operations integrated with ERP based scenarios: Mandatory if you want line discounts to actually render on the generated invoice.

2. Feature Control in Project Operations​

Once Finance is ready, navigate to Project Operations Feature control settings and enable Subscription billing. This exposes the Subscription based invoice schedule type on contract lines, adds the Subscriptions tab, and unlocks subscription views inside the Billing hub.

3. Required Dual-Write Table Maps​

Without updated dual-write maps, subscriptions will never appear on Project Operations contract lines and billing locks will fail to sync back to Finance. Microsoft Learn specifies five mandatory dual-write maps and versions:

• Project invoice proposals V2 (invoices): version 1.0.0.5
• Project contract lines (salesorderdetails): version 1.0.0.3
• Project subscription billing schedule header (msdyn_subscriptions): version 1.0.0.0
• Project subscription billing schedule lines (msdyn_subscriptionlines): version 1.0.0.0
• Project subscription billing detail lines (msdyn_subscriptionbillingdetails): version 1.0.0.0

If your team has customized out-of-the-box table maps, you will need to reapply those customizations when activating the updated map versions in the dual-write admin interface.

Step-by-Step: How the Billing Lifecycle Works​

Imagine a consulting firm managing a cloud migration project. Alongside 500 hours of engineering labor (Time and Material), the firm charges the client for 50 managed security seats every month and a quarterly compliance audit report. Here is how that flows through the new pipeline:

Step 1: Contract Line Creation (Project Operations)​

1. Open the project contract in Project Operations and navigate to Contract lines.
2. Create or open a contract line. Keep the Billing method set to Time and material, and set the Invoice schedule type to Subscription based.
3. Save the line. Dual-write synchronization automatically generates a placeholder billing schedule header in Finance pre-populated with the contract, project, customer, and invoice transaction type.

Step 2: Schedule Configuration (Dynamics 365 Finance)​

In Finance, complete the subscription details on that schedule header:

• Define the Start date, End date, and Proration rules.
• Choose the Billing frequency: Microsoft Learn documents support for one-time, daily, biweekly, monthly, quarterly, semiannually, or annually.
• Add Billing lines specifying description, transaction class, quantity, unit of measure, unit price, net amount, product, and transaction category.

A single contract can hold multiple subscription headers, each header can contain multiple billing lines, and each subscription can be billed on its own schedule—or reviewed alongside other project charges.

Step 3: Pro Forma Invoicing and the Cut-Off Guardrail (Project Operations)​

Finance calculates the schedule and synchronizes the header and billing detail lines back to Project Operations, where they appear in a read-only view on the contract line (accessible via View billing detail). When it is time to bill:

1. Open the Billing hub and inspect the Invoiceable backlog for the subscription contract line.
2. Select eligible subscription transactions and mark them Ready to invoice.
3. Select the transactions again and click Add to invoice to open the pro forma invoice summary.
4. Review the recurring charges on the Subscriptions tab, confirm the pro forma invoice in Project Operations, and let the system generate the invoice proposal in Finance for final posting.

Built-in Safeguards: Two critical controls prevent billing chaos here. First, billing details are only eligible for invoicing once they fall within the invoice cut-off date, ensuring future periods are never accidentally pulled forward. Second, the moment Project Operations initiates invoicing activity for a billing detail, dual-write sends a lock signal back to Finance, turning those specific billing detail lines read-only in Finance. Accountants can still place holds or terminate a subscription in Finance for future periods, but nobody can retroactively alter the unit price or quantity of a period currently being invoiced downstream.

Setting Up Hands-Free Automated Invoicing and Posting​

Predictable Monthly Recurring Revenue (MRR) loses half its charm if a billing clerk still has to click "Confirm" and "Post" five hundred times at month-end. Microsoft allows administrators to automate both halves of the cycle, provided two specific technical gotchas are addressed.

1. In Project Operations: Configure automatic invoice creation on the project contract using Project Operations' invoice batch capabilities, and ensure the ProcessRunner flow is running. This automates fee actual creation, marking items ready to invoice, adding them to a pro forma invoice, and confirming it.
2. In Dynamics 365 Finance: You must run Project invoice proposal V2 map version 1.0.0.5 or later. This specific update adds the ShouldAutoPost field, which carries the Post invoice automatically flag from Project Operations over to Finance. If you are stuck on version 1.0.0.4, that flag will not cross the bridge, and updating the map later will not retroactively fix proposals that already synced.
3. Configuring the Finance Batch Job: Navigate to Project management and accounting > Periodic > Invoice > Post invoice proposals. Filter the Invoice proposal table for Post invoice automatically = Yes. Crucially, you must set Late selection = Yes before setting your recurrence pattern (for example, running every 10 minutes with no end date). Without Late selection enabled, Finance freezes the query results present at the exact moment you set up the batch job and attempts to run that static list forever, completely ignoring newly synchronized invoice proposals.

Summary for Dynamics 365 Administrators​

• What is changing: Subscription billing is coming to Dynamics 365 Project Operations (Roadmap ID 576737 / MC1472430), linking Finance's recurring billing schedules directly to Project Operations contracts and pro forma invoicing.
• Scope limitation: Currently documented exclusively for Project Operations Integrated with ERP deployments and fee-type transactions (Dataverse 4.171.3551.6 and Finance 10.0.49).
• Deployment order: Enable the four core Finance Feature management switches first, enable Project Operations Feature control second, and activate the five required dual-write table maps (including invoices 1.0.0.5 and salesorderdetails 1.0.0.3).
• Automation watch-outs: Ensure Project invoice proposals V2 is on 1.0.0.5+ to sync the ShouldAutoPost field, and always enable Late selection = Yes on the Finance auto-posting batch job.