Real-time
Two-way sync
Changes in Ceridian Dayforce or Pigment instantly reflect in both systems. No stale data, no manual imports.
Human resources ⇄ Accounting and finance
Ceridian Dayforce to Pigment integration — real-time, two-way sync
Keep Ceridian Dayforce and Pigment 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 Pigment
Keep the employee, department, and cost records that Pigment and Ceridian Dayforce share consistent in real time, so the finance system and the people system stop drifting apart.
Pigment runs the money side of the company: who gets paid, what it costs, and which part of the business the cost belongs to. Ceridian Dayforce runs the people side: who works here, which team they sit in, and how their employment changes over time. The two overlap on the same people and the same org structure, because every employee is also a payee and every department is also a cost center. When that overlap is maintained by hand, a new hire, a transfer, or a termination has to be keyed twice, and the two systems start to disagree about who is active and where the cost lands.
Stacksync syncs Dimension lists, Tables, Scenarios, Data imports in Pigment with Compensation Summary & Pay Adjustments, Employee Punches & Raw Clock Entries, Employee Schedules, Org Units, Departments, Jobs & Positions in Ceridian Dayforce bi-directionally and in real time. A person added, updated, or deactivated on either side appears on the other within seconds, with field-level mapping and conflict resolution in place of CSV exports and nightly batch jobs.
That matters most when money follows a people event. A hire that finance can pay, a leaver whose access ends, a transfer that redirects cost to the right team, all happen from one change instead of two, so headcount and spend reconcile from the same set of records.
Common use cases
- 01 Keep dimension lists such as departments and cost centers consistent with master data in the ERP.
- 02 Sync headcount and compensation data from an HRIS into workforce planning models.
- 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
Status changes propagate
A role, department, or employment-status change in either system updates the other within seconds, so cost allocation, access, and reporting reflect the current state.
People-driven costs land in finance
Compensation, reimbursements, or other costs tied to a person on the Ceridian Dayforce side flow into Pigment for posting, so the books reflect what people actually cost without manual re-entry.
New person becomes a known record in finance
When someone is added in Ceridian Dayforce, a matching employee or payee record appears in Pigment, ready for payroll, expenses, or cost allocation without anyone rekeying the details.
What you can sync between Ceridian Dayforce and Pigment
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 | Pigment objects | How this pairing syncs | |
|---|---|---|---|
| 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. | Users and permissions Access controls governing which model areas a sync can touch | Work Assignments is specific to Ceridian Dayforce and Users and permissions to Pigment — 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. | Applications Planning models organized by domain such as finance, sales, or workforce | Compensation Summary & Pay Adjustments is specific to Ceridian Dayforce and Applications to Pigment — 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. | Metrics Multidimensional values holding plans and actuals; the main target for inbound data | Employee Punches & Raw Clock Entries is specific to Ceridian Dayforce and Metrics to Pigment — 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. | Dimension lists Master data like accounts, products, or employees that metrics are sliced by | Employee Schedules is specific to Ceridian Dayforce and Dimension lists to Pigment — 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. | Tables Row-based transactional data loaded into models from source systems | Org Units, Departments, Jobs & Positions is specific to Ceridian Dayforce and Tables to Pigment — 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. | Scenarios Versions such as budget, forecast, and actuals that give exported figures their context | Time Away From Work & Balances is specific to Ceridian Dayforce and Scenarios to Pigment — each maps to any object or custom field on the other side. |
How changes propagate between Ceridian Dayforce and Pigment
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 Pigment Sub-second propagation
DetectionCeridian Dayforce notifies Stacksync of record changes through webhook events. No CDC stream.
DeliveryEach detected change is written to Pigment through its API, with automatic retries and rate-limit backoff.
Pigment Ceridian Dayforce Interval-based propagation
DetectionStacksync polls Pigment for changes on an incremental schedule, reading only records changed since the previous pass. No change feed.
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.
- Pigment: Subject to the platform's API rate limits.
What ships with Ceridian Dayforce ⇄ Pigment
Connect Ceridian Dayforce and Pigment for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Ceridian Dayforce–Pigment connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Ceridian Dayforce or Pigment 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 Pigment record.
Observability
Monitoring
Track your Ceridian Dayforce ⇄ Pigment 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 Pigment.
How the Ceridian Dayforce and Pigment 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.
Pigment
- Integration surface
- REST-based import and export API
- Authentication
- API keys, issued separately for import and export
- Change detection
- no change feed; syncs run scheduled imports and exports
- Capabilities
- read · write
- Rate limits
- subject to the platform's API rate limits
How it works
How to connect Ceridian Dayforce to Pigment — 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 Pigment 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
Pigment
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Ceridian Dayforce and Pigment 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 ⇄ PigmentCustomers 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 PigmentCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Ceridian Dayforce and Pigment integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Ceridian Dayforce and Pigment: authenticate both systems, choose the objects to sync (such as Ceridian Dayforce's Work Assignments and Compensation Summary & Pay Adjustments), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Common patterns for Ceridian Dayforce and Pigment: Status changes propagate; People-driven costs land in finance; New person becomes a known record in finance. A role, department, or employment-status change in either system updates the other within seconds, so cost allocation, access, and reporting reflect the current state.
-
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. Pigment: REST-based import and export API. Authentication: API keys, issued separately for import and export. Stacksync manages authentication, retries, and rate limits on both sides.
-
Pigment: Actuals typically flow in from source systems on a schedule while plans and forecasts are edited inside Pigment, making it primarily a data destination. Ceridian Dayforce: Native Event Notifications (the Dayforce Notification Publisher) cover employee lifecycle events — Hire, Rehire, Terminate (and their cancels) and Workflow Validation — pushed to a receiver service or pulled via unacknowledged-notification queries; the publisher runs about hourly and notifications must be acknowledged. Stacksync's field mapping accounts for these differences between Ceridian Dayforce and Pigment 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 Pigment 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 Pigment connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Ceridian Dayforce–Pigment integration in-house.
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 411 integrations available for Ceridian Dayforce and Pigment.
Popular · 7 of 411
-
Ceridian Dayforce ⇄ Recurly -
Ceridian Dayforce ⇄ Rillet -
Ceridian Dayforce ⇄ Workday -
Ceridian Dayforce ⇄ Anaplan -
Pigment ⇄ Jobvite -
Pigment ⇄ Lever -
Pigment ⇄ Paylocity
No integrations match .
