M3 project management: from work-order proxies to D365 project accounting
How M3 handles project and job costing through work orders, service orders, and CAS cost accounting — and how that lightweight model translates to D365 Project Management and Accounting, which typically represents an upgrade rather than a like-for-like migration.
What you will be able to do
Identify which project construct a given M3 tenant is actually using
Map M3 work orders, service orders, and CAS job costing to D365 project types
Explain why the 'we have no projects' assumption leads to expensive Phase 2 work
Articulate the D365 Project Operations decision and when it should be considered
Introduction
M3 is an operationally excellent ERP for manufacturing, procurement, and distribution. It is not a project management system. Project and job costing capability exists in M3, but it is materially lighter than the dedicated project modules found in IFS or Infor LN, and many M3 tenants have compensated by routing project-like work through…
What M3 tenants actually use for projects
The honest answer to "how does M3 handle projects?" depends entirely on the vertical and the tenant. There are four patterns, which can appear in combination:
D365 project types and when to use them
D365 PMA offers six project types, each with distinct WIP and revenue-recognition semantics:
Revenue recognition and WIP
D365's explicit WIP accounting is the most significant capability upgrade from M3 for tenants moving beyond basic job costing. In M3, WIP on a production order sits in a cost accumulation bucket until the order is closed and CAS posts the variance.
The D365 Project Operations decision
D365 Project Operations is a separate application that extends PMA with professional services automation (PSA) capabilities: resource scheduling and utilisation, time entry from mobile devices, integration with Dynamics 365 Sales for opportunity-to-project conversion, and Microsoft Project integration for project scheduling.
D365 project accounting objects, not just labels
When an M3 tenant genuinely has project accounting — through PMS, CAS job costing, service orders or disciplined custom fields — the D365 target is a real object model, not a single dimension value. The core records are:
Knowledge check
Summary
M3's project capability is lighter than the rest of its functional estate. Most M3 tenants model project-like work through MFS work orders, OIS order types, CAS job costing, or a combination of all three, supplemented by ION workflows and custom fields.