Two colleagues going through the schedule and the open jobs

Choosing ERP for professional services

When you choose an ERP system for services and maintenance, start from the available time of your people. Test whether the system records three things correctly at once: who is available, what the time went into and how much of it is invoiced. On this page you read what you select an ERP system for services on and what to watch per growth stage. The full process is in the seven steps of an ERP selection.

What is happening in the sector

Which systems run there

What pinches at each stage

What is happening in professional services and maintenance?

Four developments currently decide what a service organisation needs from its system. If availability is your limit, look at planning above all.

Availability has become the limit, not the order book

Check whether your available people set the limit of what you can take on. Accept a job without knowing who does it and you have moved the problem to the planner, and you find out when the customer calls.

Planning is no longer a sideline next to administration, it is the core of the system.

Fixed price and subscription arrive alongside time and materials

Do your clients ask for predictability, for example a fixed price per job or a fixed amount per period? Hours still set the cost price, even when they no longer appear one to one on the invoice.

Your system has to carry both, or you lose sight of what a job actually cost.

Maintenance shifts from breakdown to contract

Do your customers buy availability rather than repairs? That calls for planned maintenance, agreements on response time, and sight of the parts that have to be in stock for it.

Planning, parts and hours belong in one flow, not in three systems with links between them.

Clients ask harder for justification per job

Do your clients ask for the time spent to be substantiated, for example in tenders? Then compare what recording costs with what reconstructing it afterwards costs.

Recording has to happen at the source, where the work is done.

What do you select an ERP system for professional services on?

Test candidates on a job you have just completed, not on a feature list. Ask every candidate the same question for each criterion, in the RFI or in a demonstration on your own job sheet.

Time recording. Does the system record time where the work happens, and on the right job? Ask: "How does an employee record hours on several jobs in one day, and who approves them before they move on?"
Planning of people. Does the system plan on availability and skills? Ask: "How does this system schedule a job based on availability and skills, and what happens when someone drops out?"
Invoicing on time and materials and fixed price. Can the system carry both forms side by side? Ask: "Show how one customer is invoiced for both a time-and-materials job and a fixed-price job."
Revenue recognition per project. Do you see per project what has been earned and what is still work in progress? Ask: "How does this system determine the revenue of a running project at month end, and where do you see the work in progress?"
Service contracts and maintenance. Can the system keep contracts, planned maintenance and parts in one flow? Ask: "How does this system record a service contract with planned maintenance, and how do the parts and hours end up on the right invoice?"

Record in a business requirements scan how much weight each of these criteria carries for you.

Which ERP systems run in professional services?

These are among the systems you meet in Dutch services and maintenance. Check for each system where it came from: the people side, the project side or the shop floor.

What it was built for and what to watch

System	What it was built for	What to watch
AFAS	Organisations where people, payroll and hours sit close together, with projects alongside.	Strong on the people side. Check whether the project side really follows how you cost work.
Unit4	Project-driven services where hours set the cost price and the justification counts.	Built around the project. With many small, fast-changing jobs it can feel heavy.
Dynamics 365 Business Central	Service firms that want materials, purchasing and stock in the same system as hours.	Broadly applicable, so the configuration decides the result. Ask who maintains that configuration when your services change.
IFS	Maintenance and service where planning, parts and job sheets run as one process.	Powerful on maintenance. The partner market is smaller, and so is your room to move.
Odoo	Service firms that manage their own configuration and build integrations with other software themselves.	The freedom is both the gain and the risk. Without an in-house administrator every change becomes an assignment for a third party.

Not an exhaustive list and not a recommendation. What fits depends on where your money is made: on projects or on maintenance.

Where does it pinch at each stage of growth?

A service organisation hits different limits than a trading or manufacturing company. The constraint moves from overview to planning, and then to justification.

Per stage of growth

Employees	What happens	Where it then pinches
Up to about 25	Everyone knows every job. Hours in a list, invoicing at month end, planning by conversation.	Little, until someone drops out. Then it shows how many agreements live only in a head or a mailbox.
25 to 100	More jobs at once, more people off site, the first fixed prices alongside time and materials.	Hours arrive late. Invoicing falls behind and nobody knows which job still has money in it.
100 to 250	Several teams or sites, contracts with response times, parts and materials running along with the work.	Planning and availability. The system shows what happened, but not who is free next week.
Above 250	Several countries or divisions, sometimes after an acquisition, and justification per client.	Uniform recording. Two teams book the same kind of hours differently, and that works through into the cost price.

In a service organisation the calendar is the stock.

A system that only records afterwards what happened does not help you with planning. Ask every candidate not what the system records, but what it shows you about the planning still to come.

Four questions that test the next stage

Put them on a job that has just been completed, not on an example from the vendor. Only then does it show what the system does with your exceptions.

What does this system show about next month’s availability, and where does that picture come from?
How does this system record a fixed-price job without losing sight of the hours spent?
Where does the engineer or consultant record hours, and how many steps sit between that moment and the invoice?
What does it take to let a contract with an agreed response time count in the schedule?

Frequently asked questions

Which ERP system suits a service organisation?

That depends on where your money is made. Project work turns on costing and post-calculation; maintenance turns on planning and parts. Those two call for different systems.

So do not start from a list of names, but from whether you mainly do project work or separate maintenance jobs. That question already rules out part of the candidates.

What is the difference between ERP and time tracking?

Time tracking records what the hours went into. ERP connects those hours to the job, the costing, the invoicing and the finances.

A standalone time system can be enough as long as the invoice does not depend on it. If it does, test whether the hours reach the invoice without retyping.

Does a maintenance firm need a separate field service system?

Only if the field work has logic of its own: planning by location, job sheets on a phone, parts from the van and a signature on completion. Without that logic a second system solves nothing your ERP system cannot already do.

Ask whether an ERP candidate can carry this itself. Test it on your own job sheet, not on the demonstration version.

How do you keep time recording and invoicing in step?

By recording hours where the work happens, tied to the job, and letting the invoice follow from that instead of assembling it separately.

Every manual step between hour and invoice is a place where errors can arise. In a demonstration, count how many steps there are.

When is a service organisation ready for a new ERP system?

When invoicing is structurally behind, planning happens outside the system, or nobody can show which job was profitable without a file of their own.

Besides growth, also watch for a change in the shape of the work, such as contracts with response times. Include this in your requirements, so you can test whether a system fits it.

Have a services choice reviewed

We work with consultants who know services and maintenance from the inside, on your side of the table. Because we are platform-independent and hold no vendor ties, we have no stake in which system it becomes.

Want your requirements sharp first? Plan a conversation about a requirements scan.

Book a consultation All ERP systems

Where we help

Getting clear whether planning or costing is your centre of gravity
Demonstrations on your own job and your own job sheet
Testing that hours and invoicing meet without retyping

In maintenance and services we have guided companies including Jansen Huybregts.