Two colleagues going through the schedule and the open jobs

ERP for professional services

In services and maintenance your stock is your people’s calendar. The system therefore has to get three things right at once: who is available, what the time went into, and how much of that reaches the invoice.

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. They meet at one point: availability is scarcer than demand, and that moves the centre of gravity to planning.

Availability has become the limit, not the order book

Skilled people are scarce. 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

Clients want predictability: 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

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

Clients want the time spent substantiated, and in tenders that substantiation is part of the job. Reconstructing it afterwards costs more time than recording it did.

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

Which ERP systems run in professional services?

These are the systems you meet most often in Dutch services and maintenance. They differ mainly in where they 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 later.
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	Organisations that want to configure and connect a lot themselves, with a team able to do it.	The freedom is both the gain and the risk. Without in-house knowledge that freedom moves to your partner.

Not an exhaustive list and not a recommendation. We hold no partnership with vendors, so we have no stake in which name you choose.

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 neatly records afterwards what happened solves no planning problem at all. Ask every candidate not what the system records, but what it shows you about the weeks still to come.

Four questions that test the next stage

Put them to every candidate, in this order. If the answer to the first stays vague, the other three tell you little.

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 your jobs last weeks or days. That distinction rules out more candidates than any feature list.

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 works fine until the invoice has to depend on it. That is where the retyping starts, and where the differences appear.

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 mostly produces an integration.

More and more ERP systems carry this themselves. 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 it goes wrong. 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.

Growth is rarely the direct trigger. More often it is a change in the shape of the work, such as contracts with response times, that suddenly leaves the system in the wrong shape.

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.

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