A1 notification for posted workers
If you have staff from another EU country working in the Netherlands, you must notify this before the work starts, and the Dutch client must check that notification. In addition, a valid A1 certificate must be available for each employee. Appfront builds the register that keeps track of who has been notified, which certificate belongs to them and when it expires.
What the notification duty and the A1 certificate require of you
The Posted Workers (Terms of Employment) Act requires a foreign employer who temporarily has staff working in the Netherlands to notify this in advance via the online notification portal. The notification includes, among other things, the work to be carried out, the location, the period and the employees involved. The Dutch client receives the notification and has a duty of its own: to check that the details are correct and to report any inaccuracies.
Then there is the A1 certificate, which is a separate matter. It shows which country's social security system the employee falls under, so that contributions are not due in two countries. The certificate is issued by the competent authority of the sending country and has a period of validity. If it is missing or has expired, that is a risk for the client and not only for the foreign employer.
In practice the two tracks get mixed up and the records turn into a folder of PDF files per project. That works as long as it involves only a handful of people. Once you work with several subcontractors, rotating crews and extensions, you lose track at exactly the moment the deployment is at its busiest. That is what we build a register for.
If you are the Dutch client, you have a duty to check on top of the notification duty, with a deadline of its own. See WagwEU software, and for checks on site the app at the gate.
How we build your register
We start with the chain: who notifies, who checks and who bears the risk. Software that does not make that distinction just moves the folder of PDF files onto a screen.
We map out which foreign service providers you work with, how deep the subcontracting chain runs and who carries out the checks on your side. That includes the question of what information you can already request under your contracts, because a register is only as good as what goes into it.
For each employee, project and period, we define which documents must be in place: the notification, the A1 certificate, identity details, employment contract and payslips. The model has to cope with extensions, because in practice an end date shifts more often than it holds.
We work in sprints and start with the side that carries the greatest risk, usually monitoring validity dates. Your own people work alongside us and test each sprint against a live project, because edge cases such as an employee assigned to two projects at once only surface that way.
We set up the alerts well before a certificate expires and hand over to the people who carry out the checks. That includes a short instruction on what to do when something is missing, so the register does not just flag issues but also leads to action.
What the register actually does
Six components that make the difference between an archive and a system that warns you before someone without valid papers is on site.
File per posted worker
One place where the notification, the A1 certificate, the period and the project come together, along with the employer and any subcontractor. If someone works on several projects, they are linked to each of them without you having to duplicate the file.
Validity date monitoring
The A1 certificate and the notified period each have an end date, and these rarely coincide. The system warns well in advance, the right person, and keeps warning until action has been taken. Letting something lapse without anyone noticing is exactly the scenario you want to rule out.
Client verification
As the client, you are required to verify the notification. We build that step in as an action with an outcome: verified, approved or returned to the service provider, with who did it and when. Without that record, you cannot demonstrate afterwards that you met your obligation.
Subcontractor portal
Your subcontractors submit their own documents instead of sending them by email. That saves your people from chasing them and ensures the data arrives in the right format and against the right project straight away.
Documents available on site
During an inspection, certain documents must be available on site. A register that also works on a phone means a site manager can show them without first having to call the office.
Overview per project and per chain
Who is on which site this week, through which employer, and which file is incomplete. That overview is useful both for the site manager on the construction site and for whoever manages the chain contractually.
Who we build for
Four situations where this register pays for itself. The emphasis differs: sometimes the risk lies with the notification, sometimes with the chain beneath it.
Construction and infrastructure
Deep subcontracting chains, changing crews and many foreign service providers. This is where the client's duty of verification weighs heaviest, and an app on the construction site is often part of the same solution.
Temp agencies and secondment firms
You are the service provider yourself and submit notifications on behalf of your employees. Your interest is that the notification is correct and aligns with your own planning and placements, so an extension does not have to be entered manually in two places.
Manufacturing and installation
Foreign fitters who come temporarily to install or maintain equipment. Often short periods, but a lot of them, so the administration per case is small but considerable in total.
Agricultural and logistics seasonal work
Large numbers at once, with a peak during which the administration falls behind fastest. A portal where the service provider submits their own documents is the difference here between staying on top of things and fixing problems afterwards.
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 does not offer an open integration for companies, so the register does not take over the notification but records that a notification was made and what it contained. What else we use depends on which systems you already run.
If your vehicles also make domestic journeys in other member states, you can keep track of the number of cabotage journeys and the supporting documents with our cabotage counter with documentation file.
For the housing of the same employees, we have a separate page on housing administration for migrant workers.
Why Appfront
We build around the date, not the document
Almost every problem in this area comes down to a date that passed without anyone noticing. That is why we design the register around validity rather than storage.
The duty to check is an action
Checking is something a person does, and the result needs to be on record. Software that merely displays a document leaves that duty, unnoticed, with whoever happened to have the screen open.
Connecting to what you already run
Your planning, your project administration and your time registration already know who is where. We pull that data in rather than having it entered again.
Honest about what software does not solve
We do not submit notifications on your behalf, and we do not assess the substance of declarations. What we build is the system that tracks, alerts and provides evidence. We tell you where that boundary lies upfront.
Security and privacy
This register consists almost entirely of personal data, some of it sensitive: identity details, nationality, payslips and residence details. That calls for a restrained set-up. For each document type we record why you need it and for how long, and we keep access as narrow as possible: a site supervisor needs to see whether someone is allowed to be on site, not what they earn.
In practice that means fields hidden per role, no full copies of identity documents where they are not strictly necessary, and a retention period that expires automatically. The subcontractor portal gets its own restricted role so that subcontractors see only their own people. All access and changes are logged, because in an inspection or a complaint it must be possible to reconstruct who viewed what and when. 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 A1 and the notification duty
The notification concerns the work: who is coming, where, when and what they will be doing. The foreign employer submits it before work starts, via the online notification portal, and the Dutch client checks it. The A1 certificate concerns social security: it shows which country's contribution rules apply, so that contributions are not paid twice. They are often confused, but they are two separate obligations, each with its own consequences if missing.
The foreign service provider, meaning the employer who has its staff work here, submits the notification. The Dutch client must check the notification for accuracy and report any omissions. This is an independent duty: you cannot simply assume the other party got it right. It is precisely this checking step that we record in the software as an action with an outcome and a name attached.
In that case it cannot be shown which system the employee falls under, with the risk that contributions turn out to be payable in the Netherlands. In an inspection by the Dutch Labour Authority, missing required documents leads to enforcement action. In practice the biggest problem is that expiry happens unnoticed: the certificate was valid at the start and the job overran. That is why we base the monitoring on the end date rather than on the moment of submission.
Your responsibility does not stop at your direct contracting party. In multi-layered chains, the practical approach is to set out contractually which layer supplies what, and to see in the register which layer is missing. For that we build a portal where each link in the chain submits its own people, so you don't have to request everything through your main contractor.
No. The notification portal has no open integration that lets business software submit on your behalf, so we don't promise that. What the register does do is track that a notification was made, what it contained and when, and flag when a notification needs to be renewed ahead of an extension. That is where mistakes happen in practice, not in filling in the form itself.
During an inspection you are usually asked for documents that demonstrate the employment relationship and terms of employment, such as the employment contract, payslips, an overview of hours worked and the A1 certificate. The exact set depends on the situation; have your lawyer determine this for each arrangement. We make sure that what you need can be shown on a phone on site.
Yes, and the emphasis shifts. Your interest is that every notification is correct and matches your own postings, and that extensions automatically trigger a new notification. You also want to be able to show your Dutch clients that your file is complete; that has become an argument in tenders.
It sits alongside it and draws from it. Your HR system knows the employees and contracts, your planning system knows the projects. The register adds the layer that isn't in there: notification, certificate, validity and inspection. We build it as a separate layer so you are not tied to a single supplier for both.
Building an A1 and notification obligation register?
Tell us what your chain looks like and where the administration currently falls through the cracks, and we'll help you think through the document model, the alerts and the portal for subcontractors. We build this as a standalone register and as part of a broader custom software project or a web application.