WBSO for startups: keeping the administration in order

Many Dutch tech startups can use the WBSO, the key scheme for research and development work. But getting the application approved isn't enough: without solid hours and project records you lose the benefit at an audit. Here's how the scheme works, which deadlines apply, and where it goes wrong.
What is the WBSO?
The WBSO (the Dutch R&D tax credit) is a fiscal scheme that lowers your research and development costs. For companies with employees it works as a reduction on the payroll tax you remit. For self-employed founders without staff there is a fixed deduction in income tax, provided you spend at least 500 hours a year on qualifying R&D work. You apply at RVO (the Netherlands Enterprise Agency), and on approval you receive an S&O declaration.
When do you qualify?
WBSO doesn't cover all development work. The core requirement: your project must be technically new to your company, with technical uncertainty about whether and how it will work. If you're building a new technical product or solving a technical problem whose outcome isn't a given, you stand a good chance. Routine development, like building a standard website or configuring existing software, doesn't qualify, and RVO has become stricter on software in recent years. Still, for startups doing genuine product development, the WBSO is often the biggest fiscal advantage available.
The administration: what RVO expects from you
The benefit stands or falls with your records, and RVO applies concrete deadlines:
- Hours administration: record R&D hours per project, per person and per day, updated within 10 working days. Reconstructing afterwards is not an option.
- Project administration: document the nature, content and progress of each R&D project, updated no later than two months after the end of each quarter.
- Notification: report the actually realised R&D hours to RVO each year before 31 March.
How the reduction lands in your payroll return
The S&O certificate is not a payment. It states an amount you are allowed to offset, and you do that offsetting yourself in your payroll tax return, period by period, across the period the certificate covers. In practice you simply remit less payroll tax.
Two rules decide what happens. Within a period you can never offset below zero: if the payroll tax you owe is lower than the amount you still have available, a remainder is left. That remainder can still be used in other periods of the same calendar year, retroactively too, through a correction message. Whatever is left at the end of the calendar year is gone.
For a startup with a small team that is not theory. If your certificate was calculated on a team you only complete in the autumn, you run into that floor in the early months, and somebody has to actively track how much is still left to offset.
What the WBSO does to your figures
The reduction is not revenue and does not belong in your books as revenue. It lowers your payroll cost, and with it your burn. That has two consequences worth knowing before an investor asks.
- Your runway looks longer with the WBSO than without it. Investors therefore regularly ask for your burn with and without the scheme, to see how dependent your plan is on the award.
- The reduction disappears the moment a project stops qualifying or the certificate expires. A cost base leaning on the scheme then jumps up in one step.
What happens if it's not in order
RVO audits on a sample basis. If your administration turns out to be incomplete or updated too late, a correction follows on your S&O declaration, and in some cases a fine on top of that correction. The benefit you had on paper evaporates after all.
The trap: application done, administration not
Many startups get the application sorted, often with an advisory firm, and then think they're done. But in the rush of building, the time tracking slips. By the time someone remembers, the 10-working-day window has long passed. The application is the easy part; the ongoing administration is what it really comes down to.
How we handle it
Honest is honest: nobody can take the hour logging and the technical project documentation off your hands. That work sits with you and your team. What we do handle: we process the WBSO credit in your payroll returns, file the annual notification with RVO, and make sure the financial side of your R&D file is correct in your bookkeeping. And we actively remind you of the registration deadlines, so the 10-working-day window and the quarterly deadline never quietly pass. That way the benefit you're entitled to actually stays yours.
In short
- WBSO lowers your R&D costs via payroll tax (or a deduction for the self-employed with at least 500 R&D hours a year).
- Your project must be technically new to your company, with technical uncertainty.
- Deadlines: hours within 10 working days, project records within two months after each quarter, notification before 31 March.
- An RVO audit with poor records means a correction and possibly a fine.
- We process the credit in your payroll, file the notification and guard your deadlines.
Part of our guide: Bookkeeping for startups: the complete guide
Curious what real-time bookkeeping looks like for your startup?
See how it works