Does your company work on sites where social security wants to see who's on-site? Then you already know Checkinatwork: before every employee starts on such a location, you're required to report their presence to the RSZ/ONSS. Most companies that still do this outside their accounting and HR system end up typing the same information twice: once for planning, once for social security.
Our CIAW connector for Odoo turns that into one step. You select the employees, pick the project and the date, and Odoo reports those presences directly to the RSZ. No separate portal, no export file, no copying data by hand.
How it works in practice
An HR user opens the CIAW → Register Presence menu, picks a site (every project with an AVW/work-declaration reference shows up in the list) and a date, and ticks the employees who need to be there that day. Odoo immediately shows the name, national number and department for each person, so a missing national registry number is caught before anything gets sent.
Once confirmed, the request goes to the RSZ in one go. Even for hundreds of people at a time, it's sent in batches so you don't have to click through each employee individually. You immediately see, person by person, whether the report was accepted, and if it's rejected, the reason is shown in plain language instead of an error code.
What happens automatically afterwards
Sending a report isn't the end of the story. In the background, the connector keeps track of every registration:
- If a report doesn't go through right away (a temporary network hiccup, for instance), the system automatically retries it, up to a configured maximum.
- Once accepted, it keeps checking with the RSZ until the report is fully validated.
- If someone ends up not showing up after all (illness, leave, a schedule change), you cancel the registration with one click, with the right reason attached.
- A registration that already exists at the RSZ can't simply be deleted from Odoo. That keeps your records consistent with what the RSZ actually has on file.
The result is an overview per employee, per site, per day, with the status right next to it: not yet sent, sent, validated, or failed. That overview also doubles as your evidence if an inspection ever comes up.
Secure, and kept separate per company
The connection with the RSZ uses a digital certificate that signs every message, as required by the RSZ. That certificate and its password are only visible to whoever manages the system; an HR user works with the connector without ever seeing them. Running multiple companies in the same Odoo environment? Each company has its own certificate and its own settings, kept cleanly apart.
Before going live, you can test the connection first: that test makes a real call to the RSZ's servers and tells you exactly what, if anything, still needs to happen, for example that your certificate still needs to be administratively linked to your company number with the government.
Good to know upfront
Two things matter for whether this fits how you work today:
The RSZ only allows registrations for today or tomorrow. That's not a limitation of our connector; it's a rule set by the RSZ itself. So you can't pre-schedule reports for next week yet.
Today, the connector reports your own employees, based on the national number stored in Odoo. If you also work with subcontractors or self-employed workers on a site, their reporting still happens separately for now. The actual work declaration (obtaining the AVW number itself) also still happens outside Odoo. The connector uses that number once you have it.
Curious whether this fits your sites?
We're happy to walk through what this looks like in your own Odoo environment, with your actual sites and the way you already plan work. Get in touch with Endoo for a demo or a no-obligation conversation.