Real-time
Two-way sync
Changes in Ceridian Dayforce or Sage 100 instantly reflect in both systems. No stale data, no manual imports.
Human resources ⇄ ERP
Ceridian Dayforce to Sage 100 integration — real-time, two-way sync
Keep Ceridian Dayforce and Sage 100 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 Sage 100
Sync the workers, org structure, and cost centers that Sage 100 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. Sage 100 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 Vendors, Inventory Items, Sales Orders, AR Invoices in Sage 100 with Employment Status, Work Assignments, Compensation Summary & Pay Adjustments, Employee Punches & Raw Clock Entries 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 Sage 100 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 customers, invoices, and payment status into a CRM so sales sees AR standing without opening the ERP.
- 02 Push e-commerce and EDI orders into the Sales Order module instead of rekeying them.
- 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
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 Sage 100 is created, updated, or deactivated, so the business system reflects the workforce as it actually is.
New hires ready to transact in Sage 100
A new person set up in Ceridian Dayforce becomes an employee record in Sage 100 in time to submit expenses, enter time, or approve a purchase, without waiting on manual setup.
One org structure
Departments, cost centers, and locations that both systems reference stay in agreement, so labor cost, approvals, and reporting in Sage 100 roll up to the same structure Ceridian Dayforce maintains.
What you can sync between Ceridian Dayforce and Sage 100
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 | Sage 100 objects | How this pairing syncs | |
|---|---|---|---|
| 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. | GL Accounts Chart of accounts read for mapping transactions in finance integrations. | Employee Punches & Raw Clock Entries is specific to Ceridian Dayforce and GL Accounts to Sage 100 — 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. | Journal Entries Posted GL activity replicated to warehouses for FP&A. | Employee Schedules is specific to Ceridian Dayforce and Journal Entries to Sage 100 — 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 AR customer master records synced to CRMs for account and credit visibility. | Org Units, Departments, Jobs & Positions is specific to Ceridian Dayforce and Customers to Sage 100 — 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. | Vendors AP vendor master records synced with procurement and payment tools. | Time Away From Work & Balances is specific to Ceridian Dayforce and Vendors to Sage 100 — 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. | Inventory Items Item master with pricing and quantities, synced to e-commerce catalogs. | Employee (HR / Person Details) is specific to Ceridian Dayforce and Inventory Items to Sage 100 — 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 Order headers and lines, the usual write target for web and EDI orders. | Employment Status is specific to Ceridian Dayforce and Sales Orders to Sage 100 — each maps to any object or custom field on the other side. |
How changes propagate between Ceridian Dayforce and Sage 100
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 Sage 100 Sub-second propagation
DetectionCeridian Dayforce notifies Stacksync of record changes through webhook events. No CDC stream.
DeliveryEach detected change is applied to Sage 100 as a row-level write, with types converted between the two schemas.
Sage 100 Ceridian Dayforce Interval-based propagation
DetectionStacksync polls Sage 100 for changes on an incremental schedule, reading only records changed since the previous pass. Scheduled 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.
What ships with Ceridian Dayforce ⇄ Sage 100
Connect Ceridian Dayforce and Sage 100 for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Ceridian Dayforce–Sage 100 connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Ceridian Dayforce or Sage 100 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 Sage 100 record.
Observability
Monitoring
Track your Ceridian Dayforce ⇄ Sage 100 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 Sage 100.
How the Ceridian Dayforce and Sage 100 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.
Sage 100
- Integration surface
- ODBC (ProvideX driver) for reads; Business Object Interface (BOI) or Sage-provided web services for writes
- Authentication
- Sage 100 company and user credentials; ODBC DSN credentials for direct reads
- Change detection
- Scheduled polling; no webhooks or change log on the integration surface
- Capabilities
- read · write
How it works
How to connect Ceridian Dayforce to Sage 100 — 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 Sage 100 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
Sage 100
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Ceridian Dayforce and Sage 100 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 ⇄ Sage 100Customers 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 Sage 100Company company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Ceridian Dayforce and Sage 100 integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Ceridian Dayforce and Sage 100: authenticate both systems, choose the objects to sync (such as Ceridian Dayforce's Employee Punches & Raw Clock Entries and Employee Schedules), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
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 Sage 100 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 Sage 100 connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Ceridian Dayforce–Sage 100 integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Ceridian Dayforce and Sage 100. 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 Sage 100: Scheduled polling; no webhooks or change log on the integration surface. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Sage 100 side: Vendors, Inventory Items, Sales Orders, AR Invoices, plus custom fields where Sage 100 exposes them. On the Ceridian Dayforce side: Employment Status, Work Assignments, Compensation Summary & Pay Adjustments, Employee Punches & Raw Clock Entries. Stacksync auto-detects both schemas and converts types between the two systems.
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 507 integrations available for Ceridian Dayforce and Sage 100.
Popular · 7 of 507
-
Ceridian Dayforce ⇄ Fishbowl Manufacturing -
Ceridian Dayforce ⇄ Infor CloudSuite - Ceridian Dayforce ⇄ Infor LN
-
Sage 100 ⇄ Greenhouse -
Sage 100 ⇄ Jobvite -
Sage 100 ⇄ Lever -
Sage 100 ⇄ Namely
No integrations match .
