Real-time
Two-way sync
Changes in Bill or Ceridian Dayforce instantly reflect in both systems. No stale data, no manual imports.
Accounting and finance ⇄ Human resources
Bill to Ceridian Dayforce integration — real-time, two-way sync
Keep Bill and Ceridian Dayforce 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 Bill and Ceridian Dayforce
Keep the employee, department, and cost records that Bill and Ceridian Dayforce share consistent in real time, so the finance system and the people system stop drifting apart.
Bill 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 Bank Accounts, Vendor Credits and Credit Memos, Bills, Vendors in Bill with Employee Schedules, Org Units, Departments, Jobs & Positions, Time Away From Work & Balances, Employee (HR / Person Details) 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 Read Payments and payment status into a reconciliation database once bills are marked paid in BILL.
- 02 Read approved Bills and their line items into a Postgres warehouse for spend, accrual, and cash-flow reporting without CSV exports.
- 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 Bill 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 Bill, ready for payroll, expenses, or cost allocation without anyone rekeying the details.
What you can sync between Bill and Ceridian Dayforce
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.
| Bill objects | Ceridian Dayforce objects | How this pairing syncs | |
|---|---|---|---|
| Chart of Accounts GL accounts used to code bills and invoices; typically mastered in the accounting system and written into BILL for consistent coding. | 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. | Chart of Accounts is specific to Bill and Org Units, Departments, Jobs & Positions to Ceridian Dayforce — each maps to any object or custom field on the other side. | |
| Bank Accounts Funding and deposit accounts; read to reconcile payments and posted transactions against the ledger. | 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. | Bank Accounts is specific to Bill and Time Away From Work & Balances to Ceridian Dayforce — each maps to any object or custom field on the other side. | |
| Vendor Credits and Credit Memos AP and AR adjustments applied against bills and invoices; synced so balances stay accurate on both sides. | 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. | Vendor Credits and Credit Memos is specific to Bill and Employee (HR / Person Details) to Ceridian Dayforce — each maps to any object or custom field on the other side. | |
| Bills Accounts-payable amounts owed to vendors, with bill line items; read and created via /v3/bills and pulled incrementally by filtering on createdTime/updatedTime. | 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. | Bills is specific to Bill and Employment Status to Ceridian Dayforce — each maps to any object or custom field on the other side. | |
| Vendors Payee master records; synced two-way with vendor/supplier tables in an ERP or accounting system so new payees don't have to be re-keyed. | 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. | Vendors is specific to Bill and Work Assignments to Ceridian Dayforce — each maps to any object or custom field on the other side. | |
| Invoices Accounts-receivable invoices sent to customers; created and read via /v3/invoices to keep billing status aligned with the ERP or CRM. | 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. | Invoices is specific to Bill and Compensation Summary & Pay Adjustments to Ceridian Dayforce — each maps to any object or custom field on the other side. |
How changes propagate between Bill and Ceridian Dayforce
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.
Bill Ceridian Dayforce Sub-second propagation
DetectionBill notifies Stacksync of record changes through webhook events. Webhook event subscriptions (POST /v3/subscriptions) for bills, vendors, payments, invoices, and bank accounts, with polling on.
DeliveryEach detected change is written to Ceridian Dayforce through its API, with automatic retries and rate-limit backoff.
Ceridian Dayforce Bill Sub-second propagation
DetectionCeridian Dayforce notifies Stacksync of record changes through webhook events. No CDC stream.
DeliveryEach detected change is written to Bill through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Bill: 20,000 requests per developer key per hour; login (POST /v3/login) capped at 200/hour; maximum 3 concurrent requests per developer key per organization. Spend & Expense API is a separate token at 60 calls/token/minute.
- 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 Bill ⇄ Ceridian Dayforce
Connect Bill and Ceridian Dayforce for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Bill–Ceridian Dayforce connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Bill or Ceridian Dayforce 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 Bill or Ceridian Dayforce record.
Observability
Monitoring
Track your Bill ⇄ Ceridian Dayforce sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Bill and Ceridian Dayforce.
How the Bill and Ceridian Dayforce connectors work
Bill
- Integration surface
- REST/JSON (BILL v3 Connect API)
- Authentication
- Session-based: POST /v3/login with username, password, organizationId, and a developer key (devKey) returns a sessionId that is passed with the devKey as headers on every subsequent call; OAuth is available for partner/embedded apps
- Change detection
- Webhook event subscriptions (POST /v3/subscriptions) for bills, vendors, payments, invoices, and bank accounts, with polling on createdTime/updatedTime list filters as the fallback
- Capabilities
- read · write · webhooks
- Rate limits
- 20,000 requests per developer key per hour; login (POST /v3/login) capped at 200/hour; maximum 3 concurrent requests per developer key per organization. Spend & Expense API is a separate token at 60 calls/token/minute.
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.
How it works
How to connect Bill to Ceridian Dayforce — 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 Bill and Ceridian Dayforce with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Bill
connected
Ceridian Dayforce
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Bill and Ceridian Dayforce 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 · Bill ⇄ Ceridian DayforceCustomers 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.
Bill Ceridian DayforceCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Bill and Ceridian Dayforce integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Bill and Ceridian Dayforce: authenticate both systems, choose the objects to sync (such as Bill's Chart of Accounts and Bank Accounts), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Bill side: Bank Accounts, Vendor Credits and Credit Memos, Bills, Vendors, plus custom fields where Bill exposes them. On the Ceridian Dayforce side: Employee Schedules, Org Units, Departments, Jobs & Positions, Time Away From Work & Balances, Employee (HR / Person Details). 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 Bill and Ceridian Dayforce: 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.
-
Bill: REST/JSON (BILL v3 Connect API). Authentication: Session-based: POST /v3/login with username, password, organizationId, and a developer key (devKey) returns a sessionId that is passed with the devKey as headers on every subsequent call; OAuth is available for partner/embedded apps. 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. Stacksync manages authentication, retries, and rate limits on both sides.
-
Bill: List endpoints support filtering and sorting on createdTime and updatedTime with ISO 8601 date-time ranges, which sync engines use to pull only incremental changes. 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 Bill and Ceridian Dayforce without custom code.
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 500 integrations available for Bill and Ceridian Dayforce.
Popular · 8 of 500
-
Bill ⇄ Hibob -
Bill ⇄ D2l Brightspace -
Bill ⇄ Oracle Fusion Cloud HCM -
Bill ⇄ Smartrecruiters -
Ceridian Dayforce ⇄ Logisense -
Ceridian Dayforce ⇄ Braintree -
Ceridian Dayforce ⇄ Navan -
Ceridian Dayforce ⇄ Ramp
No integrations match .
