Payroll integration
Deel to Sage Payroll integration: employees of your own UK entity from Deel as an import file for Sage 50 Payroll
An integration between Deel and Sage 50 Payroll prepares the employees of your own UK entity from Deel, with name, start date, pay and last working day, as an import file for Sage. Contractors and EOR employees in Deel stay out of Sage, and payroll starts the import itself, because Sage 50 Payroll has no REST API.
What the integration does
Organisations that use Deel for contractors, EOR and HR, and pay their own UK Ltd in Sage 50 Payroll, keep UK employees in Deel. Every month payroll works out who is new, who gets a raise and who is leaving, and enters that into Sage by hand.
- KoppelHet gets a token for the Deel API with read rights on people and employments.
- Signed notifications from Deel are collected until the delivery day; KoppelHet filters on hiring type and the UK legal entity.
- On the delivery day KoppelHet creates the Employee Details file and, for new pay, the Hours and Rates file.
- Payroll makes a backup and imports the files into Sage.
- Leavers go to payroll as a list, which finishes them in Sage.
What to watch for with Deel and Sage Payroll
- Deel pays UK EOR employees itself and lists them alongside own employees. KoppelHet only takes the hiring types for own employees at the UK client legal entity, so nobody is paid twice, through Deel and through Sage.
- Sage 50 Payroll has no REST API, and a user has to start every import. Where Deel reports a change immediately, KoppelHet therefore bundles the notifications into one set of files per period, with the date in the name.
- Deel only returns the NI number if a feature flag is switched on for the organisation and the request does not redact personal data. Without that setting payroll fills in the NI number in Sage, and KoppelHet leaves the field empty in the file.
- Pay is stored in Deel as an amount with a scale, such as hourly or monthly, and a currency. Sage's Hours and Rates file only changes the rate of a payment already assigned to an existing employee. KoppelHet therefore only delivers new pay once the employee is in Sage and the amount is in GBP.
- The RTI Payroll ID cannot be changed after import into Sage. KoppelHet leaves it empty so Sage creates it, and uses the Deel ID as reference, so a later file finds the same employee.
- A move from EOR through Deel to your own UK Ltd is a new employment in Deel. In Sage it becomes a new starter with the new start date; Deel has already settled the earlier period through its own payroll.
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 our UK EOR employees go to Sage as well?
No. Deel pays them. Only employees of your own UK Ltd are in the file.
Can the file go into Sage by itself?
Not without Sage's SDK, which comes with the paid Sage Developers Programme. Payroll starts the import.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Deel through the REST API (GET people with hiring_types and employments with client_legal_entity, start_date, payment and termination_last_day; additional_details only with feature flag) and signed webhooks.
- Sage 50 Payroll through File, Data Import with the CSV templates Employee Details and Employee Payments (Hours and Rates), or Advanced Data Import with an own field mapping. Hours and Rates does not work for factored payments.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Deel | Field in Sage Payroll | Notes |
|---|---|---|
hiring_type (hris_direct_employee of direct_employee) | Filter: alleen eigen werknemers | |
employments.client_legal_entity | Sage-bedrijf van de Britse Ltd | |
first_name, last_name | Naam in Employee Details | |
employments.start_date | Startdatum in Employee Details | |
Deel-ID van de werknemer | Referentie in Sage | RTI Payroll ID stays empty |
employments.payment (rate, scale, currency) | Tarief in Hours and Rates | Only in GBP and on an existing payment |
employments.termination_last_day | Lijst van vertrekkers |
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