Map Workday Projects, Project Billing, project Worktags, and the tight dependency on Workday Time Tracking to D365 Project management and accounting, cover the Project Operations decision, and address the HCM time-tracking integration explicitly.
Workday's Project Management module is tightly integrated with the rest of Financial Management and, critically, with Workday HCM. Projects in Workday are not standalone accounting objects — they are first-class Worktags, billing contracts, resource plans, and time-entry destinations simultaneously, all running through the Business…
A Workday Project is the root object. It has a unique identifier, a name, a hierarchy position (root projects may have sub-projects), a Project Type (Time and Material, Fixed Price, Cost Reimbursable, Internal), and a set of project-level Worktags (Cost Centre, Fund, Region, Programme) that default onto all transactions charged to the…
Workday's Time Tracking module is a native HCM capability on the same tenant as Financial Management. Workers record their time against projects, cost centres, and tasks through Workday's time entry pages; timesheets travel through a BPF approval chain (often including the project manager and the worker's cost centre owner);
D365 Project management and accounting (PMA) is the module included in D365 Finance that covers the full project accounting lifecycle.
Dynamics 365 Project Operations is a separate Dynamics 365 application, built on Dataverse and integrating with D365 Finance for the accounting back-end. It adds a richer delivery-management capability:
Workday Projects are tightly integrated with HCM, Time Tracking, and the Business Process Framework. The translation to D365 requires explicit decisions about project types, WBS structure, billing contracts, revenue recognition methods, and — most critically — the time-tracking integration path.