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

Dimona Declarations for Caterers

In brief: An active caterer generates dozens, even hundreds of Dimona (Belgian employee registration system) declarations per week. Each temporary worker, each student, each service requires its own declaration with the NSSO (National Social Security Office). When you mobilise 50 people for a single event, manual management is no longer an option. This guide explains the Dimona workflow specific to caterers and how Shyfter automates the entire process.

Why Dimona volume is a unique challenge for caterers

A restaurant declares its waiters and cooks once. They come back every week on the same schedule. A caterer declares dozens of different people each week, for different events, on different dates, with different schedules.

Take a typical high-season weekend: 3 simultaneous events, 25 temporary workers per event. That is 75 individual Dimona declarations for a single weekend. Over a June month with 4 busy weekends, you reach 300 declarations. Each declaration must contain the correct dates, correct hours and correct contract type.

One date error, one missed declaration for a single temporary worker, and you face a fine of 2,500 to 12,500 euros during an inspection.

How Dimona declarations work

What is Dimona?

Dimona (Déclaration Immédiate / Onmiddellijke Aangifte — Immediate Declaration) is the electronic registration system by which every Belgian employer notifies the NSSO of each worker's start and end of service. The declaration must be made before the start of the service.

Relevant declaration types for caterers

  • Dimona IN: entry into service declaration, to be made before the start of the service
  • Dimona OUT: exit from service declaration, to be made at the end of the service
  • Dimona EXT: specific type for hospitality temporary workers (JC 302)
  • Dimona STU: specific type for student workers

Required information

Each Dimona declaration contains:

  • Employer identification number (NSSO)
  • Worker's national registration number
  • Date and time of start of service
  • Expected date and time of end
  • Contract type (temporary worker, student, fixed-term, permanent)
  • Joint committee (302 for hospitality)

The automated Dimona workflow with Shyfter

Shyfter integrates Dimona declaration directly into the temporary worker mobilisation process. The workflow becomes:

  1. You create the event in Shyfter with the positions to fill
  2. You propose missions to temporary workers from the pool
  3. Temporary workers confirm their participation via the app
  4. Shyfter automatically generates the Dimona declaration for each confirmed temporary worker
  5. The declaration is sent to the NSSO before the start of the service
  6. If a temporary worker cancels, the declaration is automatically amended or cancelled
  7. After the event, logged hours feed the OUT declaration

Zero manual entry. Zero omissions. Zero date or type errors.

Dimona and different worker statuses

Hospitality temporary workers (EXT type)

The EXT type declaration is specific to the hospitality sector. Social contributions are calculated on the basis of actual pay.

Student workers (STU type)

Student workers are subject to an STU type declaration, with the benefit of reduced contributions within the 475-hour limit. The declaration must state the planned hours for quota calculation.

Flexi-job workers (FLX type)

Flexi-job workers (a Belgian employment type) have an advantageous tax and social regime. The Dimona FLX type declaration is specific. The worker must meet eligibility conditions: a main occupation of at least 4/5 time with another employer, or be a pensioner.

Practical case: a weekend with 4 events

Weekend of 21–22 June. Four events:

  • Friday evening: corporate cocktail in Brussels (8 temporary workers)
  • Saturday noon: wedding brunch in Waterloo (12 temporary workers)
  • Saturday evening: wedding in Namur (28 temporary workers)
  • Sunday noon: communion in Liège (10 temporary workers)

Total: 58 individual Dimona declarations for a single weekend.

With Shyfter, all 58 declarations are generated automatically as soon as temporary workers confirm their participation. When a temporary worker cancels on Friday, their declaration is cancelled in one click and the replacement's is created automatically.

Costly errors

  • Late declaration: a declaration sent after the start of service is late. Fine: 2,500 to 12,500 euros per late declaration
  • Missing declaration: a forgotten temporary worker is treated as undeclared work
  • Wrong declaration type: declaring a student as EXT instead of STU affects social contribution calculations

Request a demo

FAQ

How many Dimona declarations does a typical caterer need to manage per month?

Volume depends on your activity. A caterer with 4 events per weekend and an average of 20 temporary workers per event generates around 320 declarations per month. In high season (May–September), this figure can double. Automation is not a luxury: it is an operational necessity once you exceed 2–3 events per week.

What happens if a temporary worker cancels after the Dimona declaration has been sent?

The Dimona declaration must be cancelled or amended. With Shyfter, these changes are automatic: cancellation in the schedule triggers cancellation of the declaration.

Do Dimona declarations need to be sent for temporary workers working less than 4 hours?

Yes. Dimona declaration is mandatory for any service, regardless of its duration. Even for a temporary worker working 2 hours at a cocktail, the declaration is required. There is no minimum duration threshold.

Other caterer guides

Icône Shyfter

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.