Category
stayInformed
Severity
normal
Major change
False
Last modified
2026-08-12 10:04:57
Summary source
Azure OpenAI (gpt-4.1)
Action by (Graph)
—
Action by (AI)
2026-09-11 00:00:00
Services
Dynamics 365 Apps
Tags
New feature
Master tags
User, Admin, Compliance
Roadmap IDs
One-line summary
Project Revenue recognition in Dynamics 365 Project Operations can now use cost estimates instead of EAC, providing steadier revenue, improved compliance, and easier audits. GA on Sept 11, 2026.
Similar updates
More like thisMC1190099 Dynamics 365 Project Operations – Enable on-account transactions with project category support
MC1190085 Dynamics 365 Project Operations – Use general journals against projects for Integrated deployments
MC1191197 Dynamics 365 Project Operations - Edit per diem transaction date, exchange rate in expense management
MC1190094 Dynamics 365 Project Operations - Split credit card transactions in Expense Management
MC1204658 Dynamics 365 Customer Service – Simulate AI field prediction capability from Case Management Agent
MC1181915 Microsoft Dataverse, Dynamics 365 Apps – Storage capacity and entitlements update
Details
Body (from Message Center)
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:
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.
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.
Raw JSON (for debugging)
Expand/collapse the full payload below.
Show/hide raw
{
"snapshot_item": {
"action_required_by": null,
"ai_action_required_by": "2026-09-11T00:00:00Z",
"ai_actions": [],
"ai_master_tags": [
"User",
"Admin",
"Compliance"
],
"ai_model": "gpt-4.1",
"ai_summary": "Project Revenue recognition in Dynamics 365 Project Operations can now use cost estimates instead of EAC, providing steadier revenue, improved compliance, and easier audits. GA on Sept 11, 2026.",
"ai_topics": [
"Dynamics 365 Apps",
"Dynamics 365 Project Operations"
],
"category": "stayInformed",
"details_map": {},
"id": "MC1453424",
"importance": 4,
"is_major_change": false,
"last_modified": "2026-08-12T10:04:57Z",
"ms_products": [
"Dynamics 365 Apps"
],
"platforms": null,
"roadmap_ids": [],
"services": [
"Dynamics 365 Apps"
],
"severity": "normal",
"tags": [
"New feature"
],
"title": "Dynamics 365 Project Operations - Enable Project Revenue recognition using cost estimate instead of EAC"
}
}