Payroll integration
Remote to Sage Payroll integration: UK direct employees from Remote as an import file for Sage 50 Payroll
An integration between Remote and Sage 50 Payroll prepares direct employees of your own UK entity from Remote as an Employee Details file for Sage, with name, address, start date and job title, and delivers a list of end dates from offboarding. Staff Remote employs as employer of record or pays itself are not in the file, and payroll starts the import itself.
What the integration does
Organisations that use Remote for staff in countries without their own entity and also manage their own UK employees in Remote pay that UK group in Sage 50 Payroll. Payroll copies starters from Remote and sometimes only hears about a leaver after the run.
- KoppelHet fetches the direct employees from Remote, page by page, and the full employment of each UK employee.
- Per UK entity KoppelHet makes an Employee Details file with only new and changed employees.
- End dates from offboarding go on a separate list.
- Payroll makes a backup and imports the file through Data Import.
- Payroll adds pay, NI number and tax details that Remote does not supply.
What to watch for with Remote and Sage Payroll
- Remote distinguishes employee, contractor, direct_employee and global_payroll_employee. With employee Remote is the employer and with global_payroll_employee Remote runs payroll. For Sage KoppelHet only takes direct_employee at your own UK entity, so nobody gets two payslips.
- In Remote's employment we found no salary field for a direct employee. Sage also only reads payments with the Hours and Rates import for employees that already exist. KoppelHet therefore only delivers Employee Details, and payroll puts pay into Sage.
- In Remote the end date is only in the full employment, as the most recent date of the offboarding, and it can still change. Sage 50 Payroll does not read leavers through this import. KoppelHet therefore puts end dates on a separate list and flags a date that changed since the previous file.
- Each Sage company is its own administration, and a user starts the import after a backup. Remote gives the engaged_by_legal_entity_id per employment. KoppelHet makes a separate file per UK entity, so payroll imports it into the right company.
- Remote's list returns light records without country-specific data, in pages until current_page equals total_pages. Address and personal details for the Employee Details file are only in the full employment. KoppelHet fetches that for each UK employee who goes into the file.
- The RTI Payroll ID cannot be changed in Sage after the import, and an empty field lets Sage create an ID itself. KoppelHet therefore does not fill it with Remote's employment ID, but only uses that ID as a reference in the list for 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
Can Remote not run UK payroll itself?
It can as global payroll, and then 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.
- Remote API with a company token: GET /v1/employments with employment_type=direct_employee, page and page_size; GET /v1/employments/{employment_id} for engaged_by_legal_entity_id, provisional_start_date, personal_details, address_details and termination_date. Webhooks through POST /v1/webhook-callbacks as a signal.
- Sage 50 Payroll through File, Data Import with the Employee Details CSV template, or Advanced Data Import with an own field mapping.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Remote | Field in Sage Payroll | Notes |
|---|---|---|
type (direct_employee) | Filter | employee and global_payroll_employee are excluded |
engaged_by_legal_entity_id | Sage-bedrijf | One file per entity |
Remote employment-id | Works number (referentie) | Leave the RTI Payroll ID empty |
full_name en personal_details | Forename, Surname, geboortedatum | |
address_details | Adres | |
provisional_start_date | Start date | |
job_title, department | Functie en afdeling | |
termination_date | Lijst met einddatums |
Related
Greenhouse → Remote
Greenhouse to Remote integration: foreign hires as EOR employment with the country's form
Recruitee → Remote
Recruitee to Remote integration: hires abroad straight into an employment at Remote
Remote → 4PS Construct
Remote to 4PS Construct integration: own employees of the construction entity from Remote in 4PS
Remote → Active Directory
Remote to Active Directory integration: accounts for colleagues in other countries