Umanga connector

Use your Umanga data for reporting, automation and AI.

Data Panda pulls your Umanga candidates, vacancies, applications and placements into the same warehouse as your finance, marketing and operations data. From one place we turn it into dashboards, automations, AI workflows and apps that recruiters, account managers, payroll and finance read from on the same numbers.

Data Panda Reporting Automation AI Apps
Umanga logo
About Umanga

A Benelux ATS that matches candidates to vacancies the moment either changes.

Umanga is the recruitment platform built by i-Minded, a Leuven software house active since 2003. The product launched in 2020 and has grown into one of the recognised ATS choices in the Benelux and French staffing market, used by names like Randstad, SD Worx Staffing, Flexer and Orange Store, alongside in-house TA teams at large EU employers. The bet is straightforward: candidates and vacancies move all day, so the system should re-match them automatically every time either side changes, instead of waiting for a recruiter to remember.

The data model fits both an agency desk and an in-house TA team. Candidates, vacancies, applications, placements, sources, branches and consultants sit at the centre, with notes, communications and pipeline stages around them. Matching runs on Textkernel Search and Match, sourcing pulls from Indeed, Talent.com, Monsterboard, VDAB, Facebook and Instagram through Umanga Connect, and placements feed straight into the Belgian and Dutch payroll back-offices like Pratoflex, Easyflex and Paydia. Recent releases added Textkernel Jobfeed market intelligence, ChatGPT-assisted screening and commute information per candidate, on top of the older Insocial review and Power BI export hooks.

The point of pulling Umanga into a warehouse is not that the native reporting is short. It is that Umanga knows who applied, who got matched and who got placed, but it does not know what the placement billed against agency margin, which job-board spend produced the candidates that survived the first month on assignment, or how consultant productivity lines up with the branch P and L. Those answers only show up when the candidate, vacancy and placement tables sit next to your invoicing, your job-board ledger and the payroll record of who is still on assignment four weeks later.

What your Umanga data is for

What you get once Umanga is connected.

Recruitment and staffing reporting

Time-to-fill, source quality, consultant productivity and placement margin on one set of numbers, joined to job-board spend and payroll outcomes.

  • Time-to-fill per branch, vacancy family and consultant, with the pipeline stage where candidates drop off
  • Source-of-hire quality: applications, matches, placements and four-week retention per channel, not just application volume
  • Consultant productivity: live vacancies, matches sent, placements made and gross margin per consultant and branch

Process automation

Turn a placement, a stalled vacancy or a fresh match into the right downstream action across payroll, finance and the consultant desk.

  • A confirmed placement in Umanga creates the personnel record in Pratoflex, SD Worx Cobra or BambooHR with start date and cost centre filled in
  • Stalled vacancies and unanswered matches ping the responsible consultant and branch lead in the right channel
  • Job-board posting spend reconciled against the placements and four-week retained assignments it produced

AI workflows

Put candidate history, match scores and placement outcomes behind AI that sees the full recruitment picture.

  • Match scoring on open vacancies against the existing Umanga talent pool, weighted by branch and prior placement outcomes
  • Drop-off-risk scoring on new placements using interview notes, commute distance and source signal
  • Natural-language Q and A across notes, communications and the candidate timeline for consultants and branch leads

Custom apps on your data

Lightweight tools for consultants, branch leads, payroll and finance that sit on Umanga data instead of more SaaS subscriptions.

  • Consultant desk: open vacancies, matches sent, placements made and gross margin in one view per day
  • Branch scorecard with time-to-fill, fill rate, source mix and consultant productivity for the daily branch stand-up
  • Cost-per-placement tracker that mixes Umanga placements with job-board spend, internal consultant time and payroll cost
Use cases

Use cases we deliver with Umanga data.

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

Time-to-fill per vacancyDays from vacancy opened to candidate started, per vacancy family, branch, consultant and source.
Source-of-hire qualityApplications, matches, placements and four-week retained assignments per source, not just sourced volume.
Match-to-placement conversionConversion from auto-match to recruiter-sent shortlist to client interview to placement, per consultant and vacancy family.
Consultant productivityVacancies handled, matches sent, placements made and gross margin per consultant and per branch.
Cost-per-placementTotal cost of a filled vacancy: job-board spend, agency overhead, internal consultant time and onboarding cost, per channel and branch.
Placement margin and bill rateBill rate versus pay rate per placement, joined to client and branch, with margin pressure flagged before the next contract renewal.
Four-week and three-month retentionPlaced candidates still on assignment at week four, week eight and month three, joined back to the source channel and the consultant.
Branch fill rate vs targetOpen vacancies, placements made and budget consumed against the branch target per week and quarter.
Talent pool agingCandidates in the database with no contact in six months, scored against open and likely-to-open vacancies per branch.
Job-board spend ROISpend per board joined to the matches and placements it produced, with the boards that quietly stopped paying back surfaced first.
Client account profitabilityVacancies, placements and gross margin per client, with the accounts where consultant time outweighs margin flagged.
Commute and no-show riskCandidate commute distance and prior no-show signal per match, helping consultants pick the placement most likely to start on day one.
Real business questions

Answers you will finally get.

Which job boards deliver placements that are still on assignment four weeks later?

Applications and placements per Umanga source joined to the payroll record of who is still on the assignment at week four, with spend per board attributed. Job-board budget stops being defended on application volume and starts being defended on placements that survived the first month.

Which consultants are slowing down our time-to-fill, and where in the pipeline does it happen?

Matches sent, time-to-shortlist and time-to-placement per consultant and branch, joined to the pipeline stage where candidates wait longest. Branch leads see whether the slowdown sits on the consultant desk, on a specific client, or on a stage in the process that the team agreed to but never staffed properly.

What does a placement really cost us, once the job-board spend and consultant time are in?

Umanga placements joined to invoiced job-board spend, internal consultant time and onboarding cost per vacancy family and branch. The board sees the branch where direct sourcing runs cheap and the branch where job-board dependency is quietly inflating cost-per-placement, instead of a single agency-wide average.

Value for everyone in the organisation

Where each function gets value.

For finance leaders

Umanga placements reconciled against bill rates, job-board invoices and the payroll register in one view. Cost-per-placement and gross margin stop being a month-end estimate and become a number you read per branch and client in real time.

For sales leaders

Account managers see open vacancies per client, matches sent, placements made and bill-rate trend on one board, instead of refreshing Umanga per client. Margin pressure on a key account is visible the day it appears, not in the next quarterly review.

For operations

Branch leads read time-to-fill, source-of-hire quality and consultant productivity across branches on one set of numbers. Operations sees where the funnel and the branch target stop tracking each other, before the regional director asks.

Ideas

What you can automate with Umanga.

Pair with SD Worx Cobra

Send confirmed Umanga placements into SD Worx Cobra payroll

A confirmed placement in Umanga creates the personnel record in SD Worx Cobra with the gross salary, contract type, start date and cost centre already filled in, so the Belgian payroll team does not re-enter the same details a day later. Onboarding paperwork, social-security registration and first-week salary calculation all run off the same record, and the desk sees in the warehouse which confirmed placements landed on the payroll on the agreed date.

Pair with Indeed

Reconcile Indeed spend against the Umanga placements it produced

Indeed sponsored-job spend lands next to the Umanga applications, matches and placements it sourced, with four-week retention attributed back to each campaign. Marketing and TA stop arguing about whether Indeed is paying back this quarter and start looking at a single picture per branch and vacancy family, including the campaigns that quietly stopped converting.

Pair with Slack

Push the Umanga events that matter into the right Slack channel

Confirmed placements, fresh auto-matches, stalled vacancies and overdue follow-ups land in the right Slack channel: a wins channel for confirmed placements, a desk channel for new matches and a branch-lead ping when a vacancy has not moved a stage in five days. Consultants stop refreshing Umanga to see what is waiting on them, and the branch lead stops chasing follow-ups by email.

Pair with HubSpot

Run a talent-CRM-style nurture in HubSpot on the Umanga candidate pool

Strong candidates that did not get placed, alumni and silver-medal applicants from Umanga feed dedicated HubSpot lists, so the desk can run a careers newsletter and vacancy-specific re-engagement when the next opening appears. The next time a similar role opens, the warm pool gets pinged before a fresh Indeed campaign starts spending, and the warehouse shows which nurtured candidates eventually came back and got placed.

Pair with Teamleader Focus

Keep Umanga clients and Teamleader Focus accounts in step

Active client accounts in Teamleader Focus carry across as branded clients in Umanga, with contact details, account owner and contract terms in step, so the consultant desk works against the same client record finance bills against. Placements made in Umanga roll back into Teamleader as billable assignments per account, so the account manager sees vacancy volume, placements and outstanding invoices on one client view.

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 Umanga data lives.

Power BI logo
Power BI Microsoft
Microsoft Fabric logo
Fabric Microsoft
Snowflake logo
Snowflake Data warehouse
Google BigQuery logo
BigQuery Google
Tableau logo
Tableau Visualisation
Microsoft Excel logo
Excel Sheets & pivots
Three steps

From Umanga to answers in three steps.

01

Connect securely

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

02

Land in your warehouse

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

03

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.

  • Umanga 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 Umanga objects land in the warehouse?

Candidates, vacancies, applications, matches, placements, sources, branches and consultants come across as first-class tables, with notes, communications and pipeline stages around them. That covers the reporting surface a recruitment team needs without writing a custom Umanga API job for every dashboard, and it keeps the link between a placement and the consultant who made it intact in the warehouse.

We push placements from Umanga into Pratoflex, Easyflex or Paydia. Does the warehouse keep that link?

Yes. Where you also feed Pratoflex, Easyflex, Paydia or SD Worx into the warehouse, the same person identifier carries across so a candidate, match, confirmed placement and payrolled assignment stay one row through the journey. That is what lets you answer questions like 'do candidates sourced from Indeed survive the first four weeks better than candidates sourced from VDAB', not just 'how many people did we place last week'.

We run multiple branches and brands on one Umanga tenant. Can the warehouse split that?

Yes. Branch, brand and consultant metadata stay on each record, so reporting can roll up at agency level or split per branch, brand or country without losing the local view. Cost-per-placement and source-of-hire reporting can be calculated in local currency where you record bill rates and job-board spend that way, instead of a single end-of-month rate flattening the picture.

GDPR-compliant
Data stays in the EU
You own the warehouse

A first deliverable live in four to six weeks.

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