Skip to main content
Technology Partner HCM & HRIS
HCM & Payroll, connected

Dayforce + Mercans.
Better together.

Dayforce runs native payroll in its core countries and reaches the rest through in-country partners. Mercans is the single, owned alternative — compliant payroll on our own entities across 160+ countries, with results sent straight back into Dayforce.

Input to payslip Owned, not partnered
Dayforce HCMSource of truth · employee & pay data
To MercansPayroll inputs
Back to DayforcePayslips · statutory reports
Mercans HR Blizz™Validate → in-country gross-to-net
  • Dayforce nativeUS · CA · UK · AU
  • Mercans-owned160+ countries
  • Mercans-owned entities
  • Bi-directional
  • 160+ countries
  • HR Blizz engine
  • Pre-built connector
Overview

Dayforce runs your core payroll. Mercans runs the rest — as one owned operation.

Dayforce processes payroll natively in a core set of countries — the US, Canada, the UK and Australia — and extends to the rest through a network of in-country partners. Across that long tail, partner-delivered payroll can mean variable consistency, compliance and support. Mercans is the single, owned alternative: we run compliant gross-to-net on our own in-country entities across 160+ countries, then send payslips, statutory reports and results back into Dayforce. One owner, one standard, one connected view — no patchwork.

What you get
  • One owned operation, not a patchwork

    Dayforce covers the long tail through in-country partners. Mercans owns its entities and payroll engine in 160+ countries — one consistent, accountable operation.

  • Compliant where it's hardest

    Local statutory calculations, filings and in-country expertise across 160+ countries — the markets where partner-delivered payroll varies most.

  • Results back in Dayforce

    Payslips, statutory reports and payroll results flow back into Dayforce HCM for review, record-keeping and one global view of labour cost.

  • No duplicate data entry

    Payroll inputs pass automatically through the connector — nothing is re-keyed between Dayforce and payroll.

  • Fits Dayforce's model

    Dayforce calculates pay continuously; HR and the employee record stay in Dayforce as the source, while Mercans runs global payroll for the countries Dayforce doesn't run natively.

  • One owner, no middlemen

    Mercans owns the payroll engine and in-country operations end to end — no aggregators between Dayforce and pay.

How it works

Inputs from Dayforce, owned payroll, results back.

How a cycle runs
  1. 01
    Dayforce

    Dayforce HCM sends payroll inputs — employee and pay data — to Mercans through the connector.

  2. 02
    HR Blizz

    Mercans HR Blizz validates the inputs and runs payroll in-country, gross-to-net, on Mercans' own entities across 160+ countries.

  3. 03
    Back to Dayforce

    Payslips, statutory reports and payroll results flow back to Dayforce HCM.

  4. 04
    One view

    HR stays in Dayforce as the source of truth; you get one global view of labour cost and compliance.

What flows each way
Dayforce → Mercans
  • Payroll inputs
  • Employee data
  • Pay data
Mercans → Dayforce
  • Payslips
  • Statutory reports
  • Payroll results / actuals
The technical detail
Integration type
Pre-built, bi-directional connector (Dayforce ↔ Mercans HR Blizz) via Dayforce APIs — Mercans builds, maintains and updates it
Dayforce → Mercans
Payroll inputs — employee and pay data
Mercans → Dayforce
Payslips, statutory reports, payroll results / actuals
Delivery model
Mercans-owned in-country entities — not a third-party partner network
Processing
Validate inputs → in-country payroll (gross-to-net)
Coverage
160+ countries — including the markets Dayforce delivers through partners
Security
ISO 27001 · SOC 1 & 2 · ISO 27017 / 27018 · GDPR with Binding Corporate Rules
Status
Technology Partner · pre-built connector · bi-directional
Getting started

How you get connected.

  1. 01
    Phase 1 · Consult

    Talk to a Mercans expert about your Dayforce setup and the countries you run through partners today.

  2. 02
    Phase 2 · Connect

    We configure the connector and map your payroll inputs from Dayforce.

  3. 03
    Phase 3 · Validate

    We validate in parallel — proven before anything touches live pay.

  4. 04
    Phase 4 · Launch

    Go live, with one owner accountable from Dayforce input to payslip.

FAQ

Frequently asked questions

Does Mercans replace Dayforce payroll?

No. Keep Dayforce where it runs native payroll; Mercans runs the countries Dayforce delivers through partners — all connected back into Dayforce.

How is this different from Dayforce's partner network?

Dayforce covers the long tail of countries through in-country partners. Mercans owns its entities and payroll engine across 160+ countries, so you get one consistent, accountable operation instead of a patchwork of providers.

Does it work with Dayforce's continuous calculation?

Yes. HR and the employee record stay in Dayforce as the source; Mercans is the global payroll engine for the countries Dayforce doesn't run natively.

What data flows to Mercans?

Payroll inputs — employee and pay data — through the connector.

What comes back into Dayforce?

Payslips, statutory reports and payroll results / actuals, for review and record-keeping.

How many countries does it cover?

160+, gross-to-net, on Mercans-owned entities.

How secure is it?

ISO- and SOC-certified, GDPR-aligned with Binding Corporate Rules, encrypted and access-controlled.

Who actually runs my payroll?

Mercans — we own the payroll engine and in-country operations end to end, with no aggregators in the chain.

Resources

Better together, by design.

Bring your expertise to the Mercans ecosystem.

40M+Payslips a year
160Countries
0Security breaches
97%Client retention