ERP for project business — software for project-driven services
Project business covers companies that earn their living through bounded engagements rather than continuous production: agencies, management consultancies, engineering offices, architectural practices, system integrators, custom-software houses, structural-engineering firms and many specialist Mid-Market contractors. The ERP that supports them must answer four questions accurately every month: how much time went into which project, which milestones have been delivered and can be invoiced, how profitable each project actually is, and which resources are committed where for the next six months. Industry-generic ERPs handle the first two passably and the last two poorly — which is why purpose-built project-business products keep their market share even as the broader ERP world consolidates.
Time tracking and service capture
Project businesses live on accurate, prompt time entries. Every hour booked late, booked to the wrong project, or never booked at all is margin walking out the door. A project-business ERP must offer fast mobile time entry, recurring favourites, project-task hierarchies and a project-manager review step before billing. Integration with calendar tools (Outlook, Google Calendar) shortens the path from meeting to time entry. Where time entry remains painful, people skip it — and the project profitability reports become fiction.
Milestone-based billing
Project contracts in the DACH market come in three shapes: time-and-materials (T&M), fixed-price with milestones, and a hybrid mode with a fixed envelope plus T&M extras. The ERP must support all three and combine them on a single project where needed. Milestone billing requires the system to track planned vs delivered milestones, trigger invoices on milestone acceptance and handle partial-acceptance scenarios. For longer engagements, percentage-of-completion (PoC) revenue recognition under HGB (the German Commercial Code) and IFRS 15 needs to be supported natively, with the project ERP feeding the audited annual accounts via the general ledger.
Project profitability in real time
The most expensive mistake in project business is finding out at month nine of a twelve-month engagement that the project is loss-making. A good project ERP shows every project manager their current profitability picture — planned revenue, billed revenue, planned cost (people, expenses, subcontractors, third-party tooling), actual cost, deferred income — updated daily. Earned-value-management indicators (CPI, SPI) give an early warning before the cost overrun becomes visible in cash. Project profitability also has to roll up to portfolio level for the management board, ideally with drill-down to the individual time entry that explains the variance.
Resource planning and utilisation
Utilisation is the second-most-important KPI in project business after profitability. The ERP's resource-planning view must show, per consultant or engineer, the planned vs available capacity over the next 8–16 weeks, broken down by project. Soft bookings (likely but not signed), hard bookings (signed contracts) and time off all need to be visible in one view. Skill profiles, certifications and language ability matter for staffing decisions and should be a first-class data model, not a free-text field. For larger consultancies, demand pipeline integration with the CRM closes the loop: the resource manager sees which sales pipeline opportunities require which skills when they close.
Selection criteria and vendors
- Project structure with phases, work packages and tasks
- Fast mobile time tracking with offline mode
- Milestone, T&M and hybrid billing on a single project
- Percentage-of-completion revenue recognition (HGB / IFRS 15)
- Real-time project profitability with cost-type breakdown
- Resource planning with skill profiles
- Subcontractor cost capture and pass-through billing
- Project document management with version control
- Integration with CRM and HR-payroll systems
- DATEV export for the German tax accountant
DACH-relevant vendors include Vertec (Swiss specialist for consultancies), Projektron BCS (German specialist for project-driven services), Scopevisio, VARIO and the project-business modules in Microsoft Dynamics 365 BC and Microsoft Dynamics 365 F&O. SAP S/4HANA with the Professional Services module is the typical choice for larger engineering and consulting groups. For predominantly creative agencies, products like teamleader and Wrike (project-focused, not full ERPs) are common, paired with a lightweight accounting backend.
Related Topics
Frequently Asked Questions
Can a generic ERP cover project business adequately?
For very small consultancies (below ~10 people) with simple T&M billing, a generic ERP plus a spreadsheet often suffices. From around 15 fee earners, the lack of resource planning and project profitability becomes a real management problem — that is the point at which a project-specialist product (Vertec, Projektron, Scopevisio) or a full-blown configurable ERP (Microsoft Dynamics 365, SAP) starts to pay back.
How important is PoC revenue recognition for German Mittelstand project businesses?
It depends on engagement length and contract type. For projects running across a financial year-end with fixed-price elements, percentage-of-completion (PoC) recognition under HGB §252 or IFRS 15 is essentially mandatory to avoid distorting the annual accounts. Engineering firms with multi-year contracts effectively cannot operate without it.
Where does the line run between a project-business ERP and a dedicated PSA tool?
Professional Services Automation (PSA) tools such as Kantata, Replicon or Certinia focus narrowly on project execution, time and resource planning. They typically connect to a separate accounting / ERP backend. A project-business ERP includes accounting natively. For DACH Mittelstand, the integrated route (Vertec, Projektron, Microsoft Dynamics with project modules) is the more common path because of DATEV integration and audit requirements.