Real-time
Two-way sync
Changes in Ceridian Dayforce or Dynamics 365 Business Central instantly reflect in both systems. No stale data, no manual imports.
Human resources ⇄ ERP
Ceridian Dayforce to Dynamics 365 Business Central integration — real-time, two-way sync
Keep Ceridian Dayforce and Dynamics 365 Business Central 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
Live sync
stacksync.com - <1s
- latency
- 2-way
- sync
- 100M+
- records
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 Dynamics 365 Business Central
Sync the workers, org structure, and cost centers that Dynamics 365 Business Central 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. Dynamics 365 Business Central 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 Items, Sales Orders, Sales Invoices, Purchase Orders in Dynamics 365 Business Central 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 Dynamics 365 Business Central 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 Create sales orders in Business Central automatically from e-commerce or CRM order records, and sync fulfillment status back.
- 02 Mirror items and inventory levels into external channels so stock data stays current outside the ERP.
- 03 Replicate Compensation Summary and pay data into a warehouse for headcount, labor-cost, and compensation reporting without manual BI exports.
- 04 Sync time data by posting raw clock entries from a third-party scheduling tool into Dayforce, or pulling Employee Punches and Schedules into a workforce-analytics database.
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 Dynamics 365 Business Central 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 Dynamics 365 Business Central pointed at the right people.
Where Ceridian Dayforce runs payroll: labor cost in the books
Pay and compensation data from Ceridian Dayforce posts into Dynamics 365 Business Central as labor cost, so finance sees workforce spend without re-entering it by hand.
What you can sync between Ceridian Dayforce and Dynamics 365 Business Central
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 | Dynamics 365 Business Central objects | How this pairing syncs | |
|---|---|---|---|
| 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. | Sales Orders Order headers and lines created from external channels and read back for fulfillment status. | Org Units, Departments, Jobs & Positions is specific to Ceridian Dayforce and Sales Orders to Dynamics 365 Business Central — 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. | Sales Invoices Billing documents synced to CRMs and payment platforms. | Time Away From Work & Balances is specific to Ceridian Dayforce and Sales Invoices to Dynamics 365 Business Central — 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. | Purchase Orders Procurement documents exchanged with supplier-facing systems. | Employee (HR / Person Details) is specific to Ceridian Dayforce and Purchase Orders to Dynamics 365 Business Central — 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. | General Ledger Entries Posted financial transactions read for reporting; posted entries are immutable. | Employment Status is specific to Ceridian Dayforce and General Ledger Entries to Dynamics 365 Business Central — 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. | Journals Staging records for financial postings created by integrations before posting. | Work Assignments is specific to Ceridian Dayforce and Journals to Dynamics 365 Business Central — 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. | Dimensions Analytical tags (department, project) that syncs preserve for reporting integrity. | Compensation Summary & Pay Adjustments is specific to Ceridian Dayforce and Dimensions to Dynamics 365 Business Central — each maps to any object or custom field on the other side. |
How changes propagate between Ceridian Dayforce and Dynamics 365 Business Central
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 Dynamics 365 Business Central Sub-second propagation
DetectionCeridian Dayforce notifies Stacksync of record changes through webhook events. No CDC stream.
DeliveryEach detected change is written to Dynamics 365 Business Central through its API, with automatic retries and rate-limit backoff.
Dynamics 365 Business Central Ceridian Dayforce Sub-second propagation
DetectionDynamics 365 Business Central notifies Stacksync of record changes through webhook events. API webhooks (change notifications on subscribed entities) plus polling on lastModifiedDateTime.
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.
What ships with Ceridian Dayforce ⇄ Dynamics 365 Business Central
Connect Ceridian Dayforce and Dynamics 365 Business Central for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Ceridian Dayforce–Dynamics 365 Business Central connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Ceridian Dayforce or Dynamics 365 Business Central 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 Dynamics 365 Business Central record.
Observability
Monitoring
Track your Ceridian Dayforce ⇄ Dynamics 365 Business Central 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 Dynamics 365 Business Central.
How the Ceridian Dayforce and Dynamics 365 Business Central 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.
Dynamics 365 Business Central
- Integration surface
- REST API built on OData v4 (standard API v2.0), extensible with custom API pages in AL
- Authentication
- OAuth 2.0 via Microsoft Entra ID
- Change detection
- API webhooks (change notifications on subscribed entities) plus polling on lastModifiedDateTime
- Capabilities
- read · write · webhooks
How it works
How to connect Ceridian Dayforce to Dynamics 365 Business Central — 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 Dynamics 365 Business Central 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
Dynamics 365 Business Central
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Ceridian Dayforce and Dynamics 365 Business Central 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 ⇄ Dynamics 365 Business CentralCustomers 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 Dynamics 365 Business CentralCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Ceridian Dayforce and Dynamics 365 Business Central integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Ceridian Dayforce and Dynamics 365 Business Central: authenticate both systems, choose the objects to sync (such as Ceridian Dayforce's Org Units, Departments, Jobs & Positions and Time Away From Work & Balances), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Dynamics 365 Business Central: Writes use ETags with If-Match headers for optimistic concurrency, so stale updates are rejected instead of silently overwriting ERP data. Ceridian Dayforce: Reads are two-step: GET Employees returns only the XRefCodes matching the filter, then a per-employee GET fetches full HR details, so large tenants require many paged requests. Stacksync's field mapping accounts for these differences between Ceridian Dayforce and Dynamics 365 Business Central without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Ceridian Dayforce and Dynamics 365 Business Central records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Ceridian Dayforce and Dynamics 365 Business Central connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Ceridian Dayforce–Dynamics 365 Business Central integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Ceridian Dayforce and Dynamics 365 Business Central. 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 Dynamics 365 Business Central: API webhooks (change notifications on subscribed entities) plus polling on lastModifiedDateTime. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
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 509 integrations available for Ceridian Dayforce and Dynamics 365 Business Central.
Popular · 6 of 509
-
Ceridian Dayforce ⇄ Epicor ERP -
Ceridian Dayforce ⇄ Extensiv (3PL Central) -
Dynamics 365 Business Central ⇄ Paylocity -
Dynamics 365 Business Central ⇄ Ukg Ready -
Dynamics 365 Business Central ⇄ BambooHR -
Dynamics 365 Business Central ⇄ Success Factors
No integrations match .
