Real-time
Two-way sync
Changes in Ceridian Dayforce or Epicor ERP instantly reflect in both systems. No stale data, no manual imports.
Human resources ⇄ ERP
Ceridian Dayforce to Epicor ERP integration — real-time, two-way sync
Keep Ceridian Dayforce and Epicor 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.
- 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 Epicor ERP
Sync the workers, org structure, and cost centers that Epicor ERP 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. Epicor 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 Bills of materials, Customers, Suppliers, Parts in Epicor ERP with Employee (HR / Person Details), Employment Status, Work Assignments, Compensation Summary & Pay Adjustments 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 Epicor 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.
Common use cases
- 01 Sync shipment confirmations out to commerce platforms and customer portals as jobs complete.
- 02 Sync Epicor customers and AR invoices into a CRM so sales sees order history and credit status without ERP logins.
- 03 React to Dayforce Event Notifications for hire, rehire, and terminate to provision or disable IdP and app access and update downstream records as the changes post.
- 04 Replicate Compensation Summary and pay data into a warehouse for headcount, labor-cost, and compensation reporting without manual BI exports.
Common sync patterns
Reporting lines drive approvals
Manager and reporting-hierarchy changes in Ceridian Dayforce keep expense and purchase approval chains in Epicor ERP pointed at the right people.
Where Ceridian Dayforce runs payroll: labor cost in the books
Pay and compensation data from Ceridian Dayforce posts into Epicor ERP as labor cost, so finance sees workforce spend without re-entering it by hand.
Where Ceridian Dayforce is the worker system of record: one employee master
When a worker is hired, moved, or offboarded in Ceridian Dayforce, the matching employee record in Epicor ERP is created, updated, or deactivated, so the business system reflects the workforce as it actually is.
What you can sync between Ceridian Dayforce and Epicor ERP
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 | Epicor ERP objects | How this pairing syncs | |
|---|---|---|---|
| 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. | Parts Item masters that anchor inventory, BOM, and order line syncs. | Employee (HR / Person Details) is specific to Ceridian Dayforce and Parts to Epicor ERP — each maps to any object or custom field on the other side. | |
| Employment Status Effective-dated employment status and type (active, leave, terminated) that drives active/terminated state for downstream provisioning; read, and writable as new dated status records. | Sales orders Created from won CRM opportunities; status and line changes sync back out. | Employment Status is specific to Ceridian Dayforce and Sales orders to Epicor ERP — each maps to any object or custom field on the other side. | |
| Work Assignments Effective-dated position, department, location, and org-unit assignment; the most-synced record for org charts, provisioning, and analytics. Read and updatable via PATCH. | Purchase orders Synced with procurement systems and matched against receipts. | Work Assignments is specific to Ceridian Dayforce and Purchase orders to Epicor ERP — each maps to any object or custom field on the other side. | |
| 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. | Jobs Production jobs whose status feeds shop-floor dashboards and delivery-date updates. | Compensation Summary & Pay Adjustments is specific to Ceridian Dayforce and Jobs to Epicor 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. | Quotes Estimates that pair with CRM opportunities during the sales cycle. | Employee Punches & Raw Clock Entries is specific to Ceridian Dayforce and Quotes to Epicor 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. | AR invoices Billing records surfaced in CRM or finance tools for collections visibility. | Employee Schedules is specific to Ceridian Dayforce and AR invoices to Epicor ERP — each maps to any object or custom field on the other side. |
How changes propagate between Ceridian Dayforce and Epicor ERP
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 Epicor ERP Sub-second propagation
DetectionCeridian Dayforce notifies Stacksync of record changes through webhook events. No CDC stream.
DeliveryEach detected change is written to Epicor ERP through its API, with automatic retries and rate-limit backoff.
Epicor ERP Ceridian Dayforce Interval-based propagation
DetectionStacksync polls Epicor ERP for changes on an incremental schedule, reading only records changed since the previous pass. Polling on change-date fields.
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.
- Epicor ERP: Subject to the platform's API rate limits and per-tenant throttling on Kinetic cloud deployments.
What ships with Ceridian Dayforce ⇄ Epicor ERP
Connect Ceridian Dayforce and Epicor ERP for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Ceridian Dayforce–Epicor ERP connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Ceridian Dayforce or Epicor ERP 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 Epicor ERP record.
Observability
Monitoring
Track your Ceridian Dayforce ⇄ Epicor ERP 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 Epicor ERP.
How the Ceridian Dayforce and Epicor ERP 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.
Epicor ERP
- Integration surface
- REST API (OData) over Epicor business objects, plus BAQ (Business Activity Query) endpoints
- Authentication
- API key combined with basic or token authentication, depending on version and deployment
- Change detection
- Polling on change-date fields; outbound calls can be wired through BPM directives, but there is no standard webhook subscription surface
- Capabilities
- read · write
- Rate limits
- Subject to the platform's API rate limits and per-tenant throttling on Kinetic cloud deployments
How it works
How to connect Ceridian Dayforce to Epicor ERP — 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.
- 01
Connect your apps
Authenticate Ceridian Dayforce and Epicor ERP with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Ceridian Dayforce
connected
Epicor ERP
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Ceridian Dayforce and Epicor 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.
objects · Ceridian Dayforce ⇄ Epicor ERPCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Ceridian Dayforce Epicor ERPCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Ceridian Dayforce and Epicor ERP integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Ceridian Dayforce and Epicor ERP: authenticate both systems, choose the objects to sync (such as Ceridian Dayforce's Employee (HR / Person Details) and Employment Status), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes — Stacksync ships production-grade connectors for both Ceridian Dayforce and Epicor ERP. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Ceridian Dayforce: 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. On Epicor ERP: Polling on change-date fields; outbound calls can be wired through BPM directives, but there is no standard webhook subscription surface. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Epicor ERP side: Bills of materials, Customers, Suppliers, Parts, plus custom fields where Epicor ERP exposes them. On the Ceridian Dayforce side: Employee (HR / Person Details), Employment Status, Work Assignments, Compensation Summary & Pay Adjustments. 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 Epicor 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 Epicor ERP pointed at the right people.
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 510 integrations available for Ceridian Dayforce and Epicor ERP.
Popular · 7 of 510
-
Ceridian Dayforce ⇄ TikTok Shop -
Ceridian Dayforce ⇄ Unleashed Software -
Ceridian Dayforce ⇄ NetSuite -
Epicor ERP ⇄ Paylocity -
Epicor ERP ⇄ Ukg Ready -
Epicor ERP ⇄ BambooHR -
Epicor ERP ⇄ Success Factors
No integrations match .
