Häufig gestellte Fragen
What does an ERP for service providers and agencies cost?
Realistic total costs for a services ERP in the mid-market typically range between 120,000 and 650,000 euros over the first three to five years, depending on user count and depth of customisation, with the project/service module including time tracking and multi-stage billing making up the largest block. Cloud solutions are mostly billed as a subscription per user per month and avoid high upfront investments, while on-premises models additionally incur annual maintenance and update fees in the order of around 18 to 22 percent of the licence sum. Lean agency tools for small teams start considerably cheaper than integrated suites for medium-sized and large consultancies. You will find a detailed breakdown of the cost types in our guide ERP costs.
What is the difference between an ERP and a PSA solution for service providers?
PSA software (Professional Services Automation) is developed specifically for project-based service providers and puts projects, resources, utilisation and margins at the centre, while classic ERP systems integrate company-wide processes from purchasing through warehousing to financial accounting and were originally designed around material and goods flows. For pure consultancies, agencies or IT service providers, a focused PSA solution often covers the need for time tracking, skill planning and fee billing, but as soon as international locations, group consolidation or deep finance functions come into play, a service-oriented ERP is more sustainable. Many modern ERP suites now cover the PSA feature set as a dedicated project or service module, so the line blurs in practice. What matters is that project controlling, resource management and billing are seamlessly interlinked with accounting.
What distinguishes time-and-materials from fixed-price billing in an ERP?
With time-and-materials billing, the effort actually delivered is invoiced in hours plus resources used, so the volume risk sits with the customer and requirement changes can be accommodated flexibly. With a fixed price, the service provider commits to a firmly defined scope of work at a guaranteed price, shifting the calculation risk to the provider and requiring a precise requirements specification and strict scope management. A services ERP should support both models as well as hybrid forms such as capped T&M contracts and derive them correctly per project from the recorded times. Since many firms run both models in parallel, cleanly separating billable from non-billable hours in the system is a core requirement.
Which utilisation and project KPIs should a services ERP deliver?
The most important KPI for project-oriented service providers is billable utilisation, i.e. the share of billable hours in available working time; in consultancies and agencies, target values often sit in the range of roughly 70 to 80 percent depending on role and seniority level (with around 75 percent as a common benchmark), while the net rate actually achieved over the year is often lower after holidays, sick leave and internal tasks. In addition, an ERP delivers a plan/actual comparison per project, contribution margins, average hourly rates and forecasts of future utilisation. These figures should ideally emerge in real time from ongoing time tracking so that bottlenecks and unprofitable projects become visible early. A reliable data basis requires that employees record their time consistently and accurately by project and activity, ideally on mobile devices.
How does a services ERP support revenue recognition on ongoing projects?
For multi-period service projects, the question is when which revenue is recognised; under IFRS 15, for performance obligations satisfied over time, recognition is based on progress towards completion (often referred to as percentage of completion), which is frequently measured via hours worked or costs incurred relative to total expected effort. The German HGB follows the realisation principle more strictly, so internationally active or group-reporting service providers need both accounting logics in parallel. A capable ERP covers these methods through corresponding functions for project and revenue accruals and can, where needed, run several accounting standards in parallel. This allows partial invoicing, deferred revenue and period-accurate project progress to be documented in an audit-proof way.
Does a services ERP need to be able to process e-invoices (XRechnung, ZUGFeRD)?
Since 1 January 2025, the e-invoicing mandate has applied to domestic B2B transactions, and all companies have since been required to be able to receive, process and archive structured e-invoices compliant with the European standard EN 16931 in an audit-proof manner. Permitted formats are in particular XRechnung and ZUGFeRD from version 2.0.1, where ZUGFeRD combines a structured XML data set with a human-readable PDF, while XRechnung is a pure XML format. Transitional periods apply to sending: paper or PDF invoices generally remain permissible until the end of 2026, for companies with a prior-year turnover of up to 800,000 euros until the end of 2027, before all B2B companies must send e-invoices from 2028. A modern services ERP should therefore already generate and process e-invoices end to end and support the required retention in the original format.