Most Belgian employers that have invested in field time registration, mobile apps, site terminals, GPS clock-in, still face a manual step at the end of the week: someone exports a spreadsheet from the time registration system, reformats it, and re-enters the hours into SD Worx. This manual bridge is where errors accumulate, where compliance gaps appear, and where payroll teams lose the most time. Suivo’s native SD Worx integration closes the loop, sending validated hours automatically each pay period without manual re-entry.
How SD Worx processes payroll data
SD Worx (Société de Développement de la Paie) is Belgium’s largest payroll service provider, handling payroll for a significant share of Belgian employers, from small businesses to major corporations. Belgian employers who use SD Worx submit their payroll data each pay period, and SD Worx calculates gross-to-net wages, NSSO contributions, withholding tax, and produces payslips and the quarterly DmfA declaration to the NSSO.
For hourly and shift workers, the key input SD Worx requires is a precise record of hours worked per worker, broken down by hour type. The system needs to know not just “40 hours this week” but:
- Normal working time (at the base rate).
- Overtime hours (at 150% or 200%, depending on when they occurred).
- Night work hours (with the applicable sector supplement).
- Public holiday work (at 200%).
- Absence periods (sick leave, annual leave, time off in lieu) with the correct reason code.
- The cost centre or project code against which the hours should be allocated.
This level of detail is exactly what a good time registration system captures, but only if it is configured correctly and if the export to SD Worx includes all the necessary fields.
What the SD Worx integration export must contain
For a time registration integration with SD Worx to replace manual entry, the export must include, at minimum:
| Field | Description |
| Worker identifier | The SD Worx employee number or national registration number (INSZ) |
| Date | The working date (not the pay period start) |
| Start time | The clock-in time for that working period |
| End time | The clock-out time |
| Break duration | Total unpaid break time, in minutes |
| Hour type code | The SD Worx code for normal time, overtime, night work, etc. |
| Absence reason code | For absent periods, the SD Worx-defined absence category |
| Cost centre / project | If used, the allocation of those hours to a budget centre |
If any field is missing or incorrectly coded, the SD Worx calculation will default to the base rate for those hours, meaning overtime is paid at the normal rate, night supplements are missed, or the DmfA quarterly declaration is inaccurate.
Delta export vs. full weekly export
There are two approaches to transferring time data to SD Worx:
Full weekly export: Every Sunday (or the last day of the pay period), all hours for the current week are exported and loaded into SD Worx, replacing whatever was there before. Simple to implement; risky if any corrections were made directly in SD Worx after the previous export, as those corrections are overwritten.
Delta export: Only the records that changed since the last export are transmitted. New clock-ins, corrections, and approved overtime additions are sent incrementally. This approach is more technically complex but significantly reduces the risk of overwriting valid corrections and is better suited to environments where supervisors make corrections throughout the week.
For Belgian construction companies, cleaning companies, and logistics operators with large field teams, where corrections are common (workers forget to clock out, schedule changes, subcontractor records arriving late), the delta export approach produces cleaner payroll data.
Reducing payroll preparation time
Belgian employers who have integrated time registration with SD Worx consistently report the same outcome: payroll preparation that previously took one to two days per pay period now takes one to two hours. The hours are already validated in the time registration system; the export runs in minutes; SD Worx processes the data and produces payslips without manual intervention.
The remaining time is spent on exception handling: reviewing alerts (workers who didn’t clock out, unexpected overtime, absence without a code), approving corrections, and verifying that the export totals match the supervisor’s summary. This is productive review work, not manual data entry.
What to check before configuring a SD Worx integration
Before connecting your time registration platform to SD Worx:
- Confirm your SD Worx subscription includes the API or file import capability you need (SD Worx’s platform tiers have different integration options).
- Map your hour types in the time registration system to the correct SD Worx pay codes.
- Align worker identifiers: the time registration system and SD Worx must use the same employee reference number (either the SD Worx ID or the INSZ).
- Test with a single team before rolling out to the full workforce.
- Decide on the export frequency (daily, weekly, or on demand).
Suivo’s time tracking solution includes a native SD Worx export configuration. The integration is set up once and runs automatically each pay period.
Ready to connect time registration to SD Worx?
Suivo helps Belgian employers eliminate manual payroll data entry with a native connection to SD Worx, Acerta, Partena, and other Belgian payroll providers via API integrations. See Suivo products or view pricing.
