Skip to main content
Mercans Logo
SUBMIT RFP CONTACT US
HR & Payroll, in sync

HiBob + Mercans.
Better together.

Your people live in HiBob. Your payroll runs in 160+ countries. Mercans connects the two — on-demand and two-way, with Bob always the source of truth.

Book a session See how it works ↓
Live connector Bi-directional · On-demand
HiBob
Employee, comp & banking
time-off & hours
Payslips, reports
& payroll actuals
Mercans
  1. 1Bob REST API
  2. 2Parse & map
  3. 3PAC validation
  4. 4In-country payroll
  • HiBob Integration Partner
  • Pre-built Connector
  • Bi-directional
  • On-demand
  • Built & run by Mercans
  • HR Blizz engine
Overview

HR in Bob. Payroll everywhere.
One connection.

An on-demand, two-way connection between HiBob and the Mercans payroll engine — built and run by Mercans, live across 160+ countries. HiBob stays your HR system of record; Mercans does the payroll. No middleware broker sits in your data path.

What you get

  • On-demand pulls

    Trigger a full, current pull from Bob whenever a cycle runs: on your cut-off, on a schedule, or on request. Nobody re-keys anything.

  • No manual uploads

    The HR-to-payroll handover is automated end to end, from onboarding through to payment.

  • Built-in validation

    Every record is checked before pay runs; errors and anomalies are surfaced and resolved, not discovered after payday.

  • Global compliance

    Mercans' in-country engine keeps every payroll aligned with local tax and labour rules across 160+ countries.

  • One connector, no broker

    A single Mercans-built and maintained integration; no licensed middleware or third-party broker in your data path.

  • Expertise behind it

    20+ years of payroll delivery and on-the-ground teams supporting the connector through implementation and BAU.

How it works

From a change in Bob to a paid employee — end to end.

  1. 01
    HiBob

    HiBob stays the system of record — HR, org, time off. Changes made in Bob always win.

  2. 02
    Bob REST API

    Mercans pulls the data through Bob's REST API (people + absence), on-demand, on the schedule you set.

  3. 03
    HR Blizz

    HR Blizz parses and transforms the data, mapping every field.

  4. 04
    PAC

    PAC validates each record, detecting and resolving errors before pay runs.

  5. 05
    Payroll

    Payroll runs in-country, gross-to-net, across 160+ countries.

  6. 06
    Back to HiBob

    Payslips, statutory reports and payroll actuals flow back into Bob.

Two-way by design. Out of Bob: master data, compensation, banking, time-off and evaluated-hours data. Back to Bob: payslips, statutory reports and payroll actuals (plus GL and bank files out). There's no second source to reconcile — changes in Bob are always authoritative.

Download the data-flow diagramSVG file
The technical detail
Integration type
Pre-built, bi-directional connector (HiBob ↔ Mercans HR Blizz) — built and run by Mercans, no middleware or broker in the path
Connection
HiBob (Bob) REST API via a dedicated service user
Sync
On-demand — pull on your cut-off, on a schedule, or on request (not real-time)
HiBob → HR Blizz
Employee / master data, compensation, banking, time-off, evaluated hours
HR Blizz → HiBob
Payslips, statutory reports, payroll actuals (GL & bank files out)
Processing
HR Blizz parse / transform → PAC validation & error resolution → in-country payroll (gross-to-net)
Source of truth
HiBob — changes in Bob always win
Coverage
160+ countries on one connector
Security
ISO 27001 · SOC 1 & 2 · ISO 27017 / 27018 · GDPR with Binding Corporate Rules
Status
HiBob Integration Partner · Pre-built connector · Bi-directional · On-demand
Getting started

How you get connected.

Because the connector is pre-built and Mercans-run, there's no custom development and no broker to license.

  1. 01
    Phase 1 · Consult

    Talk to a Mercans expert about your Bob tenant and the countries you run.

  2. 02
    Phase 2 · Connect

    We connect via a dedicated service user on Bob's REST API, then map and transform your fields.

  3. 03
    Phase 3 · Validate

    We validate in parallel — every record checked before anything touches live pay.

  4. 04
    Phase 4 · Launch

    Go live on-demand with one owner end to end — Mercans builds, runs and maintains the connector.

FAQ

Frequently asked questions

How does it connect to my Bob tenant?

Through Bob's REST API, using a dedicated service user.

How often does it sync?

On-demand. Mercans pulls on whatever schedule you set — your cut-off, a schedule, or on request. It is not a real-time feed.

What data flows, and which way?

Out of Bob: employee / master data, compensation, banking, time-off and evaluated hours. Back to Bob: payslips, statutory reports and payroll actuals.

Which system is the source of truth?

HiBob. Changes made in Bob always win — there's no second source to reconcile.

How are errors handled?

Every record is validated before pay runs; errors and anomalies are surfaced and resolved, not discovered after payday.

Is there middleware or a broker in the path?

No. It's a single Mercans-built and maintained connector — no licensed middleware or third-party broker touches your data.

How many countries does it cover?

160+, on one connector.

Is it secure and compliant?

ISO- and SOC-certified, GDPR-aligned with Binding Corporate Rules, encrypted, and built on payroll-relevant data only.

How long does it take to implement?

The connector is pre-built — there's no custom development to begin. Full payroll go-live timing depends on scope and number of countries; a large multi-country rollout typically runs a few months.

Resources
PDF HiBob × Mercans integration datasheetPDF document SVG Data-flow diagramSVG image
40M+Payslips a year
160Countries
0Security breaches
97%Client retention
Book a session