A signed wage agreement offers little comfort when sector rules, rosters and payroll records tell another story.
Picture the end of a busy payroll week. Several shifts changed, an employee covered for a colleague, and the owner approved the final hours by telephone. Everyone has been paid. The hourly rate looks fair, staff receive a few useful extras, and the payroll provider has produced neat payslips.
Yet a harder question remains. Does the company fall within a generally binding collective labour agreement, and can it show that every relevant term was applied?
That question became costly for a private-security employer in a recent Overijssel District Court case. The court ordered correction of CAO breaches, production of supporting records and payments to current and former workers. It also awarded €25,500 in fixed compensation to the sector fund, together with collection and legal costs.
The judgment concerns security-sector agreements and historical periods. Its wider lesson matters to any employer working with sector rules. Where a CAO has been declared generally binding, a private arrangement cannot replace mandatory terms that are less favourable to the employee.
The agreement is only the beginning
Dutch employers sometimes treat a CAO as a wage table attached to the employment contract. In practice, it can govern job grading, allowances, working hours, roster changes, overtime, leave and sector contributions. Some provisions allow better individual terms. Others leave no room for deviation.
An employer within the scope of a generally binding sector CAO must apply it during the relevant period. That can apply even when the employer did not negotiate the agreement or join the employers’ organisation behind it. The company’s actual activities, the wording of the scope, the relevant dates and any valid exemption determine the position.
This is where a small company can drift into exposure without anyone behaving carelessly. An employment contract may name one role while the employee’s daily work gradually changes. A new service line can bring the business within another sector. An acquisition can bring workers with different classifications.
Payroll continues while the assumptions beneath it remain untouched.
In Dutch business practice, an administrative assumption can quickly become accepted as truth. Someone entered a classification years ago. The payroll provider copied it. The owner trusted the provider. Nobody returned to the underlying question when the work changed.
The payslip needs a story behind it
The security case shows the difference between a payment and a defensible payroll record. The employer supplied a document listing wage payments. The court required the underlying payslips, bank statements and evidence of the claimed corrections as well.
Reliable rosters were equally important. Under the applicable security CAO, missing records needed to calculate a roster-shift allowance led to an order to disclose the relevant social-insurance wage base. The employer also had to pay 10 percent of that wage base to affected current and former workers.
That 10 percent remedy belongs to this CAO and this case. The broader business lesson reaches much further. When pay depends on hours, shifts, standby work, travel, grading or irregular-hours allowances, the roster explains the payslip. The payslip explains the payroll ledger. The bank payment confirms what left the company.
Those records should tell one consistent story.
The Belastingdienst treats payroll administration as part of the basic business administration. Basic records generally remain subject to a seven-year retention period after they cease to have current relevance. For an employer, that means the record must survive a departing bookkeeper, a new payroll provider and an old dispute returning at an inconvenient moment.
A wage error becomes a cash decision
CBS reported that collectively agreed hourly wages, including special remuneration, were provisionally 4.0 percent higher in the third quarter of 2026 than a year earlier. Wage growth has cooled from its 2024 peak, but labour still costs materially more than it did twelve months ago.
That matters when a correction reaches backwards. The company may have priced and invoiced work on the assumption that labour cost was final. If allowances, classifications or roster payments require correction, yesterday’s margin calculation becomes today’s cash demand. Former workers may also need to be traced and paid.
For a small employer, this is rarely only an HR issue. It reaches pricing, liquidity, client contracts and management time. A fixed-price assignment may offer no practical route to recover the additional cost. The company pays today for a weakness built into yesterday’s roster and payroll process.
The director-liability finding in the Overijssel case also deserves attention. The court held the indirect directors personally and jointly liable for the fixed compensation. It did so in circumstances marked by prolonged non-cooperation, missing records, uncorrected breaches and unpaid workers.
That outcome does not make directors automatically liable for every payroll or CAO error. It does show why management cannot leave an unresolved CAO issue indefinitely with an adviser or administrator. Outsourcing payroll work does not outsource the employer’s responsibility for the result.
The question management should own
A sensible review starts with the company’s actual activities and job content, rather than only the CAO name printed in employment contracts. It then follows one employee with a changed roster or allowance from approved hours, through payroll, to the payslip and bank payment.
A break in that chain deserves management attention.
Current and former workers belong in the same assessment where a historical correction may be needed. So do handover arrangements with payroll providers. Access credentials, source data, exception reports and correction records remain company responsibilities, even when an external specialist performs the work.
The practical question is simple: if this pay arrangement is challenged tomorrow, can the company show what it agreed, what it paid and why the calculation was right? Can it also see the cash, people and governance consequences before they become a claim?
The owner in the opening scene may have treated employees fairly in everyday human terms. That matters. Yet good intentions and compliance with a binding CAO are different parts of the same employer duty.
A good payroll run ends with more than successful bank transfers. It ends when the contract, actual work, roster, calculation and payment still belong to the same business story.
If your payroll assumptions no longer match the work being done, review the applicable CAO and supporting records before the discrepancy becomes a claim.
The data, sourcing, and analysis behind this article were conducted by Linda Pavan Geraedts. AI was not used to identify sources, build the factual basis, or produce the analytical judgment contained here. AI was used only as a drafting aid. The final English text was personally reviewed, edited, and approved by Linda Pavan Geraedts before publication.
References
- Werkgever moet algemeen verbindend verklaarde cao's naleven · Salaris Vanmorgen
- Rechtspraak - Verified court outcome: security-sector CAO compliance, evidence failure and director liability
- Rijksoverheid - When an AVV applies, the collective agreement outranks an inferior individual deal
- Ondernemersplein - Employer duty to identify and state the applicable CAO
- Belastingdienst - Payroll and roster records as the proof layer
- CBS - The current wage-cost backdrop
- Overheid.nl
- Rijksoverheid - Welke cao moet de werkgever toepassen?
