Automation
Accounting
Payroll errors Dutch employers consistently make
Which payroll errors are Dutch employers making right now? See the eight most costly mistakes and the review that finds them before the Belastingdienst does.
•
15 mins

Intro
At a looncontrole, the Belastingdienst can issue naheffingsaanslagen covering the past five years, plus belastingrente on top. For a Dutch employer with ten employees where a single payroll error has run undetected for three years, the exposure stacks up quickly: three years of underpaid loonheffingen, belastingrente at 5% a year, a verzuimboete of up to 5,514 euros for each period's incorrect aangifte loonheffingen, and, if employees themselves were underpaid as a result, nabetaling claims carrying the statutory wettelijke verhoging that BW7:625 allows, up to 50% on top of the back pay itself.
The most common errors are consistently the same across Dutch employers: CAO salary increases not applied on time, the private-use correction for a company car calculated incorrectly, holiday pay and overtime allowances miscalculated, and the administration around employees starting or leaving not processed correctly. None of these are careless mistakes made by a distracted payroll administrator. They are structural errors that Dutch payroll complexity makes almost inevitable for any employer running salary administration without a systematic review process in place.
The reason these errors keep recurring is worth understanding before looking at any specific fix. Dutch payroll is genuinely complicated, and it changes continuously: legislation, CAO agreements, and loonheffingen rules all shift on their own schedules, and each shift creates a fresh opportunity for something to slip through unnoticed. A Dutch employer has to track the statutory minimum wage, which moved again in July 2026, the applicable CAO salary scales, renegotiated on their own cycle, the WKR vrije ruimte, which shifts with the annual wage bill, the bijtelling percentages, which differ by vehicle type and change over time, and the loonheffingskorting status of every individual employee. Each of these runs on its own update cycle, and missing any single one creates an error that compounds month after month rather than staying contained to the moment it started.
Key takeaway: A single payroll error does not stay in the month it occurred. A CAO salary increase missed in April keeps recurring in May, June, July, and every month after until someone actually catches it. Three months of a missed increase for ten employees at 50 euros each per month is already 1,500 euros in back pay exposure before interest and penalties are even added, and the Belastingdienst can pursue the underlying issue for five years back.
Getting the underlying employer obligations right from the very first hire makes everything that follows considerably easier; hiring staff as a sole proprietor covers that starting point in full.
Where Errors Actually Come From
Payroll errors do not scatter randomly across an administration. They cluster at specific points in the payroll process, and a review that understands where they actually originate finds them faster, and more completely, than trying to re-check every single payslip line by line.
Upstream data errors live in the employee master records themselves: the loonheffingsverklaring on file, the identity document, the employment contract details, the salary level and its effective date. Get any of these wrong at the source and every subsequent payroll run inherits the same error until someone fixes the record itself, not just one month's output.
Calculation errors happen when the rates, tables, or rules actually applied in the calculation are outdated or configured incorrectly: the wrong bijtelling percentage, the wrong CAO salary scale, the wrong WKR category. These tend to be consistent and systematic rather than random, the same wrong rate applied every single month until someone notices.
Compliance errors occur when a regulatory change simply never gets implemented in the payroll system: a minimum wage increase missed, a mileage rate left unchanged, a new pension contribution rate from a CAO amendment never reflected. These errors start on a specific date and accumulate forward from that point, growing larger the longer they go unnoticed.
Process layer | Error | What goes wrong | Financial consequence | The check |
|---|---|---|---|---|
Master data | Loonheffingskorting at the wrong employer | An employee applies the korting at two employers at once; withholding runs too low; the employee owes the Belastingdienst, and the employer may share liability | IB naheffing for the employee; a loonheffingen correction for the employer | Verify a signed, current loonheffingsverklaring per employee; confirm single-employer application for anyone with multiple jobs |
Master data | Missing or expired identity document | The anoniementarief, 52%, applies regardless of the employee's actual situation | 52% flat withholding versus the correct rate; a specific flag in any boekenonderzoek | Review identity document copies on file; check expiry dates annually |
Master data | TWK, a retroactive change entered with the wrong effective date | Current-month salary looks inflated, producing wrong withholding; prior months stay uncorrected | Incorrect loonheffingen across multiple periods | Review any salary mutation entered more than one period after its stated effective date |
Calculation | CAO loonsverhogingen not applied on time | Wages below the CAO rate from the actual effective date of the increase | Nabetaling plus wettelijke verhoging per affected employee; a possible Belastingdienst cross-check | Maintain a CAO calendar; apply the increase from the stated effective date, not the processing date |
Calculation | Bijtelling auto van de zaak wrong or missing | Wrong percentage, an outdated rate or the wrong EV threshold, or 0% applied without the required signed declaration and mileage log | A naheffing on the loonheffingen tied to the incorrect bijtelling; a vergrijpboete in serious cases | Verify the cataloguswaarde, the applicable percentage, and the verklaring geen privégebruik for every company car |
Calculation | WKR vrije ruimte exceeded without detection | Small reimbursements processed all year with no running total; the 80% eindheffing on the excess arrives at year-end | 80% eindheffing on the excess; belastingrente if it is paid late | Maintain a running WKR tracker updated after every payroll run |
Compliance | Minimum wage or kilometervergoeding not updated | Wages below the July 2026 minimum, or mileage reimbursed at the old rate rather than the new one | Nabetaling per affected employee; a minimum wage violation reported to the DFEI | Check the July 2026 payroll for the minimum wage, and correct mileage retroactively from January |
Compliance | DGA gebruikelijk loon below the statutory minimum | DGA salary sits under the 58,000-euro 2026 minimum | The Belastingdienst treats the shortfall as undeclared salary; a naheffing follows on the loonheffingen | Verify the DGA's salary annually against the gebruikelijk loon minimum and the highest employee salary |
Four of these eight errors are compliance failures rather than calculation mistakes: they happen not because the arithmetic itself was wrong, but because the right information was never actually available to calculate correctly in the first place. The single most effective investment a Dutch employer can make in payroll accuracy is not a more sophisticated payroll system; it is a more disciplined process for actually tracking regulatory updates as they land. Since the DGA's own salary sits inside this same table as a genuine compliance risk rather than purely an optimisation question, DGA salary vs dividend covers how that figure connects to the DGA's broader financial position.
What a Structured Review Actually Does
A structured payroll review is not a full re-calculation of every payslip issued that year. It is a systematic check of six specific points in the payroll process where errors are most likely to exist and most expensive once they go undetected, and an employer or accountant who follows this sequence once a quarter finds problems before they have a chance to compound.
The master data review starts with the employee list itself: confirm every active employee has a current signed loonheffingsverklaring, a valid identity document on file, and an employment contract that actually matches the salary and hours currently sitting in the payroll system. Any employee missing a loonheffingsverklaring should be treated as a potential anoniementarief case until the document actually arrives, and any contract salary that differs from the payroll system figure deserves immediate investigation rather than a note to check later.
The rate audit compares the payroll system's configured rates directly against the current reference sources: the Belastingdienst's own annual Handboek Loonheffingen, the applicable CAO for each employee's function, and the bijtelling catalogue for any company cars on the books. Any discrepancy between the configured rate and the reference source means an update was missed somewhere along the way, and the effective date of the correct rate determines exactly how far back the correction needs to reach.
The running comparison review sets this month's payroll output side by side with last month's. Compare the new payroll run against the previous one, and if net salary, employer costs, or pension premiums show a large deviation, that deviation deserves a specific explanation rather than a shrug. A net salary change of more than 5% for any individual employee with no documented reason attached is a genuine investigation trigger; the explanation might be entirely legitimate, a new company car, a one-off bonus, or it might reveal an error that has been sitting there uncorrected.
The WKR year-to-date check calculates the current vrije ruimte directly: take the fiscal wage bill year-to-date, apply the vrije ruimte percentages, 2.00% on the first 400,000 euros and 1.18% above that, and compare the result against every expense actually classified as WKR spending in the same period. A tracker showing more than 80% of the annual vrije ruimte already consumed by September is a genuine warning to tighten spending or pre-declare an eindheffing before it becomes unavoidable. A tracker showing 0% consumed is equally suspicious in the other direction, since it usually means WKR-eligible items are being processed incorrectly as ordinary taxable salary instead.
The Belastingdienst reconciliation checks that the aangifte loonheffingen actually matches the payroll records line for line: the total loonheffingen withheld and remitted each period should reconcile to the cent against the payroll journal, and any discrepancy points either to an incorrectly filed aangifte or to payroll records that were adjusted after that filing already went in.
The regulatory calendar check confirms every change effective in the current calendar year has actually been implemented, and in 2026 specifically, that list is long enough to be worth checking systematically rather than trusting memory alone. Since this whole review methodology mirrors what an actual Belastingdienst inspector examines during a formal audit, boekenonderzoek Belastingdienst covers that examination process directly.
The 2026 Errors Running Right Now
Three payroll errors are currently sitting undetected inside a meaningful share of Dutch employer systems in September 2026, and all three are genuinely fixable in the October payroll run for any employer who acts on them this month.
The mileage correction is the most time-sensitive of the three. The onbelaste kilometervergoeding, the tax-free business mileage rate, rose from 0.23 euros to 0.25 euros per kilometre, applied retroactively to 1 January 2026 through a ministerial policy decree published on 21 May 2026. Any employer still paying the old 0.23-euro rate owes their employees a correction of 0.02 euros per kilometre going all the way back to January. For an employee driving 800 business kilometres a month, the cumulative shortfall by September already comes to 144 euros. Processing this correctly in the October payroll means applying the higher rate from January onward and paying the accumulated arrears in one lump sum that same month; employers reimbursing through separate declaraties rather than through payroll directly should issue the correction as a supplementary reimbursement instead.
The July minimum wage check is the second. From 1 July 2026, the statutory minimum wage for employees aged 21 and over rose to 14.99 euros an hour. Any hourly or part-time employee whose contractual rate sat at or close to the previous June minimum may now be paid below the new floor if that rate was never actually updated for the July payroll run. The Belastingdienst cross-references aangifte loonheffingen data against minimum wage compliance systematically rather than occasionally, and an employer discovered paying below the July minimum needs to correct retroactively from 1 July and proactively notify the DFEI rather than waiting to be asked.
The CAO calendar gap is the third, and the least visible until someone actually goes looking for it. Several major Dutch CAOs entered new agreement periods across 2025 and 2026, with salary increases taking effect on a range of different dates throughout the year, sector by sector. An employer who relies on their payroll administrator to simply "know" when a CAO change takes effect, rather than maintaining a formal monitoring process for it, has very likely missed at least one increase somewhere along the way. Checking the relevant CAO's own published rates, or the national CAO register at caominszw.nl, for any change since the start of 2026 is the immediate action worth taking this week rather than waiting for the next scheduled review.
Watch out: A Belastingdienst boekenonderzoek covering loonheffingen almost always starts in the same three places. The inspector's first three checks are consistently the loonheffingskorting application, the DGA's own gebruikelijk loon, and the bijtelling on any company cars. These three items are simultaneously the highest-yield audit targets and among the most commonly incorrect figures in an average Dutch payroll. If your own review has to start somewhere, start there.
Making the Review a Routine, Not a Fire Drill
A payroll review that happens exactly once, corrects whatever it finds, and never repeats solves the problem for roughly three months. The structural causes behind Dutch payroll errors, continuous regulatory change, ongoing CAO negotiations, the ordinary churn of employees starting and leaving, all guarantee that new errors enter the system on a regular basis regardless of how thoroughly the last review was done. The actual fix is a routine, not a one-off exercise no matter how careful.
A regulatory calendar is the single most valuable tool in that routine: a document, or a task list entry, naming every payroll-relevant change expected during the current calendar year, minimum wage effective dates, CAO change dates, WKR vrije ruimte updates, tax table revisions, with someone specifically assigned to implement each one. For 2026, that calendar already needs to cover the July minimum wage increase, the retroactive mileage correction, the WKR vrije ruimte rise to 2.16% planned for 2027, and preparation for the incoming pseudo-eindheffing on fossil-fuel company cars from 2027 as well.
A monthly variance report takes about fifteen minutes and one page: compare this month's payroll to last month's at the level of each individual employee, document and sign off on every material variance found, and treat any variance that cannot be explained within that same payroll run as a genuine candidate for a deeper look rather than something to note and forget.
Choosing the right payroll partner shapes how much of this ongoing work an employer actually has to carry personally. A payroll provider that updates its own software automatically the moment tax tables, minimum wages, or CAO rates change, and that proactively communicates upcoming regulatory changes before they actually take effect rather than after, shifts the compliance burden away from the employer and onto the professional handling the account. Neno's payroll service is built specifically around this model: automatic regulatory updates, proactive communication of changes before they land, and monthly management information that keeps payroll accuracy visible to the DGA rather than buried somewhere inside the administration nobody checks until year-end. Since this reflects a broader shift already reshaping how Dutch businesses handle their financial administration generally, outsourcing bookkeeping Netherlands covers that wider market picture and what genuinely separates a good provider from an adequate one.
Get Your Payroll Reviewed Before the Belastingdienst Does It For You
None of these eight errors is a sign of a poorly run business. They are the predictable output of a payroll system that has to track dozens of moving regulatory parts at once, and the employers who avoid them are not the ones with the most sophisticated software; they are the ones who check systematically, on a schedule, rather than hoping nothing has slipped through since the last time anyone looked.
If you want your payroll reviewed against the current rates, tables, and regulatory calendar before an inspector does it for you, book a demo and we will walk through your specific setup together. Our team can also help you incorporate your BV or get bookkeeping and payroll running correctly from your very first hire.
FAQs
What are the most common payroll errors in the Netherlands?
CAO salary increases applied late, incorrect bijtelling on company cars, miscalculated holiday pay or overtime allowances, incorrectly processed employee start and end dates, missing identity documents triggering the anoniementarief, and a DGA salary that has quietly fallen below the current gebruikelijk loon minimum.
How does the Belastingdienst check payroll administration?
Through a boekenonderzoek focused specifically on loonheffingen, typically starting with the loonheffingskorting application, the DGA's gebruikelijk loon, and the bijtelling on company cars, alongside cross-referencing aangifte loonheffingen data against minimum wage and CAO compliance systematically.
How far back can the Belastingdienst assess payroll errors?
Generally up to five years, with belastingrente accruing from the date the correct amount should originally have been paid, plus a verzuimboete of up to 5,514 euros per incorrect period and a vergrijpboete of up to 100% of the underpaid amount for deliberate errors or gross negligence.
What is the loonheffingskorting and why does it cause payroll errors?
It is the general tax credit applied through payroll, which can only be applied at one employer at a time. When an employee with multiple jobs fails to waive it correctly at all but one employer, withholding runs too low, and the employee ends up owing the Belastingdienst the difference through their own return.
What is the TWK and why does it create payroll problems?
TWK, terugwerkende kracht, refers to a retroactive salary change, a late promotion, a delayed CAO increase, a backdated bonus, that must be allocated to its original period for the loonheffingen calculation. Entering it under the current month instead inflates that month's apparent salary and produces incorrect withholding.
What is the WKR vrije ruimte and what happens when it is exceeded?
It is the tax-free budget employers have for staff benefits, 2.00% of the first 400,000 euros of the fiscal wage bill plus 1.18% above that in 2026. Spending beyond that limit triggers an 80% eindheffing on the excess, usually discovered only at year-end if nobody has been tracking the running total.
How does the bijtelling for a company car affect payroll?
The private-use correction adds a percentage of the car's cataloguswaarde to the employee's taxable salary, 22% standard or 16% for qualifying electric vehicles up to a threshold in 2026. Errors arise from using an outdated rate, the wrong EV threshold, or applying 0% without a properly signed declaration and mileage log to support it.
What is the DGA gebruikelijk loon and is it a payroll obligation?
It is the minimum salary a DGA must draw from their own BV, 58,000 euros gross in 2026 or the highest salary paid to any employee if that figure is higher. It is a genuine payroll compliance item, not simply a tax planning choice, and the Belastingdienst checks it as one of the first items in almost every loonheffingen audit.
What changed about the kilometervergoeding in 2026?
The tax-free business mileage rate rose from 0.23 euros to 0.25 euros per kilometre, applied retroactively to 1 January 2026 through a ministerial decree published in May 2026, meaning employers still reimbursing at the old rate owe a retroactive correction covering the full year to date.
How often should a Dutch employer review their payroll?
A monthly variance check against the prior period, a quarterly review covering master data, applicable rates, and the WKR tracker, and a full annual review of the regulatory calendar alongside a reconciliation against filed aangifte loonheffingen.
Written by
Nick Knuppe
CEO & Founder

