Skip to content
Database ⇄ Human resources

InterSystems IRIS to Paylocity integration — real-time, two-way sync

Keep InterSystems IRIS and Paylocity 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 InterSystems IRIS and Paylocity

Put your workforce data where your apps can reach it: InterSystems IRIS 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. InterSystems IRIS is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Local and State Taxes, Direct Deposit, Pay Statements, Company Codes in Paylocity need to exist as queryable Globals, Namespaces, Stored Procedures, Tables in InterSystems IRIS 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 Globals, Namespaces, Stored Procedures, Tables in InterSystems IRIS with Local and State Taxes, Direct Deposit, Pay Statements, Company Codes 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 Sync operational tables in IRIS bi-directionally with a CRM so business teams work on IRIS-backed data without SQL access
  • 02 Consolidate IRIS data with other databases in an analytics warehouse for cross-system reporting
  • 03 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.
  • 04 Read Pay Statements and Direct Deposit allocations into a Postgres or warehouse database for labor-cost, GL, and headcount reporting in SQL.

Common sync patterns

One directory of record

When a person record is added, changed, or deactivated in either system, the matching row in the other stays current, ending dual maintenance.

Reporting and analytics on current data

Local and State Taxes, Direct Deposit, Pay Statements, Company Codes replicate into InterSystems IRIS 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 InterSystems IRIS, so hierarchy-driven logic and permissions don't drift.

What you can sync between InterSystems IRIS and Paylocity

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.

InterSystems IRIS objects Paylocity objects How this pairing syncs
Views SQL views expose curated slices of data for outbound replication. 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. Views is specific to InterSystems IRIS and Pay Statements to Paylocity — each maps to any object or custom field on the other side.
Schemas Schema organization scopes which tables a sync connection can see. Company Codes Read-only reference codes and descriptions (cost centers, departments, positions) used to validate field mappings on employee writes. Schemas is specific to InterSystems IRIS and Company Codes to Paylocity — each maps to any object or custom field on the other side.
Persistent Classes Object-model classes project to tables, so class data is reachable through SQL. Custom Fields Read-only company-specific custom fields returned by category, used to enrich the employee record downstream. Persistent Classes is specific to InterSystems IRIS and Custom Fields to Paylocity — each maps to any object or custom field on the other side.
Globals The underlying multidimensional storage; typically accessed indirectly via SQL or objects in syncs. 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. Globals is specific to InterSystems IRIS and Employees to Paylocity — each maps to any object or custom field on the other side.
Namespaces Namespaces partition databases and determine the connection context for integrations. 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. Namespaces is specific to InterSystems IRIS and Onboarding to Paylocity — each maps to any object or custom field on the other side.
Stored Procedures Server-side logic callable over SQL supports controlled writes and transformations. 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. Stored Procedures is specific to InterSystems IRIS and Deductions (Pay Setup) to Paylocity — each maps to any object or custom field on the other side.

How changes propagate between InterSystems IRIS and Paylocity

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.

InterSystems IRIS Paylocity Interval-based propagation

DetectionStacksync polls InterSystems IRIS for changes on an incremental schedule, reading only records changed since the previous pass. Polling (timestamp or query-based).

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

Paylocity InterSystems IRIS 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 applied to InterSystems IRIS as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • InterSystems IRIS: Constrained by database resources rather than published API rate limits.
  • 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).
What ships with InterSystems IRIS ⇄ Paylocity

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the InterSystems IRIS and Paylocity connectors work

InterSystems IRIS

Integration surface
SQL over JDBC/ODBC, plus object and REST access layers
Authentication
Database credentials
Change detection
Polling (timestamp or query-based); no standard webhook surface
Capabilities
read · write
Rate limits
Constrained by database resources rather than published API rate limits

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).
How it works

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

    Choose tables

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

InterSystems IRIS and Paylocity 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 467 integrations available for InterSystems IRIS and Paylocity.

Popular · 7 of 467
All InterSystems IRIS integrations All Paylocity 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