Data Panda brings your SD Worx absence data together with the data from the rest of your business. From one place, we turn it into dashboards, automations, AI workflows and custom apps your HR, finance and operations teams use every day.
SD Worx started in 1945 in Antwerp as a sociale dienst for employers, founded to help Belgian companies handle payroll and social legislation in the years after the war. Eighty years later it is one of the largest payroll and HR services companies in Europe, paying around five million people every month across 26 countries, with more than 95.000 client companies and over 3.000 people in Belgium across 33 offices.
The SD Worx Absences connector is a narrow slice of that platform. It pulls the employee register and the absence codes booked against each employee, the same records your HR team uses to process sick leave, holidays, training time, parental leave and educational leave. That is two tables, not a full HRIS: enough to see absence-rate drift per department, ziektewet versus verlof breakdown, or the planning gap that opens in August, and not enough to replace your SD Worx portal for day-to-day HR admin. Pulled into a warehouse, it sits next to your CRM, your ERP and your project tooling, so capacity questions get answered against real absence data instead of a monthly PDF.
Absence rate, code mix and department drift on one page, across the whole company instead of per HR report.
Turn booked absence codes into the journal entries, capacity updates and planning nudges the rest of the stack needs.
Use the absence and employee history to forecast coverage gaps and spot patterns before they hit delivery.
Small HR and ops tools that sit on SD Worx absence data instead of a month-end PDF.
A list of concrete reports, automations and AI features we have built on SD Worx Absences data. Pick the one that matches your situation.
Which department is quietly drifting up on short-term absence?
Absence rate broken out per department and per code family, with the last six months plotted against the company average. HR sees which team has three points of extra ziektewet before the quarterly committee meeting, instead of in the year-end review, and can have the conversation while the signal is still fresh.
Do we have enough people on deck during the summer and year-end weeks?
Planned holiday load per team per week, stacked next to the projects running through that period. The ops lead and the account directors see where July and August crack open below minimum coverage, while there is still room to shuffle approvals or bring a freelancer in instead of finding out on the Monday itself.
Are our absence records ready for a social-law audit right now?
Every booked absence with its code, start and end, tied to the employee and department, in a shape a controleur can read without a week of prep. Ziektewet, verlof, opleiding, ouderschapsverlof and educatief verlof each get their own roll-up, so the audit conversation runs on the booked codes themselves rather than on a stitched-together Excel.
Absence-related payroll cost per department, with ziektewet, verlof and training time separated out on the same page as the rest of the personnel cost. Month-end accrual for guaranteed salary during illness stops being a manual reclass against a PDF from HR.
Team capacity per week on one dashboard, so the pipeline conversation runs on a realistic promise date. Sales directors see where the delivery team runs below minimum coverage before they sign an aggressive deadline into a proposal.
Planned and booked absences per team per week, next to the projects and shifts that have to be covered. The ops lead sees the August gap in May, and the Monday planning call runs on real numbers rather than on who remembered to ping the group chat.
Each period, absence codes booked in SD Worx land in Business Central as the right journal entries, split across guaranteed salary during illness, paid leave and training time per department. Finance stops rekeying a monthly HR export into the ledger, and the personnel-cost line already ties back to the absence code that produced it.
Booked holidays, sick days and training time per employee flow into Teamleader Focus as unavailable hours on the planner, per project and per week. Account managers see real team capacity before they commit to a delivery date, instead of reading the leave calendar in a separate tab and doing the math in their head.
Approved leave and booked training time per developer arrive in Jira as reduced sprint capacity on the matching team board, per sprint and per assignee. Scrum masters plan the next two sprints on the hours that are really available rather than on a default 40-hour velocity the team rarely hits in July.
Planned holidays and training days of the deal owner and the assigned delivery team land on the HubSpot company record as a capacity signal, visible next to the open pipeline. Sales directors see which reps will be out when the kickoff is scheduled, so handover and delivery dates stop slipping into the first week back.
These are the 2 tables we currently pull from SD Worx Absences into your warehouse. Query them directly in SQL, join them to the rest of your stack, or build reports on top.
Missing a table you need? We can extend the sync. Tell us what is missing and we will build it for you.
You keep the reporting tool you already have. We connect it to the warehouse where your SD Worx Absences data lives.
OAuth authentication. Read-only by default. We sign a DPA and your admin keeps the keys.
Data flows into your warehouse on your schedule. Near real time or nightly, your call. You own the data.
We build the first dashboard, workflow or AI feature with you, then hand over the keys. Or we stay on for ongoing delivery.
We set up the foundation. Your team builds on top.
Best fit Teams that already have a BI analyst or data engineer and want to own the build.
We build the whole thing, end to end.
Best fit Teams without in-house BI or dev capacity. You tell us what you need and we deliver it.
You do. It lands in your warehouse, on your cloud account. We don't resell or aggregate it. If you stop working with us, the warehouse stays yours and keeps running.
Near real time for most operational systems. For heavier sources we schedule hourly or nightly. You pick based on what the reports need.
No. If you don't have one, we help you pick one and set it up as part of the first delivery. Common starting points are Snowflake, Microsoft Fabric, or a small Postgres start.
Two tables: the employee register and the absence codes booked against each employee. That covers who works for you, in which department, and every absence posted against them with its code, start and end. It does not cover payroll lines, contract detail, benefits, timesheet micro-entries or the wider HCM and workforce-management surface SD Worx offers. For absence-pattern reporting and capacity planning that slice is the right one; for full HRIS replication it is not.
The connector brings absence codes and date ranges into your warehouse, not the underlying medical notes or physician statements, because SD Worx does not expose those through the integration. Even so, the data is personal and covered by GDPR, so we set role-based access on the HR tables, keep department-manager dashboards aggregated to team level where possible, and work with your DPO on the lawful-basis mapping. This is not data we treat like invoice lines.
SD Worx runs several product lines against the same payroll engine. This connector is the absence slice of that platform; Cobra and the wider HCM products surface other pieces, like contract and payroll data. If your team also runs on Cobra or on another SD Worx module, the two connectors can be stitched together in the warehouse on employee identifier, so the absence view joins to payroll and headcount without double-entry.
We review your SD Worx Absences setup and the systems around it. Together we pick the first thing worth building.