Payroll integration
Remote to PayFit integration: direct employees of your own French entity from Remote as a collaborator in PayFit
An integration between Remote and PayFit creates a direct employee of your own French entity in Remote as a collaborator with a contract in PayFit, with name, personal email, address, job title and start date. Staff Remote employs as employer of record or pays itself do not go to PayFit.
What the integration does
Organisations that use Remote for EOR in other countries and also manage their own French employees in Remote pay those French employees in PayFit. Anyone starting in Remote as a direct employee is now created in PayFit by hand, and a moving start date does not reach it by itself.
- KoppelHet loads all employments of type direct_employee once and registers Remote's webhooks.
- On a notification KoppelHet fetches the full employment and checks the legal entity.
- A new French direct employee becomes a collaborator in PayFit, followed by a contract.
- Pay and a changed start date go as a task to the payroll administrator.
- Every night KoppelHet compares Remote's full list with the collaborators in PayFit.
What to watch for with Remote and PayFit
- Remote has the types employee, contractor, direct_employee and global_payroll_employee. Only direct_employee is someone employed by your own entity whom Remote does not pay. KoppelHet filters the list on that type and then checks whether engaged_by_legal_entity_id is the French entity.
- For direct_employee only List and Show employment are available in the Remote API; writing is not possible. The integration therefore goes one way, and HR corrects a mistake in name or address in Remote, after which KoppelHet reports the change to payroll.
- Remote's list is light and contains no country-specific data. PayFit asks for a personal email and an address with house number, street, city and postcode. KoppelHet therefore fetches the full employment for each new French employee and splits the address into the parts PayFit requires.
- In Remote's employment the start date is called provisional_start_date, and it can still move until the first working day. PayFit creates a contract with startDate, which cannot be changed through the API. KoppelHet compares the date every night and gives a moved start to payroll as a task.
- Remote has no single event for a changed employment; there are separate employment events for personal details, administrative details, status and work email. Remote itself recommends fetching the whole list again now and then. KoppelHet does that every night, so a missed notification does not become a missing collaborator in PayFit.
- PayFit only creates a contract through the API for France and returns 201 without data; the contract appears after two to five minutes. KoppelHet then checks it is there before the Remote employee counts as processed.
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
Does pay go across as well?
No. In Remote's employment we found no salary for a direct employee, and the PayFit contract does not ask for it. Payroll fills in pay in PayFit.
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 and page, page_size; GET /v1/employments/{employment_id} for engaged_by_legal_entity_id, provisional_start_date, personal_details and address_details. Webhooks through POST /v1/webhook-callbacks.
- PayFit through partner-api.payfit.com with an API key: POST /companies/{companyId}/collaborators and POST /companies/{companyId}/collaborators/{collaboratorId}/contracts (France only).
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Remote | Field in PayFit | Notes |
|---|---|---|
type (direct_employee) | Filter | employee and global_payroll_employee are excluded |
engaged_by_legal_entity_id | companyId in PayFit | Only the French entity |
full_name en personal_details | firstName, lastName | |
personal_email | personalEmail | Required in PayFit |
address_details | personalAddress (streetNumber, addressFirstLine, city, postCode, country) | |
job_title, provisional_start_date | jobTitle, startDate (contract) |
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