Real-time
Two-way sync
Changes in Paylocity or Pigment instantly reflect in both systems. No stale data, no manual imports.
Human resources ⇄ Accounting and finance
Paylocity to Pigment integration — real-time, two-way sync
Keep Paylocity and Pigment 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 Pigment
Keep the employee, department, and cost records that Pigment and Paylocity share consistent in real time, so the finance system and the people system stop drifting apart.
Pigment runs the money side of the company: who gets paid, what it costs, and which part of the business the cost belongs to. Paylocity 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 Metrics, Dimension lists, Tables, Scenarios in Pigment with Deductions (Pay Setup), Earnings (Pay Setup), Local and State Taxes, Direct Deposit in Paylocity 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 Export approved budgets and forecasts back to a warehouse or Postgres for downstream reporting.
- 02 Keep dimension lists such as departments and cost centers consistent with master data in the ERP.
- 03 Read Pay Statements and Direct Deposit allocations into a Postgres or warehouse database for labor-cost, GL, and headcount reporting in SQL.
- 04 React to the Employee Change webhook to pull the updated Employee record and propagate title, location, or manager changes to downstream apps within minutes.
Common sync patterns
Status changes propagate
A role, department, or employment-status change in either system updates the other within seconds, so cost allocation, access, and reporting reflect the current state.
People-driven costs land in finance
Compensation, reimbursements, or other costs tied to a person on the Paylocity side flow into Pigment for posting, so the books reflect what people actually cost without manual re-entry.
New person becomes a known record in finance
When someone is added in Paylocity, a matching employee or payee record appears in Pigment, ready for payroll, expenses, or cost allocation without anyone rekeying the details.
What you can sync between Paylocity and Pigment
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 | Pigment objects | How this pairing syncs | |
|---|---|---|---|
| Direct Deposit Read-only: Get All Direct Deposit and Get Employee Bank Accounts return main and additional allocations. Bank details cannot be written through the API. | Scenarios Versions such as budget, forecast, and actuals that give exported figures their context | Direct Deposit is specific to Paylocity and Scenarios to Pigment — each maps to any object or custom field on the other side. | |
| 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. | Data imports Scheduled loads that bring actuals from ERPs, CRMs, and HRIS into the model | Pay Statements is specific to Paylocity and Data imports to Pigment — 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. | Users and permissions Access controls governing which model areas a sync can touch | Company Codes is specific to Paylocity and Users and permissions to Pigment — 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. | Applications Planning models organized by domain such as finance, sales, or workforce | Custom Fields is specific to Paylocity and Applications to Pigment — 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. | Metrics Multidimensional values holding plans and actuals; the main target for inbound data | Employees is specific to Paylocity and Metrics to Pigment — 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. | Dimension lists Master data like accounts, products, or employees that metrics are sliced by | Onboarding is specific to Paylocity and Dimension lists to Pigment — each maps to any object or custom field on the other side. |
How changes propagate between Paylocity and Pigment
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 Pigment 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 Pigment through its API, with automatic retries and rate-limit backoff.
Pigment Paylocity Interval-based propagation
DetectionStacksync polls Pigment for changes on an incremental schedule, reading only records changed since the previous pass. No change feed.
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).
- Pigment: Subject to the platform's API rate limits.
What ships with Paylocity ⇄ Pigment
Connect Paylocity and Pigment for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Paylocity–Pigment connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Paylocity or Pigment 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 Pigment record.
Observability
Monitoring
Track your Paylocity ⇄ Pigment 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 Pigment.
How the Paylocity and Pigment 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).
Pigment
- Integration surface
- REST-based import and export API
- Authentication
- API keys, issued separately for import and export
- Change detection
- no change feed; syncs run scheduled imports and exports
- Capabilities
- read · write
- Rate limits
- subject to the platform's API rate limits
How it works
How to connect Paylocity to Pigment — 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.
- 01
Connect your apps
Authenticate Paylocity and Pigment with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Paylocity
connected
Pigment
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Paylocity and Pigment 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.
objects · Paylocity ⇄ PigmentCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Paylocity PigmentCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Paylocity and Pigment integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Paylocity and Pigment: authenticate both systems, choose the objects to sync (such as Paylocity's Direct Deposit and Pay Statements), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Pigment: Pigment's model is multidimensional: metrics are sliced by dimension lists, so inbound records must map to those dimensions rather than flat columns. Paylocity: The rate limit is 25 calls per second (1,500 per minute); full-employee reads must be paged and throttled to avoid HTTP 429 errors. Stacksync's field mapping accounts for these differences between Paylocity and Pigment without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Paylocity and Pigment records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Paylocity and Pigment connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Paylocity–Pigment integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Paylocity and Pigment. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Paylocity: 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. On Pigment: No change feed; syncs run scheduled imports and exports. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
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.
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 411 integrations available for Paylocity and Pigment.
Popular · 7 of 411
-
Paylocity ⇄ Hyperline -
Paylocity ⇄ QuickBooks -
Paylocity ⇄ Stripe -
Paylocity ⇄ Coupa -
Pigment ⇄ Greenhouse -
Pigment ⇄ Jobvite -
Pigment ⇄ Lever
No integrations match .
