Skip to content
Human resources ⇄ Accounting and finance

Ceridian Dayforce to Recurly integration — real-time, two-way sync

Keep Ceridian Dayforce and Recurly 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 Recurly

Keep the employee, department, and cost records that Recurly and Ceridian Dayforce share consistent in real time, so the finance system and the people system stop drifting apart.

Recurly 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 Billing Info, Measured Units and Usage, Accounts, Subscriptions in Recurly with Org Units, Departments, Jobs & Positions, Time Away From Work & Balances, Employee (HR / Person Details), Employment Status 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 Sync Accounts and Subscriptions bi-directionally with Postgres so product and provisioning systems read live entitlement state and write plan or seat changes back to Recurly.
  • 02 Trigger revenue-recognition or ERP entries when new_subscription and canceled_subscription webhooks fire.
  • 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

New person becomes a known record in finance

When someone is added in Ceridian Dayforce, a matching employee or payee record appears in Recurly, ready for payroll, expenses, or cost allocation without anyone rekeying the details.

One employee identity

A person's name, ID, or contact details corrected in either system update the other, so finance and HR reference the same person instead of maintaining two versions.

Department and cost-center alignment

The org structure maintained in Ceridian Dayforce keeps the departments or cost centers in Recurly current, so spend and headcount roll up the same way.

What you can sync between Ceridian Dayforce and Recurly

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 Recurly objects How this pairing syncs
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 Charge and credit billing documents; read-heavy for revenue reporting, and creatable through Purchases for one-off charges. Compensation Summary & Pay Adjustments is specific to Ceridian Dayforce and Invoices to Recurly — 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. Transactions Individual payment attempts — captures, refunds, and voids; typically read into a warehouse for reconciliation and dunning analysis. Employee Punches & Raw Clock Entries is specific to Ceridian Dayforce and Transactions to Recurly — 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. Line Items One-time charges and credits on an account outside a subscription; synced for accurate revenue and adjustment reporting. Employee Schedules is specific to Ceridian Dayforce and Line Items to Recurly — 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. Coupons and Redemptions Discount definitions and their application to accounts and subscriptions; read for discount and promotion analysis. Org Units, Departments, Jobs & Positions is specific to Ceridian Dayforce and Coupons and Redemptions to Recurly — 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. Billing Info Tokenized payment method (card/ACH) on an account; written when onboarding customers and read for payment-health signals (never stores raw card numbers). Time Away From Work & Balances is specific to Ceridian Dayforce and Billing Info to Recurly — 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. Measured Units and Usage Metered-billing units; usage records are posted to a subscription before each bill run for consumption-based pricing. Employee (HR / Person Details) is specific to Ceridian Dayforce and Measured Units and Usage to Recurly — each maps to any object or custom field on the other side.

How changes propagate between Ceridian Dayforce and Recurly

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 Recurly Sub-second propagation

DetectionCeridian Dayforce notifies Stacksync of record changes through webhook events. No CDC stream.

DeliveryEach detected change is written to Recurly through its API, with automatic retries and rate-limit backoff.

Recurly Ceridian Dayforce Sub-second propagation

DetectionRecurly notifies Stacksync of record changes through webhook events. Webhooks (JSON or XML, one format per endpoint) for account, subscription, payment, and invoice events, plus incremental polling of list endpoints.

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.
  • Recurly: Production sites default to 1,000 requests/min with only GET requests counting toward the limit; sandbox sites 400/min with all requests counting; the limit is a sliding 5-minute window, X-RateLimit headers report the quota, and breaches return HTTP 429.
What ships with Ceridian Dayforce ⇄ Recurly

Connect Ceridian Dayforce and Recurly for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Ceridian Dayforce–Recurly connection.

Real-time

Two-way sync

Changes in Ceridian Dayforce or Recurly instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Ceridian Dayforce or Recurly 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 Recurly record.

Observability

Monitoring

Track your Ceridian Dayforce ⇄ Recurly 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 Recurly.

How the Ceridian Dayforce and Recurly 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.
Ceridian Dayforce setup guide

Recurly

Integration surface
REST API (V3, date-versioned; legacy V2 XML API also exists)
Authentication
API key via HTTP Basic auth (key as username, blank password); keys are per-site, with separate sandbox and production keys
Change detection
Webhooks (JSON or XML, one format per endpoint) for account, subscription, payment, and invoice events, plus incremental polling of list endpoints sorted by updated_at with begin_time/end_time filters
Capabilities
read · write · webhooks
Rate limits
Production sites default to 1,000 requests/min with only GET requests counting toward the limit; sandbox sites 400/min with all requests counting; the limit is a sliding 5-minute window, X-RateLimit headers report the quota, and breaches return HTTP 429.
How it works

How to connect Ceridian Dayforce to Recurly — 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.

  1. 01

    Connect your apps

    Authenticate Ceridian Dayforce and Recurly with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Ceridian Dayforce connected
    Recurly connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Ceridian Dayforce and Recurly 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Ceridian Dayforce ⇄ Recurly
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Ceridian Dayforce Recurly
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Ceridian Dayforce and Recurly integration FAQ

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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 501 integrations available for Ceridian Dayforce and Recurly.

Popular · 8 of 501
All Ceridian Dayforce integrations All Recurly integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own