Skip to content
Human resources ⇄ Database

Paylocity to Reltio integration — real-time, two-way sync

Keep Paylocity and Reltio 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 Paylocity and Reltio

Put your workforce data where your apps can reach it: Reltio and Paylocity share the same people, positions, and org structure in real time.

Paylocity is the system of record for the people side of the business — employees, candidates, roles, and the org structure around them. Reltio is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Employees, Onboarding, Deductions (Pay Setup), Earnings (Pay Setup) in Paylocity need to exist as queryable Reference Data (RDM), Entities, Relations, Crosswalks in Reltio before an app can act on them. When that bridge is a nightly export or a hand-run CSV, every downstream system spends the day working from a roster that has already moved on.

Stacksync syncs Reference Data (RDM), Entities, Relations, Crosswalks in Reltio with Employees, Onboarding, Deductions (Pay Setup), Earnings (Pay Setup) in Paylocity field by field, in real time. You decide which system owns which fields — Paylocity typically owns identity and org attributes, while operational or computed values can flow back the other way — and Stacksync keeps every copy consistent, matching records on a stable key and resolving conflicts by rules you set.

The result is one live picture of the workforce on both sides: HR keeps its source of truth, and the database keeps a current mirror that internal apps, reports, and access controls can trust without a batch window in between.

Common use cases

  • 01 Mirror the Reltio Activity Log and change history into a database for audit, lineage, and governance reporting.
  • 02 Push cleansed, deduplicated golden records and survivorship results from Reltio back into CRM and ERP systems so every app works from the mastered record.
  • 03 Push hired candidates from an ATS into Paylocity via the Onboarding endpoint, then read Onboarding Status to confirm the record before the first payroll run.
  • 04 Upsert recurring Deductions and Earnings on employee records when benefits or 401(k) elections change in a benefits admin system, without re-keying payroll setup.

Common sync patterns

Reporting and analytics on current data

Employees, Onboarding, Deductions (Pay Setup), Earnings (Pay Setup) replicate into Reltio where they join operational tables, so headcount, roles, and status reports run on the live state without manual pulls.

Org and structure stay aligned

Groups, departments, managers, and reporting lines from Paylocity stay consistent in Reltio, so hierarchy-driven logic and permissions don't drift.

Computed and operational fields flow back

Values assembled or corrected in Reltio write onto the matching record in Paylocity where those fields are writable, keeping the people system enriched.

What you can sync between Paylocity and Reltio

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.

Paylocity objects Reltio objects How this pairing syncs
Pay Statements Read-only detailed payroll statement data — earnings, deductions, taxes, and direct deposit allocations by year, check date, or date range. Pulled for reporting, never written. 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. Pay Statements is specific to Paylocity and Entities to Reltio — each maps to any object or custom field on the other side.
Company Codes Read-only reference codes and descriptions (cost centers, departments, positions) used to validate field mappings on employee writes. Relations Typed relationships between two entities (affiliations, hierarchies, employment, households); read and written via /relations to keep account hierarchies and affiliation graphs aligned across systems. Company Codes is specific to Paylocity and Relations to Reltio — each maps to any object or custom field on the other side.
Custom Fields Read-only company-specific custom fields returned by category, used to enrich the employee record downstream. Crosswalks Per-entity references to the source systems and their record IDs; written when loading records so Reltio ties each source contribution to a golden record, and read to trace lineage back to origin systems. Custom Fields is specific to Paylocity and Crosswalks to Reltio — each maps to any object or custom field on the other side.
Employees Core HR record keyed by companyId + employeeId; two-way via Create New Employee (POST) and Update Employee (PATCH), plus Get Employee / Get All Employees for reads. Interactions Transactional or event records linked to entities (purchases, visits, activities); read and written via /interactions to enrich profiles and power 360-degree reporting. Employees is specific to Paylocity and Interactions to Reltio — each maps to any object or custom field on the other side.
Onboarding Create Employee Onboarding pushes new-hire data into Paylocity's onboarding workflow; Get Onboarding Status reads back partner onboarding progress. Write-in for hires from an ATS. 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. Onboarding is specific to Paylocity and Matches (Potential Matches) to Reltio — each maps to any object or custom field on the other side.
Deductions (Pay Setup) Recurring deduction codes at the employee level; two-way via Upsert Deduction and Delete, with Get Deduction / Get All Deductions for reads. Activity Log Immutable audit trail of changes to entities and relations via /activities; read-only, used for history, lineage, and compliance reporting. Deductions (Pay Setup) is specific to Paylocity and Activity Log to Reltio — each maps to any object or custom field on the other side.

How changes propagate between Paylocity and Reltio

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.

Paylocity Reltio Sub-second propagation

DetectionPaylocity notifies Stacksync of record changes through webhook events. Webhooks — Paylocity POSTs Employee New Hire, Employee Change, Termination, Payroll Processed, and Time Off Approval events to a callback URL.

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

Reltio Paylocity Interval-based propagation

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 Paylocity through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Paylocity: 25 requests per second (1,500 per minute); exceeding it returns HTTP 429. Every path is scoped to a Paylocity-assigned companyId (a company code, not a UUID).
  • Reltio: Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.
What ships with Paylocity ⇄ Reltio

Connect Paylocity and Reltio for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Paylocity–Reltio connection.

Real-time

Two-way sync

Changes in Paylocity or Reltio instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Paylocity or Reltio 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 Paylocity or Reltio record.

Observability

Monitoring

Track your Paylocity ⇄ Reltio sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Paylocity and Reltio.

How the Paylocity and Reltio connectors work

Paylocity

Integration surface
REST API (v1 and v2), JSON payloads
Authentication
OAuth 2.0 client credentials via the Paylocity Identity Provider (/IdentityServer/connect/token) with the WebLinkAPI scope; access tokens expire after one hour and API access must be enabled by Paylocity for the company
Change detection
Webhooks — Paylocity POSTs Employee New Hire, Employee Change, Termination, Payroll Processed, and Time Off Approval events to a callback URL; payloads carry only companyId and employeeId, so the receiver calls the relevant API to fetch changed values. Scheduled polling is used for objects without webhooks.
Capabilities
read · write · webhooks
Rate limits
25 requests per second (1,500 per minute); exceeding it returns HTTP 429. Every path is scoped to a Paylocity-assigned companyId (a company code, not a UUID).

Reltio

Integration surface
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)
Change detection
Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored watermark. Reltio has no CDC log external tools consume; separately, Reltio's event streaming can publish entity change events (created, changed, removed) to a customer-configured message queue (Amazon SQS/SNS, Google Pub/Sub, Azure Service Bus, or Kafka), which is a queue feed rather than HTTP webhooks.
Capabilities
read · write
Rate limits
Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.
How it works

How to connect Paylocity to Reltio — 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 Paylocity and Reltio 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
    Paylocity connected
    Reltio connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Paylocity and Reltio 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 · Paylocity ⇄ Reltio
    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
    Paylocity Reltio
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Paylocity and Reltio 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 431 integrations available for Paylocity and Reltio.

Popular · 7 of 431
All Paylocity integrations All Reltio 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