Project management and accounting, Project Operations, and open-project migration
How AX 2012 Project management and accounting — project types, WBS, funding sources, revenue recognition, WIP, and project-driven procurement — upgrades to D365, including the decision between staying on PMA and adopting Project Operations.
What you will be able to do
Identify the platform deltas between AX 2012 Project management and accounting and D365
Describe the decision framework for choosing D365 Project management and accounting versus Project Operations
Explain how WBS, funding sources, estimates, and revenue recognition map to D365
Plan the Wave 5 open-project and project-WIP load with reconciliation gates
Map project-driven procurement and inventory transactions to D365 project purchasing
Introduction
AX 2012 Project management and accounting is one of the more stable areas of the upgrade — project types, project groups, posting profiles, WBS activities, funding sources, and the estimate/eliminate cycle all use the same tables and the same logic in D365.
Project types and project groups
The project type controls the accounting behaviour: which accounts receive cost, which accounts receive revenue, and whether WIP is involved. This logic is identity-mapped. The data upgrade carries the project-type configuration forward.
Work breakdown structure and scheduling
Activity hierarchy. WBS activities form a hierarchy with parent-child relationships, summary tasks, and leaf-level work packages. This is unchanged from AX 2012. Effort and duration. Each activity carries planned hours (effort) and duration. The scheduling engine calculates dates based on assigned resources and calendars.
Funding sources and billing rules
A project contract can have multiple funding sources: one or more customers, an organisation (the company itself), or a grant. Funding rules determine how costs are allocated across sources (percentage split, spending limit, priority order).
Revenue recognition and WIP
Estimate: Run the estimate process to calculate percentage of completion (cost incurred ÷ total budget) and post the corresponding revenue accrual to WIP. Post estimate: Transfer the calculated amounts to the GL (debit WIP revenue, credit accrued revenue).
The Project Operations decision
Project Operations is a separate Dynamics 365 application that sits on Dataverse and integrates with Finance & Operations via dual-write. It provides:
Project-driven procurement and inventory
AX 2012 supports purchase orders pegged to a project: the PurchLine.ProjId field links the purchase to a project, and cost is posted to the project on product receipt (committed cost) and on invoice (actual cost). This is identity-mapped in D365.
Open projects and WIP at Wave 5
At Wave 5 (the canonical wave for open production, projects, and assets), any project that has not been marked as Completed or Closed is considered open. This includes:
Knowledge check
Summary
Project management and accounting is one of the most identity-mapped areas of the AX 2012 to D365 upgrade. Project types, project groups, funding sources, billing rules, WBS, and the estimate/eliminate cycle all carry forward.