Missing Dimona Flexi-Job Penalty (Belgium)

If a flexi-job shift is worked without a valid same-day Dimona (the DimDay), that day is no longer a flexi-job in the eyes of the NSSO/RSZ. It is reclassified as ordinary employment: you owe full employer social security contributions on the day’s wage, the worker loses the flexi tax exemption for that day, and repeated gaps trigger a retroactive assessment. The fix is not a better paper trail after the fact; DimDay cannot be filed retroactively. It is real-time visibility over who is about to start a shift, which is exactly what Suivo’s time tracking is built to give you, flagging a missing declaration before the worker clocks in.

What is a DimDay, and why can it not be fixed later?

DimDay is the flexi-job version of the Dimona (Déclaration Immédiate/Immediate Declaration). It is an immediate electronic declaration to the NSSO that this worker is starting this shift, and it must be filed before the shift begins, on the day it happens.

The rules that make it unforgiving:

• No grace period. The declaration has to exist before the first minute of work, not by end of day or end of week.
• No retroactive filing. You cannot log in the next morning and declare yesterday’s shift. The system will not treat a late entry as if it were on time.
• Timestamps are checked. SIOD/TSW inspectors read the DimDay timestamp against the actual start of work. A declaration filed at 18:05 for a shift that started at 18:00 is a gap.

So the “gap” is not an administrative typo you can correct. Once a worker has started without a valid DimDay, that day’s legal character is already fixed.

What are the concrete consequences of a missing DimDay?

The reclassification cascades through payroll, tax and contributions. For the affected day:

• The day becomes regular employment. Instead of the flexi regime, the wage is treated as ordinary salaried income.
• Full employer contributions fall due. The special flexi contribution no longer applies; you owe the normal employer social security contributions on that day’s wage, which are far heavier than the flexi contribution.
• The worker loses the tax advantage. Flexi-income is tax-free up to the annual threshold; income from a reclassified day does not enjoy that exemption and is treated as normally taxable.
• The wage floor logic changes. The flexi-wage and flexi holiday pay structure no longer cleanly applies, so the payroll calculation for that day has to be rebuilt on standard rules.

None of this is a fixed “fine” you can budget for. It is a recalculation, and it grows with every day involved.

How big can a retroactive NSSO assessment get?

A single missed DimDay is a bad day. A pattern is a liability. When SIOD/TSW find that flexi-job shifts were routinely worked without valid declarations, the NSSO/RSZ can issue a retroactive assessment covering every affected shift they can identify.

That assessment can reach back across the reference period under review and recalculate contributions on the ordinary-employment basis for each reclassified day. Because flexi arrangements often involve many short shifts across many workers, a “small” per-shift difference multiplies quickly. On top of the recalculated contributions, an employer that cannot show valid declarations faces the credibility problem of an inspection that has found systematic non-compliance, which shapes how the rest of the visit goes.

The honest read: the risk is not really the one forgotten shift. It is discovering during an inspection that your process never reliably produced a DimDay before work started.

Why does this hit harder since 1 July 2026?

Two 2026 changes raise the stakes. First, the flexi-job regime opened to almost all private and public sectors, so far more employers are now filing DimDays for the first time, often without settled habits. (Check your joint committee, the paritair comité, has not opted out before you hire, because opt-outs are set by Royal Decree on a quarterly basis during the transition.) Second, electronic time registration is now mandatory for any employer using flexi-job workers. That means inspectors expect a clean digital record of hours that they can line up against DimDay timestamps. A shift in your time system with no matching declaration is now easy to spot.

From 1 January 2027, working-time registration becomes mandatory for all employers, so the direction of travel is clear: the paper era is closing, and gaps that once hid in a folder now surface in data.

How does Suivo help prevent the gap?

The only real defence is to make the declaration impossible to forget and the record impossible to lose. A connected platform beats paper and disconnected tools here because the moment of clocking in is the moment the declaration matters.

With Suivo:

• Real-time hour registration captures the shift start on mobile app, badge, fixed check-in pole or vehicle, so the actual start time is recorded, not reconstructed later.
• DimDay-style alerts flag when a worker is scheduled or checking in without a matching declaration on file, before the shift runs rather than after.
• [Scheduling](https://www.suivo.com/solutions/scheduling/) distinguishes worker categories, so flexi shifts are visible as flexi and get the attention the DimDay rule demands.
• [API integrations](https://www.suivo.com/solutions/api-integrations/) connect hours to your social secretariat (Liantis, Securex, Partena, Group S, SD Worx), so the record that proves compliance is the same record that runs payroll.

For the mechanics of the declaration itself, see DimDay explained and why flexi-jobs now require electronic time registration. For the full picture, start with the complete 2026 employer guide.

Authoritative detail on the Dimona obligation is published by the NSSO at socialsecurity.belgium.be and on inspection practice by SIOD.

Book a free demo

Real-time data only helps if it leads to a decision before the shift starts. See how Suivo flags a missing declaration in time to act on it, then connects the same hours straight to payroll.

Book a free demo