wbsosubsidiesai-strategycustom-software

WBSO for AI Projects: What Counts as R&D in 2027

November 16, 202613 min readPixel Management

This article is also available in Dutch

Training an AI model on your own data feels like research, yet the Dutch enterprise agency RVO uses exactly that as an example of work that doesn't qualify.

WBSO for AI projects is the ordinary Dutch payroll tax credit for research and development (S&O in Dutch), applied to AI software: 36% of the first €391,020 of the R&D base, and only for technically new software your own employees write in a formal programming language. Rolling out ChatGPT, configuring a SaaS package or calling a language model through an API doesn't count. The AI widening promised in the Dutch coalition agreement isn't in force. If you do qualify and want to start on 1 January 2027, the deadline is Sunday 20 December.

Which AI work counts as R&D for the WBSO?

The AI work that counts as R&D is narrower than the word innovation suggests. RVO's Handleiding WBSO 2027 (version 1, November 2026, in Dutch) includes worked examples on machine learning, bots and code generation, and the line is sharp: RVO asks whether you solve a programming problem yourself, not whether the result is new to your company.

AI workR&D?Basis in the handbook
Configuring and rolling out ChatGPT, Copilot or a SaaS packageNoApplying, assembling or implementing software isn't R&D
Calling a language model through a known API and connecting it to your systemsNoPurely driving known APIs isn't R&D
Creating and training a model with TensorFlow and using it in your appNoExample "application of machine learning"
Raising a model's reliabilityNoTreated as a requirement, not a technical bottleneck
Porting an existing AI application to your own serversNoAdapting software to another platform is excluded
Your team learns a new framework or methodNo"First use": the learning phase counts as training
Generating code with Claude CodeNot by itselfPoints to building functionality
Writing the complex parts yourself that the coding assistant can't solveCan beYou explain which bottlenecks you solve and which code you write
Building a facility your programming language lacksCan beExample "bots and AI technology"
Programming a new, more efficient algorithmCan beDescribing it doesn't count, recording it in code does
Making existing software work together in a technically new wayOnly ifYou mainly developed that software yourself and already use it

"Can be" isn't hedging on our part. RVO decides per application, and the handbook's own positive examples say the work "can" be R&D.

Writing prompts and assembling a RAG pipeline don't appear in the handbook. Our reading: a prompt isn't a formal programming language, and a RAG application on an existing model and vector database falls under what the handbook excludes, new functionality based on available technology. That's our interpretation, not a statement from RVO.

Why model quality isn't a technical bottleneck for RVO

The real uncertainty in an AI project usually sits in quality: will the model reach the accuracy you need on your documents? That's the uncertainty the WBSO rules out. In the "bots and AI technology" example, problems around training a model to recognise intent aren't R&D. Nor are problems that sit purely in the statistical domain, where programming technique isn't what's holding you back. Reliability, the handbook says, is a requirement you set for the software, not a technical bottleneck.

That clashes with how AI teams experience their work. Months of iterating on training data and evaluation sets are hard and uncertain, but for the WBSO they aren't development.

This example is ours, not RVO's. Your team has to run a model within a strict response time on its own hardware, existing inference software can't do it, and you write a new technique yourself to solve that. Now the problem sits in the software. RVO's example of machines that must work together in real time follows the same logic: R&D starts where you have to build your own facilities outside the existing APIs.

The software project form (version 1.9, in Dutch) asks four substantive questions:

  1. Which concrete technical bottlenecks will you solve yourself?
  2. What will you develop yourself for each bottleneck?
  3. Which programming languages, development environments and tools do you use?
  4. Why is the solution technically new to you, and which technical risks do you expect?

Question four comes with a sentence that sinks plenty of applications: newness for an entrepreneur isn't the same as technical newness. "We're building an assistant that answers customer questions with 90% accuracy" is a functional requirement, so it fails. RVO wants to look "under the technical bonnet" and asks you to avoid loose phrases like "such as" and "among others". Its advisers may also check LinkedIn profiles and your website to judge the level of knowledge in your company.

The R&D phase ends once you've demonstrated the new working principle. The build after that, the rollout and the maintenance don't count.

What does WBSO for AI pay in 2027?

WBSO for AI projects lowers your payroll tax. It's not a payment into your account. You settle the benefit in your payroll tax return, and only after you've received an S&O declaration. The base is R&D hours times the R&D hourly wage, plus either a flat rate or your actual costs and expenditure. For 2027, RVO reported on 15 September 2026:

  • 36% of the first €391,020 of the base, 50% for starters, and 16% above that
  • A fixed R&D hourly wage of €33, up from €29, the first change since 2008
  • A flat rate of €10 per R&D hour up to 1,800 hours and €4 above that (handbook)

The €33 applies if you had no S&O declaration two years earlier, so for 2027 none covering 2025. If you did, RVO calculates your own hourly wage from what your R&D staff actually earned.

Here's a worked example, indicative only. The assumptions: a Dutch BV with no S&O declaration for 2025, not a starter, its own team spends 4,800 hours on an AI project in 2027 at €75 internal cost per hour (€360,000), and 1,500 of those hours go to technically new software. The right column shows what happens if you claim every project hour.

ItemR&D hours only (1,500)Whole project claimed (4,800)
R&D wage (hours × €33)€49,500€158,400
Flat rate€15,000€30,000
R&D base€64,500€188,400
Benefit (36%)€23,220€67,824

The left column is your budget number: €23,220, a little over 6% of project cost. The €44,604 gap to the right column isn't a missed opportunity: RVO rejects those hours, or you repay them after an audit, possibly with a fine. A starter at 50% reaches €32,250. The rise from €29 to €33 adds €2,160 here. The 16% bracket won't touch most companies of 50 to 250 staff: at €33 an hour you only reach €391,020 at about 10,276 R&D hours.

So treat the WBSO as a bonus in your AI business case, not as a load-bearing line. A project that doesn't pay back without that 6% isn't a good project. The rest of the return is covered in calculating AI ROI.

Flat rate or actual costs for GPU rental?

In this example the flat rate adds €15,000 to the base, which is worth €5,400. Actual costs win once the costs fully attributable to your R&D exceed that €15,000. The handbook lists rented equipment used solely for your own R&D and licences for specific tools you need for it. Licences for general business use, general-purpose ICT equipment, depreciation and hired labour are excluded.

There's a price. Handling takes 8 weeks longer, the choice holds for the whole calendar year, and you need a separate cost administration. Whether a GPU server that also runs production work counts as general-purpose isn't in the handbook. Ask RVO before you put that investment in your application.

The 20 December WBSO deadline is a calendar trap

The WBSO deadline for a 1 January 2027 start falls on a Sunday, and RVO's WBSO calendar (checked 2 November 2026) lists that Sunday as the date. Don't count on it moving to Monday. The helpdesk isn't available at weekends, and the handbook gives working days from 08:30 to 17:00.

DateWhat has to happenWho
Well before 20 DecembereHerkenning level 3 with authorisation for RVO services in placeAnyone without eH3
Friday 18 December, 17:00Last moment the helpdesk can helpEveryone
Sunday 20 December 2026Application with a 1 January 2027 startBVs and others with R&D staff
Friday 1 January 2027Application with a 1 January 2027 startSelf-employed applicants
Sunday 31 January 2027Application with a 1 February startBVs and others with R&D staff
Wednesday 31 March 2027Report realised R&D hours for 2026BVs and others with R&D staff
Thursday 30 September 2027Last application for 2027Everyone

The real trap is the first row. RVO's application page requires at least eH3 and warns that "it may take several weeks before your credentials are provided". If you don't have eH3 by mid-November, you've got just under five weeks for a process that can itself take weeks.

The Dutch WBSO page says self-employed applicants can file "nog op diezelfde dag" (on that same day), which isn't clear on its own. The handbook and calendar settle it: for them it's 1 January. For a BV with employees, it stays 20 December.

There's no retroactive application. Miss the date and your application starts on 1 February at the earliest, and your January hours fall outside the declaration. Running projects need a new application for the next year too. If you're short of time you can file an informal application (vormvrije aanvraag) and complete it later. If you don't withdraw it, it counts toward the maximum of 4 applications per calendar year.

Do you get WBSO if an agency builds your AI project?

You generally won't get WBSO on a software agency's invoice. The scheme rewards your own R&D: you can only claim hours of employees on your payroll, so no freelancers or agency workers. Hours worked outside the EU don't count either, which rules out nearshore teams based outside the EU.

The WBSO conditions separate two kinds of outsourcing. Outsourced research never qualifies. Outsourced work can only qualify under actual costs, and only if it's essential to your own R&D project. If the supplier solves the technical bottlenecks, there's no R&D of yours to attach those costs to.

That applies to us too: when Pixel Management builds your custom software, our invoice earns you no WBSO. A supplier can apply for its own R&D, even when it works to order, but that doesn't automatically lower your price. So don't let the WBSO decide between outsourcing and building in-house. With a genuine technical problem, a mixed setup can work: your own developers solve the bottleneck and an agency builds the application around it. Whether that bottleneck exists is a question for an honest build versus buy assessment.

Service

Learn more about custom software?

View service →

Your R&D administration has to survive an audit

The R&D administration is where an AI project can lose a granted WBSO benefit. The handbook requires hours per person, per project and per day, updated within 10 working days. Project records must be updated within 2 months of each quarter's end, and everything stays on file for 7 years. Hours spent on the administration itself aren't R&D hours.

For software, RVO names version control such as GitHub and issue tracking such as Jira as evidence. The date and the name of whoever did the R&D must be visible and stay visible, even after a migration. AI assistants need extra care here. In the code generation example, you must be able to explain which code you wrote and what the assistant contributed. Our advice is to keep that distinction visible per commit, because a reconstruction after the fact convinces nobody.

If the records don't hold up, a correction declaration may follow, and possibly a fine. If you don't report your 2027 hours in 2028, RVO sets them to zero.

RVO's handbook also warns about AI tools for writing the application: your input can be used to improve the tool and is stored on servers. A WBSO application describes your technical approach in detail, so that text doesn't belong in a public chatbot.

What's still uncertain for 2027?

The WBSO figures and the rules on AI aren't settled yet as of November 2026. Here's where things stand:

  • Parameters. RVO says the conditions and parameters are only final once the Eerste Kamer, the Dutch senate, has approved them. The Dutch government scheduled the senate's handling of the 2027 tax package for December.
  • AI widening. According to RVO, the coalition agreement announces a widening of the WBSO for AI and software, which has to fit the generic character of the scheme. The ministry is still looking into where changes are needed, and there's no date. The 2027 handbook doesn't include it. Don't budget on it.
  • Innovation box. An S&O declaration is a condition for this lower corporate tax treatment. The cabinet wants to raise the maximum flat amount from €25,000 to €100,000, expected from 1 January 2027. That proposal is only final once both chambers have passed it.

Other schemes offer little for AI right now. The MIT R&D collaboration projects for AI are temporarily closed: in the 2026 round, 18 of 77 ranked proposals were funded from €3.55 million, and on 2 September 2026 RVO gave no date for 2027. The MIT knowledge voucher won't open again, RVO says. There's a broader overview in AI funding in the Netherlands.

When should you skip the WBSO?

Skip the WBSO if one of these answers fits your AI project:

  • You have no developers of your own on the payroll.
  • The work is configuring, connecting or calling existing models and packages.
  • The only uncertainty is whether the model will be good enough.
  • Experienced developers would solve it with known techniques, even if it's new to your company.
  • It's only a few hours: 100 R&D hours at €33 plus the flat rate yield €1,548, against daily time records per person.

If a real programming problem survives this list, the WBSO is worth the effort, as long as you budget cautiously and guard the line between R&D and building. If you're unsure your AI work has reached that point, start with what actually needs developing: hiring AI consulting or an AI review answers that faster than an application will. This isn't tax advice: have a WBSO adviser or your accountant check your situation.

Curious how much time you could save?

Request a free efficiency audit. We'll analyze your processes and show you where the gains are, no strings attached.