Back to blog

2 april 2026

My schedule wasn’t talking to social security. So I made them talk.

At Tartelier we work with flexi-jobs and students on varying hours. It started as a paper calendar plus declaring every shift to social security through Dimona by hand. Now the schedule in Orageo sends the declarations itself, and the manager only steps in when something's off.

Gaëtan Steijaert
Written by Gaëtan Steijaert Software architect from Ghent

At Tartelier we work with flexi-jobs and students on varying hours. Every shift has to be declared to the Belgian social-security registry through Dimona. Start and end time, per worker, for every change. At the start our schedule was just a calendar on the wall, and my store manager keyed every declaration into the RSZ portal by hand.

What I saw

A calendar on the wall reads fine, until something shifts. Someone leaves early, someone fills in, an hour moves. And every change meant going back to the RSZ site. Type it, type it again. Two places for the same hours.

And forgetting happens, because it comes on top of the actual work. Forget a declaration, and you risk a fine.

Scheduleon paper store manager+ RSZ portal DimonaRSZ declaration Each shift on its own, keyed into the RSZ portal.
Before. The schedule on paper, and my store manager keying every shift into the RSZ portal.

What I did

I did it in two steps. First I brought the Dimona declaration into Orageo, so it goes out through the API instead of being keyed into the portal by hand. No more RSZ site, no more retyping.

Then the schedule itself moved into Orageo too. And that is where it clicks: you plan or change a shift, and the declaration follows on its own. The schedule is the declaration.

The check sits at the back on purpose, not the front. Just before a declaration goes out, the manager gets a heads-up. Do nothing, and it goes anyway. That way nothing gets forgotten, because doing nothing means declared. He only has to step in when something is off, to hold it or fix it. A Dimona declaration isn’t easy to undo, so that one window to step in is exactly the part that matters.

Orageo schedule automatic Ready to declare heads-up to the manager sends itself Dimona RSZ declaration manager can step in hold it or fix it, only when something is off
Now. The schedule sends the declaration to Dimona itself. If the manager does nothing, it goes. He only steps in when something is off.

What it gave back

My store manager no longer touches the RSZ portal, and the paper calendar is gone. The schedule sends the declarations itself, and by default they go through. Nothing forgotten, nothing done twice, and the Dimona time windows are respected without anyone having to think about them. He only looks when something deviates. And the same schedule flows on to payroll later, through Orageo’s Prestatie export.

And for you?

Got flexi-jobs or varying hours, and time leaking into separate declarations for every change? It doesn’t have to be that way. Let me come and look. The first look is free, no strings.