Project management and accounting

How IFS's four-level project hierarchy, project-driven operational connections, earned-value controls, and revenue recognition translate into D365 Project Management and Accounting — and when to extend with Project Operations — with an honest assessment of where IFS depth requires deliberate design.

What you will be able to do

• Map the IFS project hierarchy to D365 PMA project and sub-project structure
• Explain how project connections to purchase orders, shop orders, and inventory translate
• Describe IFS revenue recognition methods and their D365 equivalents
• Identify where IFS project depth exceeds a standard D365 setup and what design is required
• Articulate the three Project Operations deployment topologies — and the option of running F&O PMA without Project Operations — and when each applies

Introduction

No module in an IFS migration requires more careful design work than Project Management & Accounting. IFS was built with project-driven industries at its core — engineering contractors, capital-equipment manufacturers, defence and aerospace organisations — and its project module reflects that heritage in depth and data-model priority.

IFS project structure

Project (PROJECT_TAB) is the top of the hierarchy. It carries the project ID, planned start and end dates, the budget, the customer reference for external projects, the responsible project manager, and the accounting defaults — including the Code Part values automatically carried onto all project-related transactions.

Operational connections: purchase orders, shop orders, and inventory

IFS routes most operational transactions through projects when projects are active. This operational depth is one of the areas where IFS exceeds a default D365 configuration if that configuration has not been explicitly designed for project-driven operations.

Project cost, revenue, and earned value

Project cost accumulation in IFS flows through the KP-series PostingCtrl Posting Types to project-specific Code Part C values. The cost lands on the project in the GL simultaneously with its operational source document; there is no separate project journal step for most transaction types.

D365 Project Management & Accounting

Project (ProjTable) is the top of the hierarchy, carrying project type, project group, project contract, funding sources, customer reference, and planned dates. The project type (Time and material, Fixed-price, Investment, Cost, or Internal) drives the revenue recognition behaviour;

The Project Operations decision

D365 Project Operations is Microsoft's unified project front-end, built on Dataverse, bridging PMA in F&O with Project scheduling (Project for the Web) and resource management.

Mapping bridge: project hierarchy, activities and project-attached postings

IFS projects often sit at the centre of the estate: purchasing, manufacturing, inventory, service and revenue all point at the project structure. The bridge into D365 must therefore preserve both hierarchy and accounting behaviour.

Knowledge check

Summary

IFS's project module is one of the deepest in the market. D365 PMA with the right topology is a capable target, but the mapping requires deliberate design at every level of the hierarchy.