Data Panda brings your SD Worx Cobra 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.
Cobra is the all-in-one HRM and payroll platform SD Worx sells in the Netherlands. SD Worx itself is a Belgian payroll group founded in Antwerp in 1945, and Cobra is the Dutch-market product it built up around its 2020 acquisition of Pointlogic HR. The integrated suite holds the personnel file, the leave and verzuim registration, declaraties, and the salary engine that produces the loonstrook in one product. Dutch CAO rules, fiscal logic and social-security reporting are wired in, which is why mid-market and enterprise employers in the Netherlands run their payroll on it month after month.
The SD Worx Cobra connector pulls the payroll-output side of that platform into your warehouse. Think employee and contract master data, the pay-run results per period, the wage components that build up the gross (base salary, thirteenth-month accrual, bonus, auto-kost, pension premiums), employer and employee contributions, and the cost-centre and department allocation each line is booked against. It is the data your finance team uses to reconcile personnel cost against budget, not the HR-admin surface. Its sister connector, SD Worx Absences, covers the verlof and ziekteverzuim codes themselves; Cobra covers what those absences and the rest of the contract end up costing on the loonstrook.
Gross payroll, employer premiums and wage-component mix on one page, per department and cost centre instead of per HR export.
Turn pay-run output into the journal entries, project cost lines and billing rates the rest of the stack needs.
Use pay-run history to forecast personnel cost, catch wage-component drift and score contract decisions before they land in budget.
Small finance and HR tools that sit on SD Worx Cobra pay-run data instead of a month-end PDF.
A list of concrete reports, automations and AI features we have built on SD Worx Cobra data. Pick the one that matches your situation.
Where did personnel cost drift this quarter?
Pay-run totals split per wage component and per department, with the last six periods lined up against budget. Finance and HR see whether the quarter grew on base salary, on bonus accrual, on leasewagen load, or on employer premiums, and can bring the answer to the management committee instead of a single number that went up.
Does the hourly rate we use for project billing still match what an employee costs?
Fully-loaded cost per employee computed from the Cobra pay-run, joined to the project tooling where hours get booked. If the rate card is six months behind the last CAO increase or a new bonus scheme, it shows up here rather than at year-end when the margin conversation is already lost.
Is the payroll journal reconciling cleanly to the ledger?
Every pay-run line with its wage component, cost centre and GL account, stacked against the posted journal in Business Central or Exact. The finance controller sees the variance per cost centre during the close rather than hunting mismatches the week after, and the audit trail from loonstrook to grootboek runs on the same data.
Personnel cost broken out per wage component, department and cost centre on the same page as the rest of the P&L. The monthly close stops running on an HR PDF and a stack of reclasses, and bonus and 13e-maand accruals are already lined up when the controller opens the books.
Loaded hourly cost per delivery-team member in the CRM next to the open pipeline. Sales directors see whether the rate card still covers actual payroll cost before a proposal goes out, so project margin is decided up front rather than explained at year-end.
Pay-run cost per project and per team joined to the hours booked in project tooling, so the ops lead sees which projects run below plan and which managers carry loaded cost that no longer fits the quote.
Each period, the Cobra pay-run lands in Exact Online as the right journal entries, split per wage component, cost centre and GL account. Finance stops rekeying an HR export into the ledger, the personnel-cost line ties back to the loonstrook that produced it, and month-end reconciliation runs in the same tool the controller already uses.
Cobra pay-run totals per cost centre and wage component land in Business Central alongside the posted journal, so the controller can see variance against budget during the close instead of the week after. Employer premiums, 13e maand accrual and leasewagen cost each sit on the right GL account without a manual reclass.
Fully-loaded cost per employee from the Cobra pay-run flows into Teamleader Focus as the internal hour rate behind each project and each profile. Account managers quote against a rate card that still reflects the last cao increase and the current bonus scheme, and project margin is decided when the proposal is written rather than at year-end.
Each pay-run period, loaded cost per team member and per cost centre lands in Asana next to the project portfolio, so project leads see budget burn on the hours booked rather than on a default rate. When a cao increase or a new bonus scheme lands, the portfolio view catches up the same period instead of the year-end review.
You keep the reporting tool you already have. We connect it to the warehouse where your SD Worx Cobra 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.
The payroll-output side of the Cobra suite: employee and contract master data, the pay-run results per period, the wage components that build up gross, employer and employee contributions, and the cost-centre and department allocation each line is booked against. Things like timesheet micro-entries, document-workflow state, recruitment pipelines and the employee self-service surface are not in scope for this connector. For personnel-cost reporting and journal reconciliation that slice is the right one; for full HCM replication it is not.
Absences is the verlof- and verzuim-code slice of the SD Worx stack: who is off, with which code, when. Cobra is what the contract and those absences produce on the pay-run: base salary, 13e maand accrual, bonus, auto-kost, employer premiums, per cost centre. The two connectors share the same employee identifier, so in the warehouse they join without double-entry: the absence view lines up against the payroll cost it drives.
Individual salary data is personal and covered by GDPR, so we set role-based access on the payroll tables, keep most dashboards aggregated at cost-centre or department level, and work with your DPO on the lawful-basis mapping. Finance controllers who need the per-employee breakdown for reconciliation get it; managers viewing team cost typically see aggregates.
We review your SD Worx Cobra setup and the systems around it. Together we pick the first thing worth building.