Payroll integration
Deel to Paylocity integration: own US employees from Deel staged in Paylocity Web Link
An integration between Deel and Paylocity stages an own employee of the US legal entity in Deel as a new hire in Paylocity Web Link, with name, start date, job and pay. An administrator in Paylocity completes the record; PEO, EOR and contractor relationships in Deel stay out of Paylocity.
What the integration does
Organisations that do HR for all countries in Deel and pay their own US entity in Paylocity enter a US starter again in Paylocity. Things regularly go wrong on whether someone works through Deel as a PEO or in direct employment.
- HR creates an own employee at the US legal entity in Deel.
- KoppelHet checks hiring type and legal entity and picks the Company ID in Paylocity.
- KoppelHet sends the employee to Web Link Staging and stores the tracking number.
- The Paylocity administrator completes the record with tax details and bank account.
- KoppelHet links the final employeeId back to the Deel profile and reports records that get stuck.
What to watch for with Deel and Paylocity
- Besides the own employee Deel also has the hiring type peo, where Deel co-pays as co-employer in the United States. For Paylocity only the group from the guide for own employees counts, which according to Deel is meant for those with their own payroll provider. KoppelHet also checks the legal entity.
- Paylocity takes a new hire through the API as a staged record in Web Link, which an administrator or the Paylocity Service Bureau completes. KoppelHet therefore sends what Deel knows and leaves tax forms to Paylocity. KoppelHet stores the tracking number from the response with the Deel profile.
- A company still in Paylocity's implementation phase cannot hire employees with a future start date. In Deel starters are often set up weeks in advance. KoppelHet holds them in that phase until the start date and sends them afterwards.
- The employeeId in Paylocity may have at most ten characters, while Deel gives profiles a long UUID. KoppelHet leaves the field empty so Paylocity assigns a number, and records the relation between both IDs in its own table.
- Deel stores pay with a scale, ANNUAL by default, but also HOURLY or WEEKLY. Paylocity wants a pay type of Hourly or Salary in primaryPayRate. KoppelHet sends an hourly wage as Hourly with a rate and every other amount as an annual salary, only if the currency is USD.
- A bank account through this API replaces all existing direct deposit details of the employee in Paylocity, and the GET API does not return them. KoppelHet therefore never sends bank details; the employee or administrator fills them in Paylocity.
How we build and run it
- The integration runs on the KoppelHet platform, hosted in a data centre in the EU.
- Every sync and every error is visible in the functional log; on an error your administrator is notified.
- A change that cannot go through is not half-applied but queued for another attempt.
- KoppelHet is ISO 27001 certified. Data travels encrypted and stays on the platform no longer than needed.
- After go-live we manage the integration and adjust it when your process changes.
- The integration fits next to your existing integration layer. Only the fields in the design are transferred; the platform keeps no register of its own.
Implementation and price
This is not an app you switch on. We build the integration for your organisation on our platform, with building blocks we reuse on every project. So it is custom work that does not start from scratch.
A consultant prepares the intake and analyses both systems. We then record the mapping and exceptions field by field, test in the test or acceptance environment and go live at a moment you choose. Costs are a one-off amount for the setup and a monthly amount for platform, monitoring and support.
Frequently asked questions
Do pay changes and leavers go across as well?
Not in the first version. Those can follow later as an extension, with the APIs for existing employees.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Deel through the HRIS API with a bearer token: Employee Created Direct webhook (legal_entity_id, start_date, gross_annual_salary, job_title_id) and GET /rest/people for hiring_type, job_title, employments and compensation.
- Paylocity with OAuth 2.0 client credentials (scope WebLinkAPI): POST /v2/weblinkstaging/companies/{companyId}/employees/newemployees with the stagedEmployee model; 201 response with trackingNumber, errors with field and message.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Deel | Field in Paylocity | Notes |
|---|---|---|
hiring_type en legal_entity_id | Filter en companyId | One Company ID per payroll entity |
first_name, last_name | firstName, lastName | At most 40 characters |
employment.start_date | status.hireDate en effectiveDate | |
job_title | departmentPosition (jobTitle) | |
compensation_details (salary, scale) | primaryPayRate (payType, baseRate of annualSalary) | |
Deel profiel-id | Eigen koppeltabel | Leave employeeId empty; Paylocity assigns it |
Related
Ashby → Deel
Ashby to Deel integration: hires at the own entity as direct employee in Deel
Bullhorn → Deel
Bullhorn to Deel integration: first placement as a direct employee with a contract in Deel
Carerix → Deel
Carerix to Deel integration: successful placement as a person or contract in Deel
Deel → 4PS Construct
Deel to 4PS Construct integration: own employees of the construction entity in 4PS, with department and cost centre as dimensions