Two-way sync
Changes in Ceridian Dayforce or Macola ERP instantly reflect in both systems. No stale data, no manual imports.
Keep Ceridian Dayforce and Macola ERP in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
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. Macola ERP 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, Items, Sales Orders, Purchase Orders in Macola ERP 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 Macola ERP 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.
A new person set up in Ceridian Dayforce becomes an employee record in Macola ERP in time to submit expenses, enter time, or approve a purchase, without waiting on manual setup.
Departments, cost centers, and locations that both systems reference stay in agreement, so labor cost, approvals, and reporting in Macola ERP roll up to the same structure Ceridian Dayforce maintains.
Manager and reporting-hierarchy changes in Ceridian Dayforce keep expense and purchase approval chains in Macola ERP pointed at the right people.
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 | Macola ERP 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. | Bills of Material Manufacturing structures read for planning and costing integrations. | Work Assignments is specific to Ceridian Dayforce and Bills of Material to Macola ERP — 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. | Work Orders Shop-floor production orders tracked for status and completion syncs. | Compensation Summary & Pay Adjustments is specific to Ceridian Dayforce and Work Orders to Macola ERP — 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. | Customers Customer master records synced with CRMs so sales works from ERP truth. | Employee Punches & Raw Clock Entries is specific to Ceridian Dayforce and Customers to Macola ERP — 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. | Vendors Vendor master data aligned with procurement and AP tools. | Employee Schedules is specific to Ceridian Dayforce and Vendors to Macola ERP — 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. | Items Inventory item master records mirrored to ecommerce and planning systems. | Org Units, Departments, Jobs & Positions is specific to Ceridian Dayforce and Items to Macola ERP — 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 Orders Order entry documents created from web or CRM orders and read back for status. | Time Away From Work & Balances is specific to Ceridian Dayforce and Sales Orders to Macola ERP — each maps to any object or custom field on the other side. |
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.
DetectionCeridian Dayforce notifies Stacksync of record changes through webhook events. No CDC stream.
DeliveryEach detected change is applied to Macola ERP as a row-level write, with types converted between the two schemas.
DetectionChanges in Macola ERP are captured at the source via change data capture — no polling loop against its API. CDC or change tracking on the underlying SQL Server database, or timestamp-based polling.
DeliveryEach detected change is written to Ceridian Dayforce through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Ceridian Dayforce–Macola ERP connection.
Changes in Ceridian Dayforce or Macola ERP instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Ceridian Dayforce or Macola ERP data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Ceridian Dayforce or Macola ERP record.
Track your Ceridian Dayforce ⇄ Macola ERP sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Ceridian Dayforce and Macola ERP.
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.
Authenticate Ceridian Dayforce and Macola ERP with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Ceridian Dayforce and Macola ERP 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Ceridian Dayforce and Macola ERP: 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.
On the Macola ERP side: Vendors, Items, Sales Orders, Purchase Orders, plus custom fields where Macola ERP 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.
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 Ceridian Dayforce and Macola ERP: New hires ready to transact in Macola ERP; One org structure; Reporting lines drive approvals. A new person set up in Ceridian Dayforce becomes an employee record in Macola ERP in time to submit expenses, enter time, or approve a purchase, without waiting on manual setup.
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. Macola ERP: SQL Server database access, with product-level integration interfaces in newer Macola versions. Authentication: Database credentials (SQL Server or Windows authentication). Stacksync manages authentication, retries, and rate limits on both sides.
Macola ERP: Macola runs on Microsoft SQL Server, so integrations commonly operate at the database layer, where log-based CDC and change tracking are available. Ceridian Dayforce: Dayforce is genuinely two-way: POST adds employees, org units, raw clock entries, and schedules; PATCH updates employees, pay adjustments, jobs, positions, and org units; DELETE removes punches. Stacksync's field mapping accounts for these differences between Ceridian Dayforce and Macola ERP without custom code.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 409 integrations available for Ceridian Dayforce and Macola ERP.