Two-way sync
Changes in Ceridian Dayforce or Plex ERP instantly reflect in both systems. No stale data, no manual imports.
Keep Ceridian Dayforce and Plex ERP in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
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. Plex ERP 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 Purchase orders, Customers, Suppliers, Shipments in Plex ERP 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 Plex ERP 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.
Manager and reporting-hierarchy changes in Ceridian Dayforce keep expense and purchase approval chains in Plex ERP pointed at the right people.
Pay and compensation data from Ceridian Dayforce posts into Plex ERP as labor cost, so finance sees workforce spend without re-entering it by hand.
When a worker is hired, moved, or offboarded in Ceridian Dayforce, the matching employee record in Plex ERP is created, updated, or deactivated, so the business system reflects the workforce as it actually is.
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 | Plex ERP 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. | Production jobs Shop-floor work records combining ERP and MES data for output reporting | Compensation Summary & Pay Adjustments is specific to Ceridian Dayforce and Production jobs to Plex ERP — 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. | Sales orders Demand records written in from e-commerce or EDI channels and read out for fulfillment status | Employee Punches & Raw Clock Entries is specific to Ceridian Dayforce and Sales orders to Plex ERP — 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. | Purchase orders Procurement records mirrored to accounting and planning systems | Employee Schedules is specific to Ceridian Dayforce and Purchase orders to Plex ERP — 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. | Customers Account records kept consistent with the sales team's CRM | Org Units, Departments, Jobs & Positions is specific to Ceridian Dayforce and Customers to Plex ERP — 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. | Suppliers Vendor records aligned with procurement and AP tools | Time Away From Work & Balances is specific to Ceridian Dayforce and Suppliers to Plex ERP — 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. | Shipments Outbound logistics records synced to trading partners and tracking systems | Employee (HR / Person Details) is specific to Ceridian Dayforce and Shipments to Plex ERP — each maps to any object or custom field on the other side. |
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.
DetectionCeridian Dayforce notifies Stacksync of record changes through webhook events. No CDC stream.
DeliveryEach detected change is written to Plex ERP through its API, with automatic retries and rate-limit backoff.
DetectionStacksync polls Plex ERP 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.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Ceridian Dayforce–Plex ERP connection.
Changes in Ceridian Dayforce or Plex ERP instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Ceridian Dayforce or Plex ERP data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Ceridian Dayforce or Plex ERP record.
Track your Ceridian Dayforce ⇄ Plex ERP sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Ceridian Dayforce and Plex ERP.
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.
Authenticate Ceridian Dayforce and Plex ERP with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Ceridian Dayforce and Plex ERP 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Ceridian Dayforce and Plex ERP: authenticate both systems, choose the objects to sync (such as Ceridian Dayforce's Compensation Summary & Pay Adjustments and Employee Punches & Raw Clock Entries), map fields visually, and changes propagate both ways in milliseconds — no code required.
On the Plex ERP side: Purchase orders, Customers, Suppliers, Shipments, plus custom fields where Plex ERP exposes them. On the Ceridian Dayforce side: Time Away From Work & Balances, Employee (HR / Person Details), Employment Status, Work Assignments. Stacksync auto-detects both schemas and converts types between the two systems.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
Common patterns for Ceridian Dayforce and Plex ERP: Reporting lines drive approvals; Where Ceridian Dayforce runs payroll: labor cost in the books; Where Ceridian Dayforce is the worker system of record: one employee master. Manager and reporting-hierarchy changes in Ceridian Dayforce keep expense and purchase approval chains in Plex ERP pointed at the right people.
Ceridian Dayforce: 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. Plex ERP: REST APIs plus legacy SOAP web services. Authentication: API keys issued through the Plex Developer Portal. Stacksync manages authentication, retries, and rate limits on both sides.
Plex ERP: Plex is vendor-hosted multi-tenant SaaS, so integrations target its APIs rather than a customer-managed database. Ceridian Dayforce: Delta sync uses filterUpdatedStartDate and filterUpdatedEndDate plus filterUpdatedEntities (EmploymentStatuses, WorkAssignments, and others) to pull only records changed within a window. Stacksync's field mapping accounts for these differences between Ceridian Dayforce and Plex ERP without custom code.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 505 integrations available for Ceridian Dayforce and Plex ERP.