Payroll integration
Rippling to Sage Payroll integration: UK employees from Rippling as an import file for Sage 50 Payroll
An integration between Rippling and Sage 50 Payroll prepares new and changed employees of your own UK entity from Rippling as an Employee Details file, with name, start date, department and pay, and delivers a list of leavers. Sage 50 Payroll has no REST API, so payroll starts the import itself; Rippling's EOR and PEO workers stay out of the file.
What the integration does
Organisations that use Rippling as their HR platform and keep UK payroll in Sage 50 Payroll copy new hires and pay changes by hand each period. Someone who declined their offer in Rippling is sometimes still in Sage.
- KoppelHet reads the workers changed since the previous file, with legal entity, employment type, department and compensation.
- Only an EMPLOYEE of your own UK entity, without EOR or PEO, goes into the file.
- KoppelHet makes an Employee Details file per Sage company and a separate list of leavers.
- Payroll makes a backup and imports the file through Data Import.
- Payroll adds NI number and tax details that Rippling does not supply.
What to watch for with Rippling and Sage Payroll
- Rippling gives each worker's legal entity with a management_type such as PEO or EOR. For those workers Rippling or a partner pays the wages. KoppelHet only includes workers of your own UK entity without such a type in the Sage file.
- The country fields in the Rippling API only cover the SSN, the Canadian SIN and the New Zealand IRD number. A UK NI number is not among them. KoppelHet leaves the field in the Employee Details file empty and puts the starter on the list for payroll, unless the number is in a custom field in Rippling.
- Derived amounts in Rippling assume forty hours per week. A UK part-timer or a 37.5-hour contract thus gets a wrong hourly or annual amount. KoppelHet only uses the amount that belongs to compensation_time_period: annual pay for SALARIED, hourly pay for HOURLY.
- Sage 50 Payroll has no REST API; data goes in through Data Import with CSV templates, and a user starts that import after a backup. A Sage company is its own data file. If the organisation has two UK entities in Rippling, KoppelHet delivers a separate file per entity.
- A termination in Rippling has a type, and OFFER_DECLINED, RESCIND and RENEGE mean someone never started. KoppelHet only includes a worker in the file once the status is ACCEPTED or ACTIVE, and lists such a termination separately so payroll knows there is nothing to pay.
- The RTI Payroll ID cannot be changed in Sage after the import, and Sage creates a new ID if the field is empty. Rippling has its own worker IDs that have nothing to do with HMRC. KoppelHet therefore leaves the RTI field empty and only uses the Rippling ID as a reference.
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
Why not use Rippling for UK payroll?
If Rippling runs UK payroll for you, this integration falls away. This page is for organisations that keep Sage.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Rippling through the REST API: GET /workers with expand on user, legal_entity, employment_type, department and compensation, filter on updated_at since the previous file, termination_details and end_date; scope workers.read.
- Sage 50 Payroll through File, Data Import with the Employee Details CSV template, or Advanced Data Import with an own field mapping; Hours and Rates only for existing employees.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Rippling | Field in Sage Payroll | Notes |
|---|---|---|
legal_entity (management_type, country) | Filter en Sage-bedrijf | No EOR or PEO; one file per company |
employment_type.type | Filter: alleen EMPLOYEE | |
Rippling worker-id | Works number (referentie) | Leave the RTI Payroll ID empty |
user (naam, adres) | Forename, Surname, adres | |
start_date | Start date | |
department | Department | |
compensation (annual_compensation of hourly_wage) | Loon of uurtarief | Source amount, not a derived amount |
termination_details (type, reason), end_date | Lijst van vertrekkers |
Related
Carerix → Rippling
Carerix to Rippling integration: successful match as a hire for review in Rippling
Greenhouse → Rippling
Greenhouse to Rippling integration: every hire straight into Rippling for review
Recruitee → Rippling
Recruitee to Rippling integration: hired candidates ready to hire
Rippling → 4PS Construct
Rippling to 4PS Construct integration: own employees of the construction entity in 4PS, with department as a dimension