Two-way sync
Changes in Reltio or Workday instantly reflect in both systems. No stale data, no manual imports.
Keep Reltio and Workday in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Engineers need finance data more often than finance systems make it easy to get: for internal tools, reporting services, or logic that reacts to invoices and payments. Working through the vendor API means rate limits, pagination, and glue code that has to be maintained forever.
Stacksync mirrors Suppliers, Customers and Invoices, Journal Entries, Custom Reports (RaaS) from Workday into Matches (Potential Matches), Activity Log, Data Change Requests (DCR), Reference Data (RDM) in Reltio and keeps the two in sync bi-directionally and in real time. Your services read finance records with normal queries against Reltio, and rows your code writes or updates flow back into Workday with validation, so the finance system stays the system of record.
Updates written to the synced tables in Reltio propagate into Workday, so automations can create or correct finance records without custom integration code.
Changes in Workday appear in Reltio as row changes, so you can trigger downstream logic with the database tooling you already use.
Customers, invoices, and payments from Workday live in Reltio as regular tables or collections your team can join, index, and query.
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.
| Reltio objects | Workday objects | How this pairing syncs | |
|---|---|---|---|
| Interactions Transactional or event records linked to entities (purchases, visits, activities); read and written via /interactions to enrich profiles and power 360-degree reporting. | Compensation Pay components read into payroll, planning, and equity systems under strict access control. | Interactions is specific to Reltio and Compensation to Workday — each maps to any object or custom field on the other side. | |
| Matches (Potential Matches) Candidate duplicate pairs produced by match rules; read to review, and resolved with merge, unmerge, or not-a-match actions to control survivorship. | Time Off and Absence Balances and requests synced with scheduling and workforce tools. | Matches (Potential Matches) is specific to Reltio and Time Off and Absence to Workday — each maps to any object or custom field on the other side. | |
| Activity Log Immutable audit trail of changes to entities and relations via /activities; read-only, used for history, lineage, and compliance reporting. | Payroll Results Completed pay data exported to finance and benefits systems. | Activity Log is specific to Reltio and Payroll Results to Workday — each maps to any object or custom field on the other side. | |
| Data Change Requests (DCR) Stewardship change proposals routed through approval workflows; read and written to feed or track governed edits to golden records. | Suppliers Workday Financials vendor records aligned with procurement tools. | Data Change Requests (DCR) is specific to Reltio and Suppliers to Workday — each maps to any object or custom field on the other side. | |
| Reference Data (RDM) Managed lookup and reference values (country codes, standardized values, hierarchies); read and updated so downstream systems share consistent reference data. | Customers and Invoices Financials receivables objects synced for billing visibility where Workday Financials is used. | Reference Data (RDM) is specific to Reltio and Customers and Invoices to Workday — each maps to any object or custom field on the other side. | |
| Entities Golden records for each configured entity type (for example Organization, Individual/Contact, Location, or Product); full CRUD via /entities, so records are created, updated, and deleted, and Reltio matches and merges them by survivorship rules. | Journal Entries Accounting entries imported from external subledgers into Workday Financials. | Entities is specific to Reltio and Journal Entries to Workday — 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.
DetectionStacksync polls Reltio for changes on an incremental schedule, reading only records changed since the previous pass. Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored.
DeliveryEach detected change is written to Workday through its API, with automatic retries and rate-limit backoff.
DetectionStacksync polls Workday for changes on an incremental schedule, reading only records changed since the previous pass. Polling, including transaction-log criteria on SOAP operations to fetch objects changed since a given moment.
DeliveryEach detected change is written to Reltio through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Reltio–Workday connection.
Changes in Reltio or Workday instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Reltio or Workday data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Reltio or Workday record.
Track your Reltio ⇄ Workday sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Reltio and Workday.
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 Reltio and Workday 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 Reltio and Workday 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 Reltio and Workday: authenticate both systems, choose the objects to sync (such as Reltio's Interactions and Matches (Potential Matches)), map fields visually, and changes propagate both ways in milliseconds — no code required.
On the Workday side: Suppliers, Customers and Invoices, Journal Entries, Custom Reports (RaaS), plus custom fields where Workday exposes them. On the Reltio side: Matches (Potential Matches), Activity Log, Data Change Requests (DCR), Reference Data (RDM). 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 Reltio and Workday: Write back safely; React to financial events; Query finance data like any other data. Updates written to the synced tables in Reltio propagate into Workday, so automations can create or correct finance records without custom integration code.
Reltio: Reltio REST API (Data API) — /entities, /relations, /interactions, /activities, plus Match, RDM (reference data), and Data Change Request endpoints; base URL https://{environment}.reltio.com/reltio/api/{tenantId}. Authentication: OAuth 2.0 bearer tokens obtained from Reltio's central auth server (POST https://auth.reltio.com/oauth/token, client-credentials or password grant, application/x-www-form-urlencoded) and sent as Authorization: Bearer <token>; access tokens expire after about 60 minutes and are renewed with a refresh token, and are scoped per API (entities_api, relations_api, interactions_api, configuration_api, graphs_api). Workday: SOAP Workday Web Services (WWS), a REST API, and Reports-as-a-Service (RaaS) endpoints for custom reports. Authentication: OAuth 2.0 for the REST API; integration system users with WS-Security or certificate-based auth for SOAP. Stacksync manages authentication, retries, and rate limits on both sides.
Workday: SOAP operations such as Get_Workers accept transaction-log criteria, letting integrations request only objects changed since the last run. Reltio: The API uses OAuth 2.0: a bearer token from auth.reltio.com/oauth/token (client-credentials or password grant) is sent as Authorization: Bearer; access tokens expire after about 60 minutes and are renewed with a refresh token. Stacksync's field mapping accounts for these differences between Reltio and Workday 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 420 integrations available for Reltio and Workday.