Integration with your social secretariat

An integration with your social secretariat sends approved hours, work performed and allowances automatically from your time registration or planning app to payroll, so HR no longer retypes them every month. Aziri builds this integration as part of a custom time registration or planning app. The payroll calculation itself stays with your social secretariat.

What flows where

A typical integration. What exactly is exchanged is agreed together during the analysis.

  1. Your applicationSocial secretariat

    Approved work performed per employee per day: number of hours, start and end time, and the performance code your social secretariat uses

  2. Your applicationSocial secretariat

    Allowances and expenses, such as night premiums or mileage, if your rules calculate them in the app

  3. Social secretariatYour application

    Confirmation per entry, accepted or rejected, if your social secretariat returns it through its API, so HR sees what still needs attention

  4. Social secretariatYour application

    The list of employees with their staff number, so each record lands with the right person. Only possible if your social secretariat offers that data through an API or export

Which social secretariats does Aziri integrate with?

Every social secretariat and payroll package reads work performed in its own way. This is what we have demonstrably built, and where we have no integration yet.

Social secretariat or payroll package How the data gets there today
Pratoflex (Prato) Through the API: work performed and allowances go straight into payroll per employee per day, just like manual entry.
Group S Monthly export file (CSV) with salaries and allowances per employee.
SD Worx In an ongoing project: a monthly export file of hours worked that SD Worx imports.
Acerta, Liantis Integrated. Whether work performed goes through an import file or an API is matched to your account during the analysis.
Partena, Securex Not integrated yet. We check during the analysis which format they accept.

An HR services company that received weekly time records from its clients in Excel, each in a different layout, saves a day of admin per week this way. How the hours are recorded is explained on our page about time registration and time tracking.

Does the integration use an API or an export file?

Both are possible; which one depends on your social secretariat. A social secretariat reads work performed in two ways. Through an API, the data goes straight into payroll, and the social secretariat can report for each entry whether it was accepted. Through an export file, the app creates a file in your social secretariat’s format (often CSV or XML), which HR uploads or which is sent automatically. That works with almost every social secretariat, but the check only happens after the import.

Which of the two is possible depends on your social secretariat and sometimes on your contract. What goes across in both cases: regular hours per day, overtime, night and weekend work, absences such as leave or short leave, and allowances or expenses, each with the pay code your social secretariat uses.

How we build the integration

We start with the person who enters work performed today, because they know the pay codes and the exceptions best. Together we agree which record maps to which performance code, what happens with overtime, night work and allowances, and which rules your social secretariat already applies itself. Those agreements go into the scope you approve.

The hard part is rarely technical. Every record has to belong to the right employee for certain, even if someone’s name differs between the time clock and payroll. So we agree up front which number links them, preferably the staff number rather than the name. Before the integration goes live, we test with the real hours of one period, so you can see the entries are correct.

Why this matters more from 2027

Under the Belgian draft bill, every employer will have to record working time objectively and reliably, and be able to show during an inspection that hours were not changed afterwards. If hours are still retyped from Excel into the social secretariat’s system, you have two versions of the same figures. What has been settled and what has not, we keep track of in our blog post on mandatory time tracking from 2027.

For construction, Check in and out at Work also applies from 1 April 2027. For that we built AutoCheckIn, which checks your people in and out on site automatically and which we can connect to your time registration.

When don’t you need an integration?

Some social secretariats offer their own recording tool, and with few staff on fixed hours, entering them by hand is sometimes faster than building an integration. In that case we’ll recommend it. An integration pays off when the hours already live in another app, such as your planning or digital work order, or when HR retypes and corrects hours every month.

Frequently asked questions

Question not listed? Ask us directly.

Does it work with my social secretariat?

That depends on what your social secretariat accepts: an API, an import file or both. With Pratoflex we use the API, with Group S an export file, and for SD Worx we are building an export in an ongoing project. We also already integrate with Acerta and Liantis. For other social secretariats we check during the analysis, together with your account manager there, which format they read.

How do I know the integration calculates correctly?

Before it goes live, we send the real hours of one period and compare the result with what HR entered by hand. Only when both match does the retyping stop.

Do we have to change social secretariat?

No. Your social secretariat keeps calculating salaries, with the same payroll formulas and pay codes as today. The integration only replaces entering work performed by hand.

What does an integration with the social secretariat cost?

An integration with your social secretariat starts from €2,000. What it costs depends on the number of performance codes and allowances and whether the secretariat uses an API or an export file. If we build it together with a time registration or planning app, it sits within that project’s fixed price; a first version for one process starts from €5,000. On top of that there is an annual licence for hosting and maintenance, from €1,000.

What if a correction comes in after the export?

Then it has to be included explicitly in the next export, because some exports only cover the current month by default. In the app, a period is closed as soon as it has been sent, and anyone who wants to change it reopens it first. That way you always know which version your social secretariat has.

Can Check in and out at Work records go to the social secretariat?

Not directly, because those records go to the NSSO (RSZ/ONSS) and only show who was on site. If you want to use the same check-in as the basis for payroll, we connect AutoCheckIn or your site registration to your time registration, and the approved version goes to your social secretariat.

Tell us where things get stuck

Tell us briefly how your process works today. We’ll let you know whether custom software makes sense, roughly what a first version costs and how quickly it can be running.

We reply quickly.