Skip to content
Human resources ⇄ ERP

Ceridian Dayforce to Syspro integration — real-time, two-way sync

Keep Ceridian Dayforce and Syspro in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Ceridian Dayforce and Syspro

Sync the workers, org structure, and cost centers that Syspro and Ceridian Dayforce share in real time, so the people Ceridian Dayforce manages stay current in the system that runs finance and operations.

Ceridian Dayforce is the system of record for people: who was hired, which department and location they sit in, who they report to, and how they are paid. Syspro runs finance and operations, and much of what it does depends on that same information, from booking labor cost to approving an expense report to staffing a project. Where the two are bridged by re-keying or an overnight file, each side spends the day out of step, with new hires missing from the systems they need and leavers still active where they should not be.

Stacksync syncs Sales orders, Purchase orders, Jobs (work orders), Bills of materials in Syspro with Time Away From Work & Balances, Employee (HR / Person Details), Employment Status, Work Assignments in Ceridian Dayforce field by field, in real time, and in both directions. You decide which system owns which fields, so the people side stays authoritative for worker data while Syspro keeps its own accounting and operational detail, and every change made in one is reflected in the other within seconds instead of at the next batch run.

Common use cases

  • 01 Keep inventory balances and item masters aligned between SYSPRO and a WMS or storefront
  • 02 Mirror customers and AR invoices into a CRM so sales sees credit and billing status on the account
  • 03 Two-way sync of Employee and Work Assignment data (position, department, location, org unit) into Postgres so provisioning, internal apps, and analytics read current worker and org data in SQL while HR keeps editing in Dayforce.
  • 04 Push new hires (Employee, Employment Status, Work Assignment) from an ATS or onboarding tool into Dayforce with POST once a candidate is hired, pre-fetching valid XRefCodes for department, position, location, and pay group.

Common sync patterns

One org structure

Departments, cost centers, and locations that both systems reference stay in agreement, so labor cost, approvals, and reporting in Syspro roll up to the same structure Ceridian Dayforce maintains.

Reporting lines drive approvals

Manager and reporting-hierarchy changes in Ceridian Dayforce keep expense and purchase approval chains in Syspro pointed at the right people.

Where Ceridian Dayforce runs payroll: labor cost in the books

Pay and compensation data from Ceridian Dayforce posts into Syspro as labor cost, so finance sees workforce spend without re-entering it by hand.

What you can sync between Ceridian Dayforce and Syspro

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Ceridian Dayforce objects Syspro objects How this pairing syncs
Compensation Summary & Pay Adjustments Compensation Summary returns pay rate and frequency for reporting; Employee Pay Adjustments are written as effective-dated records via PATCH to post pay changes back to Dayforce. Suppliers AP supplier records synced with procurement and payment systems. Compensation Summary & Pay Adjustments is specific to Ceridian Dayforce and Suppliers to Syspro — each maps to any object or custom field on the other side.
Employee Punches & Raw Clock Entries Time-and-attendance punches; raw clock entries are added with POST and punches removed with DELETE, so time data flows both ways between Dayforce and scheduling or workforce tools. Inventory items The stock master, kept aligned with WMS and e-commerce catalogs. Employee Punches & Raw Clock Entries is specific to Ceridian Dayforce and Inventory items to Syspro — each maps to any object or custom field on the other side.
Employee Schedules Shift and schedule assignments; created and updated through POST and PATCH schedule endpoints and paged with pageSize, used to push schedules from a WFM tool or pull them for analytics. Sales orders Orders written in from storefronts and CRMs, with status read back out. Employee Schedules is specific to Ceridian Dayforce and Sales orders to Syspro — each maps to any object or custom field on the other side.
Org Units, Departments, Jobs & Positions Configuration reference data; POST creates org units and departments and PATCH updates job, position, department, and org-unit data. Used to resolve and validate XRefCodes when mapping employee writes. Purchase orders Procurement documents synced with supplier portals and receiving. Org Units, Departments, Jobs & Positions is specific to Ceridian Dayforce and Purchase orders to Syspro — each maps to any object or custom field on the other side.
Time Away From Work & Balances Time-off requests and accrual balances read per employee; pulled into scheduling, payroll, or absence-reporting databases and used to reconcile leave against downstream systems. Jobs (work orders) Manufacturing jobs and WIP tracked for production reporting. Time Away From Work & Balances is specific to Ceridian Dayforce and Jobs (work orders) to Syspro — each maps to any object or custom field on the other side.
Employee (HR / Person Details) Core worker record keyed by XRefCode; GET Employees returns matching XRefCodes, then a per-employee GET fetches full HR details. New hires are added with POST and edits made with PATCH, so it is read and write. Bills of materials Product structures referenced when syncing manufacturing data. Employee (HR / Person Details) is specific to Ceridian Dayforce and Bills of materials to Syspro — each maps to any object or custom field on the other side.

How changes propagate between Ceridian Dayforce and Syspro

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Ceridian Dayforce Syspro Sub-second propagation

DetectionCeridian Dayforce notifies Stacksync of record changes through webhook events. No CDC stream.

DeliveryEach detected change is written to Syspro through its API, with automatic retries and rate-limit backoff.

Syspro Ceridian Dayforce Interval-based propagation

DetectionStacksync polls Syspro for changes on an incremental schedule, reading only records changed since the previous pass. Polling.

DeliveryEach detected change is written to Ceridian Dayforce through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Ceridian Dayforce: Dayforce does not publish numeric rate limits; thresholds vary by tenant and exceeding them returns HTTP 429, so large employee reads are paged (pageSize) and throttled with backoff. Employee list calls return XRefCodes only, so each employee needs a follow-up GET.
  • Syspro: Throughput depends on the customer's server sizing; many deployments are on-premise.
What ships with Ceridian Dayforce ⇄ Syspro

Connect Ceridian Dayforce and Syspro for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Ceridian Dayforce–Syspro connection.

Real-time

Two-way sync

Changes in Ceridian Dayforce or Syspro instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Ceridian Dayforce or Syspro data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Ceridian Dayforce or Syspro record.

Observability

Monitoring

Track your Ceridian Dayforce ⇄ Syspro sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Ceridian Dayforce and Syspro.

How the Ceridian Dayforce and Syspro connectors work

Ceridian Dayforce

Integration surface
REST API (Dayforce RESTful Web Services, v1/v2), JSON payloads
Authentication
HTTP Basic authentication with a dedicated Web Services user plus the client namespace (Company ID), or an OAuth 2.0 access token from the Dayforce identity endpoint (POST dfid.dayforcehcm.com/connect/token, client_id Dayforce.HCMAnywhere.Client). Token-based auth is recommended, and the Web Services role with the Read Data subfeature must be enabled on the account.
Change detection
No CDC stream. Broad change detection uses delta polling on GET Employees with filterUpdatedStartDate/filterUpdatedEndDate and filterUpdatedEntities to pull only records changed in a window. Dayforce also has native Event Notifications (the Notification Publisher) for lifecycle events — hire, rehire, terminate, and workflow validation — delivered by push to a receiver service or by querying unacknowledged notifications; the publisher runs roughly hourly and each notification must be acknowledged.
Capabilities
read · write · webhooks
Rate limits
Dayforce does not publish numeric rate limits; thresholds vary by tenant and exceeding them returns HTTP 429, so large employee reads are paged (pageSize) and throttled with backoff. Employee list calls return XRefCodes only, so each employee needs a follow-up GET.
Ceridian Dayforce setup guide

Syspro

Integration surface
e.net Solutions business objects, exposed over REST and WCF interfaces in SYSPRO 8
Authentication
SYSPRO operator credentials exchanged for a session token
Change detection
Polling; the ERP does not expose a change feed to external consumers
Capabilities
read · write
Rate limits
Throughput depends on the customer's server sizing; many deployments are on-premise
How it works

How to connect Ceridian Dayforce to Syspro — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Ceridian Dayforce and Syspro with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Ceridian Dayforce connected
    Syspro connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Ceridian Dayforce and Syspro objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Ceridian Dayforce ⇄ Syspro
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Ceridian Dayforce Syspro
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Ceridian Dayforce and Syspro integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.