We've just launched a new feature! Check out the new dashboard.

Dimona (Belgian Employee Registration) in Events

In brief: A caterer mobilising 80 casual workers every weekend generates more than 300 Dimona (Belgian employee registration) declarations per month. Doing this manually is a ticking time bomb: missed entries, date errors, late declarations, NSSO penalties. This guide covers how Dimona works in events, declaration types by employment status (casual worker, student worker, flexi-job), legal deadlines and the automation workflow with Shyfter.

Dimona in events: exceptional volume

Dimona (Déclaration Immédiate / Onmiddellijke Aangifte — Immediate Declaration) is the compulsory notification of each worker's start and end of service to the NSSO (National Social Security Office). In a restaurant with a stable team, it is manageable. In events, it is an administrative nightmare.

The numbers speak for themselves. A caterer managing 4 events per weekend with 30 casual workers each generates 120 Dimona declarations per week. During festival season (June–August), this volume easily doubles. Over a year, a mid-sized event company generates 2,000 to 5,000 Dimona declarations.

Every missed or late declaration exposes the employer to a fine. Every date or contract type error can trigger a regularisation. The risk is all the higher because social inspection checks are frequent at public events.

Types of Dimona declarations in events

Dimona for casual workers (occasional workers)

The occasional casual worker is the typical event profile. Each assignment by a casual worker requires a Dimona IN (entry into service) and a Dimona OUT (end of service). Required information:

Worker's national identification number (NISS)
Planned start date and time of assignment
Planned end date and time of assignment
Contract type (fixed-term, temporary employment)
Employer's CBE number

In hospitality (Joint Committee 302), there is a specific "occasional worker" status allowing simplified declarations for a maximum of 50 days per year per worker.

Dimona for student workers (STU)

Student workers are subject to a Dimona STU declaration. This declaration is linked to the 475-hour allowance at reduced contributions. Specific information required:

STU type (student)
Number of planned hours for the assignment
Prior verification of available hour balance via Student@Work

Each STU declaration automatically decrements the 475-hour counter. If a student has already used their 475 hours (with you or with another employer), the STU declaration is rejected and you must switch to a regular declaration with full contributions.

Dimona for flexi-jobs (FLX)

Applicable only under Joint Committee 302. The FLX Dimona declaration requires a prior framework contract between the employer and the flexi-job worker. Each assignment is then subject to an FLX Dimona with reference to the framework contract.

Conditions to verify before the declaration:

The flexi-job worker has a main job of at least 4/5 with another employer (T-3)
The flexi framework contract is signed and registered
The assignment is in a sector eligible for flexi-job status

Dimona for agency workers

When you use a staffing agency, the Dimona declaration is the agency's responsibility, not the user's. You do not need to file Dimona declarations for these workers. But verify that the agency meets its obligations, because in the event of an inspection on your site, it is your event that is being inspected.

Legal deadlines: before the shift starts

The basic rule

The Dimona IN declaration must be made no later than at the moment the worker starts service. Not after. Not the next day. At the time of starting service or before.

In practice, it is recommended to file declarations the day before the event, once the schedule is finalised. This leaves a margin in case of a technical problem with the NSSO portal.

Modifications and cancellations

A casual worker cancels at the last minute. Another replaces them. You must:

Cancel the Dimona of the unavailable casual worker (Dimona CANCEL)
Create a new Dimona for the replacement (Dimona IN)

In events, these modifications happen daily. A manual system cannot keep up. Every missed modification leaves an incorrect record with the NSSO.

The Dimona OUT

The exit declaration (Dimona OUT) must be filed no later than the first working day following the end of the assignment. For a Saturday event, the Dimona OUT must be submitted by Monday at the latest. If there is a discrepancy between the planned hours and actual hours, the Dimona OUT corrects the data.

Risks of non-compliance

Financial penalties

Absence of a Dimona declaration is penalised by level 4 administrative fines under the Social Penal Code:

Administrative fine: 400 to 4,000 EUR per undeclared worker
Criminal fine (if prosecuted): 800 to 8,000 EUR per worker
Multiplied by the number of workers concerned

For an event with 50 undeclared casual workers, the theoretical fine can reach 200,000 EUR. This is an existential risk for a small event company.

On-site checks

The social inspection service carries out regular checks at major events, festivals and trade shows. Inspectors compare the list of people physically present at the site with the registered Dimona declarations. Each person present without a valid Dimona is an offence.

Music festivals, major fairs and sporting events are priority targets for inspections. Be prepared: always have an up-to-date list of staff present with the corresponding Dimona references.

NSSO regularisations

Beyond fines, the NSSO can demand a regularisation of social contributions for undeclared or incorrectly declared workers. A student worker declared as STU who has exceeded their 475 hours triggers a recalculation at the normal rate, retroactively. The amount can be significant over an annual volume of several hundred student assignments.

The automation workflow with Shyfter

Step 1: plan the event

Create the event in Shyfter with the phases (setup, event, breakdown), roles and time slots. Assign casual workers from your pool.

Step 2: confirm the schedule

Once confirmations are received and the schedule is finalised, confirm it. Shyfter automatically verifies:

That each casual worker has a valid NISS number in the system
That student workers have a sufficient hour balance
That flexi-job workers (Joint Committee 302) have an active framework contract
That minimum rest periods between assignments are respected

Step 3: automatic Dimona generation

Upon confirmation, Shyfter generates Dimona declarations for each assigned worker. The declaration type (standard, STU, FLX) is automatically determined based on the worker's status. You confirm the batch in one click.

Step 4: managing modifications

A casual worker cancels? You replace them in the schedule. Shyfter automatically cancels the outgoing worker's Dimona and creates the replacement's. No double entry, no risk of omission.

Step 5: post-event close-out

After the event, time tracking confirms actual hours. If clocked hours differ from planned hours (a casual worker left early, another worked overtime), Dimona OUT declarations are automatically adjusted.

Common special cases

A casual worker on two events the same day

A waiter working at a brunch from 8am to 2pm and at a cocktail reception from 6pm to 11pm on the same day requires two separate Dimona declarations if the two assignments are for different events. The tool must handle this situation without creating a conflict.

The event cancelled at the last minute

An event cancelled due to weather or a client decision requires cancellation of all associated Dimona declarations. For an event with 80 casual workers, this means 80 cancellations. Manually, that is half a day's work. With Shyfter, a bulk cancellation is all it takes.

The casual worker who changes status mid-year

A student who finishes their degree in June can no longer be declared as STU from September. A flexi-job worker who loses their main job is no longer eligible for FLX status. The system must alert when a status change affects the Dimona type.

Best practices for Dimona management in events

Plan ahead: generate Dimona declarations the day before the event, not the morning of
Verify data: an incorrect NISS number blocks the declaration and costs you time
Keep a buffer: also declare your reserve casual workers — you can cancel Dimona declarations for those who do not show up
Archive: keep Dimona confirmations for a minimum of 5 years
Train your team: the on-site coordinator must know how to verify that a casual worker is properly declared before allowing them to start
Audit monthly: compare the number of clocked assignments with the number of Dimona declarations sent to detect discrepancies

Request a demo

FAQ

What happens if a casual worker starts working without a valid Dimona declaration?

It is an offence under the Social Penal Code. In the event of an inspection, the inspector records the absence of a declaration and draws up a report. The administrative fine is 400 to 4,000 EUR per undeclared worker. In the event of a repeat offence or intentional fraud, criminal prosecution with doubled fines is possible. The solution: never allow a casual worker to start without verifying that their Dimona has been validated. With Shyfter, each schedule confirmation automatically triggers the Dimona.

How do you manage Dimona declarations when an event is cancelled on the day?

All Dimona IN declarations already submitted must be cancelled via a Dimona CANCEL declaration. If workers have already arrived at the event venue, you must still submit a Dimona OUT with the actual hours (even if the assignment was cut short). Shyfter allows you to bulk-cancel all Dimona declarations associated with an event in a single operation, avoiding 80 or 100 individual cancellations.

Can a student worker who has used up their 475 hours still work as a casual worker?

Yes, but with a regular employment contract and Dimona declaration, not STU type. Social contributions revert to the normal rate (approximately 13.07% employee share and 25% employer share), which significantly increases the cost for both parties. In practice, many student workers prefer to stop once the 475 hours are reached. Monitor the counter in advance to anticipate and recruit replacements before reaching the threshold.

Other events industry guides

Ready to transform your workforce management?

Shyfter is more than a scheduling tool. It's a complete workforce management solution designed to save you time.

Request a demo