At month-end close, the finance team is still piecing together project margins from incomplete ERP exports and manually maintained spreadsheets. Time entries live in Harvest. Project purchases are in the ERP. Cost overruns only surface two weeks after the period closes — far too late to course-correct.
This is not an edge case. It is the norm across IT services firms, engineering consultancies, architecture practices and construction companies that run project-based operations. The root cause: a generic ERP built for distribution or manufacturing, structurally incapable of handling project accounting at the depth required by IFRS 15.
This guide covers the fundamentals of project accounting in an ERP, compares the three leading modules — SAP Project System, Microsoft Dynamics 365 Project Operations and Oracle PPM — and sets out the selection criteria for mid-market and large enterprises in 2026.
Why Project Accounting Is the “Poor Relation” of Generic ERPs
The Common Problem: Projects Managed Outside the ERP
Most generic ERPs were designed to handle repetitive transactional flows: purchase orders, inventory, invoices, payroll. The project dimension — with its temporal structure, phases, work packages and analytical allocations by deliverable — is typically a bolt-on layer, poorly integrated with the core system.
The direct consequence: project-driven companies improvise. Time entries go into Harvest or Toggl. Budget tracking lives in Excel. Progress billing is calculated by hand. Each tool talks to the others via weekly CSV exports — when everything goes smoothly.
Field feedback from implementation projects across Europe and North America consistently shows that the majority of mid-market project-based companies still track profitability with tools disconnected from their ERP. The impact is direct: project margin invisible in real time, late closes, decisions made on stale data.
The Challenge: IFRS 15 Mandates Revenue Recognition Based on Progress
The standard IFRS 15 “Revenue from Contracts with Customers”, mandatory for reporting periods beginning on or after 1 January 2018 (IASB), requires that revenue be recognised as performance obligations are satisfied — not at the point of invoicing.
For project-driven companies, this means calculating the percentage of completion for every active project each month, deriving the recognised revenue, and posting contract assets (unbilled revenue) and contract liabilities (deferred revenue) accordingly. Without an ERP that automates this calculation, it becomes a monthly spreadsheet exercise — error-prone and time-consuming.
Three Project Business Models and Their ERP Needs
Three models coexist, each with distinct ERP requirements:
- Fixed-price projects: set price, contractual schedule, payment milestones. The ERP must manage the initial budget, variances, and milestone-based billing.
- Time-and-materials projects: billing based on hours worked (day rates). The ERP must integrate timesheets and auto-generate fee invoices.
- Mixed projects: fixed price with T&M for overruns. The most complex case — the ERP must manage both modes on the same engagement, sometimes across different contract lines.
The Fundamentals of Project Accounting in an ERP
WBS: The Cornerstone of Financial Project Control
The Work Breakdown Structure (WBS) is the hierarchical decomposition of a project into deliverables, phases and activities. In an ERP, the WBS serves a dual purpose: it is both the operational management structure and the analytical accounting structure.
Without a WBS that maps to the chart of accounts, costs cannot be correctly allocated — labour, purchases, overheads — to each deliverable. Profitability can only be calculated at the overall project level, not by phase or work package, which is insufficient for ongoing management and early warning.
A poorly built WBS is the single biggest cause of failure in project accounting implementations: too flat (no granularity), too deep (unmanageable for operational teams), or misaligned with the contract structure. WBS configuration requires close collaboration between the project manager, the management controller and the implementation consultant.
Cost Allocation to the Project: Labour, Purchases, Overheads
A project accounting ERP must capture three types of cost:
- Labour: hours worked, validated through a timesheet, converted to costs using the fully-loaded hourly rate per employee.
- Direct purchases: purchase orders and supplier invoices charged directly to the WBS (materials, subcontracting, travel).
- Allocated overheads: share of indirect costs (rent, infrastructure, management) assigned to the project using a pre-defined allocation key.
The classic trap: timesheets not connected to the ERP. Hours are tracked in Harvest, Toggl or Jira — but they never flow into the project’s analytical accounting. The project margin calculated by the ERP becomes fictitious, because it ignores most of the cost of delivery.
Earned Value Management (EVM): Three Indicators to Watch
Earned Value Management detects financial drift weeks before it appears in the accounts:
- BCWS (Budgeted Cost of Work Scheduled): what should have been spent according to the original schedule — the planned value.
- BCWP (Budgeted Cost of Work Performed): the budgeted value of work actually completed — the earned value.
- ACWP (Actual Cost of Work Performed): what has actually been spent to date.
BCWP below ACWP signals a cost overrun. BCWP below BCWS signals a schedule delay. An ERP that surfaces all three indicators allows a management controller to detect drift by week three of the month — not at close.
In industrial projects (construction, energy, defence), EVM is a contractual requirement on major contracts. In IT services and consulting, it remains underused — mainly because the tooling is not integrated into the ERP.
IFRS 15 Revenue Recognition: Two Methods in the ERP
IFRS 15 allows two methods for measuring the degree of completion:
- Output method: progress based on contractual milestones or units delivered. Applicable when deliverables are objectively measurable (report submitted, module delivered, contractual milestone achieved).
- Input method: progress based on the ratio of costs incurred to total estimated costs. Better suited to long-term projects with deliverables that are difficult to quantify (complex engineering, bespoke R&D).
The ERP must support both methods, ideally configurable project by project. Automated calculation of recognised revenue, contract assets and contract liabilities is the ultimate test of a project accounting module’s maturity.
SAP Project System (PS) / S/4HANA Project Management
WBS Architecture in SAP
SAP PS organises the project structure in a four-level hierarchy: Project Definition > WBS Element > Network > Activities
The WBS Element is the base unit for analytical cost allocation. Each WBS Element can be linked to one or more Networks (internal technical orders) that break work into schedulable, sequenced activities. This granularity enables extremely precise management accounting — at the cost of rigorous configuration and significant parameterisation time.
FI/CO Integration: CATS, WBS, CO-PA
SAP PS is natively integrated with the FI (Financial Accounting) and CO (Controlling) modules:
- CATS (Cross Application Time Sheet): timesheet entry with direct allocation to a WBS Element or network activity. Historically austere interface, significantly improved in SAP Fiori.
- Direct allocations: purchase orders (MM module), supplier invoices (FI-AP) and expense reports allocated to the WBS via CO cost accounts.
- CO-PA (Profitability Analysis): margin analysis by project, client, region or any combination of analytical dimensions.
IFRS 15 revenue recognition is handled via the Revenue Recognition module in S/4HANA, with recognition rules configurable by contract type (fixed price, T&M, milestone billing).
SAP S/4HANA Cloud and Project-centric Finance
Since 2023, SAP has been pushing a new paradigm: Project-centric Finance in S/4HANA Cloud Public Edition. The classic PS architecture is simplified for mid-sized project companies — fewer hierarchy levels, a more accessible Fiori interface for non-finance project managers, and tighter integration with SAP BTP for business extensions.
Strengths and Limitations
Strengths: unmatched depth of management accounting on the market, native integration with SAP MM, PP and HR, native multi-currency and multi-entity support, powerful CO-PA for multi-dimensional margin analysis.
Limitations: CATS interface still dated (improved in Fiori but not yet on par with modern PSA tools), resource planning limited without the PS Resource Management add-on, high licence and configuration costs, steep learning curve for project teams.
Target profile: large industrial groups (construction, engineering, defence, energy) already running SAP ERP, with complex multi-entity, multi-currency projects.
Microsoft Dynamics 365 Project Operations
Architecture and Positioning
Dynamics 365 Project Operations launched in 2020 from the merger of Dynamics 365 Project Service Automation (PSA) with an enhanced project management module. It is Microsoft’s answer for professional services firms — consulting, IT services, engineering and architecture practices — that run on the Microsoft 365 ecosystem.
WBS, Resources and Timesheets
Project Operations natively includes:
- A WBS editor based on Microsoft Project, allowing project decomposition into tasks and sub-tasks directly in the browser — no Project Desktop required.
- Resource management with capacity visualisation, skills matching and overallocation alerts.
- Timesheets via a Power Apps application accessible on mobile — a notable competitive advantage over SAP’s CATS interface.
- Budget tracking with real-time budget vs actual comparison and configurable alerts.
Project Operations vs Dynamics 365 Finance
Both modules are complementary but distinct, and licensed separately:
- Project Operations: operational project management (scheduling, resources, timesheets, progress tracking, proforma billing).
- Dynamics 365 Finance: cost posting, IFRS 15 revenue recognition, validated invoice generation, financial consolidation.
Mid-market companies that need full project accounting must run both modules together — which increases total licence and deployment costs.
Strengths and Limitations
Strengths: modern, intuitive interface, native integration with Teams, Outlook and SharePoint (productivity gains for project teams), time and expense capture via Power Apps on mobile, good functionality-to-price ratio for services firms, Power BI for analytical reporting.
Limitations: advanced analytical reporting requires Power BI (an additional layer to manage), less mature than SAP PS for highly complex industrial projects, IFRS 15 revenue recognition in D365 Finance requires careful configuration and a certified Microsoft implementation partner.
Target profile: mid-market and large professional services firms (consulting, IT services, engineering), already in the Microsoft 365 ecosystem, between 50 and 2,000 employees.
Oracle Project Portfolio Management (PPM) / Fusion Cloud
Oracle PPM Architecture
Oracle PPM Fusion Cloud rests on three functional pillars:
- Project Financial Management: budgets, costs, revenue, IFRS 15 accounting, provisions management.
- Project Resource Management: resource allocation, skills management, demand forecasting at 6–12 months.
- Project Execution Management: task management, team collaboration, technical progress tracking.
Integration with Oracle Fusion Finance (GL, AP, AR) is native: accounting journals are automatically generated from PPM to the General Ledger, and real-time budget tracking is available through Fusion OTBI dashboards.
Oracle Project Billing
The Project Billing module allows fine-grained billing rule configuration per project:
- Progress-based billing (automatically calculated percentage of completion)
- Contractual milestone billing
- Time and expense billing
- Mixed billing on the same engagement with different rules per contract line
Invoices are generated automatically according to the configured rules, with the ability to consolidate multiple projects into a single client invoice — a critical feature for groups managing multi-project framework contracts.
Strengths and Limitations
Strengths: very powerful for multi-project and multi-entity consolidation, native analytical reporting via OTBI with no mandatory external BI layer, precise management of contract assets and liabilities compliant with IFRS 15, excellent for programme directors managing a portfolio of 50+ simultaneous projects.
Limitations: very high initial configuration complexity (18–24 months for a full large-group deployment), licence costs among the highest on the market, heavy change management burden for project teams accustomed to simpler tools.
Target profile: large international groups (revenue above €500M), heavy engineering, energy, construction and defence sectors — often already on Oracle E-Business Suite and migrating to Fusion Cloud.
Alternative Solutions for Mid-Market Companies Without SAP or Oracle
IFS Applications / IFS Cloud
IFS is well established in heavy engineering, EPC (Engineering, Procurement, Construction), defence and aerospace. Its Project Management module natively integrates project accounting functions with a more accessible interface than SAP PS for operational teams. IFS is particularly relevant for European mid-market companies (200–2,000 employees) in complex industrial sectors seeking a SAP alternative without moving to Oracle.
Certinia (formerly FinancialForce)
Certinia runs 100% natively on Salesforce Platform. It is the natural choice for professional services firms that have already deployed Salesforce CRM and want to avoid a complex CRM-ERP integration. Project management, project billing and IFRS 15 revenue recognition coexist on the same platform as the CRM. Sales opportunities can be converted directly into projects with initial budgets and resource plans — a major operational advantage for consulting firms.
NetSuite Project Management
NetSuite offers project accounting modules suited to mid-market companies with fewer than 200 project-based employees: time and expense tracking, cost allocation to projects, milestone or T&M project billing. Less deep than SAP PS or Oracle PPM on advanced analytical functions, but deployable in 4–6 months as pure SaaS. Relevant for fast-growing companies that want a unified ERP and project accounting solution before reaching the scale that justifies a tier-1 system.
Comparison Table and Selection Guide
| Criterion | SAP PS / S/4HANA | D365 Project Operations | Oracle PPM Fusion | IFS Cloud | Certinia |
|---|---|---|---|---|---|
| Target size | Mid-market + Large | SMB+ / Mid-market services | Large enterprise | Mid-market industrial | Mid-market services |
| Project types | Fixed-price + Complex mixed | T&M + Fixed-price services | Fixed-price + Mixed | EPC / Industrial | T&M + Fixed-price |
| Native IFRS 15 | Yes (Revenue Recognition) | Yes (D365 Finance) | Yes (native PPM) | Yes | Yes |
| Group integration | Excellent (native SAP) | Good (M365) | Excellent (native Oracle) | Good | Limited (Salesforce) |
| UX for project teams | Average (improved in Fiori) | Good (Power Apps) | Good | Good | Very good |
| Deployment complexity | Very high | Medium | Very high | High | Low–Medium |
| Indicative deployment budget | > €500K | €100K–€500K | > €1M | €200K–€800K | €50K–€200K |
Quick decision guide:
- Already on SAP ERP, complex multi-entity industrial projects? SAP PS / S/4HANA.
- Microsoft 365 ecosystem, professional services firm, 50–500 employees? Dynamics 365 Project Operations + Finance.
- International group with a 50+ project portfolio and significant IT budget? Oracle PPM Fusion.
- Mid-market engineering / construction / EPC company in regulated industrial sectors? IFS Cloud.
- Already on Salesforce CRM, professional services, under 200 employees? Certinia.
- Fast-growing mid-market company, rapid deployment required, limited budget? NetSuite.
The trap to avoid: defaulting to the project accounting module bundled with your existing ERP without verifying that it covers the four fundamentals — structured WBS, connected timesheet cost allocation, EVM and automated IFRS 15 recognition. In many implementations, the native module proves insufficient in production and forces an external, disconnected project management layer — recreating exactly the problem you set out to solve.
To go further, read our guide ERP for Engineering and Consulting Firms: Project Billing, WBS and Profitability, our comparison ERP for professional services firms: PSA, staffing and project profitability, and our guide accelerated accounting close with continuous close for CFOs.
