Emprova connector

Use your Emprova data for reporting, automation and AI.

Data Panda brings your Emprova clockings, planning and leave data together with the rest of your business. From one place we turn it into dashboards, automations, AI workflows and small apps that operations, HR and finance use during the month.

About Emprova

The Benelux time & attendance suite for shift-driven companies.

Emprova is the workforce management suite from GPS nv, a Genk-based company that has built time registration, personnel planning and access control software for more than thirty years. It bundles three things production, logistics and food companies need in the same place: clock-ins through badge readers, fingerprint scanners or PIN terminals at the entrance, planning that turns shift patterns into a roster, and the self-service portal where employees check their hour balance, request leave or correct a missed clocking. The mobile app handles clockings on site, in the truck or at the customer, and a connection with every Benelux social secretariat carries the cleaned hours into the monthly payroll run.

The Emprova connector pulls that surface into your warehouse: employees and contracts, the raw clockings and the calculated performance, leave and recup balances, the planned roster against the realised one, cost centres and projects the hours are booked to, and the access events that flag who entered which zone. Once it lands next to your ERP, accounting and project tooling, the questions a plant manager keeps asking get a straight answer. Realised hours per shift against the planned roster. Overtime per cost centre against budget. Leave balance per team three months out so the summer planning starts from a number, not a guess. The point is not to replace the Emprova screens HR and the planner use every day. The point is to stop running a separate Excel for every report the rest of the business needs.

What your Emprova data is for

What you get once Emprova is connected.

Workforce and labour-cost reporting

Hours, overtime and leave on one page, per shift and cost centre instead of per Emprova export.

Realised hours per shift, team and cost centre against the planned roster
Overtime, recup and absences per team against the rolling six-month average
Labour cost per cost centre and project lined up with the finance budget

Process automation

Turn Emprova clockings and balances into the work the rest of the stack needs, instead of a planner copy-paste round.

Push approved leave into the project planner as unavailable hours
Post realised labour cost per cost centre to the accounting ledger each period
Flag negative leave balances and uncleared clockings to the team lead before payroll cut-off

AI workflows

Use Emprova history behind AI that sees the full shift, planning and absence picture.

Forecast staffing need per shift across the next four weeks from order intake and seasonality
Score teams and cost centres on absence and overtime risk before the quarter closes
Natural-language Q&A on the roster, leave balances and clocking exceptions

Custom apps on your data

Small operations and HR tools on Emprova data, not another SaaS subscription.

Plant-manager dashboard with shift coverage, overtime and leave for the week
Payroll-prep cockpit listing every clocking exception still open
Project view tying realised hours from Emprova to project margin in the ERP

Use cases

Use cases we deliver with Emprova data.

A list of concrete reports, automations and AI features we have built on Emprova data. Pick the one that matches your situation.

Realised vs planned hoursClocked hours per shift, team and cost centre against the planned roster, per day and per week.

Overtime per cost centreOvertime and recup hours per team and cost centre, trended against the six-month average.

Leave balances three months outLeave, recup and seniority balance per employee and team, projected three months ahead for summer planning.

Absence per teamShort-term illness, leave and unjustified absence per team and shift, with the company average as benchmark.

Clocking exceptionsOpen exceptions: missed clockings, double clockings and unapproved overtime ahead of payroll cut-off.

Hours per projectRealised hours from Emprova booked per project and cost unit, ready to join with project margin.

Shift coverageCoverage rate per shift and team for the next four weeks, after approved leave and known recup.

Access events by zoneWho entered which zone or building when, for the periods compliance or safety needs to reconstruct.

Payroll-prep handoverCleaned performance, overtime, leave and recup shaped for the social-secretariat run.

Mobile vs terminal clockingsShare of clockings via terminal, mobile app and browser, per team and per location.

Labour cost per projectHours times applicable rate per project and cost centre, joined to the ERP project margin.

Roster vs absence collisionsPlanned shifts that collide with already-approved leave, surfaced before the planner publishes.

Real business questions

Answers you will finally get.

Which cost centres are running on overtime this period, and what is it costing us?

Overtime hours from Emprova per team and cost centre, multiplied by the applicable rate, against the same three months last year and against the budget the controller built. The plant manager and finance see the same overtime drift two weeks before period close, instead of opening it as a number on the payroll run, and the conversation about extra capacity or shift redesign happens while the period is still moveable.

Will the summer planning hold once approved leave is taken into account?

Approved leave from Emprova projected per team and shift across June, July and August, against the published roster and the order book. The operations lead sees which week dips below the coverage threshold before the holiday period locks in, and HR can hold a leave request or push the next hire forward instead of running short on the floor in week 30.

Are clocking exceptions cleared before payroll cut-off?

Open exceptions per team and per shift, broken out by type (missed in-clock, missed out-clock, double clocking, unapproved overtime) with the team lead who owns the correction and the days left to payroll. HR stops chasing clean data on the morning of the cut-off, and the social-secretariat run leaves with hours that already line up with the roster.

Value for everyone in the organisation

Where each function gets value.

For finance leaders

Realised labour cost per cost centre and project on the same page as the rest of the P&L. Overtime, recup and shift premiums from Emprova flow into the same view, so the controller stops chasing a separate HR export every period close.

For sales leaders

Coverage and overtime risk of the assigned production team on the deal record, so account managers commit to a delivery week the floor can keep, instead of one that lands in a roster already running on overtime.

For operations

Planned vs realised hours per shift and leave balances per team on the same Monday view. The morning huddle starts on the actual roster and the actual coverage, not on a planning printout that aged over the weekend.

Ideas

What you can automate with Emprova.

Pair with SD Worx Cobra

Reconcile Emprova performance against the SD Worx Cobra payroll run

Cleaned hours, overtime and recup from Emprova line up next to the gross and wage components SD Worx Cobra returned for the same period. HR sees per employee and per cost centre where the payroll run differs from the time system, instead of opening a discussion two weeks later when a worker flags a missing premium. The next cut-off goes out with the variances already cleared.

Pair with Exact Online

Post Emprova labour cost into Exact Online

Each period, realised labour cost from Emprova lands in Exact Online split per cost centre, project and wage component. Finance stops rekeying a time-system export into the ledger, and the labour-cost line ties back to the team and shift that produced it. The month-end close runs on the same numbers production looked at the morning before.

Pair with Odoo

Tie Emprova hours to Odoo project margin

Realised hours per project from Emprova join the Odoo project record next to invoiced revenue and material cost, so the project lead sees actual margin while the project still runs. Hours that drift over the budget surface in week three instead of at handover, and the next quote uses the actual hour pattern rather than the original estimate.

Pair with Power BI

Build the production-floor dashboard in Power BI

A single Power BI page on Emprova data: planned vs realised hours per shift, overtime per cost centre, leave projection for the next four weeks and clocking exceptions still open. The plant manager and HR business partner work from the same view in the Monday meeting, instead of pulling three exports the night before.

Data model

Tables we make available.

These are the 6 tables we currently pull from Emprova into your warehouse. Query them directly in SQL, join them to the rest of your stack, or build reports on top.

Attendance Employees
Attendance Visitors
Employees
Employees Leave Balance
Terminals
Time Registration Bookings

Missing a table you need? We can extend the sync. Tell us what is missing and we will build it for you.

Your existing tools

Your data lands in a warehouse. Your BI tools read from it.

You keep the reporting tool you already have. We connect it to the warehouse where your Emprova data lives.

Power BI Microsoft

Fabric Microsoft

Snowflake Data warehouse

BigQuery Google

Tableau Visualisation

Excel Sheets & pivots

Three steps

From Emprova to answers in three steps.

Connect securely

OAuth authentication. Read-only by default. We sign a DPA and your admin keeps the keys.

Land in your warehouse

Data flows into your warehouse on your schedule. Near real time or nightly, your call. You own the data.

Reporting, automation, AI

We build the first dashboard, workflow or AI feature with you, then hand over the keys. Or we stay on for ongoing delivery.

Two ways to work with us

Pick the track that fits how you work.

Track 01

Self-serve

We set up the foundation. Your team builds on top.

Emprova connector configured and running
Warehouse set up in your cloud account
Clean access for your Power BI, Fabric or Tableau team
Documentation on what's in the data model
Sync monitoring so you're warned before reports break

Best fit Teams that already have a BI analyst or data engineer and want to own the build.

Track 02

Done for you

We build the whole thing, end to end.

Everything in Self-serve
Dashboards built to the questions your team actually asks
Automations between your systems
AI workflows scoped to real tasks your team runs
Custom apps where a dashboard does not cut it
Ongoing delivery at a pace that fits your team

Best fit Teams without in-house BI or dev capacity. You tell us what you need and we deliver it.

Before you book

Frequently asked questions.

Who owns the data?

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.

How fresh is the data?

Near real time for most operational systems. For heavier sources we schedule hourly or nightly. You pick based on what the reports need.

Do I need a warehouse already?

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.

Which Emprova tables land in the warehouse?

The connector pulls employees and contracts, the raw clocking events, the calculated daily and period performance, leave and recup balances and the calendar requests behind them, the planned roster and the realised one, cost centres, projects and cost units the hours are booked to, and the access-control events tied to badge readers and zones. That covers the time-and-attendance, planning and access surface most production, logistics and food companies need without a custom Emprova-API job.

How does this relate to the social secretariat (SD Worx, Acerta, Securex, Partena)?

Emprova is the time, planning and access layer that feeds your social secretariat each month: the clockings, calculated hours, overtime and leave sit in Emprova, the loonrun itself runs at the secretariat. The Emprova connector covers what you can see and act on in Emprova. If you also want the loonrun output (gross, employer premiums, wage components per cost centre) in the same warehouse, the SD Worx Cobra or SD Worx Absences connectors join on the employee identifier.

Clocking and access data is sensitive. How is that handled in a warehouse?

Per-employee clockings, leave reasons and access events are personal data and covered by GDPR, so we set role-based access on the workforce tables, keep team-manager dashboards aggregated where possible, and work with your DPO on the lawful-basis mapping for monitoring scenarios. Access-control events tied to safety zones can be kept in a restricted schema only the responsible roles reach. This is not data we treat like invoice lines.

GDPR-compliant

Data stays in the EU

You own the warehouse

A first deliverable live in four to six weeks.

We review your Emprova setup and the systems around it. Together we pick the first thing worth building.

Book a call See our other connectors