Three things make Belgian time registration cost differently from the same system elsewhere, and all three are structural.
Entitlements are set per joint committee rather than nationally, so a company with several committees is buying several rule sets. Payroll runs through a social secretariat with its own file format and codes, so the export is a mapping rather than a download. And on qualifying construction sites there is a statutory registration obligation with a hard date attached. None of those show up in a per-employee price, and together they usually matter more than the licence.
Key takeaways
- Belgian cost is driven by joint committees, social-secretariat file formats and statutory site registration.
- Several committees means several rule sets and several wage-code mappings, not one configuration.
- CIAO on 1 April 2027 is a fixed date, and implementation lead time is part of its cost.
Why do joint committees change the arithmetic?
Because they multiply the configuration.
Overtime supplements, shift and night premiums, ADV and, in construction, a mobility allowance are set by the applicable joint committee agreement rather than by national law with one value. A company employing hourly and salaried staff is already running at least two sets. One working across sectors may run four or five.
Each of those is a rule set to configure and test, and a wage-code mapping to build and maintain. The cost consequence is direct: count committees, not just employees, before treating a quote as comparable. It is also the number that predicts your recurring cost, because sector agreements are renegotiated and each revision is a configuration change.
What does the social secretariat relationship add?
A mapping step that companies outside Belgium do not have in the same form.
Payroll typically runs through a social secretariat, and each has its own expected structure, its own reference data and its own codes for the same concept. So “payroll integration” here means producing a file where every hour carries the right code for the right committee in the format that provider expects, not exporting a timesheet.
The practical question to put in writing: is mapping to our wage codes in scope, per committee, or only file generation? That single answer is often the largest variance between Belgian quotes, and it does not surface until implementation. Our piece on what a payroll export must contain sets out what the file actually has to carry.
How does the statutory site duty affect cost?
It adds a requirement with a date, which changes both scope and timing.
On qualifying construction sites, attendance registration is a legal obligation, and from 1 April 2027 works in immovable state worth EUR 500,000 excluding VAT or more move from Check in at Work to Check in and out at work. From that date registration must be in and out, in real time, and performed by the worker. Pre-registration is prohibited.
Three cost consequences follow:
- Every worker on a site in scope needs their own means of registering, including subcontractors. That is a registration-method decision with a hardware or licence cost attached.
- Reporting to the authority should be the same action as the site registration. Two systems means two things to buy and reconcile.
- Lead time is part of the cost. A system of any complexity takes months to implement properly, so a decision left late gets made under pressure and usually more expensively.
Separately, a general working-time registration obligation is planned from 2027 but has not been passed, worth scoping for, not worth buying in a panic over.
What pricing models are you likely to see?
| Model | How it works | Watch for |
|---|---|---|
| Per user per month | Licence scales with registered employees | Who counts as a user, subcontractors, seasonal staff? |
| Tiered by band | Price steps at headcount thresholds | Where the next step sits relative to your growth |
| Module-based | Core registration plus paid modules | Which tier the functionality you were shown sits in |
| Hardware purchase | Readers and terminals bought outright | Service life and replacement cost |
| Hardware as a service | Devices included in the monthly fee | Total over five years versus purchase |
| Implementation day rate | Configuration billed by the day | Estimated days, and what happens if it runs over |
Most Belgian quotes combine several of these, which is exactly why comparing monthly figures is unreliable and a three- and five-year total is not.
Frequently asked questions
What does a time registration system cost in Belgium?
It depends on how many joint committees, entities, sites and payroll files you run rather than on headcount alone. Ask for setup and recurring split out and itemised, then compare on a three- and five-year total. A supplier quoting from headcount alone has not scoped the Belgian complexity.
Does having several joint committees make it more expensive?
Yes, and predictably so. Each committee is a rule set to configure and a wage-code mapping to maintain, and each agreement revision is a configuration change. Count your committees before requesting a quote; it predicts both setup and recurring cost better than employee numbers.
Is Check in and out at work reporting included in the price?
Ask explicitly. On qualifying sites it is a legal obligation from 1 April 2027 with real-time registration by the worker, and whether the statutory report happens from the same system or a second one is both a cost question and a reconciliation question.
Should we buy before the 2027 deadlines?
Scope now, decide on merit. The CIAO date of 1 April 2027 is confirmed and implementation takes months, so leaving it late means deciding under pressure. The general working-time mandate is announced rather than passed, and is not a reason to rush.
What this does not solve
This article does not give a price. Belgian cost depends on committees, entities, sites and payroll setup, and a figure invented here would be the least reliable sentence in it.
It does not tell you which committee applies to which group either. That is a question for your social secretariat, and it has to be answered before configuration rather than during it.
And it does not remove the mapping work. Suivo produces hours correctly typed for the receiving system; it is not a payroll engine and does not calculate wages.
Next step: Suivo pricing sets out how the licence side is structured.
Related: Construction pricing · The ROI of time registration · The 2027 CIAO change
