Payroll integration
Deel to Paychex Flex integration: own US employees from Deel as a worker in Paychex Flex
An integration between Deel and Paychex Flex creates an own employee of the US legal entity in Deel as a worker of type EMPLOYEE in Paychex Flex, with name, full-time or part-time and start date. Paychex puts that worker on IN_PROGRESS, after which tax details and bank account are completed in Flex; PEO, EOR and contractor relationships in Deel do not go to Paychex.
What the integration does
Organisations that use Deel worldwide for HR and run payroll for their own US Inc. in Paychex Flex put a US starter into Flex by hand. Those that also use Deel as a PEO or EOR there have to check per person which party pays.
- The Flex administrator approves KoppelHet's app under Integrated Applications.
- HR creates an own employee at the US legal entity in Deel.
- KoppelHet checks hiring type and legal entity and creates a worker of type EMPLOYEE in Paychex.
- With the workerId KoppelHet adds the pay and the employee number to the worker.
- The employee or administrator fills in tax forms and bank details in Flex; KoppelHet reports workers that stay IN_PROGRESS too long.
What to watch for with Deel and Paychex Flex
- Besides own employees Deel also has the hiring type peo, for whom Deel handles payroll as co-employer in the United States. KoppelHet only sends employees from the guide for own employees to Paychex and ignores peo, eor and contractor, so nobody is paid by two parties.
- Paychex only creates workers of type EMPLOYEE or INDEPENDENT_CONTRACTOR through the API, and every new worker is IN_PROGRESS until it is completed in Flex. KoppelHet only uses EMPLOYEE, because contractors in Deel are paid through Deel.
- Deel records an employment as FULL_TIME or PART_TIME, with a part-time percentage. Paychex Flex uses the same distinction in employmentType. KoppelHet takes the value over directly; the percentage goes to payroll as a note, because working hours in Flex are set up per pay schedule.
- A partner app only gets access to a client at Paychex after that client's administrator approves the request in Flex. The request uses the company's displayId. If the organisation has more US entities in Deel, KoppelHet requests access per Paychex company and records the link with the legal entity.
- Deel only returns the US SSN in additional_details if the feature flag is on and personal data is not redacted. Paychex does not ask for the SSN at creation. KoppelHet therefore leaves it out and lets the employee fill it in themselves in Flex through the Paychex invitation.
- If the client's Paychex account is locked, Paychex returns a 423, sometimes with a workerId that must not be used. KoppelHet does not store that ID, queues the Deel employee and tries again once the account is open.
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 leavers go to Paychex as well?
Not in the first version. A last working day from Deel can follow later as an extension; until then payroll terminates the worker itself.
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, contract_oid, start_date, gross_annual_salary) and GET /rest/people with hiring_type, employments and compensation; additional_details only with feature flag.
- Paychex through https://api.paychex.com with a partner app; access per client through /management/requestclientaccess with the displayId. POST /companies/{companyId}/workers with givenName, familyName and workerType, then PATCH /workers/{workerId} and compensation on the workerId.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Deel | Field in Paychex Flex | Notes |
|---|---|---|
hiring_type en legal_entity_id | Filter: alleen eigen werknemers van de Amerikaanse entiteit | peo, eor and contractor are excluded |
legal_entity_id | companyId in Paychex | |
first_name, last_name | name.givenName, name.familyName | |
Vaste waarde | workerType EMPLOYEE | |
employment.type (FULL_TIME, PART_TIME) | employmentType | |
employment.start_date | Startdatum van de worker | |
compensation_details (salary, scale) | Compensation na aanmaken | Hourly wage or annual salary |
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