MWPRO IMPACT SCORE
OPERATIONAL IMPACT
29
0
25
50
75
100
MODERATE IMPACT • ASSESS BUSINESS IMPACT
Recommended Action:
Take a look and decide whether this affects your tenant, users or support teams.
Take a look and decide whether this affects your tenant, users or support teams.
What is MWPro Impact Score?
Watch our 60‑second explainer
Primary Audience
Tenant AdminsMicrosoft 365 AdminsIT ManagersService Owners
Why this score?
AI Confidence
HIGH
Enough detail is available to trust this assessment.
Assessment Reasoning
This feature introduces an optional change to revenue recognition calculations in Dynamics 365 Project Operations. Admin impact is moderate as finance and project configuration teams may review policies and settings if adopting the feature. User impact is minor since it mainly affects financial reporting rather than core project workflows. Urgency is low to moderate as the feature is available but does not require immediate action, and implementation effort involves review and possible configuration changes rather than major migration.
34
Admin Impact
18
User Impact
28
Urgency
32
Effort
WHAT YOU NEED TO KNOW
AT A GLANCE
Dynamics 365 Project Operations will let you base revenue recognition on cost estimates instead of EAC. This offers a steadier and more predictable approach.
END USERS
No major end-user change expected.
IT ADMINS
No immediate admin action required.
ROLLOUT TIMELINE
Upcoming:
11 September 2026
11 September 2026
📢 Official Microsoft Message Center Announcement
Dynamics 365 Project Operations – Enable Project Revenue recognition using cost estimate instead of EAC
Message ID: MC1453424
We are announcing the ability to enable Project Revenue recognition using cost estimates instead of EAC in Dynamics 365 Project Operations. This feature will reach general availability on September 11, 2026.
How does this affect me?
This feature enables users to project forecast or budget to calculate percentage of completion instead of the current estimate at completion (EAC), giving steadier revenue, clearer insights, and easier audits.
Once enabled, this feature’s capabilities include:
- Using the original project estimate for PoC calculations: Delivers stable, predictable revenue without EAC-driven fluctuations.
- Anchoring revenue recognition to a fixed baseline: Improves transparency and boosts confidence in reported project financials.
- Reducing reliance on changing forecasts: Minimizes rework and exceptions during month-end close.
- Providing clear traceability from estimate to recognition: Strengthens audit readiness and compliance.
- Aligning revenue with initial project expectations: Enhances visibility into true project performance and profitability.
- Creating smoother revenue trends across reporting periods: Enables better executive decision-making and financial planning.
- Standardizing how teams evaluate project progress: Supports consistent financial processes across the organization.
This message is for awareness, and no action is required.
For more information regarding this feature, please visit Enable Project Revenue recognition using cost estimate instead of EAC.
Source: Microsoft Message Center • Analysed by MWPro
