Rejected NSSO declaration when checking in or out: what now?

Your system forwards the registration, the NSSO checks it against its own data and responds with an acceptance or with a rejection and an error code.

Only an accepted registration puts your file in order. A registration that was sent without a response proves nothing yet.

• Dimona: the Dimona declaration is missing or incorrect, for example a new employee checking in before the Dimona is in order.
• Limosa: a foreign worker without a valid Limosa notification.
• Works declaration: the site or the contract has not been declared, or not correctly.
• Registration behaviour: duplicate check-ins or check-outs, or a check-in without a matching check-out.
• Location and technology: missing or incorrect location data, or a late registration.

1. 01Read the error code: it usually points to the underlying cause.
2. 02Find the source: does it lie with you, with the main contractor or with a subcontractor?
3. 03Correct the underlying declaration (Dimona, Limosa or Works declaration) and register again where needed.
4. 04Check that the new declaration is actually accepted.
5. 05Prevent repetition: look at whether the same error returns per crew, location or subcontractor.

An error code is not a sanction in itself. It shows what needs attention. The risk arises when nobody follows up on it.

Every declaration, in and out, is followed until the final response. Rejections appear at the top of your overview, in plain language, instead of being tucked away.

Then too, you can have your NSSO error codes read out and explained. CIAO Assist makes visible what the NSSO establishes, alongside your existing software.