Custom software for the duty of inspection on foreign hiring
The duty to notify lies with the foreign service provider, but the risk of a fine lies with you too. As the Dutch client, you must check that the notification is correct and report any inaccuracies within five days of the work starting. That is an obligation concerning data you do not enter yourself and have to obtain from a third party.
Why you are liable for someone else's form
The Dutch Posted Workers (Working Conditions) Act requires foreign service providers from the EU, the EEA and Switzerland to submit a notification in the Dutch online notification portal before work begins. It states who is coming to work, where, when and for which client.
What is often missed is the second obligation. The Dutch service recipient must check that notification for accuracy and completeness, and report any inaccuracies within five days of the work starting. If you fail to do so, you risk a fine yourself, even though you did not submit the notification and did not enter the data.
That is where the practical problem lies. The data comes from your subcontractor, who enters it in a portal you have no visibility of, and the clock starts ticking the moment the work begins. For a single project that is one task; for dozens of projects with rotating crews it is an administrative burden nobody keeps up with until an inspection arrives.
How we build this
Here, the project with its start date is the unit. If the notification and the check are attached to it, the five-day deadline becomes a prompt rather than a risk.
Which foreign parties work for you, on which projects, and who your point of contact is on each project. At most companies this is spread across procurement contracts rather than held in a single overview.
The service provider submits their notification data through a portal, rather than by email with a screenshot. Data that arrives in a structured form can be checked; a PDF cannot.
As soon as a project starts, your deadline begins. The system warns you in advance rather than on the day itself, because an inaccuracy still has to be reportable.
We take a project from last quarter and check whether you can demonstrate that you carried out the check. What is missing then would be missing in a real inspection too.
What the software actually does
The register of projects and their foreign parties underpins everything. Which components you need depends on how many chains you have and how deep they go.
Register of projects and foreign parties
For each project, which service providers are working, from when and with which people. Without that overview, the duty to check is an obligation without a subject.
Portal for the service provider
Your subcontractor submits their notification data in a structured form instead of as a screenshot in an email. That way you can check the content, not just whether it is present.
Check for accuracy and completeness
Do the people named, the period and the work match what is actually happening? The system records your check with the date and the person, because that record is your evidence.
Five-day deadline monitored
From the start date of the work, your deadline for reporting inaccuracies is running. The system alerts you in advance, so there is still time to have the service provider correct it.
Inaccuracies with follow-up
A person who is on site but was not notified, a period that is wrong. Each becomes an action with an owner and a deadline, because an inaccuracy that has been identified but not followed up counts against you in an inspection.
Evidence kept per project
Which notification was on file, what you checked, when and with what outcome. In an inspection, the question is not the notification itself but what you did with it.
Who we build for
The depth of your chain determines how much work this is. Four situations.
Construction and infrastructure
Multi-layered chains with crews that change every week. Here the problem is not the notification but keeping track of who is actually on site today; you do that with the gate app.
Food production and agriculture
Seasonal peaks with large numbers at once. The notification usually goes well at the start and then falls out of step, because people join who were not in the original submission.
Logistics and transport
Drivers and loading crews who come briefly and repeatedly. The question of whether this counts as secondment and when the clock starts is hardest here, and your lawyer answers it, not your system.
Installation and maintenance
Specialist engineers who come over for a short job. Small numbers, many projects, and precisely because of that, administration that quickly falls behind. If you work with temporary staff through an agency, this touches on your staffing software.
Test your idea first: a working prototype in 1 day
With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.
View OneDayBuild →Technology and integrations
The notification portal is a government facility, not a system you can simply integrate with. We therefore build your own registration and the portal that feeds into it, and allow for changes to the procedure.
Why Appfront
The risk is yours, the input is someone else's
We therefore build the portal in which your service provider submits their data, so you can check the content rather than just whether something came in.
The clock starts when the work starts
Not at the notification and not at the invoice. We therefore tie the deadline to the project's start date and warn you well in advance.
Your project administration already exists
Projects, suppliers and start dates are already in there. We connect to it through integrations instead of letting a second list emerge.
Your evidence is the check, not the notification
We record what you checked and when, and what followed from it. That is what an inspector asks for and what an email thread does not provide.
Security and privacy
This file contains personal data of people who are not employed by you: names, nationalities, periods of residence and sometimes identity details. You process them on the basis of a legal obligation and not because it is convenient, which means you may not record more than the check requires. We therefore set a retention period per data type and show a project manager only the people on their own project.
The portal side calls for its own consideration. Your subcontractor submits data about their staff in your system, and they must be able to trust that other parties cannot see it. In the portal, a service provider therefore sees only their own notifications. On the evidence side, your check must be recorded in a tamper-proof way; a verification statement that can be amended afterwards is not evidence in an inspection. How we handle security ourselves is set out in our information security policy; reports from outside go through our coordinated vulnerability disclosure policy.
Frequently asked questions about the WagwEU verification obligation
Because, alongside the notification obligation, the law imposes a verification obligation that rests with you. You must check that your foreign service provider's notification is correct and complete, and report any inaccuracies within five days of the start of the work. If you fail to do so, you can be fined yourself, even though you did not fill in the form.
At the start of the work, not when the notification is made or when you receive the invoice. That is why we tie the deadline to the project start date. Exactly when work begins in the case of short-term or repeated deployments is a legal question that you should settle with your own adviser.
The A1 certificate concerns social security: the country in which someone is insured. The notification obligation concerns employment conditions and who comes to work where. They often appear together in the same cases, but they are separate obligations with their own rules; the registration side of this is covered on A1 and notification obligation registration.
The notification portal is a government service, not a system you can simply connect to. What we build is your own register plus a portal in which your service provider submits its notification details in a structured way. The integration options that exist change over time; we map them out at the time of building.
The verification obligation concerns the service provider you have the contract with. In practice, other parties work beneath them, and then the question is who notifies on whose behalf. That is a contractual matter you settle in advance; we build the system so that you can record multiple layers if your contracts require it.
That is exactly the situation the verification obligation exists for. It becomes a deviation with an owner and a deadline, and you report it within your five-day period. Recording that moment matters more than the finding itself, because it demonstrates that you have fulfilled your obligation.
That is precisely when it pays off. With one large project, someone remembers it; with dozens of small ones with varying start dates, it becomes unmanageable and only comes to light during an inspection. In that situation the system is also lighter, because you mainly need deadline monitoring and less chain registration.
That depends on the number of projects and parties, whether the portal is needed, and whether it needs to integrate with your project administration. The register with deadline monitoring is usually quick to put to use and removes the immediate risk; the portal costs more. We provide a well-founded estimate after the discovery phase.
Make your verification obligation demonstrable?
Take a project from last quarter involving foreign subcontracting and try to show that you verified the notification. If you can't do it within a few minutes, that is where the work lies. We build this as a standalone application and as part of a broader custom software engagement.