Unit4 PSA to D365 Project Operations and PMA: mapping a mature project model

How Unit4's professional-services project accounting model — projects, activities, resources, timesheets, billing rules and revenue recognition — translates into D365 Project management and accounting, and when to choose Project Operations instead.

What you will be able to do

• Describe Unit4 PSA's four-level project hierarchy and map each level to D365
• Explain how resources, timesheets and expense integrate in both systems
• Map Unit4 billing rules to D365 project contract and invoice setup
• Explain the strategic choice between D365 PMA-only and Project Operations for Unit4 customers
• Describe the Project-as-Attribute-Value migration pattern for customers who never licensed PSA

Introduction

Unit4's project accounting sub-system — referred to variously as PSA (Professional Services Automation), Project Accounting or simply Projects depending on the release — is one of the strongest parts of the product.

Unit4 PSA: the project hierarchy and data model

Project — the top-level record. Carries a project code, a Project Manager Resource, a customer Relation (for billable projects), a project type (fixed-price, time-and-materials, internal, etc.), a status (planning / active / on-hold / closed), planned dates, a budget structure, a transaction currency, and a configurable bundle of…

Timesheets, expense and the posting flow

A timesheet in Unit4 is captured against the grid of Resource × Activity × Date × Time Type (productive, training, vacation, sick, internal). Once approved through the workflow engine, each timesheet line becomes a posting candidate that flows through the standard operational-event-to-voucher lifecycle (described in the Posting Engine…

Mapping to D365 PMA and Project Operations

[!IMPORTANT] The Employee / Resource fragmentation is the most consistently underestimated scope item in Unit4 migrations. A Unit4 Employee Relation that is also a PSA Resource is a single record. In D365, it fragments across HcmWorker, HcmPositionWorker, ProjResource, SysUserInfo and a Microsoft Entra ID identity.

The PMA-only versus Project Operations decision

This is the most consequential design decision of a Unit4 project-module migration and it must be made early, because it changes the Dataverse footprint, the security model and the integration topology of the entire programme.

The Project-as-Attribute-Value migration pattern

A significant proportion of Unit4 customers — particularly those in the public sector and higher education who licensed Unit4 primarily for its finance capability — use A3 as a project attribute with no PSA sub-system record behind it. "Project" for these customers is a dimension code, not a project master.

Knowledge check

Summary

Unit4 PSA is a genuinely strong project accounting model, and D365 provides equivalents of equal or greater capability. The migration is close conceptually; the effort lies in the Resource fragmentation, the Billing Rule decomposition, and the Project-as-Attribute-Value pattern.