Connecting to Paylocity
Last updated: July 27, 2026
This guide explains how to integrate Paylocity as an HRIS in YeshID. Once connected, YeshID imports your Paylocity employees on a schedule, keeps their records in sync, and can trigger onboarding and offboarding workflows from each employee’s hire and termination dates.
The integration is read-only — YeshID reads employee data from Paylocity and never writes back to it.
Before you begin
You’ll need a Paylocity company admin and a YeshID admin. HRIS management is available on Business plans and above.
Paylocity API access is not enabled by default. It has to be requested and approved by Paylocity, and there may be a cost. Step 1 covers this — plan for it to take days or weeks, not minutes.
Once your credentials are in hand, the YeshID side takes about 10–15 minutes.
Step 1: Request API access from Paylocity
Paylocity issues API credentials to the customer, not to YeshID. A company admin at your organization has to request them.
Contact your Paylocity account executive (or Paylocity support) and ask to submit a project/API access request for a third-party integration.
On the request, include:
The business case — employee data sync for identity lifecycle management (onboarding and offboarding automation).
Your primary business contact and primary technical contact. Credentials are delivered to the technical contact, so make this someone durable — ideally a role account rather than an individual who may leave.
The data access you need. YeshID needs read access to employee demographic data, specifically the Get all employees endpoint (employee
info,position, andstatusdata) for each company you want to sync.
Sign off on the access levels when Paylocity asks. Paylocity requires the customer to explicitly approve what a third party can read.
Paylocity will send your technical contact a Client ID and Client Secret.
Note: Under your Paylocity Master Agreement, you remain accountable for the access you authorize, so scope the request to employee demographics only — YeshID does not need payroll, pay rates, or deduction access.
Step 2: Collect your Paylocity credentials
Have these three values ready:
Value | Where to find it |
|---|---|
Client ID | Provided by Paylocity when your API access request is approved |
Client Secret | Provided by Paylocity alongside the Client ID. Store it in a password manager — Paylocity shows it once |
Company ID | The same company identifier you use to log in to Paylocity, shown in the upper-left corner of the Paylocity portal |
Company IDs are case-sensitive. Enter them exactly as Paylocity displays them.
If your organization has more than one Paylocity company (multiple EINs, entities, or divisions), collect every company ID you want YeshID to import from. YeshID accepts a comma-separated list and imports employees from each one into the same application.
Step 3: Connect Paylocity in YeshID
In YeshID, go to Applications → Add Application and select Paylocity from the catalog.
Open the application’s integration panel and click Connect.
Complete the Authentication section:
Client ID — the client ID from Paylocity
Client Secret — the client secret from Paylocity
Company IDs — one company ID, or several separated by commas (for example
A12345,B67890)Active Employees Only — select Yes to import only employees whose Paylocity status is Active, or No to also bring in terminated employees and upcoming hires
Save the connection. YeshID exchanges your client credentials for a bearer token with Paylocity and refreshes it automatically as it expires — you don’t need to manage tokens.
Tip: Choose No for Active Employees Only if you want YeshID to see termination dates and drive offboarding from them. With Yes, terminated employees drop out of the import entirely rather than arriving with an end date.
Step 4: Configure the employee import
Go to the application’s Employees tab and click Configure import → to open the Import Employees action.
Map fields. YeshID lists the fields Paylocity returns with a sample value for each. Standard fields — external ID, first and last name, work email, hire date, termination date, and supervisor — are mapped for you. Map anything else you want on the person record (job title, department, location) to a standard or custom person field.
Choose who to create. Add a create rule — for example employee status equals Active — so only the employees you want become YeshID people. Set whether new people start Staged or Active, and decide how to handle records with no email address.
Review and activate. Check the counts for who will be created, updated, filtered out, and skipped, then click Activate import. The first sync runs immediately and syncing continues on a schedule.
For a full walkthrough of the import wizard, including create rules and email generation, see HRIS with YeshID.
Key field mappings
YeshID reads employee demographic, position, and status data from Paylocity:
Paylocity field | YeshID person field |
|---|---|
Employee ID | External ID (required) |
First Name | First name (required) |
Last Name | Last name (required) |
Preferred Name | Preferred name |
Email Address | Work email |
Job Title | Title |
Department | Department |
Work Location | Site / location |
Employee Status | Status |
Hire Date | Start date |
Termination Date | End date |
Supervisor | Manager |
The Paylocity Employee ID is what YeshID uses to identify each person across syncs. Records without one are skipped.
Step 5: Connect lifecycle workflows (recommended)
To have Paylocity drive onboarding and offboarding, link your workflow templates to the people source with triggers:
An onboarding trigger fires from an employee’s hire date, and can be scheduled to run on that date so accounts are ready on day one.
An offboarding trigger fires when a termination date is set, staging or running offboarding so access is removed on time.
Without triggers, the integration still keeps your people records current — it just won’t start workflows on its own.
Important notes
Syncing is polling-based, not real-time. YeshID checks Paylocity on a schedule, or whenever you run a sync manually from the Employees tab. A change made in Paylocity appears in YeshID on the next sync.
Paylocity paginates employees in small pages, so imports for large companies take longer than you might expect. Let the first sync finish before judging the results.
Rotate your credentials before they expire. Paylocity requires API credentials to be rotated annually. When you get a new client secret, update it in the application’s Authentication section — nothing else about your import changes.
Multiple companies share one application. Employees from every company ID you list land in the same Paylocity application in YeshID, so your create rule and field mapping apply across all of them.
Common issues
Symptom | What to check |
|---|---|
| Client ID or Client Secret is wrong, or the secret has been rotated. Re-enter the credentials Paylocity issued |
| Your credentials aren’t authorized for the employee endpoints. Go back to your Paylocity account executive and confirm the approved access includes Get all employees |
Connection succeeds, no employees imported | Almost always a company ID problem. Confirm the ID matches the Paylocity portal exactly, including case |
Some employees missing | Check Active Employees Only — with Yes, terminated employees and some upcoming hires are excluded. Also check your create rule; filtered-out records are imported but don’t become people |
Terminated employees never offboard | Set Active Employees Only to No so YeshID can see termination dates, and confirm an offboarding trigger is connected to the people source |
People created without email addresses | Paylocity work email is blank for those employees. Either fill it in Paylocity or turn on email generation in the Who to create step |